not really. Look at the configuration of the build element for example,
you can customize source and resource directories there.
The benefit of using the maven standard directory layout [1] is that things
Just Work without the need for extra configuration everywhere. This is
especially helpful
You can specify in your pom what the directory structure looks like.
Inside build, specify sourceDirectory, testSourceDirectory, etc..
build
sourceDirectorysrc/sourceDirectory
scriptSourceDirectory/
testSourceDirectorytest/testSourceDirectory
Engineer
JTeam b.v.
-Original Message-
From: Jorg Heymans [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 10:19 AM
To: Maven Users List
Subject: Re: Directory structure
not really. Look at the configuration of the build element for example,
you can customize source and resource
On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote:
Furthermore, there might be some plugins which don't use the elements from build
and therefore might not work correctly with a different directory structure. Although I
haven't encountered any yet, it might be another reason for following the
Maybe, but I haven't encountered any problems yet.
Roald Bankras
Software Engineer
JTeam b.v.
-Original Message-
From: JeffM [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 11:19 AM
To: Maven Users List
Subject: Re: Directory structure
On 6/14/06, Roald Bankras [EMAIL
.
-Original Message-
From: JeffM [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 14, 2006 11:19 AM
To: Maven Users List
Subject: Re: Directory structure
On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote:
Furthermore, there might be some plugins which don't use the elements from build
11:49 AM
To: Maven Users List
Subject: Re: Directory structure
I'm finding it difficult to convince my colleagues why we should
refactor our codebase to introduce the M2 recommended directory
structure :(
On 6/14/06, Roald Bankras [EMAIL PROTECTED] wrote:
Maybe, but I haven't encountered any
Could you please provide a sample directory structure similar to what
you'll be using?
Matt Osborne
-Original Message-
From: Lutz Fechner [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 17, 2006 9:32 AM
To: users@maven.apache.org
Subject: Directory Structure
Hi,
I'm new to using
It will be the place for m2.
I'll propose to move the default directory in the next release of the xdoc
plugin.
We'll advice usrs to move their sources if possible or to define themself
the maven.docs.src=${basedir}/xdoc.
I'll propose also to move genapp templates to use this new layout.
Hi Arnaud
Ah, so if I got your answer right, it will be then {basedir}/xdoc and
not even what is now said in the convention document presently published
on the maven site?
thx!
Eric.
Arnaud HERITIER wrote:
It will be the place for m2.
I'll propose to move the default directory in the next
Eric Giguère wrote:
Ah, so if I got your answer right, it will be then {basedir}/xdoc and
not even what is now said in the convention document presently
published on the maven site?
No, it will be ${basedir}/src/site/xdoc like it is said on the maven
site. There is a note on this on the
svn propedit svn:ignore .
in the directory of the project and add target to that list
it's like .cvsignore.
Cheers,
Brett
On 7/30/05, Josh [EMAIL PROTECTED] wrote:
Hi. I'm new to both Maven and Subversion. I would like to put my
entire project under version control (that is, including my
This is working beautifully, thanks guys!
Josh
On 7/29/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
On Fri, Jul 29, 2005 at 02:49:39PM -0700, Josh wrote:
Hi. I'm new to both Maven and Subversion. I would like to put my
entire project under version control (that is, including my
Jesse,
Thanks for the suggestion.
Did you get your structure to work in Maven 2? In particular, are you using the
EAR patch from jira.codehaus.org MNG-576 for EAR lifecycle?
Manny
Thanks Jesse,
I will give it a go. I like the fact that you separate out the servlets as you
have. Can you package them into the appropriate web.xml/WAR when needed? It
seems a nice way to pick which servlets go with which WARs rather than putting
everything in a /webapp directory.
I'll try
I'm curious also to know if anyone from the Maven team can comment on Ken's
project directory structure for Maven 2. We are in a similar predicament
with Maven 2 with mutiple applications with multiple EARs. There doesn't
seem to be enough depth on the
this is basically my goal at the moment in regards to m2
root/
root/core
root/war1 - uses core, lib1
root/war2 - uses core, lib1, lib2
root/war3
root/ejb1 - uses lib1, core
root/ejb2 - uses lib2, core
root/lib1
root/lib2
root/ear1 - uses war1, war2, ejb1
root/ear2 - uses war3, ejb2
basically
I think you answered your own question. The only reason I would suggest
using the flattened structure is if you are using eclipse as your IDE. I
use eclipse for all of my projects and the flattened structure makes a lot
of sense to me.
So, if you're not using eclipse there's no reason to layout
Hi Ryan,
Sonnek, Ryan wrote on Friday, March 19, 2004 4:30 PM:
I think you answered your own question. The only reason I
would suggest using the flattened structure is if you are
using eclipse as your IDE. I use eclipse for all of my
projects and the flattened structure makes a lot of sense
master project)
/myproject/subproject2/project.xml (extends master project)
-Original Message-
From: Jörg Schaible [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 9:51 AM
To: Maven Users List
Subject: RE: Directory structure for projects subprojects - nested or
parallel?
Hi
now, in eclipse you CAN NOT mount 3 projects; one for the parent, and one
for each subproject. This is because the files for the subprojects are
already included in the parent project. If your subprojects extend a
project.xml in parrellel with them, you won't run into this problem.
Ex:
See inline response:
-Original Message-
From: Michael MATTOX [mailto:[EMAIL PROTECTED]
Sent: Friday, March 19, 2004 10:25 AM
To: Maven Users List
Subject: RE: Directory structure for projects subprojects - nested or
parallel?
now, in eclipse you CAN NOT mount 3 projects; one
It will not work to have this mounted as an eclipse project because of the
problems I explained before. If you are using eclipse as your CVS client,
you will likely want this mounted as an eclipse project in order to keep
info synchronized. If you are using a different CVS client, and
: RE: Directory structure for projects subprojects - nested
or parallel?
Hi Ryan,
Sonnek, Ryan wrote on Friday, March 19, 2004 4:30 PM:
I think you answered your own question. The only reason I would
suggest using the flattened structure is if you are using eclipse as
your IDE. I use
gr Hit sent ...
Sonnek, Ryan wrote on Friday, March 19, 2004 5:02 PM:
Ok,
In order to use maven in a multiproject setting, the child
projects extend the parent project. The problem lies in
having the parent project mounted in eclipse as a project
with a child project underneath. It would
What doesn't work is when you run maven eclipse from the command line
maven re-writes your .classpath and .project files. If you run:
maven -Dgoal=eclipse multiproject:goal it will supposedly look into
each directory and then build the .classpath based on each sub project's
project.xml file.
Michael MATTOX wrote on Friday, March 19, 2004 5:25 PM:
now, in eclipse you CAN NOT mount 3 projects; one for the parent, and
one for each subproject. This is because the files for the
subprojects are already included in the parent project. If your
subprojects extend a project.xml in
Hi Charles,
Charles N. Harvey III wrote on Friday, March 19, 2004 5:46 PM:
What doesn't work is when you run maven eclipse from the command
line maven re-writes your .classpath and .project files. If you run:
maven -Dgoal=eclipse multiproject:goal it will supposedly
look into each directory
28 matches
Mail list logo
