ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "martin graham (JIRA)" <j...@apache.org>
Subject [jira] Updated: (IVY-1202) install: wrong [type] declared in generated ivy file when multiple dependencies on same module in POM?
Date Fri, 02 Jul 2010 00:13:49 GMT

     [ https://issues.apache.org/jira/browse/IVY-1202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

martin graham updated IVY-1202:
-------------------------------

        Summary: install: wrong [type] declared in generated ivy file when multiple dependencies
on same module in POM?  (was: install: source artifact in dependency overrides other dependencies
on same module, wrong [type] declared?)
    Description: 
I'm installing a project  (http://repo2.maven.org/maven2/com/hp/hpl/jena/jena/2.6.3/) to a
local repository. One of the dependencies in the generated jena ivy file (on the iri 0.8 version
project) declares an artifact of that project's source files as so --> 

<dependency org="com.hp.hpl.jena" name="iri" rev="0.8" force="true" conf="compile-compile(*),master(*);runtime->runtime(*)">

<artifact name="iri" type="jar" ext="jar" conf="" m:classifier="sources" /> 
</dependency> 
This is in addition to a 'normal' dependency for the iri project which should scoop up the
iri-0.8.jar file with the compiled classes in 

The original jena .pom file has two entries for iri-0.8, one for the class files in a jar
and one for the sources, which declares a 'sources' classifier which is carried through faithfully
to the ivy file. However, I would have thought ivy would have generated a [type] other than
'jar' for the sources (even though the sources file comes in a jar, I guess that is covered
by 'ext="jar"'), as this is the type for the classes jar as well. The documentation would
seem to indicate type should be 'source'..

Thus, when jena's ivy file is processed by a bog-standard 'install' it copies only the iri-0.8-sources.jar
(rather than the iri-0.8.jar and javadocs i want as well). I end up having to run a separate
install on this project to grab all the artifacts in it. 

  was:
I'm installing a project  (http://repo2.maven.org/maven2/com/hp/hpl/jena/jena/2.6.3/) to a
local repository. One of the dependencies in the generated jena ivy file (on the iri 0.8 version
project) declares an artifact of that project's source files as so --> 

<dependency org="com.hp.hpl.jena" name="iri" rev="0.8" force="true" conf="compile-compile(*),master(*);runtime->runtime(*)">

<artifact name="iri" type="jar" ext="jar" conf="" m:classifier="sources" /> 
</dependency> 
This is in addition to a 'normal' dependency for the iri project which should scoop up the
iri-0.8.jar file with the compiled classes in 

When jena's ivy file is processed by a bog-standard 'install' it copies only the iri-0.8-sources.jar
(rather than the iri-0.8.jar and javadocs i want as well). I end up having to run a separate
install on this project to grab all the artifacts in it. 

The original jena .pom file has two entries for iri-0.8, one for the class files in a jar
and one for the sources, which declares a 'sources' classifier which is carried through faithfully
to the ivy file. However, I would have thought ivy would have generated a type other than
'jar' for the sources (even though the sources file comes in a jar, I guess that is covered
by 'ext="jar"'), as this is the type for the classes jar as well. The documentation would
seem to indicate type should be 'source'.. this seems to be my stumbling block, it thinks
it's getting me the jar file with the compiled classes in it when it's in fact the sources.

ivy version is 2.1.0, running through ant 1.8.0 


just clarifying, read poorly

> install: wrong [type] declared in generated ivy file when multiple dependencies on same
module in POM?
> ------------------------------------------------------------------------------------------------------
>
>                 Key: IVY-1202
>                 URL: https://issues.apache.org/jira/browse/IVY-1202
>             Project: Ivy
>          Issue Type: Bug
>          Components: Maven Compatibility
>    Affects Versions: 2.1.0
>         Environment: Ant 1.8.0 & ivy 2.1.0
>            Reporter: martin graham
>            Priority: Minor
>
> I'm installing a project  (http://repo2.maven.org/maven2/com/hp/hpl/jena/jena/2.6.3/)
to a local repository. One of the dependencies in the generated jena ivy file (on the iri
0.8 version project) declares an artifact of that project's source files as so --> 
> <dependency org="com.hp.hpl.jena" name="iri" rev="0.8" force="true" conf="compile-compile(*),master(*);runtime->runtime(*)">

> <artifact name="iri" type="jar" ext="jar" conf="" m:classifier="sources" /> 
> </dependency> 
> This is in addition to a 'normal' dependency for the iri project which should scoop up
the iri-0.8.jar file with the compiled classes in 
> The original jena .pom file has two entries for iri-0.8, one for the class files in a
jar and one for the sources, which declares a 'sources' classifier which is carried through
faithfully to the ivy file. However, I would have thought ivy would have generated a [type]
other than 'jar' for the sources (even though the sources file comes in a jar, I guess that
is covered by 'ext="jar"'), as this is the type for the classes jar as well. The documentation
would seem to indicate type should be 'source'..
> Thus, when jena's ivy file is processed by a bog-standard 'install' it copies only the
iri-0.8-sources.jar (rather than the iri-0.8.jar and javadocs i want as well). I end up having
to run a separate install on this project to grab all the artifacts in it. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message