[ 
http://jira.codehaus.org/browse/MGWT-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ladislav Gazo updated MGWT-76:
------------------------------

    Attachment: dir_structure.txt

complex development directory structure

> 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: dir_structure.txt, 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


Reply via email to