Hello Matthias,
you are not doing wrong stuff the destDir for the tld stuff has changed
from src/main/resources/META-INF to target/classes/META-INF.
You can delete the old META-INF in src/main/resources.
Generated sources, classes... should only created in the 'target' dir :-).
Best Regards
Bernd
Matthias Wessendorf schrieb:
Perhaps I was doing some wrong stuff,
in sandbox (and tomhawak) I have the folder /src/main/resource/META-INF
but the META-INF is not in svn (subclipse plugin for Eclipse told me),
so I guess it is *generated* during build...
however "mvn clean" doesn't remove the folders.
Can anyone clearify that I am doing (or not) wrong stuff ?
-Matthias
On 1/3/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
Do we even need the parent tags? For certain projects (tomahawk) for
instance, we want to be able to compile independent of myfaces, or
more accurately, we want the option to do so.
What advantages does the parent tag give us (other then sharing
dependencies?) I'm not sure we're even taking advantage of the
dependency thing anyways. I'm still finding my way around here ...
Sean
On 1/3/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 1/3/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
So 1.1.2 is defined in only the parent POM? What if you want to build
tomahawk by itself (without the parent pom?)
You can't build it without the parent pom-- the build will fail
because that pom is as much a 'dependency' as any of the jars you need
on the classpath.
I think this is a tricky problem. Also, if we ever release different
version numbers for the subprojects won't this cause a problem?
Once 1.1.2 is in the repository, the versioned parent pom will be
there as well, and Maven will find it.
I don't see any <relativePath> tags in the <parent> sections. If you
add them, Maven will look locally (on the filesystem) for the parent
pom as well as checking the repository.
Struts Action looks like this:
<parent>
<groupId>struts</groupId>
<artifactId>struts-build</artifactId>
<version>1.3.0-SNAPSHOT</version>
<relativePath>build/pom.xml</relativePath>
</parent>
The 'build' directory is external, included under each module. If
you're not doing that, you can use:
<relativePath>../build/pom.xml</relativePath>
I think that might help the IDE config file generation, though I'm not sure.
--
Wendy
--
Matthias Wessendorf
Zülpicher Wall 12, 239
50674 Köln
http://www.wessendorf.net
mwessendorf-at-gmail-dot-com
--
Dipl.-Ing. Bernd Bohmann - Atanion GmbH - Software Development
Bismarckstr. 13, 26122 Oldenburg, http://www.atanion.com
phone: +49 441 4082312, mobile: +49 173 8839471, fax: +49 441 4082333
