Re: Pulling API and SRC Jars from Repos

2005-10-24 Thread Arik Kfir 
cool!

On 10/24/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> On 10/24/05, Arik Kfir <[EMAIL PROTECTED]> wrote:
> > That doesn't work for me - I have to delcare an additional dependency,
>
> Yes, that's correct, but I believe the eclipse plugin automates this
> and the others can too.
>
> > As for deploying them - I bind the sources/javadoc plugins to the
> > install/deploy phases and it works. It's not optimal though (I think
> > through a profile would be better)
>
> Yes, theere is already a profile for doing this, activated by
> -DperformRelease=true
>
> - Brett
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: Pulling API and SRC Jars from Repos

2005-10-24 Thread Brett Porter 
On 10/24/05, Arik Kfir <[EMAIL PROTECTED]> wrote:
> That doesn't work for me - I have to delcare an additional dependency,

Yes, that's correct, but I believe the eclipse plugin automates this
and the others can too.

> As for deploying them - I bind the sources/javadoc plugins to the
> install/deploy phases and it works. It's not optimal though (I think
> through a profile would be better)

Yes, theere is already a profile for doing this, activated by
-DperformRelease=true

- Brett

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

Re: Pulling API and SRC Jars from Repos

2005-10-24 Thread Arik Kfir 
That doesn't work for me - I have to delcare an additional dependency,
and a classifier. Like this:


  sources


same for javadoc (no "s" in the end of javadocs... ;-)

As for deploying them - I bind the sources/javadoc plugins to the
install/deploy phases and it works. It's not optimal though (I think
through a profile would be better)


On 10/24/05, Sal Campana <[EMAIL PROTECTED]> wrote:
> 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]
> >
> >
>
>

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

Re: Pulling API and SRC Jars from Repos

2005-10-24 Thread Sal Campana 
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]
>
>

Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Brett Porter 
We are going to add this to the recommended upload request, and it is
"by default" in m2 using the release plugin. Just using deploy without
the profile activated does not do it, but this is because we don't
want to build them for snapshots and development builds due to the
time involved.

We'll get this documented, but we'll certainly be encouraging projects
on ibiblio to do so.

- Brett

On 10/23/05, Ralph Pöllath <[EMAIL PROTECTED]> wrote:
> On 23.10.2005, at 14:08, Milos Kleint wrote:
> > well, javadocs culd be published easily in maven 1.x but AFAIK it
> > was almost
> > completely unused (try searching the ibiblio.org  > ibiblio.org>repository)
> > So to get the feature useful, there should be a more aggressive
> > policy IMHO.
> > Like when uploading to remote repository always upload javadocs and
> > sources
> > as well by default.. otherwise it will be again unused.
>
> This has been discussed here previously, but I totally agree that
> javadocs and sources should be uploaded by default.
>
> Cheers,
> -Ralph.
>
> > 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]
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

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

Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Wim Deblauwe 
Wow, I was unaware of that being possible. How do you do it?

regards,

Wim

2005/10/23, Ralph Pöllath <[EMAIL PROTECTED]>:
>
> On 23.10.2005, at 14:08, Milos Kleint wrote:
> > well, javadocs culd be published easily in maven 1.x but AFAIK it
> > was almost
> > completely unused (try searching the ibiblio.org 
> >  > ibiblio.org >repository)
> > So to get the feature useful, there should be a more aggressive
> > policy IMHO.
> > Like when uploading to remote repository always upload javadocs and
> > sources
> > as well by default.. otherwise it will be again unused.
>
> This has been discussed here previously, but I totally agree that
> javadocs and sources should be uploaded by default.
>
> Cheers,
> -Ralph.
>
> > 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]
> >>
> >>
> >
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Ralph Pöllath 

On 23.10.2005, at 14:08, Milos Kleint wrote:
well, javadocs culd be published easily in maven 1.x but AFAIK it  
was almost
completely unused (try searching the ibiblio.org ibiblio.org>repository)
So to get the feature useful, there should be a more aggressive  
policy IMHO.
Like when uploading to remote repository always upload javadocs and  
sources

as well by default.. otherwise it will be again unused.


This has been discussed here previously, but I totally agree that  
javadocs and sources should be uploaded by default.


Cheers,
-Ralph.


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]







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

Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Milos Kleint 
well, javadocs culd be published easily in maven 1.x but AFAIK it was almost
completely unused (try searching the ibiblio.org repository)
So to get the feature useful, there should be a more aggressive policy IMHO.
Like when uploading to remote repository always upload javadocs and sources
as well by default.. otherwise it will be again unused.

just my 2 cents.

Milos

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]
>
>

Re: Pulling API and SRC Jars from Repos

2005-10-23 Thread Wim Deblauwe 
Cool, hopefully the idea plugin will take advantage of this soon! (and the
documentation of maven will mention how to generate such artifacts)

regards,

Wim

2005/10/22, Brett Porter <[EMAIL PROTECTED]>:
>
> 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]
>
>

Re: Pulling API and SRC Jars from Repos

2005-10-21 Thread Brett Porter 
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]

Pulling API and SRC Jars from Repos

2005-10-21 Thread Sal Campana 
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!