You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by jiangshachina <ji...@gmail.com> on 2006/11/02 10:44:33 UTC
Design projects?
Up to now, I just see the project structure as following,
project-super
|--pom.xml
|--project-app
|--pom.xml
|--content of project-app
|--project-webapp
|--pom.xml
|--content of project-webapp
|--project-ejb
|--pom.xml
|--content of project-ejb
......
Can I have more "deep" structures?
And can I have any content between projects, expects pom.xml?
For instance,
project-super
|--pom.xml
|--other content of project-super
|--project-app
|--pom.xml
|--content of project-app
a cup of Java, cheers!
Sha Jiang
--
View this message in context: http://www.nabble.com/Design-projects--tf2558714s177.html#a7130501
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Design projects?
Posted by Arnaud Bailly <ab...@oqube.com>.
jiangshachina <ji...@gmail.com> writes:
> Hello Arnaud,
> In your opinion, the directory(pom.xml located) of high-grade
> project
Not really my "opinion" :-) The packaging "pom" is enforced for
multi-modules project and this packaging does not goes through al
phases of the build.
> doesn't include any "real" files/dirs, which would be used for producing.
> We shall keep the dir clean(excepts some files for sitting). Because Maven
> cann't care the dir as standard/normal proejct.
> Can I understand your mind as above?
Understanding my mind is something I myself find sometimes difficult
so maybe these words are a bit strong :-) Anyway, that's almost right:
top-level (or intermediate nodes in the tree) do not by default
compile and package things. You can however decide to do so by binding
plugins to the build lifecycle of the project.
One example here:
http://www.mail-archive.com/users@maven.apache.org/msg54404.html
HTH
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Design projects?
Posted by jiangshachina <ji...@gmail.com>.
Hello Arnaud,
In your opinion, the directory(pom.xml located) of high-grade project
doesn't include any "real" files/dirs, which would be used for producing.
We shall keep the dir clean(excepts some files for sitting). Because Maven
cann't care the dir as standard/normal proejct.
Can I understand your mind as above?
a cup of Java, cheers!
Sha Jiang
Arnaud Bailly-3 wrote:
>
> jiangshachina <ji...@gmail.com> writes:
>
>> Can I have more "deep" structures?
>> And can I have any content between projects, expects pom.xml?
>> For instance,
>> project-super
>> |--pom.xml
>> |--other content of project-super
>> |--project-app
>> |--pom.xml
>> |--content of project-app
>>
>
> To the best of my knowledge, project with children must have packaging
> type pom. This does not mean that you cannot put content in them, but
> you won't get any artifact and lifecycle is different. I put
> documentation (ie. src/site hierarchy) in it.
>
> HTH
>
> --
> OQube < software engineering \ génie logiciel >
> Arnaud Bailly, Dr.
> \web> http://www.oqube.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Design-projects--tf2558714s177.html#a7150237
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Design projects?
Posted by Arnaud Bailly <ab...@oqube.com>.
jiangshachina <ji...@gmail.com> writes:
> Can I have more "deep" structures?
> And can I have any content between projects, expects pom.xml?
> For instance,
> project-super
> |--pom.xml
> |--other content of project-super
> |--project-app
> |--pom.xml
> |--content of project-app
>
To the best of my knowledge, project with children must have packaging
type pom. This does not mean that you cannot put content in them, but
you won't get any artifact and lifecycle is different. I put
documentation (ie. src/site hierarchy) in it.
HTH
--
OQube < software engineering \ génie logiciel >
Arnaud Bailly, Dr.
\web> http://www.oqube.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org