Bryan Stopp created ARCHETYPE-446:
-------------------------------------
Summary: Generate Mojo should use security for repository access
Key: ARCHETYPE-446
URL: https://jira.codehaus.org/browse/ARCHETYPE-446
Project: Maven Archetype
Issue Type: Bug
Components: Generator
Affects Versions: 2.2
Environment: Apache Maven 3.0.5
(r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 07:51:28-0600)
Maven home: C:\dev\tools\build\apache-maven-3.0.5
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk\7\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Reporter: Bryan Stopp
Priority: Blocker
Attachments: mvn.log
My organization uses Artifactory to host our repositories. It is secured
against unauthorized access. I have managed to expose the archetype-catalog.xml
file to public anonymous access, which allows me to access a custom archetype.
However whenever I attempt to select my custom archetype, I receive a message
stating that the archetype cannot be found. Using debug, i can see that the
Mojo is receiving an Unauthorized response from the remote system. While I
understand that the password configured in my settings.xml would not be used
for the 'vml-aem-archetype-repo', it should be used for the second resolving
entry 'central'.
The archetype resolver should use the same communication protocols, security
included, when resolving archetypes as the build tool uses for
resolving/dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
