You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by golfradio <gr...@gmail.com> on 2010/02/25 16:07:04 UTC

Custom Archetype configuration

I have a multi-module maven project. The sub modules are pluggable apps that
can be loaded in the application framework at runtime. I have created a
custom archetype for creating such a new app. Since these apps run in the
context of an enterprise framework, I need to enforce certain properties
like the groupId and the packages name. 

How do I go about locking down these properties? The archetype plugin always
allows the end user to override the default properties.

Any help is appreciated. I apologize if this has been answered in any
previous threads. I searched but could not find anything.

Thanks.
-- 
View this message in context: http://old.nabble.com/Custom-Archetype-configuration-tp27714453p27714453.html
Sent from the Maven - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: Custom Archetype configuration

Posted by Wayne Fay <wa...@gmail.com>.
> custom archetype for creating such a new app. Since these apps run in the
> context of an enterprise framework, I need to enforce certain properties
> like the groupId and the packages name.

I'm not aware of any way to lock down these properties. You could file
an issue in Jira so someone could consider adding it in a future
release.

Perhaps this could be managed in your MRM (Nexus, Archiva, etc) instead?

Wayne

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org