You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Chris Baumgartner (JIRA)" <ji...@codehaus.org> on 2007/02/22 16:31:27 UTC
[jira] Created: (MRELEASE-200) Artifacts are uploaded to wrong
directory
Artifacts are uploaded to wrong directory
-----------------------------------------
Key: MRELEASE-200
URL: http://jira.codehaus.org/browse/MRELEASE-200
Project: Maven 2.x Release Plugin
Issue Type: Bug
Environment: The maven repository is running Red Hat Linux Enterprise Server. The clients are PCs running Windows XP.
Reporter: Chris Baumgartner
Priority: Minor
When doing a release:perform, the artifacts are occassionally uploaded to the wrong directory. We are using scp from the upload. Instead of uploading to the path of "/maven-repository", the files are being uploaded to "~/om/maven-repository". For some reason it is creating a subdirectory called "om" in the user's home directory and uploading the artifacts there. It doesn't happen all the time, but it does seem to be consitently putting them there when it does fail.
I can work around this by manually moving the files, but it is very annoying.
--
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: (MRELEASE-200) Artifacts are uploaded to wrong
directory
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90732 ]
Emmanuel Venisse commented on MRELEASE-200:
-------------------------------------------
seems to be more a deploy plugin pb. Do you have the same issue when you use the deploy plugin.
The release plugin doesn't deploy files directly, it's maven that do it with the deploy plugin
> Artifacts are uploaded to wrong directory
> -----------------------------------------
>
> Key: MRELEASE-200
> URL: http://jira.codehaus.org/browse/MRELEASE-200
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Environment: The maven repository is running Red Hat Linux Enterprise Server. The clients are PCs running Windows XP.
> Reporter: Chris Baumgartner
> Priority: Minor
>
> When doing a release:perform, the artifacts are occassionally uploaded to the wrong directory. We are using scp from the upload. Instead of uploading to the path of "/maven-repository", the files are being uploaded to "~/om/maven-repository". For some reason it is creating a subdirectory called "om" in the user's home directory and uploading the artifacts there. It doesn't happen all the time, but it does seem to be consitently putting them there when it does fail.
> I can work around this by manually moving the files, but it is very annoying.
--
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] Updated: (MRELEASE-200) Artifacts are uploaded to wrong
directory
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-200:
-------------------------------------
Component/s: perform
> Artifacts are uploaded to wrong directory
> -----------------------------------------
>
> Key: MRELEASE-200
> URL: http://jira.codehaus.org/browse/MRELEASE-200
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Environment: The maven repository is running Red Hat Linux Enterprise Server. The clients are PCs running Windows XP.
> Reporter: Chris Baumgartner
> Priority: Minor
>
> When doing a release:perform, the artifacts are occassionally uploaded to the wrong directory. We are using scp from the upload. Instead of uploading to the path of "/maven-repository", the files are being uploaded to "~/om/maven-repository". For some reason it is creating a subdirectory called "om" in the user's home directory and uploading the artifacts there. It doesn't happen all the time, but it does seem to be consitently putting them there when it does fail.
> I can work around this by manually moving the files, but it is very annoying.
--
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] (MRELEASE-200) Artifacts are uploaded to wrong directory
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=300331#comment-300331 ]
Robert Scholte commented on MRELEASE-200:
-----------------------------------------
I agree with Emmanuel, I don't think it's a maven-release-plugin issue, but it's more likely a [wagon|http://maven.apache.org/wagon]-issue, which is responsible for the movements of files.
Without logs it's hard too see which causes this problem.
> Artifacts are uploaded to wrong directory
> -----------------------------------------
>
> Key: MRELEASE-200
> URL: https://jira.codehaus.org/browse/MRELEASE-200
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Environment: The maven repository is running Red Hat Linux Enterprise Server. The clients are PCs running Windows XP.
> Reporter: Chris Baumgartner
> Priority: Minor
>
> When doing a release:perform, the artifacts are occassionally uploaded to the wrong directory. We are using scp from the upload. Instead of uploading to the path of "/maven-repository", the files are being uploaded to "~/om/maven-repository". For some reason it is creating a subdirectory called "om" in the user's home directory and uploading the artifacts there. It doesn't happen all the time, but it does seem to be consitently putting them there when it does fail.
> I can work around this by manually moving the files, but it is very annoying.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-200) Artifacts are uploaded to wrong directory
Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MRELEASE-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Scholte closed MRELEASE-200.
-----------------------------------
Resolution: Incomplete
Assignee: Robert Scholte
> Artifacts are uploaded to wrong directory
> -----------------------------------------
>
> Key: MRELEASE-200
> URL: https://jira.codehaus.org/browse/MRELEASE-200
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: perform
> Environment: The maven repository is running Red Hat Linux Enterprise Server. The clients are PCs running Windows XP.
> Reporter: Chris Baumgartner
> Assignee: Robert Scholte
> Priority: Minor
>
> When doing a release:perform, the artifacts are occassionally uploaded to the wrong directory. We are using scp from the upload. Instead of uploading to the path of "/maven-repository", the files are being uploaded to "~/om/maven-repository". For some reason it is creating a subdirectory called "om" in the user's home directory and uploading the artifacts there. It doesn't happen all the time, but it does seem to be consitently putting them there when it does fail.
> I can work around this by manually moving the files, but it is very annoying.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira