Hi Marcel,

Sorry I missed your response earlier, this list is going into overdrive!

Just in case i haven't framed my problem correctly: I'm using the xdoclet plugin to generate the descriptors and the source code under the target/ directory. So far
so good.

However the next step is to package these generated files into a war file and so I changed the packaging to 'war'. But the corresponding plugin demands the existence of a web.xml file under the src/ tree (ie not generated) otherwise it will fail thus stopping
my build in its tracks.

In other words I want xdoclet to handle all of my war/ejb generation needs and the only
thing I need at the packaging stage is a .war extension.

I suppose one option is to persuade xdoclet to generate to files under src/ and not target/ but this feels wrong - for example mvn clean wouldn't get rid of generated code then.

From memory here is my xdoclet snippet - not sure it helps because as I mentioned above
I believe the problem is at the packaging stage, not generate-sources.

            <configuration>
              <task>
                <ejbdoclet>
                  <fileset includes="**/*Servlet.java"/>
                  <deploymentdescriptor/>
                  <jbosswebxml contextroot="/trading" version="4.0"/>
                </ejbdoclet>
              </task>
            </configuration>


Thanks
- Ashley

On 15 Nov 2005, at 13:05, Marcel Dullaart wrote:


I totally agree with Stphane, you should *NOT* use the jar plugin to generate a war file.
But I think the xdoclet plugin is not correctly configured.
Can you send the configuration snippet in your pom.xml?
Kind regards / Mit freundlichem Gruss / Salutations cordiales,
Marcel Dullaart
 Marcel Dullaart - my.epoline®Java architect (Portal specialist)
EUROPEAN PATENT OFFICE
Patentlaan 2 - 2280HV Rijswijk (ZH) - Netherlands
Tel: +31 (0)70 340 41 68
Web: www.epoline.org | email: [EMAIL PROTECTED]



Stephane Nicoll <[EMAIL PROTECTED]> wrote on 15-11-2005 11:20:33:

> Well, if you are generating a WAR artifact, you *have to* use war packaging. > If we provide the ability to use the JAR plugin for that, we would have a > big messy Jar plugin with each and every features (war, ejb, rar, etc).
>
> If you are using XDoclet, that's fine, check the documentation of the war
> plugin and configure it properly:
> http://maven.apache.org/plugins/maven-war-plugin/ (see webXml configuration
> item).
>
> Hope it helps,
> Stéphane
>
>
>
> On 11/14/05, Ashley Williams <[EMAIL PROTECTED]> 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>
> > >>
> > >> Thanks
> > >> AW
> > >>
> > >> ---------------------------------------------------------------------
> > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> > >> For additional commands, e-mail: [EMAIL PROTECTED]
> > >>
> > >>
> > >
> > >
> > > --
> > > .::You're welcome ::.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> .::You're welcome ::.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to