On 09/02/2013 13:01, Simone Tripodi wrote:
Salut mon ami,
I have opened ONAMI-78 Enable the tests.jar sources.jar and
test-sources.jar generation
1. Do you have interest/think it is logical to have this generation for
snapshots?
while I am +1 for -sources and -javadoc - there are jobs on Jenkins
that would upload them as well - I don' understand which is the
benefit of distributing the -test* artifacts for Onami modules. Can
you tell more, please?
ATM I am -0 for -tests*
Just like anything else, I am just lazy and like to know that a test-jar
is there is case I would need it. Andy maybe someone else will need it
(for mocking by example...).
The other approach would be to explicitely generate that test-jar if a
module needs it (I didn't look if this is already the case in trunk code).
But I even know people who don't like using test-jar from one module in
another. Don't know what you think about it.
2. Do you think the proposed solution is acceptable?
Unneeded keeping the -test* artifacts out, it should be enough
promoting the -sources and -javadoc plugins from release profile in
the regular one.
If we don't generate test-jar, we would avoid the maven-jar-plugin issue.
However, I am -0 to enroll javadoc in the snapshot. The javadoc
generation takes time, and I wouldn't want each time I 'mvn install' to
wait long times for the javadoc to be generated.
Waiting for your feedback, TIA and have a nice WE!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simonetripodi
http://www.99soft.org/
