Hi GB,

Here's how my EAR is configured; the application.xml is properly included.

File located here:
ProjectEAR\src\main\resources\META-INF\application.xml

pom.xml:
     <plugin>
       <groupId>org.apache.maven.plugins</groupId>
       <artifactId>maven-ear-plugin</artifactId>
       <configuration>
         <archive>
           <manifest>
             <addClasspath>true</addClasspath>
           </manifest>
         </archive>
       </configuration>
     </plugin>

Give that a try.

Wayne

On 5/30/06, Guillaume Bilodeau <[EMAIL PROTECTED]> wrote:
Hi all,

Since Maven 2.0 doesn't support application.xml generation for the J2EE 1.2 
specification (I understand, this is 2006 after all), I'm trying to include a 
custom-built application.xml file in my EAR but with no success.

I'm using a project with multiple modules following a flat directory structure.  The EAR 
module contains both pom.xml file and application.xml (custom-built) files.  Executing 
"mvn package" produces the following error message:

[INFO] Including custom application.xml[application.xml]
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error copying EAR sources

Embedded error: File application.xml does not exist

My pom.xml in the EAR project contains the following configuration:

  <build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <configuration>
          <applicationXml>application.xml</applicationXml>
        </configuration>
      </plugin>
    </plugins>
  </build>

What am I doing wrong?  Where should I place my application.xml file, and using 
what path should I reference it in the pom.xml?  Is this at all necessary - is 
there support for the 1.2 spec now?

Thanks a bunch,
GB




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to