Look at the Maven SuperPOM  (
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html
#Super_POM ) since that is where the *defaults* come from.

In the start of the build section properties are set for where source
and test code is plus some other items. I put all of those, as-is but
commented out into the our Maven *template* we provide on the assumption
that Maven is easy once you know what drives what. ;-)

________________________________

Curt Yanko | Continuous Integration Services
Making IT Happen, one build at a time


-----Original Message-----
From: benxs [mailto:[email protected]] 
Sent: Friday, October 08, 2010 6:25 AM
To: [email protected]
Subject: How to use Maven with a different (=non-default) project
structure?


Assume I want (or have) to use a different project structure from the
built-in default project structure of Maven (=the one which is generated
by archetype:generate).

Where do I have to adjust maven config files resp. in pom.xml to be able
to use the new project structure?

Ben
--
View this message in context:
http://maven.40175.n5.nabble.com/How-to-use-Maven-with-a-different-non-d
efault-project-structure-tp3204372p3204372.html
Sent from the Maven - Users mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]


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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to