Maven 2.x Release Plugin

Releasing publich nodes with mergeID, but this node only for internal use and not valid with XSD

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 2.0-beta-9
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    1

Description

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>

Issue Links

relates to

Task - A task that needs to be done. MNG-4945 Remove mergeId from public POM

  • Trivial - Cosmetic problem like misspelt words or misaligned text.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Hafga added a comment -

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

Show
Hafga added a comment - 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
Hide
Permalink
Karl M. Davis added a comment - - edited

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.

Show
Karl M. Davis added a comment - - edited 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.

People

  • Assignee:
    Unassigned
    Reporter:
    Hafga
Vote (3)
Watch (4)

Dates

  • Created:
    Updated: