You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jesse Kuhnert (JIRA)" <ji...@codehaus.org> on 2006/05/19 07:49:41 UTC
[jira] Created: (MAVENUPLOAD-912) tapestry repo sync?(for 4.0.2
release)
tapestry repo sync?(for 4.0.2 release)
--------------------------------------
Key: MAVENUPLOAD-912
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-912
Project: maven-upload-requests
Type: Task
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
[jira] Commented: (MAVENUPLOAD-912) tapestry repo sync?(for 4.0.2
release)
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-912?page=comments#action_66051 ]
Carlos Sanchez commented on MAVENUPLOAD-912:
--------------------------------------------
Will copy tapestry pom, tapestry-annotations, contrib and portlet are wrong
> tapestry repo sync?(for 4.0.2 release)
> --------------------------------------
>
> Key: MAVENUPLOAD-912
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-912
> Project: maven-upload-requests
> Type: Task
> 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
[jira] Commented: (MAVENUPLOAD-912) tapestry repo sync?(for 4.0.2
release)
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-912?page=comments#action_65987 ]
Carlos Sanchez commented on MAVENUPLOAD-912:
--------------------------------------------
There was an outage with the machine that syncs the repos and converts m1->m2, will try to go with a workaround asap
maven-repository is only for m2 builds and deployed with m2, not manually
> tapestry repo sync?(for 4.0.2 release)
> --------------------------------------
>
> Key: MAVENUPLOAD-912
> URL: http://jira.codehaus.org/browse/MAVENUPLOAD-912
> Project: maven-upload-requests
> Type: Task
> 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
[jira] Closed: (MEV-400) tapestry repo sync?(for 4.0.2 release)
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ 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