Created: (MNG-4211) ability to use maven via proxy stopped between maven version 2.0.10 and 2.1. Probably due to addition of wagon 1.0-beta-4+

ability to use maven via proxy stopped between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
---------------------------------------------------------------------------------------------------------------------------

                 Key: MNG-4211
                 URL: http://jira.codehaus.org/browse/MNG-4211
             Project: Maven 2
          Issue Type: Bug
          Components: Artifacts and Repositories
    Affects Versions: 2.1.0, 2.2.0
         Environment: WinXP SP2
            Reporter: Robert Glover Jr
         Attachments: jira_files_4_total.zip

  At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
  Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180857#action_180857 ]

Robert Glover Jr commented on MNG-4211:
---------------------------------------

I (the creator of this JIRA)  was asked by a maven developer to try to find out the brand of the proxy server being used.  I was stopped in my tracks however by a directive from a company spokesman to not divulge any information concerning the brand of proxy server.  So I must apologetically say that even though it would be a big help to solve this JIRA, I am forbidden to say the brand of proxy server.  (I don't know it myself and am forbidden from even asking what it is).

> ability to use maven via proxy stopped between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

     [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-4211:
----------------------------

         Priority: Blocker  (was: Major)
    Fix Version/s: 3.0-alpha-3
                   2.2.1
          Summary: [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+  (was: ability to use maven via proxy stopped between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+)

I'll have to do some poking around here locally with a proxy appliance, but the problem is complicated by the fact that many users configure proxies for use with Maven, and there seem to be no other problem reports like this one.

Without knowing what type of proxy is causing this problem, it's going to be very difficult to fix.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.1, 3.0-alpha-3
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180874#action_180874 ]

Wayne Fay commented on MNG-4211:
--------------------------------

> Without knowing what type of proxy is causing this problem, it's going to be very difficult to fix.

Which is what I told Robert originally on the Users list... One way or another, you're going to have to get us that information, Robert. Even if you're forbidden from asking or passing it on. Big companies are so stupid sometimes -- I would know, I've worked for several of them.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.1, 3.0-alpha-3
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180878#action_180878 ]

Robert Glover Jr commented on MNG-4211:
---------------------------------------

I will investigate whether there is a legitimate way for me to provide that information.  I agree it seems ridiculous that I can't provide such basic information in this context when the company is totally anonymous and entirely obfuscated in the JIRA. I will do what I can but it's an uphill battle to say the least..

Please notice what I found from a google of "Wagon 1.0-beta-4". (See below).  It does look like change WAGON-225 might be the culprit, don't you think?

The Wagon 1.0-beta-4 candidate has been staged.

This release includes 4 fixes. You can take a look at the release
notes here:
    http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10335&styleName=Html&version=14310

* [WAGON-222] - Empty file transfer causes NPE
* [WAGON-224] - ChecksumObserver sets digest == null on transfer
error, leading to NPE's if checksum downloads are retried with same
observer instance
* [WAGON-225] - proxyInfoProvider is never used
* [WAGON-226] - filePermissions and directoryPermissions are not set
correctly for FTP

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.1, 3.0-alpha-3
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

     [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason van Zyl updated MNG-4211:
-------------------------------

    Fix Version/s:     (was: 2.2.1)
                       (was: 3.0-alpha-3)

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

     [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Brett Porter updated MNG-4211:
------------------------------

    Fix Version/s: 2.2.1

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.1
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

     [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MNG-4211:
----------------------------

    Fix Version/s:     (was: 2.2.1)
                   2.2.2

will revisit once we get these other regressions solved, since this one is sparse on information we could use to debug/diagnose.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185079#action_185079 ]

Sylvain Marié commented on MNG-4211:
------------------------------------

Hi John,

Any news concerning that topic ? We are behind a company's proxy and maven 2.2.0 does not seem to work. Our partners at another company have the same issue. Did the configuration file change for proxies ?

Thanks

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185394#action_185394 ]

John Casey commented on MNG-4211:
---------------------------------

@Sylvain: Please try out the first release candidate of Maven 2.2.1 to see whether this helps. It's at:

https://repository.apache.org/content/repositories/maven-staging-025/org/apache/maven/apache-maven/2.2.1-RC1/

I'm not certain whether yours is the same problem that was reported by Robert, since so many things can go wrong with proxies. For instance, one of the main fixes for 2.2.1 aims to re-enable the use of NTLM proxies, which don't always work with the httpclient-driven wagon. Since we switched from using the Sun implementation in 2.2.0, it may simply be a matter of going back to something that supports NTLM for your issue.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185404#action_185404 ]

Sylvain Marié commented on MNG-4211:
------------------------------------

Hi John, I've tried your 2.2.1-RC1 and it helps to solve this issue (but there is still a bug because  

                                           <configuration>
                        <wagonProvider>lightweight</wagonProvider>
                  </configuration>

is used only for one dependency download: if there are several dependencies in this repository it hangs. This doe not happen if the configuration is provided by commandline option
                                             -Dmaven.wagon.provider.http=lightweight -Dmaven.wagon.provider.https=lightweight
, as described in the email I sent you. There is also a big side-effect for us since it seems to impact other wagons, in particular the wagon-svn, see email)


Anyway it is strange because even with RC2.2.1, I have additionally to set java proxy features for https in the mvn.bat script (-Dhttps.proxyHost and -Dhttps.proxyPort). I remember a time (maybe maven 2.0.6 ?) where this was not needed, and where maven worked fine with our proxy using just the settings' <proxies> section. It is sad that this behaviour is now lost..

Best regards,


Sylvain

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185933#action_185933 ]

John Casey commented on MNG-4211:
---------------------------------

@Sylvain-

Unfortunately, one of the bugfixes I had for RC1 addressed the single-download problem...but it got lost in version-control on my localhost, and didn't make it into RC1. This and the other issue with cross-pollution of wagon providers has been addressed in RC2.

I'm not sure about the need to set https.proxyHost/Port, though. Can you try out 2.2.1-RC2:

https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2

and report your results to the '[PLEASE TEST] Maven 2.2.1-RC2' thread out on the users or dev list? That would be a great help.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190721#action_190721 ]

Frank Cornelis commented on MNG-4211:
-------------------------------------

Apparently 2.2.1 still has some proxy issues. At work I'm having difficulties compiling my software because we're sitting behind a proxy over there. I have a mixture of both http and https repositories, and this doesn't really work apparently. At home (direct connection) the build works as expected.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=190905#action_190905 ]

John Casey commented on MNG-4211:
---------------------------------

@Frank:

Do you have any information about what type of proxy is being used? Can you attach a debug log from a failing build? If so, just run with -X and pipe or redirect the output to a file, then attach that file to this issue.

On linux/mac, I'd do something like this:

{noformat}
mvn -X clean install 2>&1 | tee build.log
{noformat}

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=191997#action_191997 ]

Eric Berry commented on MNG-4211:
---------------------------------

We've also seen this issue in 2.1.0, 2.2.0, and 2.2.1.  We are using Artifactory (2.0.8) as our maven proxy.  We have Artifactory proxied behind Apache using SSL.  Here is a sample error we get from Maven, unfortunately (-X is not turned on).  This can happen with plugins or dependencies.  The solution is to rerun maven 1 or more times until the problem goes away.

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] A required plugin was not found: Plugin could not be found - check that the goal name is correct: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/maven/ccad-firebird-maven-flex-plugin/3.1.0-SNAPSHOT/ccad-firebird-maven-flex-plugin-3.1.0-SNAPSHOT.jar does not exist

Try downloading the file manually from the project website.

Then, install it using the command:
    mvn install:install-file -DgroupId=com.ccadllc.firebird.maven -DartifactId=ccad-firebird-maven-flex-plugin -Dversion=3.1.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file there:
    mvn deploy:deploy-file -DgroupId=com.ccadllc.firebird.maven -DartifactId=ccad-firebird-maven-flex-plugin -Dversion=3.1.0-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]


  com.ccadllc.firebird.maven:ccad-firebird-maven-flex-plugin:maven-plugin:3.1.0-SNAPSHOT

from the specified remote repositories:
  central (https://vmswdev1/artifactory/repo)


  com.ccadllc.firebird.maven:ccad-firebird-maven-flex-plugin:maven-plugin:3.1.0-SNAPSHOT

from the specified remote repositories:
  central (https://vmswdev1/artifactory/repo)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192047#action_192047 ]

Eric Berry commented on MNG-4211:
---------------------------------

Captured the problem with -X:

23-Sep-2009 20:04:13   [DEBUG]   Artifact resolved
23-Sep-2009 20:04:13 [DEBUG] ccad-firebird-core-base-common: using locally installed snapshot
23-Sep-2009 20:04:13 [DEBUG] Trying repository central
23-Sep-2009 20:04:13 [DEBUG] Checking for pre-existing User-Agent configuration.
23-Sep-2009 20:04:13 [DEBUG] Adding User-Agent configuration.
23-Sep-2009 20:04:13 [DEBUG] Connecting to repository: 'central' with url: 'https://vmswdev1/artifactory/repo'.
23-Sep-2009 20:04:13 Downloading: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar
23-Sep-2009 20:04:13 [DEBUG] sending ==> If-Modified-Since: Thu, 24-Sep-09 03:03:09 GMT
23-Sep-2009 20:04:13 (1253761389000)
23-Sep-2009 20:04:29 [DEBUG] https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar - Status code: 404
23-Sep-2009 20:04:29 [DEBUG] File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29 org.apache.maven.wagon.ResourceDoesNotExistException: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29        at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:603)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:475)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:456)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run(DefaultArtifactResolver.java:433)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
23-Sep-2009 20:04:29        at java.lang.Thread.run(Thread.java:636)
23-Sep-2009 20:04:29 [DEBUG] File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Try downloading the file manually from the project website.
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Then, install it using the command:
23-Sep-2009 20:04:29    mvn install:install-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Alternatively, if you host your own repository you can deploy the file there:
23-Sep-2009 20:04:29    mvn deploy:deploy-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Path to dependency:
23-Sep-2009 20:04:29        1) com.ccadllc.dks:com.ccadllc.dks.assembly:p2-repository:1.0.0-S5_SNAPSHOT
23-Sep-2009 20:04:29        2) com.ccadllc.osgi:com.ccadllc.osgi.appserver:p2-repository:1.0.8-SNAPSHOT
23-Sep-2009 20:04:29        3) com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29  com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 from the specified remote repositories:
23-Sep-2009 20:04:29  central (https://vmswdev1/artifactory/repo)
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 org.apache.maven.artifact.resolver.ArtifactNotFoundException: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Try downloading the file manually from the project website.
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Then, install it using the command:
23-Sep-2009 20:04:29    mvn install:install-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Alternatively, if you host your own repository you can deploy the file there:
23-Sep-2009 20:04:29    mvn deploy:deploy-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Path to dependency:
23-Sep-2009 20:04:29        1) com.ccadllc.dks:com.ccadllc.dks.assembly:p2-repository:1.0.0-S5_SNAPSHOT
23-Sep-2009 20:04:29        2) com.ccadllc.osgi:com.ccadllc.osgi.appserver:p2-repository:1.0.8-SNAPSHOT
23-Sep-2009 20:04:29        3) com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29  com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 from the specified remote repositories:
23-Sep-2009 20:04:29  central (https://vmswdev1/artifactory/repo)
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:456)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run(DefaultArtifactResolver.java:433)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
23-Sep-2009 20:04:29        at java.lang.Thread.run(Thread.java:636)
23-Sep-2009 20:04:29 Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29        at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:603)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:475)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
23-Sep-2009 20:04:29        ... 6 more

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192048#action_192048 ]

