Well heck! That makes it easy :)
I've updated Ivy RoundUp to (a) support the ivyde:source and ivyde:javadoc
attributes on ivy.xml files and (b) automatically add these attributes when
appropriate.
Try it out and let me know if that helps!
-Archie
2012/2/27 Nicolas Lalevée
Le 26 févr. 2012 à 21:56, Archie Cobbs a écrit :
2012/2/25 Nicolas Lalevée nicolas.lale...@hibnet.org
Le 24 févr. 2012 à 23:03, Archie Cobbs a écrit :
People have complained about this for a long time.
The semantic of the types in an ivy.xml is specified by the one writing
them. So for
2012/2/25 Nicolas Lalevée nicolas.lale...@hibnet.org
Le 24 févr. 2012 à 23:03, Archie Cobbs a écrit :
People have complained about this for a long time.
The semantic of the types in an ivy.xml is specified by the one writing
them. So for each repository there could probably be as many
Le 24 févr. 2012 à 23:03, Archie Cobbs a écrit :
People have complained about this for a long time.
I may be biased but in my opinion this is clearly an IvyDE problem: IvyDE
should be associating sources to JARs using ivy configurations, not
filenames. In fact, ivy does not define
Hi Everybody
For a long while I've been rather frustrated with the the jar of this
class file belongs to ivy.xml message that pops up in eclipse with
certain projects. I searched for other messages on this subject but
found nothing conclusive.
I'm using eclipse indigo and helios, both with
People have complained about this for a long time.
I may be biased but in my opinion this is clearly an IvyDE problem: IvyDE
should be associating sources to JARs using ivy configurations, not
filenames. In fact, ivy does not define filenames, the user of ivy does
(see this
