You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@ant.apache.org by "Andrew (JIRA)" <ji...@apache.org> on 2010/04/21 04:01:49 UTC

[jira] Created: (IVY-1186) Rules not properly applied to parent projects

Rules not properly applied to parent projects
---------------------------------------------

                 Key: IVY-1186
                 URL: https://issues.apache.org/jira/browse/IVY-1186
             Project: Ivy
          Issue Type: Bug
          Components: Core
    Affects Versions: 2.1.0
            Reporter: Andrew


It seems that rules are not properly applied to parent projects when rules are applied to them. If the parent project is explicitly installed first, then there are no problems, but if they are not then something breaks.

e.g. I have to do the following:
{noformat}
<ivy:install organisation="org.apache.ws" module="xmlrpc" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
{noformat}
Before
{noformat}
<ivy:install organisation="org.apache.ws" module="xmlrpc-common" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
{noformat}

Otherwise it fails with an error similar to
{noformat}
public: bad organisation found in
http://repo1.maven.org/maven2/org/apache/xmlrpc/xmlrpc/3.0/xmlrpc-3.0.pom:
expected='org.apache.xmlrpc found='org.apache.ws'
{noformat}

Given that I have the following rule:
{noformat}
<rule>
	<fromsystem>
		<src org="(org\.apache).ws" module="xmlrpc.*" />
		<dest org="$o1.xmlrpc" module="$m0" />
	</fromsystem>
	<tosystem>
		<src org="(org\.apache)\.xmlrpc" module="xmlrpc.*" />
		<dest org="$o1.ws" module="$m0" />
	</tosystem>
</rule>
{noformat}

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


[jira] Resolved: (IVY-1186) Rules not properly applied to parent projects

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene resolved IVY-1186.
--------------------------------

    Resolution: Fixed

I've committed a fix in SVN trunk that should fix the problem.
Could you give it a try to see if it works for  your setup?

thanks,
Maarten

> Rules not properly applied to parent projects
> ---------------------------------------------
>
>                 Key: IVY-1186
>                 URL: https://issues.apache.org/jira/browse/IVY-1186
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0
>            Reporter: Andrew
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> It seems that rules are not properly applied to parent projects when rules are applied to them. If the parent project is explicitly installed first, then there are no problems, but if they are not then something breaks.
> e.g. I have to do the following:
> {noformat}
> <ivy:install organisation="org.apache.ws" module="xmlrpc" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
> {noformat}
> Before
> {noformat}
> <ivy:install organisation="org.apache.ws" module="xmlrpc-common" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
> {noformat}
> Otherwise it fails with an error similar to
> {noformat}
> public: bad organisation found in
> http://repo1.maven.org/maven2/org/apache/xmlrpc/xmlrpc/3.0/xmlrpc-3.0.pom:
> expected='org.apache.xmlrpc found='org.apache.ws'
> {noformat}
> Given that I have the following rule:
> {noformat}
> <rule>
> 	<fromsystem>
> 		<src org="(org\.apache).ws" module="xmlrpc.*" />
> 		<dest org="$o1.xmlrpc" module="$m0" />
> 	</fromsystem>
> 	<tosystem>
> 		<src org="(org\.apache)\.xmlrpc" module="xmlrpc.*" />
> 		<dest org="$o1.ws" module="$m0" />
> 	</tosystem>
> </rule>
> {noformat}

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


[jira] Assigned: (IVY-1186) Rules not properly applied to parent projects

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene reassigned IVY-1186:
----------------------------------

    Assignee: Maarten Coene

> Rules not properly applied to parent projects
> ---------------------------------------------
>
>                 Key: IVY-1186
>                 URL: https://issues.apache.org/jira/browse/IVY-1186
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0
>            Reporter: Andrew
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> It seems that rules are not properly applied to parent projects when rules are applied to them. If the parent project is explicitly installed first, then there are no problems, but if they are not then something breaks.
> e.g. I have to do the following:
> {noformat}
> <ivy:install organisation="org.apache.ws" module="xmlrpc" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
> {noformat}
> Before
> {noformat}
> <ivy:install organisation="org.apache.ws" module="xmlrpc-common" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
> {noformat}
> Otherwise it fails with an error similar to
> {noformat}
> public: bad organisation found in
> http://repo1.maven.org/maven2/org/apache/xmlrpc/xmlrpc/3.0/xmlrpc-3.0.pom:
> expected='org.apache.xmlrpc found='org.apache.ws'
> {noformat}
> Given that I have the following rule:
> {noformat}
> <rule>
> 	<fromsystem>
> 		<src org="(org\.apache).ws" module="xmlrpc.*" />
> 		<dest org="$o1.xmlrpc" module="$m0" />
> 	</fromsystem>
> 	<tosystem>
> 		<src org="(org\.apache)\.xmlrpc" module="xmlrpc.*" />
> 		<dest org="$o1.ws" module="$m0" />
> 	</tosystem>
> </rule>
> {noformat}

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


[jira] Updated: (IVY-1186) Rules not properly applied to parent projects

Posted by "Maarten Coene (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maarten Coene updated IVY-1186:
-------------------------------

    Fix Version/s: 2.2.0-RC1

> Rules not properly applied to parent projects
> ---------------------------------------------
>
>                 Key: IVY-1186
>                 URL: https://issues.apache.org/jira/browse/IVY-1186
>             Project: Ivy
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.0
>            Reporter: Andrew
>            Assignee: Maarten Coene
>             Fix For: 2.2.0-RC1
>
>
> It seems that rules are not properly applied to parent projects when rules are applied to them. If the parent project is explicitly installed first, then there are no problems, but if they are not then something breaks.
> e.g. I have to do the following:
> {noformat}
> <ivy:install organisation="org.apache.ws" module="xmlrpc" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
> {noformat}
> Before
> {noformat}
> <ivy:install organisation="org.apache.ws" module="xmlrpc-common" revision="3.0"  from="installerChain" to="local" transitive="true" overwrite="true" />
> {noformat}
> Otherwise it fails with an error similar to
> {noformat}
> public: bad organisation found in
> http://repo1.maven.org/maven2/org/apache/xmlrpc/xmlrpc/3.0/xmlrpc-3.0.pom:
> expected='org.apache.xmlrpc found='org.apache.ws'
> {noformat}
> Given that I have the following rule:
> {noformat}
> <rule>
> 	<fromsystem>
> 		<src org="(org\.apache).ws" module="xmlrpc.*" />
> 		<dest org="$o1.xmlrpc" module="$m0" />
> 	</fromsystem>
> 	<tosystem>
> 		<src org="(org\.apache)\.xmlrpc" module="xmlrpc.*" />
> 		<dest org="$o1.ws" module="$m0" />
> 	</tosystem>
> </rule>
> {noformat}

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