On 11/01/07, DJP JEAN-PROST Dominique <[EMAIL PROTECTED]> wrote:
I would like my team to deploy to my repository the following jars : binaries 
(of course), sources and javadoc. As javadoc generation is a bit time costly, I 
would like to get it generated only on the deploy phase, so that, everyday work 
is not slowed by this generation. I did the following in my pom :

Source and javadoc jars are normally only created when performing a
release, so it shouldn't impact on day-to-day work?

Unfortunalty, the 2 jars are generated in the deploy phase, but are not copied 
in the repository. I guess they are not registred in the deploy phase to get 
copied or something like that ?

Is there something I have to change to get it work, or do I have to change the 
phase to install (for instance) to get them copied during the deploy phase ?

I'd recommend using a profile to control the generation of
source/javadoc jars rather than moving them to a different phase.

By the way, concerning the eclipse:eclipse -DdownloadSources. This plugin tries 
to get the sources of every dependency of my pom. As all of the dependencies I 
use don't publish nor sources nor javadoc, it keep on trying to download them, 
each time I use eclipse:eclipse. Is there a way to tell eclipse:eclipse not to 
try downloading a set of sources / javadoc ?

See MECLIPSE-174 [1], fixed in 2.3.

Mark

[1] http://jira.codehaus.org/browse/MECLIPSE-174

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to