Eric Berry commented on MNG-4211:
---------------------------------

Captured the problem with -X:

23-Sep-2009 20:04:13   [DEBUG]   Artifact resolved
23-Sep-2009 20:04:13 [DEBUG] ccad-firebird-core-base-common: using locally installed snapshot
23-Sep-2009 20:04:13 [DEBUG] Trying repository central
23-Sep-2009 20:04:13 [DEBUG] Checking for pre-existing User-Agent configuration.
23-Sep-2009 20:04:13 [DEBUG] Adding User-Agent configuration.
23-Sep-2009 20:04:13 [DEBUG] Connecting to repository: 'central' with url: 'https://vmswdev1/artifactory/repo'.
23-Sep-2009 20:04:13 Downloading: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar
23-Sep-2009 20:04:13 [DEBUG] sending ==> If-Modified-Since: Thu, 24-Sep-09 03:03:09 GMT
23-Sep-2009 20:04:13 (1253761389000)
23-Sep-2009 20:04:29 [DEBUG] https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar - Status code: 404
23-Sep-2009 20:04:29 [DEBUG] File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29 org.apache.maven.wagon.ResourceDoesNotExistException: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29        at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:603)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:475)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:456)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run(DefaultArtifactResolver.java:433)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
23-Sep-2009 20:04:29        at java.lang.Thread.run(Thread.java:636)
23-Sep-2009 20:04:29 [DEBUG] File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Try downloading the file manually from the project website.
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Then, install it using the command:
23-Sep-2009 20:04:29    mvn install:install-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Alternatively, if you host your own repository you can deploy the file there:
23-Sep-2009 20:04:29    mvn deploy:deploy-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Path to dependency:
23-Sep-2009 20:04:29        1) com.ccadllc.dks:com.ccadllc.dks.assembly:p2-repository:1.0.0-S5_SNAPSHOT
23-Sep-2009 20:04:29        2) com.ccadllc.osgi:com.ccadllc.osgi.appserver:p2-repository:1.0.8-SNAPSHOT
23-Sep-2009 20:04:29        3) com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29  com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 from the specified remote repositories:
23-Sep-2009 20:04:29  central (https://vmswdev1/artifactory/repo)
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 org.apache.maven.artifact.resolver.ArtifactNotFoundException: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Try downloading the file manually from the project website.
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Then, install it using the command:
23-Sep-2009 20:04:29    mvn install:install-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Alternatively, if you host your own repository you can deploy the file there:
23-Sep-2009 20:04:29    mvn deploy:deploy-file -DgroupId=com.ccadllc.firebird.core -DartifactId=ccad-firebird-core-base-common -Dversion=3.1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 Path to dependency:
23-Sep-2009 20:04:29        1) com.ccadllc.dks:com.ccadllc.dks.assembly:p2-repository:1.0.0-S5_SNAPSHOT
23-Sep-2009 20:04:29        2) com.ccadllc.osgi:com.ccadllc.osgi.appserver:p2-repository:1.0.8-SNAPSHOT
23-Sep-2009 20:04:29        3) com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29  com.ccadllc.firebird.core:ccad-firebird-core-base-common:jar:3.1.0-SNAPSHOT
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29 from the specified remote repositories:
23-Sep-2009 20:04:29  central (https://vmswdev1/artifactory/repo)
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:228)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:90)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.resolveArtifact(DefaultArtifactResolver.java:456)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver$ResolveArtifactTask.run(DefaultArtifactResolver.java:433)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
23-Sep-2009 20:04:29        at hidden.edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
23-Sep-2009 20:04:29        at java.lang.Thread.run(Thread.java:636)
23-Sep-2009 20:04:29 Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: File: https://vmswdev1/artifactory/repo/com/ccadllc/firebird/core/ccad-firebird-core-base-common/3.1.0-SNAPSHOT/ccad-firebird-core-base-common-3.1.0-SNAPSHOT.jar does not exist
23-Sep-2009 20:04:29        at org.apache.maven.wagon.shared.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:603)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:116)
23-Sep-2009 20:04:29        at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:475)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:372)
23-Sep-2009 20:04:29        at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
23-Sep-2009 20:04:29        ... 6 more

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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

       

    [ http://jira.codehaus.org/browse/MNG-4211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=192050#action_192050 ]

Eric Berry commented on MNG-4211:
---------------------------------

After taking a look at the artifactory log, it looks like artifactory is timing out reading from the remote repository.

> [regression] proxy access broken between maven version 2.0.10 and 2.1. Probably due to addition of  wagon 1.0-beta-4+
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: MNG-4211
>                 URL: http://jira.codehaus.org/browse/MNG-4211
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.1.0, 2.2.0
>         Environment: WinXP SP2
>            Reporter: Robert Glover Jr
>            Priority: Blocker
>             Fix For: 2.2.2
>
>         Attachments: jira_files_4_total.zip
>
>
>   At a large company, maven become impossible to use via proxy when maven upgraded from 1.0.10 to 2.1.  maven has always worked fine via proxy in 2.0.9 and continues to work fine.  however maven via proxy always fails in version 2.1.0 and higher.  
>   Attached is a  zip file containing   1) log of GMAIL chat between the creater of this JIRA and a maven developer.  2) two console outputs of running maven 2.2. RC3 showing the proxy failure messages.  3) setting.xml (with comments stripped out)

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