You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "apache maillist (JIRA)" <ji...@codehaus.org> on 2009/09/03 19:51:41 UTC
[jira] Created: (MRM-1245) Archiva cache/create corrupt/invalid pom
and jar in its internal directory
Archiva cache/create corrupt/invalid pom and jar in its internal directory
--------------------------------------------------------------------------
Key: MRM-1245
URL: http://jira.codehaus.org/browse/MRM-1245
Project: Archiva
Issue Type: Bug
Components: remote proxy
Affects Versions: 1.1.4
Environment: Linux
Reporter: apache maillist
Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189767#action_189767 ]
Wendy Smoak commented on MRM-1245:
----------------------------------
So you're saying that instead of sending 404 Not Found, Archiva is *inventing* an invalid pom and jar?
Can you try it with the latest release (1.2.2) and see if it's still a problem?
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190658#action_190658 ]
apache maillist commented on MRM-1245:
--------------------------------------
Yes, it was "fix" (Archiva's default). After changing to "fail", the invented pom and jar no longer created after putting spring repos back to the proxy connector. Does this mean Archiva should be implemented using "fail" as default?
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom, inventedPOMandJar.JPG
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190567#action_190567 ]
Brett Porter commented on MRM-1245:
-----------------------------------
it sounds like you have your proxy misconfigured. The remote should send a 404 if not found, not a 200 with content. Regardless, if you set the checksum policy to fail then this shouldn't occur.
Can you confirm?
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom, inventedPOMandJar.JPG
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189730#action_189730 ]
Wendy Smoak commented on MRM-1245:
----------------------------------
Are you saying you uploaded/deployed a pom with a <dependency> that does not exist? Actually, you picked the 'remote proxy' component, so is this a 'bad' pom that was proxied in from a remote repository?
As far as I know, Archiva does not require transitive closure of the artifacts it manages.
What behavior would you like to see?
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189766#action_189766 ]
apache maillist commented on MRM-1245:
--------------------------------------
No, not upload/deploy
I am running mvn clean install on pom.xml which has the dependency that is not available on Archiva's remote repositories. Archiva creates/caches the none-available dependency artifact's pom and jar in its internal directory which pom is invaild, and jar is corrupted (see attached).
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid pom
and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
apache maillist updated MRM-1245:
---------------------------------
Attachment: inventedPOMandJar.JPG
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom, inventedPOMandJar.JPG
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189907#action_189907 ]
apache maillist commented on MRM-1245:
--------------------------------------
1.2.2 has the same "invented" invalid pom and jar, please see attached screenshot
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom, inventedPOMandJar.JPG
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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] Issue Comment Edited: (MRM-1245) Archiva cache/create
corrupt/invalid pom and jar in its internal directory
Posted by "Wendy Smoak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189730#action_189730 ]
Wendy Smoak edited comment on MRM-1245 at 9/3/09 1:12 PM:
----------------------------------------------------------
Are you saying you uploaded/deployed a pom with a <dependency> that does not exist? Actually, you picked the 'remote proxy' component, so is this a 'bad' pom that was proxied in from a remote repository?
As far as I know, Archiva does not require transitive dependency closure of the artifacts it manages.
What behavior would you like to see?
was (Author: wsmoak):
Are you saying you uploaded/deployed a pom with a <dependency> that does not exist? Actually, you picked the 'remote proxy' component, so is this a 'bad' pom that was proxied in from a remote repository?
As far as I know, Archiva does not require transitive closure of the artifacts it manages.
What behavior would you like to see?
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189790#action_189790 ]
apache maillist commented on MRM-1245:
--------------------------------------
The Archiva UI has the link to the artifact, but gives you 404 if you click the link, however, the pom and jar are invented on the file system under Archiva "internal" directory.
I will try 1.2.2 and report back.
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid pom
and jar in its internal directory
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MRM-1245.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
the default is in fact already fail for checksums
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Assignee: Brett Porter
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom, inventedPOMandJar.JPG
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190253#action_190253 ]
apache maillist commented on MRM-1245:
--------------------------------------
I think I may found the root cause, it is the spring framework remote maven repos we are proxying.
http://s3browse.com/explore/maven.springframework.org/release/org/springframework
http://s3browse.com/explore/maven.springframework.org/milestone/org/springframework
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom, inventedPOMandJar.JPG
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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: (MRM-1245) Archiva cache/create corrupt/invalid
pom and jar in its internal directory
Posted by "apache maillist (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRM-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189727#action_189727 ]
apache maillist commented on MRM-1245:
--------------------------------------
dependency section:
<dependency>
<groupId>boguslog4j</groupId>
<artifactId>boguslog4</artifactId>
<version>1.0.0</version>
</dependency>
> Archiva cache/create corrupt/invalid pom and jar in its internal directory
> --------------------------------------------------------------------------
>
> Key: MRM-1245
> URL: http://jira.codehaus.org/browse/MRM-1245
> Project: Archiva
> Issue Type: Bug
> Components: remote proxy
> Affects Versions: 1.1.4
> Environment: Linux
> Reporter: apache maillist
> Attachments: boguslog4j-1.0.0.jar, boguslog4j-1.0.0.pom
>
>
> Currently running 1.1.4, and when putting a dependency section that is not available internally or externally, Achriva creates/caches corrupt/invalid pom and jar in the internal directory
--
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