Hi all
I agree with any solution, but I have no idea how to implement it.
If we do not include the uberjar as the Maven2 plugin's dependency,
we run into two problems:
- The Maven2 plugin would need to depend on each and every
container we have. And, if a new container is added, we'd need
to add it in two different locations. Not good.
- The integration tests on containers are executed with the
uberjar, and this for all containers. Hence, the same would need
to be rewritten for the Maven2 plugin and for each container,
which in my opinion just doubles the effort unnecessarily.
If you have improvement ideas, feel free to commit. I personally
prefer to work on
https://jira.codehaus.org/browse/CARGO-1005 (still
not solved but is critical) or
https://jira.codehaus.org/browse/CARGO-1008 (solved, but needed the
uberjar refactoring things).
Thank you
S. Ali Tokmen
http://ali.tokmen.com/
GSM (ch): +41 79 207 29 22 [Swisscom]
GSM (fr): +33 66 43 00 555 [Orange]
GSM (tr): +90 555 266 52 73 [Avea]
My AIM, ICQ, MSN Messenger and Yahoo IM
contact details are on http://contact.ali.tokmen.com
On 2011/06/30 12:01, Benjamin Bentmann wrote:
Anders
Hammar wrote:
Well, you're creating a dependency from
the maven plugin to teh uber jar
which is not good. It is always better to use the correct
libraries (i.e.
independent jars) instead of the uber jar.
+1. Besides the arguments given, the uber JAR appears to lack a
proper source bundle which makes debugging anything using it a
PITA.
Benjamin
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
