[
http://jira.codehaus.org/browse/MGWT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177346#action_177346
]
Ladislav Gazo commented on MGWT-76:
-----------------------------------
- the problem is that we don't have all relevant projects in one directory
(workspace directory) and it doesn't make sense to point to root directory of
all possible projects
- what will plugin choose if you have in a workspace two projects - one from
trunk and second from a branch with same group/artifact/version/type? How we
will exclude such projects?
- from my experience while debugging GWT project and to work without restarting
hosted mode and recompile, both sources and classes must be there. I know
everything relevant is copied to target/classes but that is only "classes"
part, not "sources" path. And sources path (with Java sources, resources, ...)
can be defined in several ways in pom.xml and there can be multiple resources
locations
- and what about seniors? ;) they are omitted? :) I like the idea of scanning
but to improve performance of scanning the least complex tree should be
scanned. So the only thing I am saying there might be (and there are) disjunct
trees that need to be scanned to be able to work correctly with this plugin
- yes it is easily possible to use another file then "pom.xml", there is -f
parameter for that and if you have e.g. pom for testing showcase then it is
handy to direct it there. But I mentioned it is rare and optional and not
needed that much now.
- and maybe it is not absolutely clear what is the purpose of this all - it is
for fluent debugging across many related and interconnected projects/libraries.
It does make no sense for other scenarios but greatly helps here to press just
"refresh" button in browser after source change somewhere deep down in
dependent project
> Solution for multi module builds and hosted mode
> ------------------------------------------------
>
> Key: MGWT-76
> URL: http://jira.codehaus.org/browse/MGWT-76
> Project: Maven 2.x GWT Plugin
> Issue Type: Improvement
> Affects Versions: 1.1, 2.0
> Reporter: Stefan Raubal
> Attachments: gwt-maven-plugin-MGWT-76.rev9744.patch
>
>
> The suggested improvement would ease rapid application development for multi
> module environments:
> The sources of referenced modules should be added to the hosted mode
> classpath instead of the JAR dependency (if the projects are referenced in a
> reactor build).
> The totsp plugin was preparing a solution for multi module builds that share
> the source folders directly. This sounded very promising and was discussed
> here:
> http://code.google.com/p/gwt-maven/issues/detail?id=149
> Nicolas stated correctly in a discussion that the manual configuration step
> used in the totsp patch has drawbacks and proposed a different solution:
> <quote>
> The use of some external XML file to setup "artifact" path as a project path
> is not very maven-compliant, as Maven likes all the config to be in POM. Such
> a feature could be nice but should be supported at maven-core level, not just
> inside a plugin.
> An better option COULD be to reuse code from maven-eclipse-plugin that scans
> the workspace for other maven project and automagically replaces artifacts
> reference with project references. This is a stronger approach : user don't
> have to configure it's path in some XML (that is user dependent, so it SHOULD
> not be stored in SVN and refered from POM) and the plugin code will check the
> candidate project matches the expected version to avoid missconfiguration.
> </quote>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
