You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Sharma, Jaikumar" <ja...@barco.com> on 2006/04/19 12:43:12 UTC

Customized directory structure to produce artifacts / classes ?

Dear Maven Users!
 
M2 build produces standard directory structure as a result of  build
process, is it possible to override the same and customize ------- compile,
package, JAR, WAR, JavaDocs etc to the folder structure as per the
organization specific directory standard ? or is it customizable in POMs ?
 
Thanks for your help!
 
Regards, Jaikumar
 
 
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liability for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.

Re: Customized directory structure to produce artifacts / classes ?

Posted by Simon Kitching <sk...@apache.org>.
On Wed, 2006-04-19 at 12:43 +0200, Sharma, Jaikumar wrote:
> Dear Maven Users!
>  
> M2 build produces standard directory structure as a result of  build
> process, is it possible to override the same and customize ------- compile,
> package, JAR, WAR, JavaDocs etc to the folder structure as per the
> organization specific directory standard ? or is it customizable in POMs ?

Yes, Maven2 can be configured via the POM to handle just about any
directory structure. Of course that's more complicated than using the
standard structures, but it's not too bad.

See the documentation on the maven site for:
  <sourceDirectory>
  <testSourceDirectory>
  <outputDirectory>
  etc
as well as config attributes for specific plugins.

This page lists all the possible xml elements in a POM:
http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html

One thing you will find very hard to work against, though, is maven's
desire to create one "artifact" (eg jar or war) per pom.xml file. Even
that's possible to work around in some cases, but only with significant
effort. There are very good reasons for maven's approach here of course.
So in practice if you want to apply Maven to existing projects you are
likely to need to make at least some changes in the project structure.

If you're just starting with maven2 then there's a great maven2 book
available via the mergere.com site:
  http://www.mergere.com/products.jsp

Regards,

Simon



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