You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Hafga (JIRA)" <ji...@codehaus.org> on 2009/10/13 10:44:26 UTC
[jira] Created: (MRELEASE-491) Releasing publich nodes with
mergeID, but this node only for internal use and not valid with XSD
Releasing publich nodes with mergeID, but this node only for internal use and not valid with XSD
------------------------------------------------------------------------------------------------
Key: MRELEASE-491
URL: http://jira.codehaus.org/browse/MRELEASE-491
Project: Maven 2.x Release Plugin
Issue Type: Bug
Affects Versions: 2.0-beta-9
Reporter: Hafga
Attachments: poms.zip
If you release a POM this plugin will add mergeId node. This node only allowed for internal use. But this version of POM will publish to repository: http://maven.apache.org/ref/2.1.0/maven-model/maven.html
<resources>
<resource>
<mergeId>resource-0</mergeId>
<directory>src/main/resources</directory>
</resource>
</resources>
<testResources>
<testResource>
<mergeId>resource-1</mergeId>
<directory>src/test/resources</directory>
</testResource>
</testResources>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-491) Releasing publich nodes with
mergeID, but this node only for internal use and not valid with XSD
Posted by "Karl M. Davis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201571#action_201571 ]
Karl M. Davis commented on MRELEASE-491:
----------------------------------------
This issue is particularly frustrating as it prevents me from using m2eclipse with any non-SNAPSHOT parent POMs I might have released. m2eclipse will flag the parent POM's mergeId element as invalid and refuse to build the child project.
> Releasing publich nodes with mergeID, but this node only for internal use and not valid with XSD
> ------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-491
> URL: http://jira.codehaus.org/browse/MRELEASE-491
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-9
> Reporter: Hafga
> Attachments: poms.zip
>
>
> If you release a POM this plugin will add mergeId node. This node only allowed for internal use. But this version of POM will publish to repository: http://maven.apache.org/ref/2.1.0/maven-model/maven.html
> <resources>
> <resource>
> <mergeId>resource-0</mergeId>
> <directory>src/main/resources</directory>
> </resource>
> </resources>
> <testResources>
> <testResource>
> <mergeId>resource-1</mergeId>
> <directory>src/test/resources</directory>
> </testResource>
> </testResources>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-491) Releasing publich nodes with
mergeID, but this node only for internal use and not valid with XSD
Posted by "Hafga (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=194521#action_194521 ]
Hafga commented on MRELEASE-491:
--------------------------------
This problem has started with version 2.0-beta-8 and is in 2.0-beta-9, too.
In version 2.0-beta-7 no mergeId will be published
> Releasing publich nodes with mergeID, but this node only for internal use and not valid with XSD
> ------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-491
> URL: http://jira.codehaus.org/browse/MRELEASE-491
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-9
> Reporter: Hafga
> Attachments: poms.zip
>
>
> If you release a POM this plugin will add mergeId node. This node only allowed for internal use. But this version of POM will publish to repository: http://maven.apache.org/ref/2.1.0/maven-model/maven.html
> <resources>
> <resource>
> <mergeId>resource-0</mergeId>
> <directory>src/main/resources</directory>
> </resource>
> </resources>
> <testResources>
> <testResource>
> <mergeId>resource-1</mergeId>
> <directory>src/test/resources</directory>
> </testResource>
> </testResources>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-491) Releasing publich nodes
with mergeID, but this node only for internal use and not valid with XSD
Posted by "Karl M. Davis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201571#action_201571 ]
Karl M. Davis edited comment on MRELEASE-491 at 12/7/09 10:18 AM:
------------------------------------------------------------------
This issue is particularly frustrating as it prevents me from using m2eclipse with any non-SNAPSHOT parent POMs I might have released. m2eclipse will flag the parent POM's mergeId element as invalid and refuse to build the child project.
Also, reverting back to 2.0-beta-7 does not seem to resolve this problem for me (Maven v2.2.1). My guess is that this problem is caused by another library that the release plugin makes use of-- maybe maven-model? I'm not sure, though, if it's safe to "peg" the version of that plugin in my POM.
was (Author: karlmdavis):
This issue is particularly frustrating as it prevents me from using m2eclipse with any non-SNAPSHOT parent POMs I might have released. m2eclipse will flag the parent POM's mergeId element as invalid and refuse to build the child project.
Also, reverting back to 2.0-beta-7 does not seem to resolve this problem for me (Maven v2.2.1). My guess is that this problem is caused by another library that the release plugin makes use of.
> Releasing publich nodes with mergeID, but this node only for internal use and not valid with XSD
> ------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-491
> URL: http://jira.codehaus.org/browse/MRELEASE-491
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-9
> Reporter: Hafga
> Attachments: poms.zip
>
>
> If you release a POM this plugin will add mergeId node. This node only allowed for internal use. But this version of POM will publish to repository: http://maven.apache.org/ref/2.1.0/maven-model/maven.html
> <resources>
> <resource>
> <mergeId>resource-0</mergeId>
> <directory>src/main/resources</directory>
> </resource>
> </resources>
> <testResources>
> <testResource>
> <mergeId>resource-1</mergeId>
> <directory>src/test/resources</directory>
> </testResource>
> </testResources>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MRELEASE-491) Releasing publich nodes
with mergeID, but this node only for internal use and not valid with XSD
Posted by "Karl M. Davis (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=201571#action_201571 ]
Karl M. Davis edited comment on MRELEASE-491 at 12/7/09 10:11 AM:
------------------------------------------------------------------
This issue is particularly frustrating as it prevents me from using m2eclipse with any non-SNAPSHOT parent POMs I might have released. m2eclipse will flag the parent POM's mergeId element as invalid and refuse to build the child project.
Also, reverting back to 2.0-beta-7 does not seem to resolve this problem for me (Maven v2.2.1). My guess is that this problem is caused by another library that the release plugin makes use of.
was (Author: karlmdavis):
This issue is particularly frustrating as it prevents me from using m2eclipse with any non-SNAPSHOT parent POMs I might have released. m2eclipse will flag the parent POM's mergeId element as invalid and refuse to build the child project.
> Releasing publich nodes with mergeID, but this node only for internal use and not valid with XSD
> ------------------------------------------------------------------------------------------------
>
> Key: MRELEASE-491
> URL: http://jira.codehaus.org/browse/MRELEASE-491
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Affects Versions: 2.0-beta-9
> Reporter: Hafga
> Attachments: poms.zip
>
>
> If you release a POM this plugin will add mergeId node. This node only allowed for internal use. But this version of POM will publish to repository: http://maven.apache.org/ref/2.1.0/maven-model/maven.html
> <resources>
> <resource>
> <mergeId>resource-0</mergeId>
> <directory>src/main/resources</directory>
> </resource>
> </resources>
> <testResources>
> <testResource>
> <mergeId>resource-1</mergeId>
> <directory>src/test/resources</directory>
> </testResource>
> </testResources>
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira