[jira] (MINVOKER-169) install goal with extraArtifacts will download things which are not needed
Karl-Heinz Marbaise created MINVOKER-169:
Summary: install goal with extraArtifacts will download things
which are not needed
Key: MINVOKER-169
URL: https://jira.codehaus.org/browse/MINVOKER-169
Project: Maven Invoker Plugin
Issue Type: Improvement
Affects Versions: 1.8
Reporter: Karl-Heinz Marbaise
I have create integration test which use extraArtifacts
org.apache.maven.plugins:maven-failsafe-plugin:2.17:maven-plugin which will
download things like this:
{code}
Downloaded:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/plugins/maven-surefire-plugin/2.17/maven-surefire-plugin-2.17-site-source.zip
(40 KB at 92.7 KB/sec)
{code}
This looks wrong.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (ARCHETYPE-460) archetype:generate does not use settings.xml when archetype is in repository with restricted access
heapifyman created ARCHETYPE-460: Summary: archetype:generate does not use settings.xml when archetype is in repository with restricted access Key: ARCHETYPE-460 URL: https://jira.codehaus.org/browse/ARCHETYPE-460 Project: Maven Archetype Issue Type: Bug Components: Generator Affects Versions: 2.2 Environment: Apache Maven 3.2.2 Java version: 1.8.0_05, vendor: Oracle Corporation Default locale: de_DE, platform encoding: Cp1252 OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" Reporter: heapifyman Priority: Blocker I have an archetype deployed to an Artifactory repository with restricted access. I have defined the with , and in my settings.xml. When I run "mvn archetype:generate -DarchetypeRepository=" I get "Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Not authorized , ReasonPhrase:Unauthorized." Apparently, archetype:generate does not take into account the access rights defined in settings.xml -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (ARCHETYPE-460) archetype:generate does not use settings.xml when archetype is in repository with restricted access
[ https://jira.codehaus.org/browse/ARCHETYPE-460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=349184#comment-349184 ] heapifyman commented on ARCHETYPE-460: -- FYI, I have read: http://maven.apache.org/archetype/maven-archetype-plugin/faq.html#authentication I know I can add a to my settings.xml with my-archetype-id-repo and the needed username and password. However, this is hugely impractical for 2 reasons: 1. I have to add one entry for each archetype to my settings.xml 2. Every developer needs to do that. Manually! There does not seem to be a way to automate this... If archetype plugin cannot figure out the right credentials automatically, wouldn't it be possible to add another parameter like "archetypeRepositoryId" so I can pass in the correct repository ID which points to the credentials in settings.xml? > archetype:generate does not use settings.xml when archetype is in repository > with restricted access > --- > > Key: ARCHETYPE-460 > URL: https://jira.codehaus.org/browse/ARCHETYPE-460 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Affects Versions: 2.2 > Environment: Apache Maven 3.2.2 > Java version: 1.8.0_05, vendor: Oracle Corporation > Default locale: de_DE, platform encoding: Cp1252 > OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos" >Reporter: heapifyman >Priority: Blocker > > I have an archetype deployed to an Artifactory repository with restricted > access. > I have defined the with , and in my > settings.xml. > When I run > "mvn archetype:generate > -DarchetypeRepository=" > I get > "Caused by: org.apache.maven.wagon.authorization.AuthorizationException: Not > authorized , ReasonPhrase:Unauthorized." > Apparently, archetype:generate does not take into account the access rights > defined in settings.xml -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (SCM-763) Password masking on linux does not work
Tobias Kalmes created SCM-763: - Summary: Password masking on linux does not work Key: SCM-763 URL: https://jira.codehaus.org/browse/SCM-763 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-svn Affects Versions: 1.9 Environment: Jenkins 1.502 on a SLES11 Reporter: Tobias Kalmes Passwords are not masked in the log output on Linux machines. The masking works as intended on Windows machines. On linux machines tho the password is printed in clear text. This seems to be a problem due to the additional single quotes that are added around the parameters on linux machines. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-343) Link to shared area is wrong
Karl-Heinz Marbaise created MSHARED-343: --- Summary: Link to shared area is wrong Key: MSHARED-343 URL: https://jira.codehaus.org/browse/MSHARED-343 Project: Maven Shared Components Issue Type: Bug Components: maven-reporting-exec Affects Versions: maven-reporting-exec-1.2 Reporter: Karl-Heinz Marbaise Priority: Minor On the page of the http://maven.apache.org/shared/maven-reporting-exec/ the link to the maven shared components shows the following: http://maven.apache.org/shared/maven-shared-components-LATEST/index.html which is wrong. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MNG-5605) ssh-wagon hangs
[ https://jira.codehaus.org/browse/MNG-5605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reopened MNG-5605: - I'll reopen until some one verifies this as fixed with Maven 3.2.2. > ssh-wagon hangs > --- > > Key: MNG-5605 > URL: https://jira.codehaus.org/browse/MNG-5605 > Project: Maven > Issue Type: Bug > Components: Deployment >Affects Versions: 3.2.1 >Reporter: Frank Cornelis >Priority: Blocker > > When releasing (using maven-release-plugin) via Maven 3.1.1 everything works > as expected. When doing the same via Maven 3.2.1, ssh-wagon all of the sudden > hangs on the second ssh upload. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
