Can't you hook up xdoclet to kick in earlier than the error would occur?
Ashley Williams on 14/11/05 22:28, wrote:
Yes the ear plugin seems to be doing its job fine.
However I need a way to make the web project generate a file with a
.war extension
so that it will be found ok.
I can't add the following tag:
<packaging>war</packaging>
because this makes the war behaviour kick in and I get the following
error:
..../WEB-INF/web.xml does not exist.
And of course I'm not providing one because I want xdoclet to generate
it for me.
I think the ideal solution would be to configure the maven-jar-plugin
to use a
different extension, but I'd have to branch the code on my machine and...
... I really wouldn't want to do that!!
Has anyone else come up against this problem?
Thanks
- AW
On 14 Nov 2005, at 12:29, Stephane Nicoll wrote:
Well, your war project should produce a war file. Is the packaging of
your
war project set to war? I am not sure it is related to the EAR plugin.
Hope it helps,
Stéphane
On 11/14/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
Has anyone had success on getting xdoclet to play nicely with the ear
plugin? I have a project set up that builds ejb then war and then ear
for both of them.
----project
----ejb (produces .jar)
----war (produces .jar - perhaps should produce .war)
----ear (looks for .war - perhaps should look for .jar)
The problem I'm having is that war (xdoclet/webdoclet) produces an
artifact with a .jar extension whereas the ear plugin looks for an
artifact with a .war extension. One idea I had was to configure the
jar plugin to generate an extension of my choosing for my xdoclet pom
but it looks as if .jar is hardcoded there.
<crosses fingers that this can be solved in under 20 keystrokes>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
