You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Brinker, Don-NONEMP" <db...@collegeboard.org> on 2011/04/11 05:08:17 UTC
archetype:generate as an authorized user?
Hey all,
We've got a server in place at my company serving up local artifacts. To secure the server (and not expose our stuff anymore than we have to) we have users defined and anonymous access disabled. So far so good - we can query and deploy artifacts just fine.
Now here's where things get interesting: archetype:generate doesn't seem to pay any attention to my settings.xml. The server logs that it received an unauthenticated user request for the catalog. I was HOPING generate would match the archetypeCatalog URL to the URL of a repository in my settings, but no luck. Is there any way to specify the server when calling archetype:generate? I'd really rather NOT reduce security to be able to use archetypes, if it can be avoided.
(If it matters, we're using Artifactory, but since the problem is coming from the client, I suspect the same problem would happen with Nexus or anything else).
Apologies if this is a FAQ, but I didn't see anything about it after a bit of beating the Internet with the Google Stick, sooooo...
Thanks
- Don
Re: archetype:generate as an authorized user?
Posted by Jesse Glick <je...@oracle.com>.
On Sun, Apr 10, 2011 at 11:08 PM, Brinker, Don-NONEMP
>> I was HOPING generate would match the archetypeCatalog URL to the URL of a repository in my settings, but no luck.
On 04/11/2011 01:40 PM, Wendy Smoak wrote:
> It doesn't match by url, it matches by repository id. Is there a way to send a repo id in addition to the url?
The FAQ claims that ${artifactId}-repo will be used as a repository ID, but this does not sound like a usable system; if you have dozens of archetypes defined in your
work environment, you would have to create dozens of near-identical repository definitions in every developer's settings.xml, on top of what other Maven usage already
requires!
You would reasonably expect that archetype:generate would look up things like authentication settings based on archetypeRepository and/or archetypeCatalog using a reverse
URL -> ID match, or offer an explicit repository ID parameter.
Don's problem reminds me of a bug I came across (but relating to mirrors rather than authentication): http://jira.codehaus.org/browse/ARCHETYPE-366
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: archetype:generate as an authorized user?
Posted by Wendy Smoak <ws...@gmail.com>.
On Sun, Apr 10, 2011 at 11:08 PM, Brinker, Don-NONEMP
<db...@collegeboard.org> wrote:
> We've got a server in place at my company serving up local artifacts. To secure the server (and not expose our stuff anymore than we have to) we have users defined and anonymous access disabled. So far so good - we can query and deploy artifacts just fine.
>
> Now here's where things get interesting: archetype:generate doesn't seem to pay any attention to my settings.xml. The server logs that it received an unauthenticated user request for the catalog. I was HOPING generate would match the archetypeCatalog URL to the URL of a repository in my settings, but no luck.
It doesn't match by url, it matches by repository id. Is there a way
to send a repo id in addition to the url?
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: archetype:generate as an authorized user?
Posted by Wayne Fay <wa...@gmail.com>.
> Now here's where things get interesting: archetype:generate doesn't seem to pay any attention to my settings.xml. The server logs that it received an unauthenticated user request for the catalog. I was HOPING generate would match the archetypeCatalog URL to the URL of a repository in my settings, but no luck. Is there any way to specify the server when calling archetype:generate? I'd really rather NOT reduce security to be able to use archetypes, if it can be avoided.
I've never had any need for such a feature -- to be honest, I don't
use archetypes much either. Does Artifactory allow you to set up a
"public" repo/group that has no user security, and then you could just
publish your archetypes there? The rest of your repo would still be
secured etc.
Wayne
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: archetype:generate as an authorized user?
Posted by Justin Edelson <ju...@justinedelson.com>.
On Sun, Apr 10, 2011 at 11:08 PM, Brinker, Don-NONEMP
<db...@collegeboard.org> wrote:
> Hey all,
>
> We've got a server in place at my company serving up local artifacts. To secure the server (and not expose our stuff anymore than we have to) we have users defined and anonymous access disabled. So far so good - we can query and deploy artifacts just fine.
>
> Now here's where things get interesting: archetype:generate doesn't seem to pay any attention to my settings.xml. The server logs that it received an unauthenticated user request for the catalog. I was HOPING generate would match the archetypeCatalog URL to the URL of a repository in my settings, but no luck. Is there any way to specify the server when calling archetype:generate? I'd really rather NOT reduce security to be able to use archetypes, if it can be avoided.
>
> (If it matters, we're using Artifactory, but since the problem is coming from the client, I suspect the same problem would happen with Nexus or anything else).
>
> Apologies if this is a FAQ, but I didn't see anything about it after a bit of beating the Internet with the Google Stick, sooooo...
This is indeed a FAQ:
http://maven.apache.org/archetype/maven-archetype-plugin/faq.html#authentication
>
> Thanks
>
> - Don
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org