Maven 2.x Ear Plugin

<ejbSourceIncludes> does not honor directory navigation

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Not A Bug
  • Affects Version/s: 2.4.2
  • Fix Version/s: None
  • Labels:
    None
  • Environment:
    Linux
  • Number of attachments :
    0

Description

Background:

[ftg@ftgme2 application]$ pwd
/home/ftg/PSS/PSSEJBEARProject/src/main/application
[ftg@ftgme2 application]$ ls
derby-ds.xml
...
[ftg@ftgme2 application]$ pwd
/home/ftg/dvd/dvd-ear/src/main/application
[ftg@ftgme2 application]$ ls
derby-ds.x

"dvd-ear" inherits from "PSSEJBEARProject". PSSEJBEARProject contains:

      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <version>2.4.2</version>
        <configuration>

          <!--
            Generate an application.xml file.
          -->
          <generateApplicationXml>true</generateApplicationXml>

          <!--
            JARs which should be included in this EAR.  Everyone
            gets common-java, and ejb-ejb.
          -->
          <modules>
            <jarModule>
              <groupId>org.profsoftsvcs</groupId>
              <artifactId>ejb-ejb</artifactId>
              <includeInApplicationXml>false</includeInApplicationXml>
            </jarModule>
            <jarModule>
              <groupId>org.profsoftsvcs</groupId>
              <artifactId>common-java</artifactId>
              <includeInApplicationXml>false</includeInApplicationXml>
            </jarModule>
          </modules>

          <!--
            We want to keep the JBoss DataSource descriptors in one
            place, and include them here.  Since the paths below will
            be interpreted relative to our child's basedir, we must
            play games with parent directories.
          -->
          <earSourceIncludes>../../../../../PSS/PSSEJBEARProject/src/main/application/**,**</earSourceIncludes>

          <!--
            The JBoss-specific configuration.  Including this for
            other application servers won't hurt.
          -->
          <jboss>

            <version>5</version>

            <!--
              The DataSources that should be specific to this EAR.
              These will not be visible to other applications in the
              container, and prevent any dependency on our EAR's part
              on global DataSources configured for the entire container.
            -->
            <data-sources>
              <data-source>derby-ds.xml</data-source>
            </data-sources>

          </jboss>

        </configuration>
      </plugin>

dvd-ear contains:

      <!--
        Additions and overrides for the generation of the EAR file.
      -->
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-ear-plugin</artifactId>
        <configuration>

          <!--
            Specify our EJB JARFile.
          -->
          <modules>
            <ejbModule>
              <groupId>org.profsoftsvcs</groupId>
              <artifactId>dvd-ejb</artifactId>
            </ejbModule>
          </modules>

        </configuration>
      </plugin>

The problem is that in the resulting EAR file, the root contains derby-ds.x (from the default ejbSourceDirectory - /home/ftg/dvd/dvd-ear/src/main/application) but not derby-ds.xml from /home/ftg/PSS/PSSEJBEARProject/src/main/application.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Frank Griffin added a comment -

Somehow, my XML snippet above got munged. The ending part of the "ejbSourceIncludes" value is actually "/*,*" (two asterisks in each case).

Show
Frank Griffin added a comment - Somehow, my XML snippet above got munged. The ending part of the "ejbSourceIncludes" value is actually "/* , *" (two asterisks in each case).
Hide
Permalink
Frank Griffin added a comment -

Must be a JIRA thing; the double asterisks show up as singles even in the above comment.

Show
Frank Griffin added a comment - Must be a JIRA thing; the double asterisks show up as singles even in the above comment.
Hide
Permalink
Dennis Lundberg added a comment -

You can not use a relative path to shared resources between different Maven projects, even if they inherit from one another. The correct way to do this is to bundle up the resources into an artifact, a ZIP archive, that you install into the repository. Then you add a dependency on that artifact in each of the projects that need that resource.

Brian blogged about it:
http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/

Show
Dennis Lundberg added a comment - You can not use a relative path to shared resources between different Maven projects, even if they inherit from one another. The correct way to do this is to bundle up the resources into an artifact, a ZIP archive, that you install into the repository. Then you add a dependency on that artifact in each of the projects that need that resource. Brian blogged about it: http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/
Hide
Permalink
Frank Griffin added a comment -

Ah, much nicer, thanks.

Show
Frank Griffin added a comment - Ah, much nicer, thanks.

People

  • Assignee:
    Unassigned
    Reporter:
    Frank Griffin
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: