ant-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Matzon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (IVY-1141) dependencies failed using branch attribute (and extra attrubutes)
Date Fri, 11 Jun 2010 10:15:13 GMT

    [ https://issues.apache.org/jira/browse/IVY-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12877766#action_12877766
] 

Brian Matzon commented on IVY-1141:
-----------------------------------

Similar problem, and workaround didn't work.

Usually our projects have been relying on 'trunk' as default and then each project would sit
the branch as needed when publishing. This would be stored in this layout: [organisation]/[module]/[branch]/[artifact]-[revision].[ext]

During a branch process, I instead changed the 'ivy.default.branch' to our branch name and
then changed the 'trunk' dependencies to trunk.
Dependencies on trunk then failed with the 'bad branch name: expected='trunk' found='xxx-1.0-dev''

I then created a new artifact which had branch="trunk" and then everything works as expected.

So, a fix to this could be to re-publish all modules, making sure that they contain the branch
attribute. Not sure how you would do that on maven tho ;)

It looks to me as if ivy is using 'ivy.default.branch' if it doesn't locate the branch name
in the ivy file, despite the fact that it locates the ivy file based on the branch='trunk'
I specify in my dependency.

I dont know if turning of checkConsistency will work - nor do I think its a good idea to do
so.

> dependencies failed using branch attribute (and extra attrubutes)
> -----------------------------------------------------------------
>
>                 Key: IVY-1141
>                 URL: https://issues.apache.org/jira/browse/IVY-1141
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0
>         Environment: windows 
>            Reporter: Daniel Schwager
>
> *** Investigation
> i tried to use the branch attribute inside my projekt DEV like this:
> 	<ivy-module version="1.1">
> 		<info ... module="DEV" ....
> 		<dependency org="testng" name="testng" 
> 			branch="mybranch1" rev="latest.integration"  
> 			conf="compile,tests->default"/>
> 		.....
> If I now try to resolve my dependencies, it failed
> because ivy 2.1.0 try to resolve the latest version (5.6) of testng/testng
> which has NO branch-keyword inside it's ivy.xml. The ivy.xml
> of version testng/testng/4.6 contains the following:
> <ivy-module version="1.1">
>     <info
>         organisation="testng" module="testng"
>         branch="mybranch1"  revision="4.6.1.2"
>         status="release"         
>         publication="20060227000000">
>       .....
> It looks like the resolver skip this 4.6.1.2 version (which is the only one containing
the 
> branch attribute "mybranch1") and try to download the 5.6 (containing NO branch attribute
!). 
> I go the following error message:
> [ivy:configure] :: Ivy 2.1.0 - 20090925235825 :: http://ant.apache.org/ivy/ ::
> ...
> 	---------------------------------------------------------------------
> [ivy:resolve] :: problems summary ::
> [ivy:resolve] :::: WARNINGS
> [ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] 		::          UNRESOLVED DEPENDENCIES         ::
> [ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] 		:: testng#testng#mybranch1;latest.integration: several problems occured
while resolving dependency: testng#testng#mybranch1;latest.integration {compile=[default],
tests=[default]}:
> [ivy:resolve] 	java.text.ParseException: inconsistent module descriptor file found in
'I:\testng\testng\5.6\ivy.xml': bad branch name: expected='mybranch1' found='null'; 
> [ivy:resolve] 	java.text.ParseException: inconsistent module descriptor file found in
'http://ivyrepos.dtnet.de/testng/testng/5.6/ivy.xml': bad branch name: expected='mybranch1'
found='null'; 
> [ivy:resolve] 		::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve] 
> [ivy:resolve] :::: ERRORS
> [ivy:resolve] 		shared-filesystem: bad branch name found in I:\testng\testng\5.6\ivy.xml:
expected='mybranch1 found='null'
> [ivy:resolve] 		shared-web: bad branch name found in http://ivyrepos.dtnet.de/testng/testng/5.6/ivy.xml:
expected='mybranch1 found='null'
> [ivy:resolve] 
> [ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
> *** Make it reproducable
> I create a VERY small sample project (build.xml & ivy.xml)
> using a sample ivyrepos on our server.
> Could somebody look closer to the problem by downloading the project from
>     http://www.opensource-online.org/fileadmin/swd/ivy/ivy-test.zip
> To run, yust unzip and start "ant -f build.xml" and you can see the failure:
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]           ::          UNRESOLVED DEPENDENCIES         ::
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]           :: testng#testng#mybranch1;latest.integration: java.text.ParseException:
inconsistent module descriptor file found in 'http:/
> www.opensource-online.org/fileadmin/swd/ivy/testng/testng/5.6/ivy.xml': bad branch name:
expected='mybranch1' found='';
> [ivy:resolve]           ::::::::::::::::::::::::::::::::::::::::::::::
> [ivy:resolve]
> [ivy:resolve] :::: ERRORS
> [ivy:resolve]           default: bad branch name found in http://www.opensource-online.org/fileadmin/swd/ivy/testng/testng/5.6/ivy.xml:
expected='myb
> anch1 found=''
> [ivy:resolve]
> [ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
> *** Same problem using extra attributes instead auf branch attribute
> if tried a workaround not using the branch-keyword but defining a own extra atrribute
like this:
> <ivy-module version="2.0" xmlns:swd="http://softwaredemo.de/ivy/extra">
>  ...
> 		<dependency org="testng" name="testng"  swd:suite="mybranch-e2" rev="latest.integration"
 
> 					conf="compile,tests->default"/>
> But this tells me a similar result - also a failure.
> regards
> Danny
> P.S.: refer also to http://old.nabble.com/dependencies-failed-using-branch-attribute-td26411302.html

-- 
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