Ok. I just made a quick test: 1.0-alpha-1 (as shown in the examples)
seems to be to old and doesn't work with the current maven version.
I found a snapshot version 1.0-beta-1-SNAPSHOT deployed on the codehaus
snapshot repository [1]. This version seems to work. To be able to use
the snapshot you need to declare the snapshot repository somewhere as
shown here [2].
Hope this helps
-Tim
[1]
http://snapshots.repository.codehaus.org/org/codehaus/mojo/xdoclet-maven-plugin/1.0-beta-1-SNAPSHOT/
[2] http://mojo.codehaus.org/using-sandbox-plugins.html
Vaidya, Supriya A (US - Chicago) schrieb:
Thanks Tim!
I modified by EJB's pom.xml to contain the following -
<plugin>
<artifactId>xdoclet-maven-plugin</artifactId>
<groupId>org.codehaus.mojo</groupId>
<version>1.0-alpha-1</version>
<executions>
<execution>
<goals>
<goal>xdoclet</goal>
</goals>
<phase>generate-sources</phase>
</execution>
</executions>
</plugin>
However, when I run the mvn xdoclet:xdoclet command, I get the following
error:
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO] null
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.AbstractMethodError
at
org.codehaus.plexus.component.configurator.converters.ComponentValueS
etter.configure(ComponentValueSetter.java:247)
at
org.codehaus.plexus.component.configurator.converters.composite.Objec
tWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java
:137)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator
.configureComponent(BasicComponentConfigurator.java:56)
I visited a few posts and find that users in '05 when the plugin was
first released, had to modify the xdoclet's POM in the respository. Is
this still the case? Or am I using the wrong version? Also, WHICH POM
should I be modifying if necessary in the respository? There are loads
of subdirectories of the xdoclet repository...
-----Original Message-----
From: Tim Kettler [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 15, 2007 9:51 AM
To: Maven Users List
Subject: Re: Generating EJB home/remote interfaces with maven
Hi,
the maven-ejb-plugin doesn't help you to generate your home/remote
interfaces. It is just for packaging your poject to a valid ejb jar.
As far as I know, there is no ejbgen-plugin for maven 2. The only one
I'm aware of [1] is for maven 1. However, you should be able to use
xdoclet [2] and the xdoclet-plugin [3] to do what you want.
-Tim
[1] http://www.codeczar.com/products/maven-ejbgen-plugin/
[2] http://xdoclet.sourceforge.net/xdoclet/index.html
[3] http://mojo.codehaus.org/xdoclet-maven-plugin/overview.html
Vaidya, Supriya A (US - Chicago) schrieb:
Hi:
Is there an equivalent to ejbGen in Maven-ejb plugins? How do I use
it?
If you could point me to any available documentation, that would be
fine
too... I tried the following:
1. In my EJB's pom.xml - I use the maven-ejb-plugin.
2. My resources directory in teh EJB project contains the ejb-jar.xml
and teh weblogic-ejb-jar.xml, which mentions the home and remote
interface names.
3. In my project root, I run the mvn install command
This command creates teh EAR with teh EJB jar and the WAR files, but
does not generate any EJB stubs. How do I trigger this?
This message (including any attachments) contains confidential
information intended for a specific individual and purpose, and is
protected by law. If you are not the intended recipient, you should
delete this message.
Any disclosure, copying, or distribution of this message, or the
taking of any action based on it, is strictly prohibited. [v.E.1]
---------------------------------------------------------------------
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]
