[jira] Updated: (MRELEASE-334) Can't release project due to non released dependencies
[ http://jira.codehaus.org/browse/MRELEASE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kamen Petroff updated MRELEASE-334: --- Attachment: maven-release-manager.patch Sorry, this is the working patch! > Can't release project due to non released dependencies > -- > > Key: MRELEASE-334 > URL: http://jira.codehaus.org/browse/MRELEASE-334 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-7 >Reporter: Kamen Petroff > Attachments: maven-release-manager.patch, maven-release-manager.patch > > > I guess the problem is already known. But once again > in maven-release-manager 1.0-alpha-4 > org/apache/maven/shared/release/phase/CheckDependencySnapshotsPhase.java -- 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] Created: (MRELEASE-334) Can't release project due to non released dependencies
Can't release project due to non released dependencies -- Key: MRELEASE-334 URL: http://jira.codehaus.org/browse/MRELEASE-334 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-7 Reporter: Kamen Petroff Attachments: maven-release-manager.patch I guess the problem is already known. But once again in maven-release-manager 1.0-alpha-4 org/apache/maven/shared/release/phase/CheckDependencySnapshotsPhase.java -- 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] Created: (MNG-2803) Inheritance of plugin properties
Inheritance of plugin properties Key: MNG-2803 URL: http://jira.codehaus.org/browse/MNG-2803 Project: Maven 2 Issue Type: Improvement Components: Plugin API Reporter: Kamen Petroff It would be beneficial, if some plugin configuration properties (of list, map or array type, not simple types) could be extended from the parent POM by inheritance. Currently the value specified in the child configuration overwrites the value specified by the parent POM. This is OK for simple properties. For collection properties however, it would be nice, if the collection specified by the parent is extended with the entries specified by the child configuration. As an illustration imagine a parent POM defining a plugin configuration: -- com.company.package1 com.company.package2 -- It would be nice if a child POM could *add* to the from the parent another like this: -- com.company.package3 -- This is however not possible, as the property in the child configuration overwrites the one specified in the parent's configuration. This forces the child POM to specify all three entries in its plugin configuration. It should be somehow possible to specify on a per property basis, if the parent's collection property is to be extended or overwritten. I tried to implement this "collection property inheritance" in my plugin, by iterating down the parent MavenProjects and accessing their Xpp3Dom configuration directly. This works fine. However when the LifeCycle is forked (by the clover plugin for example), project.getParent() returns null. Does someone have an idea how to access the Parent's POM plugin configuration? -- 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
