You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-user@ant.apache.org by "Marziou, Gael" <ga...@hp.com> on 2009/02/09 16:16:41 UTC
IvyDE 2.0.0.beta1 does not download sources nor javadocs
Hello,
I am running Eclipse 3.4.1, I was using IvyDE 2.0.0.alpha1 which was working fine downloading jar files, sources and javadocs but since I have updated IvyDE 2.0.0.beta1 I get only the jars and not the sources nor javadocs.
I also tried with trunk build and it has same issue.
Is it a known issue or should I log it to JIRA?
Thanks,
Gael
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
> Actually since the version 2.0-RC2, Ivy is handling the
> sources/javadoc declaration for maven pom.xml [1]. So you
> should not have any worries in getting the sources/javadoc of
> an artifact in a maven repository, even proxied.
Great, I did not know.
> Or do you mean that in your case, the maven proxy is
> generating the ivy.xml.
No, I meant that we often have to create manually ivy.xml files because of wrong dependencies in pom.xml or lack of configuration/scopes for optional dependencies.
So we should be fine.
Thanks,
Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On mercredi 18 février 2009 15:03:17 Marziou, Gael wrote:
> Hi Nicolas,
>
> Don't you think the use case I described below makes sense?
>
> Thanks,
>
> Gael
>
> > -----Original Message-----
> > From: Marziou, Gael
> > Sent: Thursday, February 12, 2009 3:20 PM
> > To: ivy-user@ant.apache.org
> > Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
> >
> > > What has been removed in beta1 is the use case where in the ivy.xml
> > > the sources are not declared. So IvyDE was trying itself
> >
> > without the
> >
> > > Ivy API to get some sources, based on the "source suffixes".
> > > I think reenabling this feature will be a waste of http connection
> > > resources and so responsiveness for some incomplete ivy.xml.
> >
> > Well, I think it's unfortunate that this behaviour was
> > removed because that was one of the reasons I "sold" Ivy to my team.
> > What about making it optional if you are concerned by performance?
> >
> > Also, being forced to edit the ivy.xml to add sources and
> > javadocs is not very user friendly especially when you are
> > using a maven proxy like Nexus or Artifactory. In this
> > situation, most of the users will rely on the retrieved pom
> > and may not want to create an ivy.xml just for getting
> > javadocs and sources added to their Eclipse build path.
Actually since the version 2.0-RC2, Ivy is handling the sources/javadoc
declaration for maven pom.xml [1]. So you should not have any worries in
getting the sources/javadoc of an artifact in a maven repository, even
proxied.
Or do you mean that in your case, the maven proxy is generating the ivy.xml.
So then you have in your proxy some ivy.xml generated by an Ivy older than the
RC2, which doesn't include the source declaration ?
Nicolas
[1] https://issues.apache.org/jira/browse/IVY-325
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
Hi Nicolas,
Don't you think the use case I described below makes sense?
Thanks,
Gael
> -----Original Message-----
> From: Marziou, Gael
> Sent: Thursday, February 12, 2009 3:20 PM
> To: ivy-user@ant.apache.org
> Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>
>
> > What has been removed in beta1 is the use case where in the ivy.xml
> > the sources are not declared. So IvyDE was trying itself
> without the
> > Ivy API to get some sources, based on the "source suffixes".
> > I think reenabling this feature will be a waste of http connection
> > resources and so responsiveness for some incomplete ivy.xml.
>
> Well, I think it's unfortunate that this behaviour was
> removed because that was one of the reasons I "sold" Ivy to my team.
> What about making it optional if you are concerned by performance?
>
> Also, being forced to edit the ivy.xml to add sources and
> javadocs is not very user friendly especially when you are
> using a maven proxy like Nexus or Artifactory. In this
> situation, most of the users will rely on the retrieved pom
> and may not want to create an ivy.xml just for getting
> javadocs and sources added to their Eclipse build path.
>
> Thanks,
>
> Gael
>
>
>
>
>
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
> What has been removed in beta1 is the use case where in the
> ivy.xml the sources are not declared. So IvyDE was trying
> itself without the Ivy API to get some sources, based on the
> "source suffixes".
> I think reenabling this feature will be a waste of http
> connection resources and so responsiveness for some
> incomplete ivy.xml.
Well, I think it's unfortunate that this behaviour was removed because that was one of the reasons I "sold" Ivy to my team.
What about making it optional if you are concerned by performance?
Also, being forced to edit the ivy.xml to add sources and javadocs is not very user friendly especially when you are using a maven proxy like Nexus or Artifactory. In this situation, most of the users will rely on the retrieved pom and may not want to create an ivy.xml just for getting javadocs and sources added to their Eclipse build path.
Thanks,
Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Mitch Gitman <mg...@gmail.com>.
That makes perfect sense now. The point that hadn't occurred to me was that,
while the source artifact now has to be declared in the ivy.xml, the suffix
is still needed to associate source artifacts with their corresponding
classes artifacts.
Thanks, Nicolas, for the detailed explanation.
On Thu, Feb 12, 2009 at 3:16 AM, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> wrote:
> First, IvyDE will try to build your classpath. So you need to provide some
> conf, and then IvyDE will select the retrieved artifacts that match the
> "accepted types" (type= the type of the ratifact in your ivy.xml). By
> default
> the accepted types are: "jar,bundle,ejb,maven-plugin", everything that
> would
> reference some bunch of .class.
>
> Then IvyDE will try to attach the sources to the jars (same process will
> occur
> for the javadoc). So still relying on the ivy.xml of the dependency, IvyDE
> will try to find artifact that are sources, so the "Sources types":
> "source",
> everything that would reference some bunch of .java
> Then IvyDE has found source artifact, but how to found out with source for
> which jar. IvyDE relies on the artifact names. For instance your have some
> jars:
> slf4j-api.jar
> slf4j-simple.jar
> slf4j-nop.jar
> IvyDE will use the "sources suffixes" : "-source,-sources,-src".
> So for slf4j-api.jar it will try:
> slf4j-api-source.jar
> slf4j-api-sources.jar
> slf4j-api-src.jar
> Hopefully in your ivy.xml you have defined some source artifacts:
> slf4j-api-src.jar
> slf4j-simple-source.jar
> slf4j-nop-source.jar
> And IvyDE will be alble to find out which sources for which jar.
>
> What has been removed in beta1 is the use case where in the ivy.xml the
> sources are not declared. So IvyDE was trying itself without the Ivy API to
> get some sources, based on the "source suffixes".
> I think reenabling this feature will be a waste of http connection
> resources
> and so responsiveness for some incomplete ivy.xml.
>
> Nicolas
>
>
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On mercredi 11 février 2009 20:48:30 Mitch Gitman wrote:
> Dmitriy, I appreciate your testimony that this is a powerful feature. But
> am I understanding correctly from Nicolas et al that as of beta1 this
> feature is now disabled? And if that's the case, shouldn't the whole
> "Classpath container configuration" section of the IvyDE plugin preferences
> page go away? What am I missing here?
>
> This goes back to the following statement from Nicolas: "So the fix in your
> issue is to just declare the source and javadoc in your ivy.xml files in
> your repository."
>
> But what does declaring the source and Javadoc in your ivy.xml bring you in
> terms of automatic IvyDE support in Eclipse?
First, IvyDE will try to build your classpath. So you need to provide some
conf, and then IvyDE will select the retrieved artifacts that match the
"accepted types" (type= the type of the ratifact in your ivy.xml). By default
the accepted types are: "jar,bundle,ejb,maven-plugin", everything that would
reference some bunch of .class.
Then IvyDE will try to attach the sources to the jars (same process will occur
for the javadoc). So still relying on the ivy.xml of the dependency, IvyDE
will try to find artifact that are sources, so the "Sources types": "source",
everything that would reference some bunch of .java
Then IvyDE has found source artifact, but how to found out with source for
which jar. IvyDE relies on the artifact names. For instance your have some
jars:
slf4j-api.jar
slf4j-simple.jar
slf4j-nop.jar
IvyDE will use the "sources suffixes" : "-source,-sources,-src".
So for slf4j-api.jar it will try:
slf4j-api-source.jar
slf4j-api-sources.jar
slf4j-api-src.jar
Hopefully in your ivy.xml you have defined some source artifacts:
slf4j-api-src.jar
slf4j-simple-source.jar
slf4j-nop-source.jar
And IvyDE will be alble to find out which sources for which jar.
What has been removed in beta1 is the use case where in the ivy.xml the
sources are not declared. So IvyDE was trying itself without the Ivy API to
get some sources, based on the "source suffixes".
I think reenabling this feature will be a waste of http connection resources
and so responsiveness for some incomplete ivy.xml.
Nicolas
>
> Here's what I would expect Nicolas's statement to imply. In your ivy.xml,
> you would declare configurations with names like source and javadoc. Then
> in your IvyDE preferences page, you would have the opportunity to specify
> those configuration names. Then voilà, Eclipse would automatically open the
> artifacts associated with those configurations, provided they still had the
> expected types, i.e. source and javadoc.
>
> Using this Ivy-centric approach would also make it trivially easy to
> support Dmitriy's feature request: "for example to associate a single
> source ZIP with multiple JAR artifacts."
>
> I have to plead guilty to not having read the documentation. For some
> reason, it hadn't occurred to me to even seek out a documentation page for
> IvyDE:
> http://ant.apache.org/ivy/ivyde/history/latest-milestone/index.html
>
> On Wed, Feb 11, 2009 at 10:10 AM, Dmitriy Korobskiy
<dk...@gmail.com>wrote:
> > Mitch,
> >
> > this is a killer feature that I like a lot. I think it could be a big
> > selling point for Ivy. Not sure if Maven Eclipse plugins
> > could achieve that - does anybody know?
> >
> > Imagine just one developer setting up ivy.xml and all team members
> > getting it from SCM, doing couple of clicks, and - voilà,
> > all JARs are on the classpath, all or most have source code and Javadocs
> > attached. You can then browse through all of source
> > code with ease and just hover over a method to see its full Javadoc.
> >
> > Ah, if only IvyDE can attach Javadocs successfully. I'm yet to see it.
> > I have a dream... (sorry for a possible sacrilege).
> >
> > Regarding types and suffixes - IvyDE docs explain it. They are needed to
> > attach these artifacts to a main JAR artifact.
> > I wonder if this configuration could be more flexible in the future - for
> > example to associate a single source ZIP with multiple JAR artifacts,
> > or specify a subdirectories as source or Javadoc roots.
> > For now, I can live with repackaging to resolove these issues.
> >
> > Mitch Gitman wrote:
> >> Nicolas, I'm trying to understand the impact of this change. Suppose an
> >> Ivy
> >> module publishes artifacts for source and Javadoc. Presumably, there are
> >> "source" and "javadoc" Ivy configurations, or the like.
> >>
> >> I don't quite see the relevance then of the following fields in the Ivy
> >> plugin configuration for Eclipse:
> >>
> >> - Sources types
> >> - Sources suffixes
> >> - Javadoc types
> >> - Javadoc suffixes
> >>
> >> Can you offer a use case where these fields are still being used to look
> >> for
> >> something? I should also ask, what does "Sources types" (with a possible
> >> value like "source") mean?
> >>
> >> I must confess, I've never used this feature myself to begin with.
> >> Whenever
> >> Eclipse would complain that it could not find the source for a class, I
> >> would just click the button and manually navigate to the source ZIP on
> >> the enterprise repository. Clumsy, I'll admit, but I wasn't aware of a
> >> better way.
> >>
> >> On Wed, Feb 11, 2009 at 7:12 AM, Nicolas Lalevée <
> >> nicolas.lalevee@hibnet.org
> >>
> >>> wrote:
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> Actually the feature you were using with IvyDE 2.0.0.alpha1 was removed
> >>> in
> >>> beta1: make IvyDE try to find the sources and the javadocs even if they
> >>> are
> >>> not
> >>> declared in the ivy.xml.
> >>> I removed that feature as for me it was only usefull when using IvyDE
> >>> with
> >>> a
> >>> maven repository, as Ivy didn't exposed the source and javadoc. As Ivy
> >>> does
> >>> now support it (IVY-325), this feature was remove to try to not waste
> >>> the IDE
> >>> responsivness. See also a related issue: IVYDE-128
> >>>
> >>> So the fix in your issue is to just declare the source and javadoc in
> >>> your
> >>> ivy.xml files in your repository.
> >>>
> >>> Nicolas
> >>>
> >>>> Gael
> >>>>
> >>>>> -----Original Message-----
> >>>>> From: Marziou, Gael
> >>>>> Sent: Tuesday, February 10, 2009 1:52 PM
> >>>>> To: ivy-user@ant.apache.org
> >>>>> Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
> >>>>>
> >>>>>> I think you are hitting this issue:
> >>>>>> https://issues.apache.org/jira/browse/IVYDE-146
> >>>>>
> >>>>> Merci Nicolas, the description matches indeed.
> >>>>>
> >>>>> But in this case I don't understand why I still have the
> >>>>> issue with trunk build #20 IvyDE-updatesite on Hudson server,
> >>>>> this fix is supposed to be included.
> >>>>>
> >>>>> Gael
> >
> > --
> > DK AIM: DKroot1, Skype: DKroot
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Mitch Gitman <mg...@gmail.com>.
Dmitriy, I appreciate your testimony that this is a powerful feature. But am
I understanding correctly from Nicolas et al that as of beta1 this feature
is now disabled? And if that's the case, shouldn't the whole "Classpath
container configuration" section of the IvyDE plugin preferences page go
away? What am I missing here?
This goes back to the following statement from Nicolas: "So the fix in your
issue is to just declare the source and javadoc in your ivy.xml files in
your repository."
But what does declaring the source and Javadoc in your ivy.xml bring you in
terms of automatic IvyDE support in Eclipse?
Here's what I would expect Nicolas's statement to imply. In your ivy.xml,
you would declare configurations with names like source and javadoc. Then in
your IvyDE preferences page, you would have the opportunity to specify those
configuration names. Then voilà, Eclipse would automatically open the
artifacts associated with those configurations, provided they still had the
expected types, i.e. source and javadoc.
Using this Ivy-centric approach would also make it trivially easy to support
Dmitriy's feature request: "for example to associate a single source ZIP
with multiple JAR artifacts."
I have to plead guilty to not having read the documentation. For some
reason, it hadn't occurred to me to even seek out a documentation page for
IvyDE:
http://ant.apache.org/ivy/ivyde/history/latest-milestone/index.html
On Wed, Feb 11, 2009 at 10:10 AM, Dmitriy Korobskiy <dk...@gmail.com>wrote:
> Mitch,
>
> this is a killer feature that I like a lot. I think it could be a big
> selling point for Ivy. Not sure if Maven Eclipse plugins
> could achieve that - does anybody know?
>
> Imagine just one developer setting up ivy.xml and all team members getting
> it from SCM, doing couple of clicks, and - voilà,
> all JARs are on the classpath, all or most have source code and Javadocs
> attached. You can then browse through all of source
> code with ease and just hover over a method to see its full Javadoc.
>
> Ah, if only IvyDE can attach Javadocs successfully. I'm yet to see it.
> I have a dream... (sorry for a possible sacrilege).
>
> Regarding types and suffixes - IvyDE docs explain it. They are needed to
> attach these artifacts to a main JAR artifact.
> I wonder if this configuration could be more flexible in the future - for
> example to associate a single source ZIP with multiple JAR artifacts,
> or specify a subdirectories as source or Javadoc roots.
> For now, I can live with repackaging to resolove these issues.
>
>
> Mitch Gitman wrote:
>
>> Nicolas, I'm trying to understand the impact of this change. Suppose an
>> Ivy
>> module publishes artifacts for source and Javadoc. Presumably, there are
>> "source" and "javadoc" Ivy configurations, or the like.
>>
>> I don't quite see the relevance then of the following fields in the Ivy
>> plugin configuration for Eclipse:
>>
>> - Sources types
>> - Sources suffixes
>> - Javadoc types
>> - Javadoc suffixes
>>
>> Can you offer a use case where these fields are still being used to look
>> for
>> something? I should also ask, what does "Sources types" (with a possible
>> value like "source") mean?
>>
>> I must confess, I've never used this feature myself to begin with.
>> Whenever
>> Eclipse would complain that it could not find the source for a class, I
>> would just click the button and manually navigate to the source ZIP on the
>> enterprise repository. Clumsy, I'll admit, but I wasn't aware of a better
>> way.
>>
>> On Wed, Feb 11, 2009 at 7:12 AM, Nicolas Lalevée <
>> nicolas.lalevee@hibnet.org
>>
>>
>>> wrote:
>>>
>>>
>>
>>
>>
>>> Actually the feature you were using with IvyDE 2.0.0.alpha1 was removed
>>> in
>>> beta1: make IvyDE try to find the sources and the javadocs even if they
>>> are
>>> not
>>> declared in the ivy.xml.
>>> I removed that feature as for me it was only usefull when using IvyDE
>>> with
>>> a
>>> maven repository, as Ivy didn't exposed the source and javadoc. As Ivy
>>> does
>>> now support it (IVY-325), this feature was remove to try to not waste the
>>> IDE
>>> responsivness. See also a related issue: IVYDE-128
>>>
>>> So the fix in your issue is to just declare the source and javadoc in
>>> your
>>> ivy.xml files in your repository.
>>>
>>> Nicolas
>>>
>>>
>>>
>>>> Gael
>>>>
>>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Marziou, Gael
>>>>> Sent: Tuesday, February 10, 2009 1:52 PM
>>>>> To: ivy-user@ant.apache.org
>>>>> Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>>>>>
>>>>>
>>>>>
>>>>>> I think you are hitting this issue:
>>>>>> https://issues.apache.org/jira/browse/IVYDE-146
>>>>>>
>>>>>>
>>>>> Merci Nicolas, the description matches indeed.
>>>>>
>>>>> But in this case I don't understand why I still have the
>>>>> issue with trunk build #20 IvyDE-updatesite on Hudson server,
>>>>> this fix is supposed to be included.
>>>>>
>>>>> Gael
>>>>>
>>>>>
>>>>
>>>
>>
>>
>>
>
> --
> DK AIM: DKroot1, Skype: DKroot
>
>
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Dmitriy Korobskiy <dk...@gmail.com>.
Mitch,
this is a killer feature that I like a lot. I think it could be a big
selling point for Ivy. Not sure if Maven Eclipse plugins
could achieve that - does anybody know?
Imagine just one developer setting up ivy.xml and all team members
getting it from SCM, doing couple of clicks, and - voilà,
all JARs are on the classpath, all or most have source code and Javadocs
attached. You can then browse through all of source
code with ease and just hover over a method to see its full Javadoc.
Ah, if only IvyDE can attach Javadocs successfully. I'm yet to see it.
I have a dream... (sorry for a possible sacrilege).
Regarding types and suffixes - IvyDE docs explain it. They are needed to
attach these artifacts to a main JAR artifact.
I wonder if this configuration could be more flexible in the future -
for example to associate a single source ZIP with multiple JAR artifacts,
or specify a subdirectories as source or Javadoc roots.
For now, I can live with repackaging to resolove these issues.
Mitch Gitman wrote:
> Nicolas, I'm trying to understand the impact of this change. Suppose an Ivy
> module publishes artifacts for source and Javadoc. Presumably, there are
> "source" and "javadoc" Ivy configurations, or the like.
>
> I don't quite see the relevance then of the following fields in the Ivy
> plugin configuration for Eclipse:
>
> - Sources types
> - Sources suffixes
> - Javadoc types
> - Javadoc suffixes
>
> Can you offer a use case where these fields are still being used to look for
> something? I should also ask, what does "Sources types" (with a possible
> value like "source") mean?
>
> I must confess, I've never used this feature myself to begin with. Whenever
> Eclipse would complain that it could not find the source for a class, I
> would just click the button and manually navigate to the source ZIP on the
> enterprise repository. Clumsy, I'll admit, but I wasn't aware of a better
> way.
>
> On Wed, Feb 11, 2009 at 7:12 AM, Nicolas Lalevée <nicolas.lalevee@hibnet.org
>
>> wrote:
>>
>
>
>> Actually the feature you were using with IvyDE 2.0.0.alpha1 was removed in
>> beta1: make IvyDE try to find the sources and the javadocs even if they are
>> not
>> declared in the ivy.xml.
>> I removed that feature as for me it was only usefull when using IvyDE with
>> a
>> maven repository, as Ivy didn't exposed the source and javadoc. As Ivy does
>> now support it (IVY-325), this feature was remove to try to not waste the
>> IDE
>> responsivness. See also a related issue: IVYDE-128
>>
>> So the fix in your issue is to just declare the source and javadoc in your
>> ivy.xml files in your repository.
>>
>> Nicolas
>>
>>
>>> Gael
>>>
>>>
>>>> -----Original Message-----
>>>> From: Marziou, Gael
>>>> Sent: Tuesday, February 10, 2009 1:52 PM
>>>> To: ivy-user@ant.apache.org
>>>> Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>>>>
>>>>
>>>>> I think you are hitting this issue:
>>>>> https://issues.apache.org/jira/browse/IVYDE-146
>>>>>
>>>> Merci Nicolas, the description matches indeed.
>>>>
>>>> But in this case I don't understand why I still have the
>>>> issue with trunk build #20 IvyDE-updatesite on Hudson server,
>>>> this fix is supposed to be included.
>>>>
>>>> Gael
>>>>
>>
>
>
--
DK
AIM: DKroot1, Skype: DKroot
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Mitch Gitman <mg...@gmail.com>.
Nicolas, I'm trying to understand the impact of this change. Suppose an Ivy
module publishes artifacts for source and Javadoc. Presumably, there are
"source" and "javadoc" Ivy configurations, or the like.
I don't quite see the relevance then of the following fields in the Ivy
plugin configuration for Eclipse:
- Sources types
- Sources suffixes
- Javadoc types
- Javadoc suffixes
Can you offer a use case where these fields are still being used to look for
something? I should also ask, what does "Sources types" (with a possible
value like "source") mean?
I must confess, I've never used this feature myself to begin with. Whenever
Eclipse would complain that it could not find the source for a class, I
would just click the button and manually navigate to the source ZIP on the
enterprise repository. Clumsy, I'll admit, but I wasn't aware of a better
way.
On Wed, Feb 11, 2009 at 7:12 AM, Nicolas Lalevée <nicolas.lalevee@hibnet.org
> wrote:
>
> Actually the feature you were using with IvyDE 2.0.0.alpha1 was removed in
> beta1: make IvyDE try to find the sources and the javadocs even if they are
> not
> declared in the ivy.xml.
> I removed that feature as for me it was only usefull when using IvyDE with
> a
> maven repository, as Ivy didn't exposed the source and javadoc. As Ivy does
> now support it (IVY-325), this feature was remove to try to not waste the
> IDE
> responsivness. See also a related issue: IVYDE-128
>
> So the fix in your issue is to just declare the source and javadoc in your
> ivy.xml files in your repository.
>
> Nicolas
>
> >
> > Gael
> >
> > > -----Original Message-----
> > > From: Marziou, Gael
> > > Sent: Tuesday, February 10, 2009 1:52 PM
> > > To: ivy-user@ant.apache.org
> > > Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
> > >
> > > > I think you are hitting this issue:
> > > > https://issues.apache.org/jira/browse/IVYDE-146
> > >
> > > Merci Nicolas, the description matches indeed.
> > >
> > > But in this case I don't understand why I still have the
> > > issue with trunk build #20 IvyDE-updatesite on Hudson server,
> > > this fix is supposed to be included.
> > >
> > > Gael
>
>
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On mardi 10 février 2009 17:41:54 Marziou, Gael wrote:
> I looked at the code of IvyResolveJob.java that was patched to fix
> IVYDE-146, I have found messages like:
>
> monitor.subTask("searching javadoc for " + artifact);
>
> Should I see this message logged in the Ivy console?
> Currently I don't.
Actually the feature you were using with IvyDE 2.0.0.alpha1 was removed in
beta1: make IvyDE try to find the sources and the javadocs even if they are not
declared in the ivy.xml.
I removed that feature as for me it was only usefull when using IvyDE with a
maven repository, as Ivy didn't exposed the source and javadoc. As Ivy does
now support it (IVY-325), this feature was remove to try to not waste the IDE
responsivness. See also a related issue: IVYDE-128
So the fix in your issue is to just declare the source and javadoc in your
ivy.xml files in your repository.
Nicolas
>
> Gael
>
> > -----Original Message-----
> > From: Marziou, Gael
> > Sent: Tuesday, February 10, 2009 1:52 PM
> > To: ivy-user@ant.apache.org
> > Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
> >
> > > I think you are hitting this issue:
> > > https://issues.apache.org/jira/browse/IVYDE-146
> >
> > Merci Nicolas, the description matches indeed.
> >
> > But in this case I don't understand why I still have the
> > issue with trunk build #20 IvyDE-updatesite on Hudson server,
> > this fix is supposed to be included.
> >
> > Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Dmitriy Korobskiy <dk...@gmail.com>.
Nicolas,
I have opened IVYDE-166 with a (hopefully) reproducible test case in the
ticket.
Nicolas Lalevée wrote:
> On jeudi 12 février 2009 20:11:38 Dmitriy Korobskiy wrote:
>
>> Nicolas,
>>
>> this is very strange. If Javadoc is attached, it should work in all
>> these 3 places: tooltip, Javadoc view and Shift+F2.
>> I'd not suspect Jadclipse. I'm using Jadclipse as well, BTW. However,
>> you never know...
>>
>> I wasn't able to reopen IVYDE-55:
>> https://issues.apache.org/jira/browse/IVYDE-55. I left a comment with
>> all details there.
>>
>> Could somebody with the right privileges please reopen it? It is not
>> resolved in beta1.
>>
>
> I think you should open an new jira issue. The underlying real issue might not
> be related to what has been fixed with IVYDE-55.
>
> Nicolas
>
>
>
>> Nicolas Lalevée wrote:
>>
>>> On mercredi 11 février 2009 20:47:56 Dmitriy Korobskiy wrote:
>>>
>>>> Nicolas,
>>>>
>>>> you can easily check whether source or Javadoc attachment happened:
>>>>
>>>> - expand Ivy container and find the main artifact JAR
>>>> - right-click to Properties (or Alt-Enter)
>>>> - see whether the source zip is attached or not
>>>> - see if Javadoc location specifies "Javadoc in archive"
>>>>
>>>> I do see Javadocs attachments working in my IDE. Make sure that your JAR
>>>> with attached Javadoc comes first in the Build classpath order.
>>>> When sources *or* Javadocs are attached, Eclipse makes use of it in the
>>>> following places:
>>>>
>>>> 1. Tooltip - hover over a library method
>>>>
>>>> 2. Javadoc view. If neither source nor Javadoc is attached, you'd see a
>>>> message:
>>>> /Note: This element neither has attached source nor attached Javadoc and
>>>> hence no Javadoc could be found./
>>>>
>>>> When Javadocs are attached, you can also use them in :
>>>> 3. Shift+F2 - browse external Javadoc which is very handy.
>>>>
>>> Something weired in happening in my Eclipse. In both my simple project
>>> and my Ivy project I got the javadoc attached but not the sources. And
>>> for both project:
>>> * in the tooltip: no javadoc or source
>>> * in the javadoc view: no javadoc or source
>>> * Shift+F2 : works like a charm for both...
>>>
>>> I think I cannot help you further with your issue, my Eclipse seems
>>> fracked up (maybe because of JadClipse ?).
>>>
>>> Nicolas
>>>
>>>
>>>> Nicolas Lalevée wrote:
>>>>
>>>>> On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
>>>>>
>>>>>> Hi, all
>>>>>>
>>>>>> I have a slightly different issue - IvyDE is downloading sources, but
>>>>>> Javadocs do not work for the life of me.
>>>>>> I had that issue a year and a half ago with IvyDE 1.2, and it seems
>>>>>> now as a resurgence of closed IvyDE-55:
>>>>>> https://issues.apache.org/jira/browse/IVYDE-55.
>>>>>>
>>>>>> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and
>>>>>> IvyDE 2.0.0.beta1. The difference with your, Gael, configuration from
>>>>>> what I understood could be that I declare all artifacts explicitly in
>>>>>> ivy.xml.
>>>>>>
>>>>>> Here are the steps.
>>>>>> 1. ivy.xml
>>>>>> <?xml version="1.0"?>
>>>>>> <?xml version="1.0"?>
>>>>>> <ivy-module version="2.0"
>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.x
>>>>>> sd "> <info organisation="xxx" module="mmm" status="integration" />
>>>>>> <configurations>
>>>>>> <conf name="compile" />
>>>>>> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
>>>>>> <conf name="ide" extends="compile" description="+ Javadocs and
>>>>>> sources" />
>>>>>> </configurations>
>>>>>> <dependencies defaultconf="compile,war->default;ide->ide(default)">
>>>>>> <dependency org="apache" name="commons-logging" rev="1.1"/>
>>>>>> </dependencies>
>>>>>> </ivy-module>
>>>>>>
>>>>>> 2. Repository files:
>>>>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
>>>>>> g- 1.1 -doc.zip
>>>>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
>>>>>> g- 1.1 -src.zip
>>>>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
>>>>>> g- 1.1 .jar
>>>>>>
>>>>>> 3. commons-logging-1.1-ivy.xml
>>>>>> <?xml version="1.0"?>
>>>>>> <?xml-stylesheet type="text/xsl"
>>>>>> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
>>>>>> <ivy-module version="2.0"
>>>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.x
>>>>>> sd "> <info organisation="apache" module="commons-logging"
>>>>>> revision="1.1" status="release"/>
>>>>>> <configurations>
>>>>>> <conf name="default"/>
>>>>>> <conf name="ide" extends="default" description="JavaDoc and
>>>>>> sources"/> </configurations>
>>>>>> <publications>
>>>>>> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
>>>>>> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
>>>>>> conf="ide"/>
>>>>>> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
>>>>>> conf="ide"/>
>>>>>> </publications>
>>>>>> </ivy-module>
>>>>>>
>>>>>> I get commons-logging-1.1.jar with an attached source, but not
>>>>>> Javadocs.
>>>>>>
>>>>> I have some similar configuration to yours. Looking into the properties
>>>>> of the jar in the IvyDE container, they look good. But me too the
>>>>> javadoc view tells me that nothing is attached.
>>>>> I then setup an non-Ivy project, with a jar and some attached javadoc.
>>>>> Eclipse tells me that it looks good ("Validate..." button). But the
>>>>> javadoc view still tell me that nothing is attached... Am I missing
>>>>> something here ? Could you try to setup some simple non-Ivy project and
>>>>> tells me if it works ? And if it works post your .classpath ?
>>>>>
>>>>> Nicolas
>>>>>
>>>>>
>>>>>
>>>>> Nicolas
>>>>>
>>>>>
>>>>>> Marziou, Gael wrote:
>>>>>>
>>>>>>>> I think you are hitting this issue:
>>>>>>>> https://issues.apache.org/jira/browse/IVYDE-146
>>>>>>>>
>>>>>>> Merci Nicolas, the description matches indeed.
>>>>>>>
>>>>>>> But in this case I don't understand why I still have the issue with
>>>>>>> trunk build #20 IvyDE-updatesite on Hudson server, this fix is
>>>>>>> supposed to be included.
>>>>>>>
>>>>>>> Gael
>>>>>>>
>
>
>
--
DK
AIM: DKroot1, Skype: DKroot
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On jeudi 12 février 2009 20:11:38 Dmitriy Korobskiy wrote:
> Nicolas,
>
> this is very strange. If Javadoc is attached, it should work in all
> these 3 places: tooltip, Javadoc view and Shift+F2.
> I'd not suspect Jadclipse. I'm using Jadclipse as well, BTW. However,
> you never know...
>
> I wasn't able to reopen IVYDE-55:
> https://issues.apache.org/jira/browse/IVYDE-55. I left a comment with
> all details there.
>
> Could somebody with the right privileges please reopen it? It is not
> resolved in beta1.
I think you should open an new jira issue. The underlying real issue might not
be related to what has been fixed with IVYDE-55.
Nicolas
>
> Nicolas Lalevée wrote:
> > On mercredi 11 février 2009 20:47:56 Dmitriy Korobskiy wrote:
> >> Nicolas,
> >>
> >> you can easily check whether source or Javadoc attachment happened:
> >>
> >> - expand Ivy container and find the main artifact JAR
> >> - right-click to Properties (or Alt-Enter)
> >> - see whether the source zip is attached or not
> >> - see if Javadoc location specifies "Javadoc in archive"
> >>
> >> I do see Javadocs attachments working in my IDE. Make sure that your JAR
> >> with attached Javadoc comes first in the Build classpath order.
> >> When sources *or* Javadocs are attached, Eclipse makes use of it in the
> >> following places:
> >>
> >> 1. Tooltip - hover over a library method
> >>
> >> 2. Javadoc view. If neither source nor Javadoc is attached, you'd see a
> >> message:
> >> /Note: This element neither has attached source nor attached Javadoc and
> >> hence no Javadoc could be found./
> >>
> >> When Javadocs are attached, you can also use them in :
> >> 3. Shift+F2 - browse external Javadoc which is very handy.
> >
> > Something weired in happening in my Eclipse. In both my simple project
> > and my Ivy project I got the javadoc attached but not the sources. And
> > for both project:
> > * in the tooltip: no javadoc or source
> > * in the javadoc view: no javadoc or source
> > * Shift+F2 : works like a charm for both...
> >
> > I think I cannot help you further with your issue, my Eclipse seems
> > fracked up (maybe because of JadClipse ?).
> >
> > Nicolas
> >
> >> Nicolas Lalevée wrote:
> >>> On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
> >>>> Hi, all
> >>>>
> >>>> I have a slightly different issue - IvyDE is downloading sources, but
> >>>> Javadocs do not work for the life of me.
> >>>> I had that issue a year and a half ago with IvyDE 1.2, and it seems
> >>>> now as a resurgence of closed IvyDE-55:
> >>>> https://issues.apache.org/jira/browse/IVYDE-55.
> >>>>
> >>>> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and
> >>>> IvyDE 2.0.0.beta1. The difference with your, Gael, configuration from
> >>>> what I understood could be that I declare all artifacts explicitly in
> >>>> ivy.xml.
> >>>>
> >>>> Here are the steps.
> >>>> 1. ivy.xml
> >>>> <?xml version="1.0"?>
> >>>> <?xml version="1.0"?>
> >>>> <ivy-module version="2.0"
> >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >>>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.x
> >>>>sd "> <info organisation="xxx" module="mmm" status="integration" />
> >>>> <configurations>
> >>>> <conf name="compile" />
> >>>> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
> >>>> <conf name="ide" extends="compile" description="+ Javadocs and
> >>>> sources" />
> >>>> </configurations>
> >>>> <dependencies defaultconf="compile,war->default;ide->ide(default)">
> >>>> <dependency org="apache" name="commons-logging" rev="1.1"/>
> >>>> </dependencies>
> >>>> </ivy-module>
> >>>>
> >>>> 2. Repository files:
> >>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
> >>>>g- 1.1 -doc.zip
> >>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
> >>>>g- 1.1 -src.zip
> >>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-loggin
> >>>>g- 1.1 .jar
> >>>>
> >>>> 3. commons-logging-1.1-ivy.xml
> >>>> <?xml version="1.0"?>
> >>>> <?xml-stylesheet type="text/xsl"
> >>>> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
> >>>> <ivy-module version="2.0"
> >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >>>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.x
> >>>>sd "> <info organisation="apache" module="commons-logging"
> >>>> revision="1.1" status="release"/>
> >>>> <configurations>
> >>>> <conf name="default"/>
> >>>> <conf name="ide" extends="default" description="JavaDoc and
> >>>> sources"/> </configurations>
> >>>> <publications>
> >>>> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
> >>>> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
> >>>> conf="ide"/>
> >>>> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
> >>>> conf="ide"/>
> >>>> </publications>
> >>>> </ivy-module>
> >>>>
> >>>> I get commons-logging-1.1.jar with an attached source, but not
> >>>> Javadocs.
> >>>
> >>> I have some similar configuration to yours. Looking into the properties
> >>> of the jar in the IvyDE container, they look good. But me too the
> >>> javadoc view tells me that nothing is attached.
> >>> I then setup an non-Ivy project, with a jar and some attached javadoc.
> >>> Eclipse tells me that it looks good ("Validate..." button). But the
> >>> javadoc view still tell me that nothing is attached... Am I missing
> >>> something here ? Could you try to setup some simple non-Ivy project and
> >>> tells me if it works ? And if it works post your .classpath ?
> >>>
> >>> Nicolas
> >>>
> >>>
> >>>
> >>> Nicolas
> >>>
> >>>> Marziou, Gael wrote:
> >>>>>> I think you are hitting this issue:
> >>>>>> https://issues.apache.org/jira/browse/IVYDE-146
> >>>>>
> >>>>> Merci Nicolas, the description matches indeed.
> >>>>>
> >>>>> But in this case I don't understand why I still have the issue with
> >>>>> trunk build #20 IvyDE-updatesite on Hudson server, this fix is
> >>>>> supposed to be included.
> >>>>>
> >>>>> Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Dmitriy Korobskiy <dk...@gmail.com>.
Nicolas,
this is very strange. If Javadoc is attached, it should work in all
these 3 places: tooltip, Javadoc view and Shift+F2.
I'd not suspect Jadclipse. I'm using Jadclipse as well, BTW. However,
you never know...
I wasn't able to reopen IVYDE-55:
https://issues.apache.org/jira/browse/IVYDE-55. I left a comment with
all details there.
Could somebody with the right privileges please reopen it? It is not
resolved in beta1.
Nicolas Lalevée wrote:
> On mercredi 11 février 2009 20:47:56 Dmitriy Korobskiy wrote:
>
>> Nicolas,
>>
>> you can easily check whether source or Javadoc attachment happened:
>>
>> - expand Ivy container and find the main artifact JAR
>> - right-click to Properties (or Alt-Enter)
>> - see whether the source zip is attached or not
>> - see if Javadoc location specifies "Javadoc in archive"
>>
>> I do see Javadocs attachments working in my IDE. Make sure that your JAR
>> with attached Javadoc comes first in the Build classpath order.
>> When sources *or* Javadocs are attached, Eclipse makes use of it in the
>> following places:
>>
>> 1. Tooltip - hover over a library method
>>
>> 2. Javadoc view. If neither source nor Javadoc is attached, you'd see a
>> message:
>> /Note: This element neither has attached source nor attached Javadoc and
>> hence no Javadoc could be found./
>>
>> When Javadocs are attached, you can also use them in :
>> 3. Shift+F2 - browse external Javadoc which is very handy.
>>
>
> Something weired in happening in my Eclipse. In both my simple project and my
> Ivy project I got the javadoc attached but not the sources. And for both
> project:
> * in the tooltip: no javadoc or source
> * in the javadoc view: no javadoc or source
> * Shift+F2 : works like a charm for both...
>
> I think I cannot help you further with your issue, my Eclipse seems fracked up
> (maybe because of JadClipse ?).
>
> Nicolas
>
>
>> Nicolas Lalevée wrote:
>>
>>> On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
>>>
>>>> Hi, all
>>>>
>>>> I have a slightly different issue - IvyDE is downloading sources, but
>>>> Javadocs do not work for the life of me.
>>>> I had that issue a year and a half ago with IvyDE 1.2, and it seems now
>>>> as a resurgence of closed IvyDE-55:
>>>> https://issues.apache.org/jira/browse/IVYDE-55.
>>>>
>>>> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and IvyDE
>>>> 2.0.0.beta1. The difference with your, Gael, configuration from what I
>>>> understood could be that I declare all artifacts explicitly in ivy.xml.
>>>>
>>>> Here are the steps.
>>>> 1. ivy.xml
>>>> <?xml version="1.0"?>
>>>> <?xml version="1.0"?>
>>>> <ivy-module version="2.0"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd
>>>> "> <info organisation="xxx" module="mmm" status="integration" />
>>>> <configurations>
>>>> <conf name="compile" />
>>>> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
>>>> <conf name="ide" extends="compile" description="+ Javadocs and
>>>> sources" />
>>>> </configurations>
>>>> <dependencies defaultconf="compile,war->default;ide->ide(default)">
>>>> <dependency org="apache" name="commons-logging" rev="1.1"/>
>>>> </dependencies>
>>>> </ivy-module>
>>>>
>>>> 2. Repository files:
>>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-
>>>> 1.1 -doc.zip
>>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-
>>>> 1.1 -src.zip
>>>> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-
>>>> 1.1 .jar
>>>>
>>>> 3. commons-logging-1.1-ivy.xml
>>>> <?xml version="1.0"?>
>>>> <?xml-stylesheet type="text/xsl"
>>>> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
>>>> <ivy-module version="2.0"
>>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd
>>>> "> <info organisation="apache" module="commons-logging" revision="1.1"
>>>> status="release"/>
>>>> <configurations>
>>>> <conf name="default"/>
>>>> <conf name="ide" extends="default" description="JavaDoc and
>>>> sources"/> </configurations>
>>>> <publications>
>>>> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
>>>> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
>>>> conf="ide"/>
>>>> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
>>>> conf="ide"/>
>>>> </publications>
>>>> </ivy-module>
>>>>
>>>> I get commons-logging-1.1.jar with an attached source, but not Javadocs.
>>>>
>>> I have some similar configuration to yours. Looking into the properties
>>> of the jar in the IvyDE container, they look good. But me too the javadoc
>>> view tells me that nothing is attached.
>>> I then setup an non-Ivy project, with a jar and some attached javadoc.
>>> Eclipse tells me that it looks good ("Validate..." button). But the
>>> javadoc view still tell me that nothing is attached... Am I missing
>>> something here ? Could you try to setup some simple non-Ivy project and
>>> tells me if it works ? And if it works post your .classpath ?
>>>
>>> Nicolas
>>>
>>>
>>>
>>> Nicolas
>>>
>>>
>>>> Marziou, Gael wrote:
>>>>
>>>>>> I think you are hitting this issue:
>>>>>> https://issues.apache.org/jira/browse/IVYDE-146
>>>>>>
>>>>> Merci Nicolas, the description matches indeed.
>>>>>
>>>>> But in this case I don't understand why I still have the issue with
>>>>> trunk build #20 IvyDE-updatesite on Hudson server, this fix is supposed
>>>>> to be included.
>>>>>
>>>>> Gael
>>>>>
>
>
>
--
DK
AIM: DKroot1, Skype: DKroot
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On mercredi 11 février 2009 20:47:56 Dmitriy Korobskiy wrote:
> Nicolas,
>
> you can easily check whether source or Javadoc attachment happened:
>
> - expand Ivy container and find the main artifact JAR
> - right-click to Properties (or Alt-Enter)
> - see whether the source zip is attached or not
> - see if Javadoc location specifies "Javadoc in archive"
>
> I do see Javadocs attachments working in my IDE. Make sure that your JAR
> with attached Javadoc comes first in the Build classpath order.
> When sources *or* Javadocs are attached, Eclipse makes use of it in the
> following places:
>
> 1. Tooltip - hover over a library method
>
> 2. Javadoc view. If neither source nor Javadoc is attached, you'd see a
> message:
> /Note: This element neither has attached source nor attached Javadoc and
> hence no Javadoc could be found./
>
> When Javadocs are attached, you can also use them in :
> 3. Shift+F2 - browse external Javadoc which is very handy.
Something weired in happening in my Eclipse. In both my simple project and my
Ivy project I got the javadoc attached but not the sources. And for both
project:
* in the tooltip: no javadoc or source
* in the javadoc view: no javadoc or source
* Shift+F2 : works like a charm for both...
I think I cannot help you further with your issue, my Eclipse seems fracked up
(maybe because of JadClipse ?).
Nicolas
>
> Nicolas Lalevée wrote:
> > On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
> >> Hi, all
> >>
> >> I have a slightly different issue - IvyDE is downloading sources, but
> >> Javadocs do not work for the life of me.
> >> I had that issue a year and a half ago with IvyDE 1.2, and it seems now
> >> as a resurgence of closed IvyDE-55:
> >> https://issues.apache.org/jira/browse/IVYDE-55.
> >>
> >> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and IvyDE
> >> 2.0.0.beta1. The difference with your, Gael, configuration from what I
> >> understood could be that I declare all artifacts explicitly in ivy.xml.
> >>
> >> Here are the steps.
> >> 1. ivy.xml
> >> <?xml version="1.0"?>
> >> <?xml version="1.0"?>
> >> <ivy-module version="2.0"
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd
> >>"> <info organisation="xxx" module="mmm" status="integration" />
> >> <configurations>
> >> <conf name="compile" />
> >> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
> >> <conf name="ide" extends="compile" description="+ Javadocs and
> >> sources" />
> >> </configurations>
> >> <dependencies defaultconf="compile,war->default;ide->ide(default)">
> >> <dependency org="apache" name="commons-logging" rev="1.1"/>
> >> </dependencies>
> >> </ivy-module>
> >>
> >> 2. Repository files:
> >> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-
> >>1.1 -doc.zip
> >> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-
> >>1.1 -src.zip
> >> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-
> >>1.1 .jar
> >>
> >> 3. commons-logging-1.1-ivy.xml
> >> <?xml version="1.0"?>
> >> <?xml-stylesheet type="text/xsl"
> >> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
> >> <ivy-module version="2.0"
> >> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd
> >>"> <info organisation="apache" module="commons-logging" revision="1.1"
> >> status="release"/>
> >> <configurations>
> >> <conf name="default"/>
> >> <conf name="ide" extends="default" description="JavaDoc and
> >> sources"/> </configurations>
> >> <publications>
> >> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
> >> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
> >> conf="ide"/>
> >> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
> >> conf="ide"/>
> >> </publications>
> >> </ivy-module>
> >>
> >> I get commons-logging-1.1.jar with an attached source, but not Javadocs.
> >
> > I have some similar configuration to yours. Looking into the properties
> > of the jar in the IvyDE container, they look good. But me too the javadoc
> > view tells me that nothing is attached.
> > I then setup an non-Ivy project, with a jar and some attached javadoc.
> > Eclipse tells me that it looks good ("Validate..." button). But the
> > javadoc view still tell me that nothing is attached... Am I missing
> > something here ? Could you try to setup some simple non-Ivy project and
> > tells me if it works ? And if it works post your .classpath ?
> >
> > Nicolas
> >
> >
> >
> > Nicolas
> >
> >> Marziou, Gael wrote:
> >>>> I think you are hitting this issue:
> >>>> https://issues.apache.org/jira/browse/IVYDE-146
> >>>
> >>> Merci Nicolas, the description matches indeed.
> >>>
> >>> But in this case I don't understand why I still have the issue with
> >>> trunk build #20 IvyDE-updatesite on Hudson server, this fix is supposed
> >>> to be included.
> >>>
> >>> Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Dmitriy Korobskiy <dk...@gmail.com>.
Nicolas,
you can easily check whether source or Javadoc attachment happened:
- expand Ivy container and find the main artifact JAR
- right-click to Properties (or Alt-Enter)
- see whether the source zip is attached or not
- see if Javadoc location specifies "Javadoc in archive"
I do see Javadocs attachments working in my IDE. Make sure that your JAR
with attached Javadoc comes first in the Build classpath order.
When sources *or* Javadocs are attached, Eclipse makes use of it in the
following places:
1. Tooltip - hover over a library method
2. Javadoc view. If neither source nor Javadoc is attached, you'd see a
message:
/Note: This element neither has attached source nor attached Javadoc and
hence no Javadoc could be found./
When Javadocs are attached, you can also use them in :
3. Shift+F2 - browse external Javadoc which is very handy.
Nicolas Lalevée wrote:
> On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
>
>> Hi, all
>>
>> I have a slightly different issue - IvyDE is downloading sources, but
>> Javadocs do not work for the life of me.
>> I had that issue a year and a half ago with IvyDE 1.2, and it seems now
>> as a resurgence of closed IvyDE-55:
>> https://issues.apache.org/jira/browse/IVYDE-55.
>>
>> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and IvyDE
>> 2.0.0.beta1. The difference with your, Gael, configuration from what I
>> understood could be that I declare all artifacts explicitly in ivy.xml.
>>
>> Here are the steps.
>> 1. ivy.xml
>> <?xml version="1.0"?>
>> <?xml version="1.0"?>
>> <ivy-module version="2.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
>> <info organisation="xxx" module="mmm" status="integration" />
>> <configurations>
>> <conf name="compile" />
>> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
>> <conf name="ide" extends="compile" description="+ Javadocs and
>> sources" />
>> </configurations>
>> <dependencies defaultconf="compile,war->default;ide->ide(default)">
>> <dependency org="apache" name="commons-logging" rev="1.1"/>
>> </dependencies>
>> </ivy-module>
>>
>> 2. Repository files:
>> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1
>> -doc.zip
>> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1
>> -src.zip
>> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1
>> .jar
>>
>> 3. commons-logging-1.1-ivy.xml
>> <?xml version="1.0"?>
>> <?xml-stylesheet type="text/xsl"
>> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
>> <ivy-module version="2.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
>> <info organisation="apache" module="commons-logging" revision="1.1"
>> status="release"/>
>> <configurations>
>> <conf name="default"/>
>> <conf name="ide" extends="default" description="JavaDoc and sources"/>
>> </configurations>
>> <publications>
>> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
>> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
>> conf="ide"/>
>> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
>> conf="ide"/>
>> </publications>
>> </ivy-module>
>>
>> I get commons-logging-1.1.jar with an attached source, but not Javadocs.
>>
>
> I have some similar configuration to yours. Looking into the properties of the
> jar in the IvyDE container, they look good. But me too the javadoc view tells
> me that nothing is attached.
> I then setup an non-Ivy project, with a jar and some attached javadoc. Eclipse
> tells me that it looks good ("Validate..." button). But the javadoc view still
> tell me that nothing is attached... Am I missing something here ? Could you
> try to setup some simple non-Ivy project and tells me if it works ? And if it
> works post your .classpath ?
>
> Nicolas
>
>
>
> Nicolas
>
>
>
>
>
>> Marziou, Gael wrote:
>>
>>>> I think you are hitting this issue:
>>>> https://issues.apache.org/jira/browse/IVYDE-146
>>>>
>>> Merci Nicolas, the description matches indeed.
>>>
>>> But in this case I don't understand why I still have the issue with trunk
>>> build #20 IvyDE-updatesite on Hudson server, this fix is supposed to be
>>> included.
>>>
>>> Gael
>>>
>
>
>
--
DK
AIM: DKroot1, Skype: DKroot
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On mardi 10 février 2009 21:01:01 Dmitriy Korobskiy wrote:
> Hi, all
>
> I have a slightly different issue - IvyDE is downloading sources, but
> Javadocs do not work for the life of me.
> I had that issue a year and a half ago with IvyDE 1.2, and it seems now
> as a resurgence of closed IvyDE-55:
> https://issues.apache.org/jira/browse/IVYDE-55.
>
> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and IvyDE
> 2.0.0.beta1. The difference with your, Gael, configuration from what I
> understood could be that I declare all artifacts explicitly in ivy.xml.
>
> Here are the steps.
> 1. ivy.xml
> <?xml version="1.0"?>
> <?xml version="1.0"?>
> <ivy-module version="2.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
> <info organisation="xxx" module="mmm" status="integration" />
> <configurations>
> <conf name="compile" />
> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
> <conf name="ide" extends="compile" description="+ Javadocs and
> sources" />
> </configurations>
> <dependencies defaultconf="compile,war->default;ide->ide(default)">
> <dependency org="apache" name="commons-logging" rev="1.1"/>
> </dependencies>
> </ivy-module>
>
> 2. Repository files:
> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1
>-doc.zip
> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1
>-src.zip
> {repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1
>.jar
>
> 3. commons-logging-1.1-ivy.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl"
> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
> <ivy-module version="2.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
> <info organisation="apache" module="commons-logging" revision="1.1"
> status="release"/>
> <configurations>
> <conf name="default"/>
> <conf name="ide" extends="default" description="JavaDoc and sources"/>
> </configurations>
> <publications>
> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
> conf="ide"/>
> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
> conf="ide"/>
> </publications>
> </ivy-module>
>
> I get commons-logging-1.1.jar with an attached source, but not Javadocs.
I have some similar configuration to yours. Looking into the properties of the
jar in the IvyDE container, they look good. But me too the javadoc view tells
me that nothing is attached.
I then setup an non-Ivy project, with a jar and some attached javadoc. Eclipse
tells me that it looks good ("Validate..." button). But the javadoc view still
tell me that nothing is attached... Am I missing something here ? Could you
try to setup some simple non-Ivy project and tells me if it works ? And if it
works post your .classpath ?
Nicolas
Nicolas
>
> Marziou, Gael wrote:
> >> I think you are hitting this issue:
> >> https://issues.apache.org/jira/browse/IVYDE-146
> >
> > Merci Nicolas, the description matches indeed.
> >
> > But in this case I don't understand why I still have the issue with trunk
> > build #20 IvyDE-updatesite on Hudson server, this fix is supposed to be
> > included.
> >
> > Gael
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
I looked at the code of IvyResolveJob.java that was patched to fix IVYDE-146, I have found messages like:
monitor.subTask("searching javadoc for " + artifact);
Should I see this message logged in the Ivy console?
Currently I don't.
Gael
> -----Original Message-----
> From: Marziou, Gael
> Sent: Tuesday, February 10, 2009 1:52 PM
> To: ivy-user@ant.apache.org
> Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>
>
> > I think you are hitting this issue:
> > https://issues.apache.org/jira/browse/IVYDE-146
>
> Merci Nicolas, the description matches indeed.
>
> But in this case I don't understand why I still have the
> issue with trunk build #20 IvyDE-updatesite on Hudson server,
> this fix is supposed to be included.
>
> Gael
>
>
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Dmitriy Korobskiy <dk...@gmail.com>.
Gael,
for me - it's attaching sources, but not Javadocs. Weird.
I think that we've confirmed at least the issue with Javadocs. Shall I
reopen IVYDE-55?
Marziou, Gael wrote:
> Hi Dmitriy,
>
> I tried your way of doing and IvyDE (trunk) downloaded both the source and javadoc but it did not change the build path to attach these source and javadoc zip files to the commons-logging-1.1.jar build path entry.
> So to me, it's not the expected behavior that I had when using alpha1 and classifiers.
>
> The only workaround I found is to downgrade to alpha1.
>
> Gael
>
>
>
>> -----Original Message-----
>> From: Dmitriy Korobskiy [mailto:dkroot1@gmail.com]
>> Sent: Tuesday, February 10, 2009 9:01 PM
>> To: ivy-user@ant.apache.org
>> Subject: Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>>
>> Hi, all
>>
>> I have a slightly different issue - IvyDE is downloading
>> sources, but Javadocs do not work for the life of me.
>> I had that issue a year and a half ago with IvyDE 1.2, and it
>> seems now as a resurgence of closed IvyDE-55:
>> https://issues.apache.org/jira/browse/IVYDE-55.
>>
>> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution)
>> and IvyDE 2.0.0.beta1. The difference with your, Gael,
>> configuration from what I understood could be that I declare
>> all artifacts explicitly in ivy.xml.
>>
>> Here are the steps.
>> 1. ivy.xml
>> <?xml version="1.0"?>
>> <?xml version="1.0"?>
>> <ivy-module version="2.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schem
>> as/ivy.xsd">
>> <info organisation="xxx" module="mmm" status="integration" />
>> <configurations>
>> <conf name="compile" />
>> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
>> <conf name="ide" extends="compile" description="+
>> Javadocs and sources" />
>> </configurations>
>> <dependencies defaultconf="compile,war->default;ide->ide(default)">
>> <dependency org="apache" name="commons-logging" rev="1.1"/>
>> </dependencies>
>> </ivy-module>
>>
>> 2. Repository files:
>> {repository}\apache\commons-logging\commons-logging-1.1\common
>> s-logging-1.1-doc.zip
>> {repository}\apache\commons-logging\commons-logging-1.1\common
>> s-logging-1.1-src.zip
>> {repository}\apache\commons-logging\commons-logging-1.1\common
>> s-logging-1.1.jar
>>
>> 3. commons-logging-1.1-ivy.xml
>> <?xml version="1.0"?>
>> <?xml-stylesheet type="text/xsl"
>> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
>> <ivy-module version="2.0"
>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schem
>> as/ivy.xsd">
>> <info organisation="apache" module="commons-logging" revision="1.1"
>> status="release"/>
>> <configurations>
>> <conf name="default"/>
>> <conf name="ide" extends="default" description="JavaDoc
>> and sources"/>
>> </configurations>
>> <publications>
>> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
>> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
>> conf="ide"/>
>> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
>> conf="ide"/>
>> </publications>
>> </ivy-module>
>>
>> I get commons-logging-1.1.jar with an attached source, but
>> not Javadocs.
>>
>> Marziou, Gael wrote:
>>
>>>
>>>
>>>
>>>> I think you are hitting this issue:
>>>> https://issues.apache.org/jira/browse/IVYDE-146
>>>>
>>>>
>>> Merci Nicolas, the description matches indeed.
>>>
>>> But in this case I don't understand why I still have the
>>>
>> issue with trunk build #20 IvyDE-updatesite on Hudson server,
>> this fix is supposed to be included.
>>
>>> Gael
>>>
>>>
>>>
>>>
>> --
>> DK
>> AIM: DKroot1, Skype: DKroot
>>
>>
>>
--
DK
AIM: DKroot1, Skype: DKroot
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
Hi Dmitriy,
I tried your way of doing and IvyDE (trunk) downloaded both the source and javadoc but it did not change the build path to attach these source and javadoc zip files to the commons-logging-1.1.jar build path entry.
So to me, it's not the expected behavior that I had when using alpha1 and classifiers.
The only workaround I found is to downgrade to alpha1.
Gael
> -----Original Message-----
> From: Dmitriy Korobskiy [mailto:dkroot1@gmail.com]
> Sent: Tuesday, February 10, 2009 9:01 PM
> To: ivy-user@ant.apache.org
> Subject: Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>
> Hi, all
>
> I have a slightly different issue - IvyDE is downloading
> sources, but Javadocs do not work for the life of me.
> I had that issue a year and a half ago with IvyDE 1.2, and it
> seems now as a resurgence of closed IvyDE-55:
> https://issues.apache.org/jira/browse/IVYDE-55.
>
> I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution)
> and IvyDE 2.0.0.beta1. The difference with your, Gael,
> configuration from what I understood could be that I declare
> all artifacts explicitly in ivy.xml.
>
> Here are the steps.
> 1. ivy.xml
> <?xml version="1.0"?>
> <?xml version="1.0"?>
> <ivy-module version="2.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schem
> as/ivy.xsd">
> <info organisation="xxx" module="mmm" status="integration" />
> <configurations>
> <conf name="compile" />
> <conf name="war" /> <!-- Artifacts to be included in a WAR -->
> <conf name="ide" extends="compile" description="+
> Javadocs and sources" />
> </configurations>
> <dependencies defaultconf="compile,war->default;ide->ide(default)">
> <dependency org="apache" name="commons-logging" rev="1.1"/>
> </dependencies>
> </ivy-module>
>
> 2. Repository files:
> {repository}\apache\commons-logging\commons-logging-1.1\common
> s-logging-1.1-doc.zip
> {repository}\apache\commons-logging\commons-logging-1.1\common
> s-logging-1.1-src.zip
> {repository}\apache\commons-logging\commons-logging-1.1\common
> s-logging-1.1.jar
>
> 3. commons-logging-1.1-ivy.xml
> <?xml version="1.0"?>
> <?xml-stylesheet type="text/xsl"
> href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
> <ivy-module version="2.0"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schem
> as/ivy.xsd">
> <info organisation="apache" module="commons-logging" revision="1.1"
> status="release"/>
> <configurations>
> <conf name="default"/>
> <conf name="ide" extends="default" description="JavaDoc
> and sources"/>
> </configurations>
> <publications>
> <artifact name="commons-logging-1.1" type="jar" conf="default"/>
> <artifact name="commons-logging-1.1-src" type="source" ext="zip"
> conf="ide"/>
> <artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
> conf="ide"/>
> </publications>
> </ivy-module>
>
> I get commons-logging-1.1.jar with an attached source, but
> not Javadocs.
>
> Marziou, Gael wrote:
> >
> >
> >> I think you are hitting this issue:
> >> https://issues.apache.org/jira/browse/IVYDE-146
> >>
> >
> > Merci Nicolas, the description matches indeed.
> >
> > But in this case I don't understand why I still have the
> issue with trunk build #20 IvyDE-updatesite on Hudson server,
> this fix is supposed to be included.
> >
> > Gael
> >
> >
> >
>
> --
> DK
> AIM: DKroot1, Skype: DKroot
>
>
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Dmitriy Korobskiy <dk...@gmail.com>.
Hi, all
I have a slightly different issue - IvyDE is downloading sources, but
Javadocs do not work for the life of me.
I had that issue a year and a half ago with IvyDE 1.2, and it seems now
as a resurgence of closed IvyDE-55:
https://issues.apache.org/jira/browse/IVYDE-55.
I'm using Eclipse 3.4.1 platform (IBM RAD 7.5.1 distribution) and IvyDE
2.0.0.beta1. The difference with your, Gael, configuration from what I
understood could be that I declare all artifacts explicitly in ivy.xml.
Here are the steps.
1. ivy.xml
<?xml version="1.0"?>
<?xml version="1.0"?>
<ivy-module version="2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
<info organisation="xxx" module="mmm" status="integration" />
<configurations>
<conf name="compile" />
<conf name="war" /> <!-- Artifacts to be included in a WAR -->
<conf name="ide" extends="compile" description="+ Javadocs and
sources" />
</configurations>
<dependencies defaultconf="compile,war->default;ide->ide(default)">
<dependency org="apache" name="commons-logging" rev="1.1"/>
</dependencies>
</ivy-module>
2. Repository files:
{repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1-doc.zip
{repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1-src.zip
{repository}\apache\commons-logging\commons-logging-1.1\commons-logging-1.1.jar
3. commons-logging-1.1-ivy.xml
<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl"
href="http://ivyrep.jayasoft.org/ivy-doc.xsl"?>
<ivy-module version="2.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd">
<info organisation="apache" module="commons-logging" revision="1.1"
status="release"/>
<configurations>
<conf name="default"/>
<conf name="ide" extends="default" description="JavaDoc and sources"/>
</configurations>
<publications>
<artifact name="commons-logging-1.1" type="jar" conf="default"/>
<artifact name="commons-logging-1.1-src" type="source" ext="zip"
conf="ide"/>
<artifact name="commons-logging-1.1-doc" type="javadoc" ext="zip"
conf="ide"/>
</publications>
</ivy-module>
I get commons-logging-1.1.jar with an attached source, but not Javadocs.
Marziou, Gael wrote:
>
>
>> I think you are hitting this issue:
>> https://issues.apache.org/jira/browse/IVYDE-146
>>
>
> Merci Nicolas, the description matches indeed.
>
> But in this case I don't understand why I still have the issue with trunk build #20 IvyDE-updatesite on Hudson server, this fix is supposed to be included.
>
> Gael
>
>
>
--
DK
AIM: DKroot1, Skype: DKroot
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
> I think you are hitting this issue:
> https://issues.apache.org/jira/browse/IVYDE-146
Merci Nicolas, the description matches indeed.
But in this case I don't understand why I still have the issue with trunk build #20 IvyDE-updatesite on Hudson server, this fix is supposed to be included.
Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Nicolas Lalevée <ni...@hibnet.org>.
On lundi 09 février 2009 17:47:04 Marziou, Gael wrote:
> > It looks like I know a little less than you do on this
> > matter, but I'm guessing that this has something to do with
> > the "Sources suffixes:" and "Javadoc suffixes:" entries in
> > the Ivy preferences of Eclipse. My preferences show these as,
> > respectively:
> > -source,-sources,-src
> > -javadoc,-javadocs,-doc,-docs
> >
> > For your Wicket module in your repository, what are the full
> > names of the files that contain source and Javadoc? Could it
> > be that somehow these filenames don't conform to the suffix
> > conventions?
>
> Yes, we use the "standards" which map to our Ivy preferences:
>
> wicket-1.3.5.jar
> wicket-1.3.5-sources.jar
> wicket-1.3.5-javadoc.jar
>
> Don't forget that this is working fine with alpha1, and my team mates are
> still in alpha1.
I think you are hitting this issue:
https://issues.apache.org/jira/browse/IVYDE-146
Nicolas
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
> It looks like I know a little less than you do on this
> matter, but I'm guessing that this has something to do with
> the "Sources suffixes:" and "Javadoc suffixes:" entries in
> the Ivy preferences of Eclipse. My preferences show these as,
> respectively:
> -source,-sources,-src
> -javadoc,-javadocs,-doc,-docs
>
> For your Wicket module in your repository, what are the full
> names of the files that contain source and Javadoc? Could it
> be that somehow these filenames don't conform to the suffix
> conventions?
Yes, we use the "standards" which map to our Ivy preferences:
wicket-1.3.5.jar
wicket-1.3.5-sources.jar
wicket-1.3.5-javadoc.jar
Don't forget that this is working fine with alpha1, and my team mates are still in alpha1.
Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Mitch Gitman <mg...@gmail.com>.
It looks like I know a little less than you do on this matter, but I'm
guessing that this has something to do with the "Sources suffixes:" and
"Javadoc suffixes:" entries in the Ivy preferences of Eclipse. My
preferences show these as, respectively:
-source,-sources,-src
-javadoc,-javadocs,-doc,-docs
For your Wicket module in your repository, what are the full names of the
files that contain source and Javadoc? Could it be that somehow these
filenames don't conform to the suffix conventions?
On Mon, Feb 9, 2009 at 8:18 AM, Marziou, Gael <ga...@hp.com> wrote:
> > I'd be curious how you were able to download the source and
> > Javadoc in the first place. I'm not the best expert on what
> > has changed with IvyDE, but ultimately, the Eclipse IvyDE is
> > just an interface to Ivy, so it's a matter of making sure
> > that, for a given module, you have a configuration that
> > obtains the source and Javadoc.
>
> We manage our own artifact repository.
> In my understanding, downloading the sources and javadocs for a module is a
> feature of IvyDE not Ivy, it does not require any specific configuration, it
> does rely only on classifier extension.
> This was working well in IvyDE alpha1.
>
> > If I may ask, what is the Ivy module or dependency for which
> > you're trying to download the source and Javadoc? And could
> > you show the ivy.xml file for that module? (I'm guessing you
> > may not know this.)
>
> The dependency was on Wicket but I could reproduce the issue with any
> module that was working with alpha1.
> I attached the ivy.xml but frankly I doubt it'll help.
>
> > Also, could you right-click on your Eclipse project? Select Build
> > Path->Configure Build Path. Select the Libraries tab. Click
> > on the entry
> > Path->for
> > your project's ivy.xml file and click Edit. What are the
> > names of the configurations you have checked? Or are any
> > checked? It is these configurations that are going to need a
> > path to get to the configurations for your dependencies that
> > expose their source or Javadoc.
>
> It depends of the project I'm looking at, some of them are using [*], some
> of them are using [eclipse] configuration that we have defined.
>
>
> Gael
>
RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by "Marziou, Gael" <ga...@hp.com>.
> I'd be curious how you were able to download the source and
> Javadoc in the first place. I'm not the best expert on what
> has changed with IvyDE, but ultimately, the Eclipse IvyDE is
> just an interface to Ivy, so it's a matter of making sure
> that, for a given module, you have a configuration that
> obtains the source and Javadoc.
We manage our own artifact repository.
In my understanding, downloading the sources and javadocs for a module is a feature of IvyDE not Ivy, it does not require any specific configuration, it does rely only on classifier extension.
This was working well in IvyDE alpha1.
> If I may ask, what is the Ivy module or dependency for which
> you're trying to download the source and Javadoc? And could
> you show the ivy.xml file for that module? (I'm guessing you
> may not know this.)
The dependency was on Wicket but I could reproduce the issue with any module that was working with alpha1.
I attached the ivy.xml but frankly I doubt it'll help.
> Also, could you right-click on your Eclipse project? Select Build
> Path->Configure Build Path. Select the Libraries tab. Click
> on the entry
> Path->for
> your project's ivy.xml file and click Edit. What are the
> names of the configurations you have checked? Or are any
> checked? It is these configurations that are going to need a
> path to get to the configurations for your dependencies that
> expose their source or Javadoc.
It depends of the project I'm looking at, some of them are using [*], some of them are using [eclipse] configuration that we have defined.
Gael
Re: IvyDE 2.0.0.beta1 does not download sources nor javadocs
Posted by Mitch Gitman <mg...@gmail.com>.
I'd be curious how you were able to download the source and Javadoc in the
first place. I'm not the best expert on what has changed with IvyDE, but
ultimately, the Eclipse IvyDE is just an interface to Ivy, so it's a matter
of making sure that, for a given module, you have a configuration that
obtains the source and Javadoc.
If I may ask, what is the Ivy module or dependency for which you're trying
to download the source and Javadoc? And could you show the ivy.xml file for
that module? (I'm guessing you may not know this.)
Also, could you right-click on your Eclipse project? Select Build
Path->Configure Build Path. Select the Libraries tab. Click on the entry for
your project's ivy.xml file and click Edit. What are the names of the
configurations you have checked? Or are any checked? It is these
configurations that are going to need a path to get to the configurations
for your dependencies that expose their source or Javadoc.
On Mon, Feb 9, 2009 at 7:16 AM, Marziou, Gael <ga...@hp.com> wrote:
> Hello,
>
> I am running Eclipse 3.4.1, I was using IvyDE 2.0.0.alpha1 which was
> working fine downloading jar files, sources and javadocs but since I have
> updated IvyDE 2.0.0.beta1 I get only the jars and not the sources nor
> javadocs.
>
> I also tried with trunk build and it has same issue.
>
> Is it a known issue or should I log it to JIRA?
>
> Thanks,
>
> Gael