Brett, So are you saying that if the jars are named correctly (i.e. xxx-javadoc and xxx-src) that Maven2 will automatically pull them to the local repository? So if my project has a dep on a 3rd party jar, and they've included the src and api jars, then Maven2 will pull them to my local repo as well? Is there a setting for this? (Sorry, I know I keep saying the same thing, I'm just trying to make sure you knew what I meant, I'm floored that this is in!)
If so, then this is fantastic!! This was part of the behaviour we were achieving in our custom plugin.... The next piece of the puzzle is for the ide plugins to also recognize the existance of the local jars and add them to the tool's config file.... thx! -S On 10/21/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > In Maven2, yes, it is standardised (-src and -javadoc) and they can be > published to the repository by default. > > - Brett > > On 10/21/05, Sal Campana <[EMAIL PROTECTED]> wrote: > > Are there any plans to add support of optionally specifying API and SRC > jars > > for a given dependency? > > > > We've built a plugin to do this, and then update our IDE, but its not > > standard...but if it were standard in Maven (extra xml tags?) then all > the > > IDE plugins would support it.... > > > > Based on this page: > > > > *http://docs.codehaus.org/pages/viewpage.action?pageId=22230* > > > > It seems the classifier attribute can be used to associate src and api > jars > > with a regular jar dependency. It shows *javasrc and *javadoc... > > > > Will the extensions be "standardized"? > > > > It seems that if Maven would standardize how these things are defined, > then > > generic plugins could be made for the IDEs which can take advantage of > this. > > > > > > Thx! > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
