You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/05/29 08:38:41 UTC

[jira] Closed: (MEV-400) tapestry repo sync?(for 4.0.2 release)

     [ http://jira.codehaus.org/browse/MEV-400?page=all ]
     
Carlos Sanchez closed MEV-400:
------------------------------

     Assign To: Carlos Sanchez
    Resolution: Fixed

> tapestry repo sync?(for 4.0.2 release)
> --------------------------------------
>
>          Key: MEV-400
>          URL: http://jira.codehaus.org/browse/MEV-400
>      Project: Maven Evangelism
>         Type: Bug

>     Reporter: Jesse Kuhnert
>     Assignee: Carlos Sanchez

>
>
> I'm very sorry for what looks like another goof up on my part. Didn't notice the missing poms until ~after~ the jars had been deployed. I tried touching all of the files in the directory to get whatever scripts may be running against them to pick up the missing 4.0.2 poms but no luck. 
> We are going to be moving to maven2 very soon, so hopefully these things will happen less often then. 
> P.S. I noticed a new maven-repository directory with the new maven2 directory structure (ie /www/www.apache.org/maven-repository) , is this the preferred deployment location now?

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