You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Trevor L. Torrez (JIRA)" <ji...@codehaus.org> on 2009/06/30 18:18:05 UTC
[jira] Created: (MEV-626) Missing POM for Apache "neethi"
Missing POM for Apache "neethi"
-------------------------------
Key: MEV-626
URL: http://jira.codehaus.org/browse/MEV-626
Project: Maven Evangelism
Issue Type: Bug
Components: Invalid POM
Reporter: Trevor L. Torrez
Seems this was opened (and rejected) under the maven-upload project (MAVENUPLOAD-1823). The lack of a POM was, however, causing our build to fail in certain situations; I'm not sure what situations, but it has something to do with it being either a transitive dependency or a direct dependency.
This also affects version 2.0.1; curiously 2.0.3 and 2.0.4 don't have a {{maven-metadata.xml}} file, but I don't know if that would also cause problems.
--
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] Closed: (MEV-626) Missing POM for Apache "neethi"
Posted by "Juven Xu (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MEV-626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Juven Xu closed MEV-626.
------------------------
Resolution: Won't Fix
Assignee: Juven Xu
this requires a fix on apache repo, then sync to central
see https://issues.sonatype.org/browse/MVNCENTRAL-2
> Missing POM for Apache "neethi"
> -------------------------------
>
> Key: MEV-626
> URL: http://jira.codehaus.org/browse/MEV-626
> Project: Maven Evangelism
> Issue Type: Bug
> Components: Invalid POM
> Reporter: Trevor L. Torrez
> Assignee: Juven Xu
>
> Seems this was opened (and rejected) under the maven-upload project (MAVENUPLOAD-1823). The lack of a POM was, however, causing our build to fail in certain situations; I'm not sure what situations, but it has something to do with it being either a transitive dependency or a direct dependency.
> This also affects version 2.0.1; curiously 2.0.3 and 2.0.4 don't have a {{maven-metadata.xml}} file, but I don't know if that would also cause problems.
--
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