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.lale...@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-u...@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
