Hello:

I am having problems with the maven-ear-plugin as the only version I can
find is 2.1.

I assume the problem is that I'm not using the 2.2-SNAPSHOT as
documented @
http://maven.apache.org/plugins/maven-ear-plugin/howto.html.

I have tried http://snapshots.maven.codehaus.org/maven2 and
http://cvs.apache.org/maven-snapshot-repository/ with no avail.

When trying this:

<build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <configuration>
           [...]
           <modules>
             <webModule>
               <groupId>artifactGroupId</groupId>
               <artifactId>artifactId</artifactId>
               <contextRoot>/custom-context-root</contextRoot>
             </webModule>
          </modules>
        </configuration>
      </plugin>
    </plugins>
  </build>

I receive:

[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
----
[INFO] Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-ear-plugin:2.1

Cause: Cannot find setter nor field in
org.apache.maven.plugin.ear.WebModule for 'version'


Cheers,

Christiaan Veerman
IT Consultant
KnowledgeStorm, Inc.
Direct: 678-597-5941
Cell: 404-771-6126
Fax: 678-597-5917
mailto:[EMAIL PROTECTED]
2520 Northwinds Parkway, Suite 600
Alpharetta, Georgia 30004
www.knowledgestorm.com <http://www.knowledgestorm.com/> 
KnowledgeStorm - Reach. Search. Results.

****DISCLAIMER
The information contained in this e-mail and attachments, if any, is 
confidential and may be subject to legal privilege.  If you are not the 
intended recipient, you must not use, copy, distribute or disclose the e-mail 
and its attachment, or any part of its content or take any action in reliance 
of it.  If you have received this e-mail in error, please e-mail the message 
back to the sender by replying and then deleting it.  We cannot accept 
responsibility for loss or damage arising from the use of this e-mail or 
attachments, and recommend that you subject these to your virus checking 
procedures prior to use

Reply via email to