[jira] [Commented] (MSHARED-604) Honor none default localRepository
[
https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780255#comment-15780255
]
Guillaume Boué commented on MSHARED-604:
To change the local repository, you can use the {{RepositoryManager}} class,
and call {{setLocalRepositoryBasedir}} by passing it the
{{ProjectBuildingRequest}}:
{code:java}
@Component
private RepositoryManager repositoryManager;
buildingRequest = repositoryManager.setLocalRepositoryBasedir( buildingRequest,
localRepositoryPath );
{code}
I am not sure what the {{localRepository}} field is doing, perhaps it should be
removed.
> Honor none default localRepository
> ---
>
> Key: MSHARED-604
> URL: https://issues.apache.org/jira/browse/MSHARED-604
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-aritfact-transfer
>Affects Versions: maven-artifact-transfer-0.9.0
>Reporter: Dan Tran
>
> ArtifactResolver ignores localRepository settings in the request
> ProjectBuildingRequest. It always use the default location when maven starts
> Use case: I have a use case to resolve a maven artifact with local repo is
> under maven 'target' directory
> maven-compat does work my case.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSHARED-604) Honor none default localRepository
[ https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780277#comment-15780277 ] Dan Tran commented on MSHARED-604: -- Thanks for the suggestion, however, it does not work either. Debug thru the code, no traces of aether interacting with local repo set under buildingRequest. > Honor none default localRepository > --- > > Key: MSHARED-604 > URL: https://issues.apache.org/jira/browse/MSHARED-604 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-aritfact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Dan Tran > > ArtifactResolver ignores localRepository settings in the request > ProjectBuildingRequest. It always use the default location when maven starts > Use case: I have a use case to resolve a maven artifact with local repo is > under maven 'target' directory > maven-compat does work my case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MSHARED-604) Honor none default localRepository
[ https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15780277#comment-15780277 ] Dan Tran edited comment on MSHARED-604 at 12/27/16 12:19 PM: - Thanks for the suggestion, however, it does not work either. Debug thru the code, no traces of maven-artifact-transfer interacting with local repo set under buildingRequest. was (Author: dantran): Thanks for the suggestion, however, it does not work either. Debug thru the code, no traces of aether interacting with local repo set under buildingRequest. > Honor none default localRepository > --- > > Key: MSHARED-604 > URL: https://issues.apache.org/jira/browse/MSHARED-604 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-aritfact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Dan Tran > > ArtifactResolver ignores localRepository settings in the request > ProjectBuildingRequest. It always use the default location when maven starts > Use case: I have a use case to resolve a maven artifact with local repo is > under maven 'target' directory > maven-compat does work my case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MRELEASE-973) Please keep the property performRelease or provide an alternativ for it
Oliver B. Fischer created MRELEASE-973:
--
Summary: Please keep the property performRelease or provide an
alternativ for it
Key: MRELEASE-973
URL: https://issues.apache.org/jira/browse/MRELEASE-973
Project: Maven Release Plugin
Issue Type: Wish
Components: perform
Affects Versions: 3.0.0
Reporter: Oliver B. Fischer
Priority: Critical
Fix For: 3.0.0
MRELEASE-896 deprecates the {{useReleaseProfile}} and changed its default value
from {{true}} to {{false}}.
Unfortunately this disabled also the setting of the property {{performRelease}}
which we use to enable multiple profiles during the release process.
At least we need a possibility to enable multiple, sometimes different,
profiles during a release and its preparation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MPIR-288) Add a skipEmptyReport option
[ https://issues.apache.org/jira/browse/MPIR-288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781356#comment-15781356 ] Hudson commented on MPIR-288: - SUCCESS: Integrated in Jenkins build maven-plugins #8048 (See [https://builds.apache.org/job/maven-plugins/8048/]) [MPIR-288] Add a skipEmptyReport option o Updated the IT to account for skipEmptyReport to default to 'true'. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1776203]) * (edit) maven-project-info-reports-plugin/src/it/minimal-pom/pom.xml [MPIR-288] Add a skipEmptyReport option o Updated the IT to account for skipEmptyReport to default to 'true'. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1776201]) * (edit) maven-project-info-reports-plugin/src/it/full-pom/pom.xml > Add a skipEmptyReport option > > > Key: MPIR-288 > URL: https://issues.apache.org/jira/browse/MPIR-288 > Project: Maven Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.7 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 2.8 > > > Similar to MPMD-168, it should be possible to skip generation of empty > reports which do not contain any valuable information. > Some canditates are dependencies, cim, scm, issues, mailinglist, etc. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MANT-86) Retire the plugin
[ https://issues.apache.org/jira/browse/MANT-86?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781385#comment-15781385 ] Hudson commented on MANT-86: SUCCESS: Integrated in Jenkins build maven-plugins #8049 (See [https://builds.apache.org/job/maven-plugins/8049/]) [MANT-86] Retire the plugin o Removed the plugin form the aggregator POM. It is on its way to get retired and currently produces IT failures on Jenkins. Fixing ITs for a plugin getting retired makes no sense. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1776208]) * (edit) pom.xml > Retire the plugin > - > > Key: MANT-86 > URL: https://issues.apache.org/jira/browse/MANT-86 > Project: Maven Ant Plugin > Issue Type: Wish >Affects Versions: 3.0 >Reporter: Karl Heinz Marbaise > Fix For: 3.0 > > > We should start a VOTE > http://maven.apache.org/developers/retirement-plan-plugins.html at the > 2015/02/01 to ultimately retire this plugin... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (WAGON-479) Preemptive auth with HTTP Provider might fail because BasicScheme is add as completed to the AuthCache
Michael Osipov created WAGON-479:
Summary: Preemptive auth with HTTP Provider might fail because
BasicScheme is add as completed to the AuthCache
Key: WAGON-479
URL: https://issues.apache.org/jira/browse/WAGON-479
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http
Affects Versions: 2.11
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 2.12
Currently, to prepopulate preemptive authentication for target and proxy,
{{BasicScheme}} is created and {{processChallenge()}} is called. Then it is
added to the {{AuthCache}}. This causes two issues:
1. The [reference
documentation|https://hc.apache.org/httpcomponents-client-4.5.x/tutorial/html/authentication.html#d5e717]
never shows to do so.
2. With the Jetty 8 upgrade of all tests several unit tests failed because the
scheme was set to {{completed=true}} initially and never reacted on requested
preemptive auth or simply obstained from responding to {{401}} with proper
credentials altogether.
This issue has been found during WAGON-474.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (WAGON-474) Upgrade and revise all tests for Jetty 8
[ https://issues.apache.org/jira/browse/WAGON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened WAGON-474: -- > Upgrade and revise all tests for Jetty 8 > > > Key: WAGON-474 > URL: https://issues.apache.org/jira/browse/WAGON-474 > Project: Maven Wagon > Issue Type: Task >Affects Versions: 2.11 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 2.12 > > > All test code currently relies on Jetty 6 which is ten years old and not > really represents today's servers and repository managers like Sonatype Nexus. > Tasks: > * Revise all code for Jetty 8.1 (last Java 1.6 version) > * Check for inconsistencies and errors > * Fix constant test failures on non-Windows platforms which are likely due to > bad code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (WAGON-479) Preemptive auth with HTTP Provider may fail because BasicScheme is added as completed=true to the AuthCache
[
https://issues.apache.org/jira/browse/WAGON-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-479:
-
Summary: Preemptive auth with HTTP Provider may fail because BasicScheme is
added as completed=true to the AuthCache (was: Preemptive auth with HTTP
Provider might fail because BasicScheme is add as completed to the AuthCache)
> Preemptive auth with HTTP Provider may fail because BasicScheme is added as
> completed=true to the AuthCache
> ---
>
> Key: WAGON-479
> URL: https://issues.apache.org/jira/browse/WAGON-479
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.11
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.12
>
>
> Currently, to prepopulate preemptive authentication for target and proxy,
> {{BasicScheme}} is created and {{processChallenge()}} is called. Then it is
> added to the {{AuthCache}}. This causes two issues:
> 1. The [reference
> documentation|https://hc.apache.org/httpcomponents-client-4.5.x/tutorial/html/authentication.html#d5e717]
> never shows to do so.
> 2. With the Jetty 8 upgrade of all tests several unit tests failed because
> the scheme was set to {{completed=true}} initially and never reacted on
> requested preemptive auth or simply obstained from responding to {{401}} with
> proper credentials altogether.
> This issue has been found during WAGON-474.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5457) Show repository id when downloading or uploading from/to a remote repository
[
https://issues.apache.org/jira/browse/MNG-5457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781441#comment-15781441
]
Hudson commented on MNG-5457:
-
SUCCESS: Integrated in Jenkins build maven-plugins #8051 (See
[https://builds.apache.org/job/maven-plugins/8051/])
[MNG-5457] Show repository id when downloading or uploading from/to a remote
repository
o Updated to account for recent log messages in 3.4+. (schulte:
[http://svn.apache.org/viewvc/?view=rev&rev=1776211])
* (edit)
maven-dependency-plugin/src/it/projects/copy-from-remote-repository/verify.groovy
[MNG-5457] Show repository id when downloading or uploading from/to a remote
repository
o Updated to account for recent log messages in 3.4+. (schulte:
[http://svn.apache.org/viewvc/?view=rev&rev=1776210])
* (edit)
maven-dependency-plugin/src/it/projects/copy-from-remote-repository/verify.groovy
* (edit)
maven-dependency-plugin/src/it/projects/unpack-from-remote-repository/verify.groovy
> Show repository id when downloading or uploading from/to a remote repository
>
>
> Key: MNG-5457
> URL: https://issues.apache.org/jira/browse/MNG-5457
> Project: Maven
> Issue Type: Improvement
> Components: General
>Affects Versions: 3.0.5
>Reporter: Hervé Boutemy
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
> Attachments: 2016-05-18_204749.png
>
>
> currently, the log only show the url being downloaded:
> {noformat}Downloading:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
> nothing is told about the repository id.
> But as shown in MNG-5181, repository id is an important information since it
> is stored in local repository to limit artifact scope: it would be useful
> IMHO to display the id in the output, like
> {noformat}Downloading from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> Downloaded from central:
> http://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/23/maven-plugins-23.pom
> (9 KB at 98.7 KB/sec){noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MNG-5761) Dependency management is not transitive.
[ https://issues.apache.org/jira/browse/MNG-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781478#comment-15781478 ] Hudson commented on MNG-5761: - SUCCESS: Integrated in Jenkins build maven-plugins #8052 (See [https://builds.apache.org/job/maven-plugins/8052/]) [MNG-5761] Dependency management is not transitive. o Updated to disable this IT for Maven >= 3.4. As long as the model version 5.0.0 PDT file is not implemented, it makes no sense to assert resolution results to remain permanent accross decades of Maven versions. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1776212]) * (edit) maven-dependency-plugin/src/it/projects/tree/invoker.properties > Dependency management is not transitive. > > > Key: MNG-5761 > URL: https://issues.apache.org/jira/browse/MNG-5761 > Project: Maven > Issue Type: Bug > Components: Dependencies >Affects Versions: 3.2.5 >Reporter: Jeff Schnitzer >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > Attachments: MNG-5761.zip > > > A detailed description of the issue is here: > http://stackoverflow.com/questions/28312975/maven-dependencymanagement-version-ignored-in-transitive-dependencies > The short of it is that maven appears to be using the wrong > version in a transitive dependency. There are two > relevant sections in the build, one pulled in by guice > and one pulled in by gwizard-parent. These are the dependency paths from the > top: > gwizard-example -> gwizard-config -> gwizard-parent > gwizard-example -> gwizard-config -> guice -> guice-parent > gwizard-parent's dependencyManagement specifies guava 18 > guice-parent's dependencyManagement specifies guava 16 > Guava 16 is winning. This seems highly undesirable, and in fact it breaks our > build. I would expect that in a version # fight, "closest to the top" should > win. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MSHARED-604) Honor none default localRepository
[ https://issues.apache.org/jira/browse/MSHARED-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed MSHARED-604. Resolution: Implemented details at http://maven.40175.n5.nabble.com/API-to-resolve-a-version-range-artifact-td5889934.html > Honor none default localRepository > --- > > Key: MSHARED-604 > URL: https://issues.apache.org/jira/browse/MSHARED-604 > Project: Maven Shared Components > Issue Type: Bug > Components: maven-aritfact-transfer >Affects Versions: maven-artifact-transfer-0.9.0 >Reporter: Dan Tran > > ArtifactResolver ignores localRepository settings in the request > ProjectBuildingRequest. It always use the default location when maven starts > Use case: I have a use case to resolve a maven artifact with local repo is > under maven 'target' directory > maven-compat does work my case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6139) Addition of command line option 'legacy-dependency-management'.
[ https://issues.apache.org/jira/browse/MNG-6139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781534#comment-15781534 ] Christian Schulte commented on MNG-6139: @[~struberg]: Current master has this command line option requested by you. We discussed this a bit on dev@ and I'd like to remove that command line option. Since you requested this, can you please either start a discussion on dev@ or in this issue to clarify why such a command line option should be provided. * [http://www.mail-archive.com/dev@maven.apache.org/msg111747.html] * [http://www.mail-archive.com/dev@maven.apache.org/msg111800.html] * [http://www.mail-archive.com/dev@maven.apache.org/msg111804.html] > Addition of command line option 'legacy-dependency-management'. > --- > > Key: MNG-6139 > URL: https://issues.apache.org/jira/browse/MNG-6139 > Project: Maven > Issue Type: New Feature >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Critical > Fix For: 3.4.0 > > > See the issues this issue is linked to. The command line option will simply > allow users to disable the bugfixes and get the former incorrect behaviour. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6140) update documentation's dependency graph with resolver + resolver-provider + slf4j-provider
[ https://issues.apache.org/jira/browse/MNG-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MNG-6140. -- Resolution: Fixed Assignee: Hervé Boutemy > update documentation's dependency graph with resolver + resolver-provider + > slf4j-provider > -- > > Key: MNG-6140 > URL: https://issues.apache.org/jira/browse/MNG-6140 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6140) update documentation's dependency graph with resolver + resolver-provider + slf4j-provider
[ https://issues.apache.org/jira/browse/MNG-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6140: --- Description: http://maven.apache.org/ref/3-LATEST/ > update documentation's dependency graph with resolver + resolver-provider + > slf4j-provider > -- > > Key: MNG-6140 > URL: https://issues.apache.org/jira/browse/MNG-6140 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: 3.4.0 > > > http://maven.apache.org/ref/3-LATEST/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6110) Upgrade Aether to Maven Resolver 1.2
[ https://issues.apache.org/jira/browse/MNG-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6110: --- Comment: was deleted (was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #32 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/32/]) [MNG-6110] Upgrade Aether to Maven Resolver 1.2 (schulte: rev 39b8fc01142afb4abce4607da2dd9447bef48cb6) * (edit) maven-resolver-provider/pom.xml ) > Upgrade Aether to Maven Resolver 1.2 > > > Key: MNG-6110 > URL: https://issues.apache.org/jira/browse/MNG-6110 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.3.9 >Reporter: Harald Wellmann >Assignee: Christian Schulte > Fix For: 3.4.0 > > > Replace Aether by Maven Resolver to make use of the latest bugfixes and > enhancements related to dependency collection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6110) Upgrade Aether to Maven Resolver 1.2
[ https://issues.apache.org/jira/browse/MNG-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6110: --- Comment: was deleted (was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #25 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/25/]) [MNG-6110] Upgrade Aether to Maven Resolver 1.2 (schulte: rev 47ff8321fc7a0f423178708ddf35e3f97258e5ea) * (edit) maven-embedder/pom.xml * (edit) apache-maven/pom.xml * (edit) maven-core/pom.xml * (edit) maven-compat/pom.xml * (edit) pom.xml * (edit) maven-aether-provider/pom.xml ) > Upgrade Aether to Maven Resolver 1.2 > > > Key: MNG-6110 > URL: https://issues.apache.org/jira/browse/MNG-6110 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.3.9 >Reporter: Harald Wellmann >Assignee: Christian Schulte > Fix For: 3.4.0 > > > Replace Aether by Maven Resolver to make use of the latest bugfixes and > enhancements related to dependency collection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6110) Upgrade Aether to Maven Resolver 1.2
[ https://issues.apache.org/jira/browse/MNG-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6110: --- Comment: was deleted (was: FAILURE: Integrated in Jenkins build maven-3.x Jigsaw #27 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/27/]) [MNG-6110] Upgrade Aether to Maven Resolver 1.2 (schulte: rev 58554032fe026f3fa3588be7911505d1aa1fff3f) * (edit) maven-compat/pom.xml * (add) maven-resolver-provider/src/test/resources/repo/ut/simple/dependency/1.0/dependency-1.0.jar * (delete) maven-aether-provider/src/test/java/org/apache/maven/repository/internal/util/ConsoleRepositoryListener.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelCache.java * (delete) maven-aether-provider/src/test/resources/repo/ut/simple/artifact/maven-metadata.xml * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/RemoteSnapshotMetadataGenerator.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenMetadata.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/SnapshotMetadataGeneratorFactory.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/VersionsMetadata.java * (delete) maven-aether-provider/src/test/java/org/apache/maven/repository/internal/DefaultVersionRangeResolverTest.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenSnapshotMetadata.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/RelocatedArtifact.java * (add) maven-resolver-provider/src/site/site.xml * (delete) maven-aether-provider/src/test/java/org/apache/maven/repository/internal/MavenRepositorySystemUtilsTest.java * (delete) maven-aether-provider/src/test/resources/repo/ut/simple/dependency/maven-metadata.xml * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultArtifactDescriptorReader.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResultFilter.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/VersionsMetadataGenerator.java * (delete) maven-aether-provider/src/test/resources/repo/ut/simple/dependency/1.0/dependency-1.0.jar * (delete) maven-aether-provider/src/test/java/org/apache/maven/repository/internal/AbstractRepositoryTestCase.java * (add) maven-resolver-provider/src/test/resources/repo/ut/simple/dependency/1.0/dependency-1.0-sources.jar * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/ArtifactDescriptorUtils.java * (add) maven-resolver-provider/src/test/resources/repo/org/apache/maven/its/mng-3092/maven-metadata.xml * (delete) maven-aether-provider/src/test/java/org/apache/maven/repository/internal/RepositorySystemTest.java * (delete) maven-aether-provider/src/test/resources/repo/ut/simple/parent/maven-metadata.xml * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenRepositorySystemUtils.java * (add) maven-resolver-provider/src/test/java/org/apache/maven/repository/internal/RepositorySystemTest.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/MavenAetherModule.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/SnapshotMetadataGeneratorFactory.java * (add) maven-resolver-provider/src/test/resources/repo/org/apache/maven/its/dep-mng5324/07.20.3-SNAPSHOT/maven-metadata.xml * (add) maven-resolver-provider/src/test/resources/repo/ut/simple/parent/1.0/parent-1.0.pom * (add) maven-resolver-provider/src/test/resources/repo/ut/simple/artifact/1.0/artifact-1.0.jar * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenResolverModule.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/VersionsMetadataGenerator.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/VersionsMetadataGeneratorFactory.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/VersionRangeResultFilter.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/MavenAetherModule.java * (add) maven-resolver-provider/src/main/java/org/apache/maven/repository/internal/DefaultModelCache.java * (delete) maven-aether-provider/src/main/java/org/apache/maven/repository/internal/DefaultVersionRangeResolver.java * (add) maven-resolver-provider/src/test/resources/repo/ut/simple/artifact/maven-metadata.xml * (delete) maven-aether-
[jira] [Commented] (MNG-6110) Upgrade Aether to Maven Resolver 1.2
[ https://issues.apache.org/jira/browse/MNG-6110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15781611#comment-15781611 ] Hudson commented on MNG-6110: - SUCCESS: Integrated in Jenkins build maven-3.x #1476 (See [https://builds.apache.org/job/maven-3.x/1476/]) MNG-6110 updated introduction (hboutemy: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=65960ac18c8121648fe163612375a2ba5f4535c2]) * (edit) maven-resolver-provider/src/site/apt/index.apt > Upgrade Aether to Maven Resolver 1.2 > > > Key: MNG-6110 > URL: https://issues.apache.org/jira/browse/MNG-6110 > Project: Maven > Issue Type: Dependency upgrade > Components: Dependencies >Affects Versions: 3.3.9 >Reporter: Harald Wellmann >Assignee: Christian Schulte > Fix For: 3.4.0 > > > Replace Aether by Maven Resolver to make use of the latest bugfixes and > enhancements related to dependency collection. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (WAGON-480) Non-threadsafe HttpClientContext is shared between threaded use of HttpClientWagon
Michael Osipov created WAGON-480:
Summary: Non-threadsafe HttpClientContext is shared between
threaded use of HttpClientWagon
Key: WAGON-480
URL: https://issues.apache.org/jira/browse/WAGON-480
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http
Affects Versions: 2.11
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 2.12
The
[{{HttpClientContext}}|https://hc.apache.org/httpcomponents-client-ga/httpclient/apidocs/org/apache/http/client/protocol/HttpClientContext.html]
is used as an instance private object, populated only once during
{{connect()}}. The Wagon instance can be shared between multiple threads
causing any kind of side effects to the requests like failing auth or abnormal
redirects.
With the Jetty 8 upgrade of all tests several unit tests failed to authenticate.
This issue has been found during WAGON-474.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (WAGON-481) Senstive (auth) information is not cleared when HttpClientWagon is disconnected
Michael Osipov created WAGON-481:
Summary: Senstive (auth) information is not cleared when
HttpClientWagon is disconnected
Key: WAGON-481
URL: https://issues.apache.org/jira/browse/WAGON-481
Project: Maven Wagon
Issue Type: Bug
Components: wagon-http
Affects Versions: 2.11
Reporter: Michael Osipov
Assignee: Michael Osipov
Fix For: 2.12
{{AuthCache}} and {{CredentialsProvider}} are never cleared when
{{Wagon#disconnect()}} is called which may leave sensitive information in
memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (WAGON-481) Sensitive (auth) information is not cleared when HttpClientWagon is disconnected
[
https://issues.apache.org/jira/browse/WAGON-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated WAGON-481:
-
Summary: Sensitive (auth) information is not cleared when HttpClientWagon
is disconnected (was: Senstive (auth) information is not cleared when
HttpClientWagon is disconnected)
> Sensitive (auth) information is not cleared when HttpClientWagon is
> disconnected
>
>
> Key: WAGON-481
> URL: https://issues.apache.org/jira/browse/WAGON-481
> Project: Maven Wagon
> Issue Type: Bug
> Components: wagon-http
>Affects Versions: 2.11
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 2.12
>
>
> {{AuthCache}} and {{CredentialsProvider}} are never cleared when
> {{Wagon#disconnect()}} is called which may leave sensitive information in
> memory.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (WAGON-474) Upgrade and revise all tests for Jetty 8
[ https://issues.apache.org/jira/browse/WAGON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-474: - Attachment: TEST-org.apache.maven.wagon.providers.http.HttpWagonTest.xml Here is Surefire XML depicting the race conditions between main thread and Jetty's qtp thread. > Upgrade and revise all tests for Jetty 8 > > > Key: WAGON-474 > URL: https://issues.apache.org/jira/browse/WAGON-474 > Project: Maven Wagon > Issue Type: Task >Affects Versions: 2.11 >Reporter: Michael Osipov >Assignee: Michael Osipov > Fix For: 2.12 > > Attachments: > TEST-org.apache.maven.wagon.providers.http.HttpWagonTest.xml > > > All test code currently relies on Jetty 6 which is ten years old and not > really represents today's servers and repository managers like Sonatype Nexus. > Tasks: > * Revise all code for Jetty 8.1 (last Java 1.6 version) > * Check for inconsistencies and errors > * Fix constant test failures on non-Windows platforms which are likely due to > bad code -- This message was sent by Atlassian JIRA (v6.3.4#6332)
