You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "rednix (JIRA)" <ji...@apache.org> on 2009/03/18 13:51:50 UTC
[jira] Created: (IVY-1051) install task copies wrong and not all
retrieved jars to local repository
install task copies wrong and not all retrieved jars to local repository
------------------------------------------------------------------------
Key: IVY-1051
URL: https://issues.apache.org/jira/browse/IVY-1051
Project: Ivy
Issue Type: Bug
Affects Versions: 2.0
Environment: 2.0.0; checked using Eclipse 3.4.2 under Windows XP; Ant 1.7.0; jdk1.5.0_05
Reporter: rednix
I've stumbled upon a strange behaviour:
While trying to install org.apache.struts / struts2-core / 2.1.6 from the remote repository ibiblio to our local repo I noticed that instead of the jar-file with the class files - the one with the javadoc files was copied to the local filesystem. But all artefacts (docs, sources, and jar with classes) were retrieved by the task (and resides afterwards fine in the ivy-cache folder); but only the jar file with the docs was renamed - using the naming-pattern for the jar containing the classes! - and copied to the resulting local folder structure. The generated ivy.xml contains references to all artefacts (docs, sources, jar with classes).
The used install-task:
<ivy:install organisation="org.apache.struts" module="struts2-core" revision="2.1.6"
overwrite="true" from="resolverChain" to="local" transitive="true" />
resolverChain is a chain of resolvers using the ibiblio resolver as the first one in the chain. local refers to a filesystem and points to the current project root in Eclipse.
Contents of the folder "org.apache.struts\struts2-core\2.1.6" after running the install task:
struts2-core-ivy.xml.sha1
struts2-core-ivy.xml.md5
struts2-core-2.1.6.jar.sha1
struts2-core-2.1.6.jar.md5
struts2-core-ivy.xml
struts2-core-2.1.6.jar (this is 4.832 KB in size and contains just the docs - but should be 720 KB containing the class files!)
I'll append a logfile of the install-task run to this issue shortly.
Contents of the ivy cache folder after running the install task:
..\.ivy2\cache\org.apache.struts
\ivy-2.1.6.xml
\ivy-2.1.6.xml.original
\ivydata-2.1.6.properties
\jars\struts2-core-2.1.6.jar (720 KB)
\javadocs\struts2-core-2.1.6-javadoc.jar (4.832 KB)
\sources\struts2-core-2.1.6-sources.jar (758 KB)
Excerpt of the generated ivy-2.1.6.xml:
<publications>
<artifact name="struts2-core" type="jar" ext="jar" conf="master"/>
<artifact name="struts2-core" type="source" ext="jar" conf="sources" m:classifier="sources"/>
<artifact name="struts2-core" type="javadoc" ext="jar" conf="javadoc" m:classifier="javadoc"/>
</publications>
Btw: using the retrieve task - there is no problem - getting the correct jar file with the classes at once.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (IVY-1051) install task copies wrong and not all
retrieved jars to local repository
Posted by "rednix (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/IVY-1051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
rednix updated IVY-1051:
------------------------
Attachment: 2009-03-18_IVY-1051.log
The generated log for the install task run.
> install task copies wrong and not all retrieved jars to local repository
> ------------------------------------------------------------------------
>
> Key: IVY-1051
> URL: https://issues.apache.org/jira/browse/IVY-1051
> Project: Ivy
> Issue Type: Bug
> Affects Versions: 2.0
> Environment: 2.0.0; checked using Eclipse 3.4.2 under Windows XP; Ant 1.7.0; jdk1.5.0_05
> Reporter: rednix
> Attachments: 2009-03-18_IVY-1051.log
>
>
> I've stumbled upon a strange behaviour:
> While trying to install org.apache.struts / struts2-core / 2.1.6 from the remote repository ibiblio to our local repo I noticed that instead of the jar-file with the class files - the one with the javadoc files was copied to the local filesystem. But all artefacts (docs, sources, and jar with classes) were retrieved by the task (and resides afterwards fine in the ivy-cache folder); but only the jar file with the docs was renamed - using the naming-pattern for the jar containing the classes! - and copied to the resulting local folder structure. The generated ivy.xml contains references to all artefacts (docs, sources, jar with classes).
> The used install-task:
> <ivy:install organisation="org.apache.struts" module="struts2-core" revision="2.1.6"
> overwrite="true" from="resolverChain" to="local" transitive="true" />
> resolverChain is a chain of resolvers using the ibiblio resolver as the first one in the chain. local refers to a filesystem and points to the current project root in Eclipse.
> Contents of the folder "org.apache.struts\struts2-core\2.1.6" after running the install task:
> struts2-core-ivy.xml.sha1
> struts2-core-ivy.xml.md5
> struts2-core-2.1.6.jar.sha1
> struts2-core-2.1.6.jar.md5
> struts2-core-ivy.xml
> struts2-core-2.1.6.jar (this is 4.832 KB in size and contains just the docs - but should be 720 KB containing the class files!)
> I'll append a logfile of the install-task run to this issue shortly.
> Contents of the ivy cache folder after running the install task:
> ..\.ivy2\cache\org.apache.struts
> \ivy-2.1.6.xml
> \ivy-2.1.6.xml.original
> \ivydata-2.1.6.properties
> \jars\struts2-core-2.1.6.jar (720 KB)
> \javadocs\struts2-core-2.1.6-javadoc.jar (4.832 KB)
> \sources\struts2-core-2.1.6-sources.jar (758 KB)
> Excerpt of the generated ivy-2.1.6.xml:
> <publications>
> <artifact name="struts2-core" type="jar" ext="jar" conf="master"/>
> <artifact name="struts2-core" type="source" ext="jar" conf="sources" m:classifier="sources"/>
> <artifact name="struts2-core" type="javadoc" ext="jar" conf="javadoc" m:classifier="javadoc"/>
> </publications>
> Btw: using the retrieve task - there is no problem - getting the correct jar file with the classes at once.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.