[ http://jira.codehaus.org/browse/MEV-400?page=all ]
Carlos Sanchez moved MAVENUPLOAD-912 to MEV-399:
------------------------------------------------
Bundle URL: (was:
/www/www.apache.org/dist/java-repository/tapestry/poms)
Project URL: (was: http://jakarta.apache.org/tapestry)
Contributor URL: (was: http://jakarta.apache.org/tapestry/dev.html)
Workflow: jira (was: Maven New)
Issue Type: Bug (was: Task)
Key: MEV-399 (was: MAVENUPLOAD-912)
Project: Maven Evangelism (was: maven-upload-requests)
> 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
>
>
> 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
