[jira] Created: (MEV-38) POM for commons-jelly-tags-ant has incorrect artifact & references bogus dependency

Bug Components: Invalid POM Reporter: J. Matthew Pryor http://www.ibiblio.org/maven2/commons-jelly/commons-jelly-tags-ant/1.0/commons-jelly-tags-ant-1.0.pom has an incorrect artifact ID and also maskes reference to a SNAPSHOT version of commons-jelly which has no POM 4.0.0 commons-jelly-

[jira] Commented: (MNG-576) Support of EAR lifecycle

[ http://jira.codehaus.org/browse/MNG-576?page=comments#action_42739 ] J. Matthew Pryor commented on MNG-576: -- I am pretty sure this is the same basic problem that has frustrated my attempts to write an M2 plugin to support Eclipse PDE artifacts. The

[jira] Commented: (MNG-359) support project inheritence with flat project layout

[ http://jira.codehaus.org/browse/MNG-359?page=comments#action_39744 ] J. Matthew Pryor commented on MNG-359: -- The requirement is really simple. Eclipse does not allow projects to contain other projects and I like having my master project POM

RE: Maven Artifact/Deploy plugin 1.3 Released

I seems to have mucked something up, I get the following: C:\proj>maven plugin:download -DgroupId=maven -DartifactId=maven-artifact-plugin -Dversion=1.3 __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3 Plugin cache wil