Is there some compelling reason why these files are created outside of
*target*?  The idea of *target* is to be home to all artifacts of the
build process.

________________________________

Curt Yanko | Continuous Integration Services | UnitedHealth Group IT 
Making IT Happen, one build at a time, 600 times a day
 

> -----Original Message-----
> From: anders.g.ham...@gmail.com 
> [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar
> Sent: Friday, December 03, 2010 3:22 AM
> To: Maven Users List
> Subject: Re: Catch 22 with clean phase
> 
> Phillip, you should notice (once again) that fighting Maven 
> best practice is causing you extra trouble. You should create 
> a mojo that cleans these files.
> It can be created smart enough to detect if anything needs to 
> be done or not. Put the mojo in the plugin that creates the 
> files in the first please, and you'll have everything nicely 
> packaged together.
> Then, if you find yourself configuring several maven projects 
> in a similar manner. where you're binding this plugin to 
> create files and then clean them, you should start to think 
> about creating your own packaging type. All of a sudden 
> you're following Maven best-practice and you (and every other 
> user in your corp doing the same thing) will think: "Hey, 
> Maven rocks!" As it does, if you don't fight it!
> 
> /Anders
> On Fri, Dec 3, 2010 at 02:12, Brian Topping 
> <topp...@codehaus.org> wrote:
> 
> >
> > On Dec 2, 2010, at 7:05 PM, Wayne Fay wrote:
> >
> > >> Ok, so this is working great now, except for one 
> problem.  It runs 
> > >> great the first time, but if I run "mvn clean" a second 
> time, the 
> > >> batch file is not there so it can't call it and it 
> returns with an 
> > >> error.
> > >
> > > Turn your batch file into a plugin and these problems 
> will magically 
> > > go
> > away.
> >
> > I have to agree here.  Creating a plugin is easy, and we 
> will refund 
> > your purchase price of Maven if you do not find the Plugin 
> interface 
> > to be the easiest one you've ever seen.
> > 
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
> 

This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.


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

Reply via email to