Ashley,
I understand what your are trying to achieve. The thing is, changing the
extension is not enough. Invoking such goals as 'install, deploy' needs your
project to be properly configured. Typically, even if you had the ability to
change the extension, the archive would still be deployed as a
I'm sure you have some wisdom to pass onto me but can't work out
the point you are making. Am I using the plugin configs inefficiently
and if so do you have an example for me?
I (think) we're in agreement that the war plugin does more than file
extension which has been the very problem for me.
H
Ashley,
We want to avoid that. Using the war plugin is not only a matter of file
extension. Your project needs to be defined properly.
Thanks,
Stéphane
On 11/19/05, Ashley Williams <[EMAIL PROTECTED]> wrote:
>
> Hi Stéphane, missed you response until now.
>
> webXml property works so first of al
Hi Stéphane, missed you response until now.
webXml property works so first of all I'm very pleased about that.
However this is a little bit hacky as I'm just conning the war plugin
to copy something
that is already in the right place for copying anyway.
The setting I was suggesting to was si
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 pack
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
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
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
p
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:
war
because this makes the war behaviour kick in and I get the following
error:
/WEB-INF
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 e
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 .w
11 matches
Mail list logo
