I think this still wouldn't solve the duplicated classes issue
(depending on wicket and wicket-extensions in the same time).
Peter
2011-01-24 19:23 keltezéssel, Michael O'Cleirigh írta:
I looked into the wicket/pom.xml and the maven-source-plugin is disabled:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-source-plugin</artifactId>
<configuration>
<!-- Do not deploy -sources.jar file.
This project has no .java files
-->
<attach>false</attach>
</configuration>
</plugin>
But google found this goal for the plugin:
http://maven.apache.org/plugins/maven-source-plugin/aggregate-mojo.html
I haven't tested it but the description of 'Aggregate sources for all
modules in an aggregator project.' sounds like
exactly what you want for these tasks.
Mike
the aggregate is there to protect users if/when we split more things
out...
-igor
On Mon, Jan 24, 2011 at 10:06 AM, Jeremy Thomerson
<jer...@wickettraining.com> wrote:
On Mon, Jan 24, 2011 at 11:50 AM, Igor
Vaynberg<igor.vaynb...@gmail.com>wrote:
have the wicket module not create an
aggregate jar, just list all the dependencies.
Then we don't need the wicket module at all, right? Or I'm
misunderstanding
what you mean by "list all the dependencies" - which I assume to mean
"document the jars you need somewhere".
--
Jeremy Thomerson
http://wickettraining.com
*Need a CMS for Wicket? Use Brix! http://brixcms.org*
