Never mind. Plug-in generates WAR file with no version, but installs into
repository with version in a file name.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 21, 2003 9:19 PM
To: 'Maven Users List'
Subject: RE: Inconsistent EJB, WAR and EAR properties (MAVEN-349)
The workaround would need to have the EAR use the right name for the WAR
file.
Versioning the WAR file will make paths in the appserver be something like
/apps-1.2.1/... Instead of /apps/...
Unless you explicitly configure around it?
- Brett
-Original Message-
From: Boris Ekelchik [mailto:[EMAIL PROTECTED]
Sent: Friday, 22 August 2003 9:27 AM
To: 'Maven Users List'
Subject: Inconsistent EJB, WAR and EAR properties (MAVEN-349)
It's mentioned in JIRA MAVEN-349 issue, but still unresolved
in the current HEAD version.
The problem is that webapp war file is generated without
version in the file name. So when you declare it as a war
type dependency in the EAR project.xml, maven looks for a WAR
artifact which has version number in its file name and of
course doesn't find it.
From cvs HEAD:
EJB:
j:set var=maven.ejb.final.name
value=${maven.build.dir}/${maven.final.name}.jar/
...
ant:jar jarfile=${maven.ejb.final.name}
EAR:
ant:ear destfile=${maven.build.dir}/${maven.final.name}.ear
WAR:
ant:property name=maven.war.final.name
value=${pom.artifactId}.war/
...
ant:jar
destfile=${maven.war.build.dir}/${maven.war.final.name}
basedir=${maven.war.webapp.dir}
update=true
index=true
Would this be a workaround for now?
j:set var=maven.war.final.name
value=${maven.final.name}.war/
Thanks
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
