[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[ https://jira.codehaus.org/browse/MNG-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332186#comment-332186 ] Herve Boutemy commented on MNG-5509: maven-doap-plugin ITs deactivated for affected maven version

[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[ https://jira.codehaus.org/browse/MNG-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5509: --- Affects Version/s: 3.0.4 > org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[ https://jira.codehaus.org/browse/MNG-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5509: --- Affects Version/s: 3.1.0-alpha-1 > org.apache.maven.repository.legacy.DefaultWagonManager should set Use

[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[ https://jira.codehaus.org/browse/MNG-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5509: --- Description: When Maven is directly using Wagon it is missing the User-Agent. Aether's {{org.eclipse.aether

[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[ https://jira.codehaus.org/browse/MNG-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332185#comment-332185 ] Herve Boutemy commented on MNG-5509: confirmed with maven-doap-plugin MDOAP-38, doapfile, basic a

[jira] (WAGON-401) Access Denied due to missing User-Agent

[ https://jira.codehaus.org/browse/WAGON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed WAGON-401. Resolution: Won't Fix Assignee: Robert Scholte Found a way with MNG-5509 to fix this

[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

[ https://jira.codehaus.org/browse/MNG-5509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MNG-5509. --- Resolution: Fixed Fix Version/s: 3.1.1 Assignee: Robert Scholte Fixed in [c9950d77|http://gi

[jira] (MNG-5509) org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent

Robert Scholte created MNG-5509: --- Summary: org.apache.maven.repository.legacy.DefaultWagonManager should set User-Agent Key: MNG-5509 URL: https://jira.codehaus.org/browse/MNG-5509 Project: Maven 2 & 3

[jira] (MCHANGES-320) Remove obsolete Changes report from plugin's site

[ https://jira.codehaus.org/browse/MCHANGES-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332181#comment-332181 ] Herve Boutemy commented on MCHANGES-320: changles.xml content updated in [r1519195|http:/

[jira] (WAGON-401) Access Denied due to missing User-Agent

[ https://jira.codehaus.org/browse/WAGON-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated WAGON-401: - Attachment: accessdenied-test.patch > Access Denied due to missing User-Agent > ---

[jira] (WAGON-401) Access Denied due to missing User-Agent

Robert Scholte created WAGON-401: Summary: Access Denied due to missing User-Agent Key: WAGON-401 URL: https://jira.codehaus.org/browse/WAGON-401 Project: Maven Wagon Issue Type: Improvement

[jira] (SUREFIRE-1026) Allow SurefireBooter framework to use alternative resolve for test classes

[ https://jira.codehaus.org/browse/SUREFIRE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1026: - Fix Version/s: 3.0 > Allow SurefireBooter framework to use alternative resolve for test

[jira] (SUREFIRE-1026) Allow SurefireBooter framework to use alternative resolve for test classes

[ https://jira.codehaus.org/browse/SUREFIRE-1026?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=332177#comment-332177 ] Andreas Gudian commented on SUREFIRE-1026: -- We plan to support stuff like that with a s

[jira] (SUREFIRE-1025) TestSetRunListener.testSetCompleted() should write files first before reporting the completion on console.

[ https://jira.codehaus.org/browse/SUREFIRE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1025: - Issue Type: Wish (was: Bug) > TestSetRunListener.testSetCompleted() should write files

[jira] (SUREFIRE-1025) TestSetRunListener.testSetCompleted() should write files first before reporting the completion on console.

[ https://jira.codehaus.org/browse/SUREFIRE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1025: - Fix Version/s: 2.17 > TestSetRunListener.testSetCompleted() should write files first be

[jira] (SUREFIRE-1024) "verify" goal ignores "dependenciesToScan" parameter when checking tests existence

[ https://jira.codehaus.org/browse/SUREFIRE-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-1024: - Fix Version/s: 2.17 > "verify" goal ignores "dependenciesToScan" parameter when checkin