Message:
The following issue has been closed.
Resolver: dion gillard
Date: Tue, 31 Dec 2002 6:20 AM
I think the ear plugin has been fixed for a while now
---------------------------------------------------------------------
View the issue:
http://jira.werken.com/secure/ViewIssue.jspa?key=MAVEN-140
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MAVEN-140
Summary: J2ee plugin inconsistencies
Type: Improvement
Status: Closed
Priority: Major
Resolution: FIXED
Time Spent: Unknown
Estimate: 1 week
Project: maven
Component: None
Assignee: dion gillard
Reporter: dion gillard
Created: Mon, 14 Oct 2002 6:53 PM
Updated: Tue, 31 Dec 2002 6:20 AM
Environment: N/A
Description:
>From Nathan Coast:
Hi,
I've been using the j2ee and war plugins quite extensively and have
noticed some inconsistencies / typos. I figured an email rather than a
patch is more useful so we can decide what is best in each case.
Cheers
Nathan
******************************************************************
j2ee:ear
<echo>Building EAR ${pom.id}</echo>
<mkdir dir="${maven.war.build.dir}" />
<ear earfile="${maven.war.build.dir}/${pom.id}.ear"
appxml="${maven.j2ee.ear.appxml}">
1) the ear file is built using ${pom.id}.ear rather than
${maven.final.name}.ear
2) the directories are maven.war.build.dir should probably be
maven.ear.build.dir :) need an entry in plugin.properties.
Alternatively get rid of the type specific prop and just use the
maven.build.dir property. This seems to make sense to me, as its
unlikely that you'll be building more than one type of component within
a single project.
******************************************************************
j2ee:ear-install
3) there is no ear-install (like the jar-install and war-install), could
do with one to get ear dists in to my local repo, e.g.
<goal name="j2ee:ear-install"
prereqs="j2ee:ear"
description="Install the ear in the local repository">
<property name="maven.ear.install.dir"
value="${maven.repo.local}/${pom.id}/jars"/>
<mkdir dir="${maven.ear.install.dir}"/>
<copy file="${maven.ear.build.dir}/${maven.final.name}.ear"
tofile="${maven.ear.install.dir}/${maven.final.name}.ear"/>
</goal>
*******************************************************************
war:war-install
<goal name="war:install"
prereqs="war:war"
description="Install the war in the local repository">
<property name="maven.war.install.dir"
value="${maven.repo.local}/${pom.id}/wars"/>
<mkdir dir="${maven.war.install.dir}"/>
4) war files get deployed to a 'wars' sub-directory. This has caused
problems for me when building an ear file that has a dependency on a
war. ATM I have to manually copy the war to the jars dir to make
dependencies work. If we install to type-specific subdirs in the local
repo, the dependency code needs to know where to look for jars depending
upon component type.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.werken.com/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
