declare source and javadoc artifacts in maven2 modules

• Key: IVY-325
• Type: Improvement
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Xavier Hanin
• Reporter: Xavier Hanin
• Component/s: Maven Compatibility
• Affects Version/s: 1.4
• Fix Version/s: 2.0-RC1

Description

Maven2 modules created when Ivy parses poms do not declare any source or javadoc artifact, while they sometimes offer one on ibiblio. Declaring such artifact could ease the integration of maven2 modules with source and javadoc attachments.

Comments

[Howard M. Lewis Ship]

I think this falls under a general heading of "lets make it easier to download sources along with jars." Half the point of working in open source is so that I can have access to the source code. I don't miss the days of stepping through Weblogic code ...

[Xavier Hanin]

I've just implemented this, now m2 modules expose both a "sources" and "javadoc" configuration, containing the corresponding artifact if it exists.

I agree that this is not enough to work with sources and javadocs easily. Indeed, you can easily get sources and/or javadoc of one dependency, but it doesn't work transitively. To get sources and/or javadoc only of artifacts requested by the configurations actually needed, some kind of flag would be better.

Thanks for this.
Support for fetching sources also transitively would be really good.
We would not like to add all dependencies for projects in top level just because we need also their sources.

[Brian Matzon]

This now breaks a lot of applications that do not have [type] in the artifact pattern as source and javadoc jars (with the same name) is being downloaded, resulting in an error since they try to overwrite each other.

should install have an exclude section to avoid getting these?

[Xavier Hanin]

Maybe we should have a flag to disable this feature for better backward compatibility. Could you open a JIRA?

[Brian Matzon]

I have created a new issue: IVY-1021
Hope to have this solved quickly!