Issue Details (XML | Word | Printable)

Key: IVY-936
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Maarten Coene
Reporter: Simon Brunning
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Ivy

Can't use latest.release for pom dependencies

Created: 06/Oct/08 04:31 PM   Updated: 21/Oct/08 10:02 PM
Return to search
Component/s: Maven Compatibility
Affects Version/s: 2.0-RC1
Fix Version/s: 2.0-RC2

Time Tracking:
Not Specified

File Attachments:
  Size
Zip Archive Licensed for inclusion in ASF works spring-webmvc-example-resolution-from-ivy-cache.zip 2008-10-08 02:10 PM Simon Brunning 352 kB
Issue Links:
Cloners
 
Duplicate
 

Resolution Date: 21/Oct/08 09:59 PM


 Description  « Hide
When using the ibibio resolver, the generated ivy.xml doesn't include source and javadoc artifacts declaration.
AFAIU the Maven doc, the pom.xml doesn't declare them. They declare themself by being available or not.

IvyDE does this check itself, so it works fine in Eclipse. So some code should be ported from IvyDE to Ivy. Then we will be able to get the source also with an ant task.



 All   Comments   Work Log   Change History   Subversion Commits      Sort Order: Ascending order - Click to sort in descending order
Simon Brunning added a comment - 06/Oct/08 04:32 PM
Doesn't appear to have been fixed as of 2.0 rc-1.

Maarten Coene added a comment - 06/Oct/08 08:56 PM
I've updated the title to the real problem...

The problem occurred with the following dependency:
<dependency org="org.apache.ws.commons.schema" name="XmlSchema" rev="latest.release" conf="api->runtime" />


Maarten Coene added a comment - 06/Oct/08 08:56 PM
workaround: use "latest.integration"

Maarten Coene added a comment - 06/Oct/08 09:14 PM
I've fixed your problem in SVN trunk.
Could you give it a try with trunk version of latest snapshot from http://teamcity.jetbrains.com/viewLog.html?&buildTypeId=bt125&buildId=lastSuccessful ?

Simon Brunning added a comment - 08/Oct/08 12:08 PM
Sorry - doesn't appear to have fixed the problem I'm having. I'm still not getting source and javadoc jars downloaded. I'll try and monkey up a bare bones example of the problem.

Simon Brunning added a comment - 08/Oct/08 02:10 PM
Example - src and javadoc not downloaded.

Simon Brunning added a comment - 08/Oct/08 02:13 PM
As an example we are resolving spring-webmvc ver 2.5.5 from http://repo1.maven.org/maven2/

i.e. http://repo1.maven.org/maven2/org/springframework/spring-webmvc/2.5.5

As you can see there is a sources.jar at this location which is not being brought down using the trunk version specified in the last comment. The attachment is a copy of the files from the Ivy Cache after a clean resolve.


Maarten Coene added a comment - 08/Oct/08 07:22 PM
I cannot reproduce your problem.
If I add following dependency:
<dependency org="org.springframework" name="spring-webmvc" rev="latest.release" conf="default" />

I end up with a source declaration in the ivy-file in the cache:

	<publications>
		<artifact name="spring-webmvc" type="jar" ext="jar" conf="master"/>
		<artifact name="spring-webmvc" type="source" ext="jar" conf="sources" m:classifier="sources"/>
	</publications>

Could you post your settings.xml and build.xml file?


Maarten Coene added a comment - 14/Oct/08 07:33 PM
Simon,

do you have more info?

Maarten


Maarten Coene added a comment - 21/Oct/08 09:59 PM
No further news from Simon, so I'll mark this as fixed because it works for me.

This problem may occur for instance if the the default ibiblio patterns are overwritten and the classifier token isn't specified.
But without seeing the settings.xml file it is hard to see what's going wrong.