You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Dave Brosius (JIRA)" <ji...@codehaus.org> on 2010/11/19 02:05:05 UTC

[jira] Created: (MRM-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Proxying of xml files from one archiva server to another fails, when jar files succeed
--------------------------------------------------------------------------------------

                 Key: MRM-1429
                 URL: http://jira.codehaus.org/browse/MRM-1429
             Project: Archiva
          Issue Type: Bug
          Components: remote proxy
    Affects Versions: 1.3.1
         Environment: ubuntu 10.10 32bit x86
            Reporter: Dave Brosius
            Priority: Minor


This is what i did,

1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.

2) Edited the jetty.xml file of the remote directory install to use port 9090

3) Started both archivas

4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:

    Identifier: proxy
    Name: Proxy of Local
    URL: http://localhost:8080/archiva/repository/internal/
    UserName: as defined
    Password: as defined
    Timeout in Seconds: 60
    Type: Maven 2.x repository

5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:

    Network Proxy: (direct connection)
    Managed Repository: internal
    Remote Repository: proxy
    (all other settings defaulted)

6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:

    Group Id: com.mebigfatguy
    Artifact Id: fb-contrib
    Version: 4.6.0
    Packaging: jar
    Classifier: (blank)
    Generate Maven 2 POM: checked
    Artifact file: fb-contrib.jar
    Repository Id: internal

    and submitted it.

7) Next brought up firefox and entered url for the archiva in the remote dir (9090)

    http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>

    and file is successfully downloaded

8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:

    Group Id: com.mebigfatguy
    Artifact Id: build
    Version: 4.6.0
    Packaging: xml
    Classifier: (blank)
    Generate Maven 2 POM: checked
    Artifact file: build.xml
    Repository Id: internal

    and submitted it.

9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)

    http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>

    and the file is successfully downloaded

10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)

    http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>

    Artifact is *not downloaded *and get this error page


        HTTP ERROR 404

    Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:

        Resource does not exist

------------------------------------------------------------------------
/Powered by Jetty:///


-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243957#action_243957 ] 

Brett Porter commented on MRM-1429:
-----------------------------------

I just noticed that due to the wiki rendering the above comment previously looked wrong. Can you confirm you tested it with the two asterisks at the front?

I'd need to test this otherwise, I can't see why it wouldn't work.

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Dave Brosius (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243717#action_243717 ] 

Dave Brosius commented on MRM-1429:
-----------------------------------

I tried that as well, doesn't seem to do anything

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Dave Brosius (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247104#action_247104 ] 

Dave Brosius commented on MRM-1429:
-----------------------------------

Super, thanks alot, i'll give that a try.

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Assignee: Brett Porter
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter closed MRM-1429.
-----------------------------

       Resolution: Not A Bug
    Fix Version/s:     (was: 1.3.3)
         Assignee: Brett Porter

ok, I'll need to explain what's going on here.

The proxy is failing due to missing checksums on the 8080 repository, and the connector being set to fail if that's the case.

The reason the checksums are missing is because the UploadAction relies on the metadata consumer to correct them. However that only does so for files listed in "artifacts" on the scanning page, which on 8080 does not include XML. So the previous tip was correct, just on the wrong server and at the wrong point in time (before upload).

I'll file this as a new issue

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Assignee: Brett Porter
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Dave Brosius (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243959#action_243959 ] 

Dave Brosius commented on MRM-1429:
-----------------------------------

i used asterick asterick forward-slash asterick dot xml

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MRM-1429:
------------------------------

    Fix Version/s: 1.3.3

will try and take a closer look at this. If you come up with more info (or a patch!), that'd be helpful.

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>             Fix For: 1.3.3
>
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243696#action_243696 ] 

Brett Porter edited comment on MRM-1429 at 11/21/10 6:35 PM:
-------------------------------------------------------------

I know it's not intuitive, but does this work if you got to the "Repository Scanning" page, and add \*\*/\*.xml to the list of artifacts?

      was (Author: brettporter):
    I know it's not intuitive, but does this work if you got to the "Repository Scanning" page, and add **/*.xml to the list of artifacts?
  
> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=246962#action_246962 ] 

Brett Porter commented on MRM-1429:
-----------------------------------

I was able to reproduce on the steps you've used

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>             Fix For: 1.3.3
>
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

-- 
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-1429) Proxying of xml files from one archiva server to another fails, when jar files succeed

Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MRM-1429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=243696#action_243696 ] 

Brett Porter commented on MRM-1429:
-----------------------------------

I know it's not intuitive, but does this work if you got to the "Repository Scanning" page, and add **/*.xml to the list of artifacts?

> Proxying of xml files from one archiva server to another fails, when jar files succeed
> --------------------------------------------------------------------------------------
>
>                 Key: MRM-1429
>                 URL: http://jira.codehaus.org/browse/MRM-1429
>             Project: Archiva
>          Issue Type: Bug
>          Components: remote proxy
>    Affects Versions: 1.3.1
>         Environment: ubuntu 10.10 32bit x86
>            Reporter: Dave Brosius
>            Priority: Minor
>
> This is what i did,
> 1) Downloaded archiva 1.3.1 standalone, and unzipped it into two directories called local and remote.
> 2) Edited the jetty.xml file of the remote directory install to use port 9090
> 3) Started both archivas
> 4) On archiva in remote dir (9090) added a remote repository thru the gui that had this information:
>     Identifier: proxy
>     Name: Proxy of Local
>     URL: http://localhost:8080/archiva/repository/internal/
>     UserName: as defined
>     Password: as defined
>     Timeout in Seconds: 60
>     Type: Maven 2.x repository
> 5) On archiva in remote dir (9090) added a proxy connector thru the gui that had this information:
>     Network Proxy: (direct connection)
>     Managed Repository: internal
>     Remote Repository: proxy
>     (all other settings defaulted)
> 6) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: fb-contrib
>     Version: 4.6.0
>     Packaging: jar
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: fb-contrib.jar
>     Repository Id: internal
>     and submitted it.
> 7) Next brought up firefox and entered url for the archiva in the remote dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and file is successfully downloaded
> 8) On archiva in local dir (8080) uploaded an artifact thru the gui that had this information:
>     Group Id: com.mebigfatguy
>     Artifact Id: build
>     Version: 4.6.0
>     Packaging: xml
>     Classifier: (blank)
>     Generate Maven 2 POM: checked
>     Artifact file: build.xml
>     Repository Id: internal
>     and submitted it.
> 9) Next brought up firefox and entered url for the archiva in the *local* dir (8080)
>     http://localhost:8080/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     and the file is successfully downloaded
> 10) Next brought up firefox and entered url for the archiva in the *remote* dir (9090)
>     http://localhost:9090/archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml <http://localhost:9090/archiva/repository/internal/com/mebigfatguy/fb-contrib/4.6.0/fb-contrib-4.6.0.xml>
>     Artifact is *not downloaded *and get this error page
>         HTTP ERROR 404
>     Problem accessing /archiva/repository/internal/com/mebigfatguy/build/4.6.0/build-4.6.0.xml. Reason:
>         Resource does not exist
> ------------------------------------------------------------------------
> /Powered by Jetty:///

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