It's a problem with the websites being generated on the SNAPSHOT.
JarModule is there only in EAR plugin 2.3 which is not yet released.
So far javaModule was used which was a weird name so we refactored it.
Anyway, you don't need to configure the EAR plugin like this at all.
You only need to specify artifacts in the modules configuration if you
want to customize the way it's bundled (URI, filename, context root
for a webapp, etc). If you use the defaulting, you don't need any
config at all.
HTH,
Stéphane
On 12/11/06, Randall Fidler <[EMAIL PROTECTED]> wrote:
Hello,
I found part of the issue… it the EJB projects pom I had the
build type set as JAR and the dependency entry in the pom which was building
the EAR also listed the import as a jar… when I switched both to 'ejb'
(package and dependency type) things started working a little better but
only for the ejb entry.
Now that the ejb works, when I try using the jarModule:
<jarmodule>
<groupId>myGroup</groupId>
<artifactId>my.commons</artifactId>
</jarmodule>
It complains when I try to use the ejbModule and jarModule but runs fine
with only ejbModule. I've checked the dependency of the jarModule resource
and all is well, it's package type is 'jar', it's dependency type is 'jar'
and I'm using it with 'jarModule' so… ?
Again, any input is appreciated!
Thanks,
Randall
________________________________
From: Randall Fidler
[mailto:[EMAIL PROTECTED]
Sent: Monday, December 11, 2006 8:49 AM
To: [email protected]
Subject: Maven EAR plugin issue
Hello,
Looking for some insight regarding the maven ear plugin.
Project setup is:
+ App pom (contains sub-project module entries)
- commons (creates jar with POJOs), let's say it's maven id is
'my.commons'
- ejb jar, maven id is 'my.ejb'
- service, creates an 'ear' ß ear plugin sits here
For now I'm just trying to use the following to include the POJOs and the
ejb jar
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
<modules>
<ejbModule>
<groupId>myGroup</groupId>
<artifactId>my.ejb</artifactId>
</ejbModule>
<jarmodule>
<groupId> myGroup
</groupId>
<artifactId>my.commons</artifactId>
</jarmodule>
</modules>
</configuration>
</plugin>
While produces an error stating:
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven
-ear-plugin:2.2
Cause: Class 'org.apache.maven.plugin.ear.EarModule' cannot
be instantiated
Using the maven "-e" switch shows that it has a problem with DOM, which I
assume is a parsing error of the configuration:
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven
-ear-plugin:2.2
Cause: Class 'org.apache.maven.plugin.ear.EarModule' cannot
be instantiated
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException:
Error configuring: org.a
pache.maven.plugins:maven-ear-plugin. Reason: Unable to
parse the created DOM fo
r plugin configuration
Also, if I take out the the modules it runs, which is obviously because it
doesn't have anything to do, i.e. this works fine:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-ear-plugin</artifactId>
<configuration>
<modules>
</modules>
</configuration>
</plugin>
Knowing that, could this issue be I'm missing a field for the modules? I.e.
ejbModule and jarModule?
Any help is appreciated.
Best regards,
Randall
NOTE:
Top level pom has:
<packaging>pom</packaging>
<modules>
<module>commons</module> ß my.commons
<module>server</module> ß my.ejb
<module>service</module> ß contains ear build
</modules>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
