On 21 Aug 07, at 9:43 AM 21 Aug 07, Stefano Bagnara wrote:
Jason van Zyl ha scritto:
I'm not sure this is something we want to encourage before the
patches
are applied. Keeping the sources and javadoc JARs together seems like
a good thing to do. The sources and javadocs located in different
locations doesn't seem to make much sense to me and there's no real
explanation within the report.
I see there are 4 open bugs depending on this feature request:
http://jira.codehaus.org/browse/MASSEMBLY-231
http://jira.codehaus.org/browse/MSOURCES-20
http://jira.codehaus.org/browse/MJAVADOC-142
http://jira.codehaus.org/browse/MDEPLOY-61
This does not seem only related to javadocs and source jars. What kind
of "real explanation" do you expect for a similar feature request?
The purpose of separating and what real value there is in separating
them.
IMHO adding a feature does not mean "encouraging" its usage: it simply
means make it possible (you know there are always corner cases when
using maven).
If it's possible people will do it because they can, not necessarily
because it makes any sense. I don't like adding features just because
someone wants the feature. So again, what real value is there in
separating the sources, javadocs or any other secondary artifact from
the primary artifact.
What problems do you see in applying this patch apart the
encouragement
issue?
If you are using the IDE integration how is it going to know where to
find the sources and javadocs for debugging. That's one simple case.
By adding a tweak to make the deployment diverge from the standard
you potentially ruin the integration with other tooling. Separating
the deployment makes IDE integration not work, makes getting sources
or Javadocs not work for the command-line IDE integration. The
assumption, at a fundamental level, in Maven is that the secondary
artifacts are always deployed with the primary artifact.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
