Better integration of source/javadoc types

[GoogleCodeExporter]

In companies where developers use both Eclipse and Idea it would be very
nice to have the same kind of integration for source and javadocs as in
"official" IvyDE which uses name suffixes:

If the main jar name is "x-1.0.0.jar" the source jar is named
"x-1.0.0-sources.jar" for example.

Original issue reported on code.google.com by dpredo...@gmail.com on 26 Jan 2009 at 10:02

[GoogleCodeExporter]

Are you talking about recognizing dependencies as being of the 'source' type? 
If so,
IvyIDEA recognizes the following artifact types:
  SOURCE_TYPES = {"source", "src", "sources", "srcs"}
  JAVADOC_TYPES = {"javadoc", "doc", "docs", "apidoc", "apidocs", "documentation",
"documents"};
  CLASSES_TYPES = {"jar", "sar", "war", "ear"}
These are hardcoded for now, and the strings in the array are the type name 
given in
the ivy.xml of module. So IvyIDEA does not use the suffix to identify the 
artifact type.

If this is not what you mean, could you please elaborate?

Original comment by guy.mah...@gmail.com on 27 Jan 2009 at 4:34

[GoogleCodeExporter]

Yes, that's the problem - people using Idea/IvyIdea are not able to share the
repository for source types that's in the form that's typically used by 
Eclipse/IvyDE
(and to be frank, they are the majority, so we are the ones that have to 
adapt). So -
it would be nice to be able to use the IvyDE compatible, suffix based model in
IvyIdea too.

Original comment by dpredo...@gmail.com on 29 Jan 2009 at 10:30

[GoogleCodeExporter]

Original comment by guy.mah...@gmail.com on 21 Feb 2009 at 5:08

• Changed state: Accepted

[GoogleCodeExporter]

Yes, please support this suffix-based method. It has the advantage that there 
is no
need for an entry in the ivy.xml for it. 

sources should be: <artifact-name>-<version>-sources.jar in the sources folder.
javadocs should be: <artifcat-name>-<version>-javadocs.jar in the javadocs 
folder.

Please note that the version is in the middle and not at the end. Thx a lot!

Original comment by andreas....@gmail.com on 17 Mar 2009 at 12:47

[GoogleCodeExporter]

So does IvyIDEA support resolving and downloading the source and javadoc 
dependencies?

I noticed that if I use eclipse first it will download the source and javadoc 
into
the ivy2 cache and works. At that point if I start intellj it will find the
source/javadoc. If I wipe out the cache and then have intellj resolve it will 
not
download the source or javadoc. Is this the missing part in the IvyIDEA or is 
there
some configure missing from the ivy.xml?

Original comment by dandiod...@gmail.com on 23 Feb 2010 at 6:41

[GoogleCodeExporter]

Never mind figured it out. We were publishing our sources with a conf of src 
and our
javadoc with a conf of javadoc. So I changed the dependency reference to have 
the
those it it downloaded them now. Something like:
<dependency org="some org" name="foo" conf="compile->default;src;javadoc"/>

Original comment by dandiod...@gmail.com on 24 Feb 2010 at 12:21