You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Steve Cohen <st...@comcast.net> on 2010/12/16 14:42:46 UTC
What scope should source and javadoc dependencies be declared with?
Kind of a newb9ie question:
I wish to update a project to use the later version of a dependency.
There are some incompatibilities and I'd like to try to come up to speed
quickly. In the past I've simply gone to the project's web site and
browsed or downloaded javadoc and/or source. But what's the right maven
way to handle this? None of the scopes' definitions seem to fit this case?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: What scope should source and javadoc dependencies be declared with?
Posted by Anders Hammar <an...@hammar.net>.
You don't specify anything, you just either configure m2e to download
sources/javadoc och right-click on the dependency and select
"Maven->Download...".
http://www.sonatype.com/books/m2eclipse-book/reference/dependencies.html#dependencies-sect-downloading-source
/Anders
On Fri, Dec 17, 2010 at 04:21, Steve Cohen <sc...@javactivity.org> wrote:
> Actually, that's what I am using. Ok, where in the m2eclipse user
> interface SHOULD I add the javadoc dependencies? Is it in the dependencies
> section of the POM editor and if not, then where?
>
> On 12/16/2010 02:36 PM, Reynald Borer wrote:
>
>>
>> Hi Steve,
>>
>>
>> Note sure what you are trying to do here but source and javadoc
>> dependencies are not defined to be added as dependencies. Instead they are
>> used by tools like m2eclipse [1] that download them whenever you access a
>> class of one of your dependency. M2eclipse is really convenient, you should
>> try it.
>>
>>
>> Regards,
>> Reynald
>>
>>
>> P.S: Link:
>> [1]: http://m2eclipse.sonatype.org/
>>
>> On Thursday, December 16, 2010 at 14:42 , Steve Cohen wrote:
>>
>> Kind of a newb9ie question:
>>>
>>> I wish to update a project to use the later version of a dependency.
>>> There are some incompatibilities and I'd like to try to come up to speed
>>> quickly. In the past I've simply gone to the project's web site and
>>> browsed or downloaded javadoc and/or source. But what's the right maven
>>> way to handle this? None of the scopes' definitions seem to fit this
>>> case?
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: What scope should source and javadoc dependencies be declared
with?
Posted by Steve Cohen <sc...@javactivity.org>.
Actually, that's what I am using. Ok, where in the m2eclipse user
interface SHOULD I add the javadoc dependencies? Is it in the
dependencies section of the POM editor and if not, then where?
On 12/16/2010 02:36 PM, Reynald Borer wrote:
>
> Hi Steve,
>
>
> Note sure what you are trying to do here but source and javadoc dependencies are not defined to be added as dependencies. Instead they are used by tools like m2eclipse [1] that download them whenever you access a class of one of your dependency. M2eclipse is really convenient, you should try it.
>
>
> Regards,
> Reynald
>
>
> P.S: Link:
> [1]: http://m2eclipse.sonatype.org/
>
> On Thursday, December 16, 2010 at 14:42 , Steve Cohen wrote:
>
>> Kind of a newb9ie question:
>>
>> I wish to update a project to use the later version of a dependency.
>> There are some incompatibilities and I'd like to try to come up to speed
>> quickly. In the past I've simply gone to the project's web site and
>> browsed or downloaded javadoc and/or source. But what's the right maven
>> way to handle this? None of the scopes' definitions seem to fit this case?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>
>>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: What scope should source and javadoc dependencies be
declared with?
Posted by Reynald Borer <re...@gmail.com>.
Hi Steve,
Note sure what you are trying to do here but source and javadoc dependencies are not defined to be added as dependencies. Instead they are used by tools like m2eclipse [1] that download them whenever you access a class of one of your dependency. M2eclipse is really convenient, you should try it.
Regards,
Reynald
P.S: Link:
[1]: http://m2eclipse.sonatype.org/
On Thursday, December 16, 2010 at 14:42 , Steve Cohen wrote:
> Kind of a newb9ie question:
>
> I wish to update a project to use the later version of a dependency.
> There are some incompatibilities and I'd like to try to come up to speed
> quickly. In the past I've simply gone to the project's web site and
> browsed or downloaded javadoc and/or source. But what's the right maven
> way to handle this? None of the scopes' definitions seem to fit this case?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>