Hi Nidhi,
you need to be a little bit more specific. Wich files exactly are duplicated? Can you
please post the structure of the geneated ear. Also if you can post your actual pom's that
would be very helpful.
I absolutly don't have a clue when (or if) the patch gets applied. I'm just a maven user
like you :-) But if you create an account in jira you can vote for the issue to express
that you too are interrested that it gets applied.
Of course you can just get the sources of the ejb plugin from svn (it's available at
http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-ejb-plugin) just like you did
for the ejb3 and par plugins, then apply the patch to the sources and install the ejb
plugin to your local repo.
-Tim
Nidhi Tuli schrieb:
Hi Tim,
I tried using the plugins you gave me for par and ejb3 files. They
generate the *.ejb3 and *.par but it is including all the files in both
ejb3 and par.
The problem with ejb3 and par including all the files are that ear
contains the duplicate copy of EJBs and when it tries to deploy it tries
to deploy 2 times and hence throws "JNDI Name Already Bound" Exception.
Ideally par should only have persistence files(Entity Bean) and rest
should be in ejb3. Is there a way I can configure these plugins to only
include the wanted file?
Also when do you think the fix you did in maven-ejb-plugin for making
'ejb-jar.xml' will be made available?
Thanks
Nidhi
-----Original Message-----
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 07, 2006 11:53 AM
To: Maven Users List
Subject: Re: ejb3 plugin
Tim Kettler schrieb:
Hi Nidhi,
you can checkout the maven-ejb3-plugin vie svn from the maven sandbox
at:
http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-ejb3-plugin
you then probably also want the maven-par-plugin from:
http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-par-plugin
Once you have the plugins on your harddrive you can install them to
your
local repository by executing 'mvn install' in the project root
directories.
There is an attached zip file (test-prj.zip) at
http://jira.codehaus.org/browse/MNG-1723 which contains a very
minimalistic test project with an EJB3 project and an EAR project that
packages the EJB file. You can use that as an starting point for your
project.
However, according to the latest draft of the spec (see section 6.2 of
ejb-3_0-pfd-spec-persistence.pdf and chapter 19 of
ejb-3_0-pfd-spec-ejbcore.pdf)
Enterprise Beans are packaged in plain Jar files (not .ejb3 and .par).
So if you use an EJB3 implementation that implements the latest spec
(like the one from JBoss) you can use the 'standard' maven-ejb-plugin.
The only problem with this is that the plugin enforces the presence of
an 'ejb-jar.xml' file which is not needed with EJB3 if you use
annotations. I submitted a patch for the plugin
(http://jira.codehaus.org/browse/MEJB-6) to make the 'ejb-jar.xml'
optional but i don't know if this will be applyed in the near furure.
...applied in the near future.
Grmmph.
-Tim
Nidhi Tuli schrieb:
Hi,
I just started working on Maven 2 and trying to build my EJB3 project
using maven2. Any ideas what plug-in should I use? In one of the
articles I am advised to do ejb3 on the jar file which I created. The
package for that is suggested to be "maven-ejb3-plugin" with groupId
of
goal bindings "org.apache.maven.plugins". But I am not able to find
this
plugin?
Any suggestions?
Thanks
Nidhi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
