maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian Topping (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MEAR-45) Building Apache-hosted plugins with empty repo fails
Date Mon, 16 Oct 2006 18:36:52 GMT
    [ http://jira.codehaus.org/browse/MEAR-45?page=comments#action_77775 ] 
            
Brian Topping commented on MEAR-45:
-----------------------------------

The other option would be to add the following to every POM (since the parent is unresolvable,
it can't be put in the parent just once...)

{code:xml}
  <pluginRepositories>
      <pluginRepository>
          <id>apache</id>
          <name>Apache Snapshot Repo</name>
          <url>http://people.apache.org/maven-snapshot-repository/</url>
          <snapshots>
              <enabled>true</enabled>
          </snapshots>
      </pluginRepository>
  </pluginRepositories>
{code}

> Building Apache-hosted plugins with empty repo fails
> ----------------------------------------------------
>
>                 Key: MEAR-45
>                 URL: http://jira.codehaus.org/browse/MEAR-45
>             Project: Maven 2.x Ear Plugin
>          Issue Type: Bug
>            Reporter: Brian Topping
>   Original Estimate: 20 minutes
>  Remaining Estimate: 20 minutes
>
> Many of the Apache-hosted plugins depend on POM versions that don't exist in HEAD and
were never deployed.  For instance, maven-ear-plugin depends on parent POM version 2-SNAPSHOT.
 It wouldn't be an issue except that deploying these compiled plugins then requires deploying
the parent POM, which doesn't really exist any more.  
> Presumably this is happening because developers haven't cleared their repo and built
in a while.  :-)

-- 
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

        

Mime
View raw message