[
http://jira.codehaus.org/browse/MOJO-549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99575
]
Jörg Hohwiller commented on MOJO-549:
-------------------------------------
One more:
If you want to split your client code into multiple modules, you should add
this to your parent POM:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<executions>
<execution>
<id>source-jar</id>
<phase>package</phase>
<goals>
<goal>jar</goal>
</goals>
</execution>
</executions>
</plugin>
This will cause that on mvn install also your sources are build and installed
(as artifactId-sources.jar)
Then if you depend on another module, you use:
<dependency>
<groupId>foo.bar</groupId>
<artifactId>Foo</artifactId>
<version>1.0</version>
</dependency>
<dependency>
<groupId>foo.bar</groupId>
<artifactId>Foo</artifactId>
<version>1.0</version>
<classifier>sources</classifier>
</dependency>
BTW: It would be even easier if the sources would be directly included in the
regular jar. Has anyone managed to do this?
A disadvantage would be that the regular jar gets bigger while the sources are
not needed when the application is deployed.
> submitting new gwt-plugin
> -------------------------
>
> Key: MOJO-549
> URL: http://jira.codehaus.org/browse/MOJO-549
> Project: Mojo
> Issue Type: New Feature
> Components: Plugin Submission
> Environment: Gentoo Linux, maven-2.0.4, java build Blackdown-1.4.2-03
> Reporter: kristian meier
> Attachments: gwt-plugin.tar.gz, gwt-plugin2.tar.gz,
> gwt-plugin3.tar.gz, gwt-plugin_forkShellParam.patch.txt
>
>
> after asking the mojo-mailing list if there is interest in a
> gwt-maven-plugin, I hereby attaching the plugin code. I tried to obey the
> developer guidelines, but I have to admint I did have quite a struggle with
> it. so any feedback is welcome.
> I wanted to contribute a plugin with which you can compile GWT applications
> (code.google.com/gwt) from within maven. actually I have also two archetypes
> along with this plugin, but I do not know how to incorporate these in the
> given plugin structure of codehaus. so I just took the plugin tried to follow
> the guidelines as much as possible and added some documentation to it.
> the best understanding you get if you follow the example from the docu. I
> also stopped at a certain point, because first I want to see what Codehaus is
> doing with this and how I can contribute to this plugin when it is part of
> the mojo-project.
> with best wishes
> Kristian
--
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
