The "goals" in Maven are either phases of the lifecycle, or a direct execution of a plugin:goal. You can't create new phases yourself, but you can make plugins and bind them to the phases. You might want to also take a look at http://www.sonatype.com/book
You can do what you want from a CI system, but not in the same way you would approach it with Ant. Rather than a super-goal, you would make a profile that adds additional plugins to the existing build lifecycle. -----Original Message----- From: simon [mailto:[EMAIL PROTECTED] Sent: Sunday, June 15, 2008 8:16 AM To: Maven Users List Subject: Re: How to build a own goal On Sun, 2008-06-15 at 03:26 -0700, chokdee wrote: > Hello Tim > > thanks for the quick answer. > Normally I use a masterbuild target for do all the necessary stuff for > cruisecontrol. > So, run unit test with emma, make javadoc etc. > I saw that I can do it with calling more targets at once in cruisecontrol. > But i prefer to write a goal for that. > > Another sinple problem I have is, that I want to make a copy job to deploy > the jar to a non maven project. > In ant: > <target name="copy-to-otherproject"> > <copy todir="../anotherproject/lib" > > ... > > Can you help? I just have some general advice for you. Maven is not ant. It is nothing like ant. Ant is a full programming language, with some built-in functions that are convenient for compiling code. Maven is a build tool that has some configurable behaviour. Therefore you cannot just "port" from ant to maven. I suggest you read the maven books carefully, in particular the section about the maven "lifecycle". Regards, Simon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
