On 12/29/05, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
> That is what I'm ending up doing as well. Really, Maven needs another
> property like "topdir" that is the directory of the top most parent
> pom.xml. Thus, we could base things off of that if needed.
We plan to include the ability to hav
http://maven.apache.org/maven-model/maven.html has all the possible tags in
the POM and following that are some descriptions of what they are for. Its
sort of like wandering in a dark cave but there is some useful stuff there.
-- Lee
On 12/28/05, Daniel Kulp <[EMAIL PROTECTED]> wrote:
>
>
> That
That is what I'm ending up doing as well. Really, Maven needs another
property like "topdir" that is the directory of the top most parent
pom.xml. Thus, we could base things off of that if needed.
Actually, is there a list of properties that we CAN use listed online
someplace?
Dan
On We
Since I use Eclipse I have to sort of flatten out the project structure. So
the structure looks like this:
base
+ build (this is parent, children are ../ear and ../war1 and so forth)
+ ear (parent is ../build)
+ war1 (ditto)
+ war2
+ jar1
+ jar2
I just put the common files, license.txt, checkstyl
Two idea :
- Refactor in order to be able to place those resources into a separated
module used as a dependency by the other "subproject".
- If not possible, see if you can use links into your repository (need unix
like platform)
> -Original Message-
> From: Daniel Kulp [mailto:[EMAIL
