I agree, I'd suggest an archetype is more useful here. On 06/04/2011, at 10:06 PM, Benson Margulies wrote:
> One interesting problem here is ossrh. Since you can only have one > parent, people will have to choose between this one and the ossrh > parent. Or you could make two of this. Or you could just make this an > archetype? > > On Wed, Apr 6, 2011 at 7:03 AM, Jochen Wiedmann > <jochen.wiedm...@gmail.com> wrote: >> Hi, >> >> this proposal isn't related to a plugin. Nevertheless, my personal >> feeling is that Mojo would be a good place for it. >> >> In Maven 3, a lot of improvements have been made. Unfortunately, this >> includes some that I personally consider questionable, in particular >> the decision to remove deployment of site.xml by default and removal >> of most of the wagon plugins. It has been required to add code >> handling these to almost any project I am aware of, either directly or >> indirectly by updating the parent. >> >> I am aware of some other settings, which I would personally call >> recommended, like setting the source encoding to UTF8, specifying a >> directory src/main/filtered-resources, adding goals like >> source:jar-no-fork and javadoc:jar to the release profile and other >> stuff like that. These are basically constant upon every project I am >> aware of. Nevertheless, they need to be handled in every project >> again, thus cluttering the pom, which should be as plain and simple as >> possible. >> >> My idea would be to provide a parent pom for other projects, not for >> Mojo. We might call it simple-project-parent, or something similar. >> The idea is that new projects, which live outside Mojo might derive >> from it. Stuff like plugin version numbers etc. would stay outside, >> because these are definitely project dependent. >> >> WDYT? >> >> Thanks, >> >> Jochen >> >> -- >> I Am What I Am And That's All What I Yam (Popeye) >> >> --------------------------------------------------------------------- >> To unsubscribe from this list, please visit: >> >> http://xircles.codehaus.org/manage_email >> >> >> > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
