Issue Details (XML | Word | Printable)

Key: MPEAR-23
Type: New Feature New Feature
Status: Closed Closed
Resolution: Fixed
Priority: Minor Minor
Assignee: Felipe Leme
Reporter: Wiley Fuller
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Maven 1.x Ear Plugin

need to be able to set location of resources within the EAR file

Created: 13/Oct/04 08:20 PM   Updated: 20/Jun/05 09:52 AM   Resolved: 10/Nov/04 10:34 PM
Return to search
Component/s: None
Affects Version/s: None
Fix Version/s: 1.6

Time Tracking:
Original Estimate: 3 hours
Original Estimate - 3 hours
Remaining Estimate: 3 hours
Remaining Estimate - 3 hours
Time Spent: Not Specified
Time Spent - Not Specified

File Attachments: 1. Text File ejb-target-path-patch.txt (1 kB)
2. XML File maven.xml (2 kB)
3. XML File project.xml (3 kB)



 Description  « Hide

The EAR plugin does not currently provide a way of changing the path of included resources.
This is a problem for weblogic server 8.1, if you want to place bundled JARs into the /APP-INF/lib directory, so that they are available to all the other modules contained in the EAR file.

I think the best solution would be to mirror the war.target.path property of the WAR plugin, and create an ear.target.path property.

The Dependency element would look something like the following.

<dependency>
<id>third-party</id>
<version>1.0</version>
<properties>
<ear.target.path>/APP-INF/lib</ear.target.path>
</properties>
</dependency>



Wiley Fuller added a comment - 17/Oct/04 08:46 PM

A patch to allow dependencies to be added to the EAR file with arbitrary paths.
This implementation is different to the implementation of war.target.path. It uses the ant zipfileset element instead of copying the dependencies to the desired path before adding.


Wiley Fuller made changes - 17/Oct/04 08:46 PM
Field Original Value New Value
Attachment ejb-target-path-patch.txt [ 13234 ]
Felipe Leme made changes - 20/Oct/04 07:27 AM
Assignee Felipe Leme [ felipeal ]
Wiley Fuller added a comment - 09/Nov/04 08:20 PM

Added the maven.xml file for testing this change.


Wiley Fuller made changes - 09/Nov/04 08:20 PM
Attachment maven.xml [ 13344 ]
Wiley Fuller added a comment - 09/Nov/04 08:20 PM

Added project.xml file for testing this issue.


Wiley Fuller made changes - 09/Nov/04 08:20 PM
Attachment project.xml [ 13345 ]
Felipe Leme added a comment - 10/Nov/04 10:34 PM

fixed with minor changes


Felipe Leme made changes - 10/Nov/04 10:34 PM
Fix Version/s 1.6 [ 11001 ]
Status Open [ 1 ] Closed [ 6 ]
Resolution Fixed [ 1 ]
Felipe Leme added a comment - 15/Nov/04 10:33 PM

Due to fix for MPEAR-26 I changed the new property to ear.bundle.dir (instead of ear.target.path).


Dale Wyttenbach added a comment - 20/Jun/05 09:52 AM

Has anyone verified that this solution addresses the problem for WL 8.1? I was unable to get an EAR to deploy without modifying the generated application.xml and manually add the "APP-INF/lib" path info:

<module>
<java>APP-INF/lib/foo.jar</java>
</module>

Shouldn't the plugin do this automatically given that I have defined this property in the jar dependency?

<ear.bundle.dir>APP-INF/lib</ear.bundle.dir>