Stefan Prange wrote:
yes there is.
Our operations team defined this convention. Their deploy script looks for
ear files that are named after this pattern. But the timestamp part after
the appname.ear_ is completely arbitrary. It's meant to be a version
marker to distinguish different EAR files.
for helping me.
Bye, Stefan
--
View this message in context:
http://www.nabble.com/maven-ant-tasks-2.0.7%3A-Hot-to-package-an-artifact--tf4527753s177.html#a12939367
Sent from the Maven - Users mailing list archive at Nabble.com
On Thu, September 27, 2007 8:09 pm, Stefan Prange wrote:
there are two reasons.
1. I didn't want to create a new java project only to package an EAR file.
Well, this reason is not quite cogent, I suppose. When using Maven one
should engage with Maven's multi module approach.
We relented and
let Maven
build the WAR and after that do the EAR wrapping.
Now my question is:
How can I use the maven-ant-tasks-2.0.7 to package the war, i.e. to say the
equivalent of mvn package ?
I tried the artifact:install .. task of the maven-ant-tasks-2.0.7 but this
task doesn't process the maven build
build.xml file. The ANT file should let Maven
build the WAR and after that do the EAR wrapping.
Now my question is:
How can I use the maven-ant-tasks-2.0.7 to package the war, i.e. to say the
equivalent of mvn package ?
You can't.
The maven ant tasks enable you to use the maven dependency management
On Thu, September 27, 2007 1:15 pm, Stefan Prange wrote:
I'm building an artifact with a mixture of ANT and Maven. The artifact has
the packaging type war but I need to have it wrapped also in an EAR
file.
Instead of creating a second EAR-Maven-Module I decided to have only one
module with
While converting an existing project to use maven I ran into this issue.
I needed to be able to provide a set of ant tasks that existed in the
ant only version of the project.
My solution was to create a general purpose ant macrodef that could be
used to ensure a project module was up to
a
separate EAR module.
Bye, Stefan
--
View this message in context:
http://www.nabble.com/maven-ant-tasks-2.0.7%3A-Hot-to-package-an-artifact--tf4527753s177.html#a12927151
Sent from the Maven - Users mailing list archive at Nabble.com
Tim Kettler wrote:
How can I use the maven-ant-tasks-2.0.7 to package the war, i.e. to say
the
equivalent of mvn package ?
You can't.
The maven ant tasks enable you to use the maven dependency management
features from ant, nothing more.
Hi Tim,
thanks for clarifying the purpose
Stefan Prange schrieb:
Graham Leggett wrote:
On Thu, September 27, 2007 1:15 pm, Stefan Prange wrote:
Is there a reason for this decision? The simplest way to handle ears and
wars is to have the war as an artifact, and the ear as an artifact, and
just let maven do everything for you.
What
/repository/repositories
/profile/profiles
/settings
Furthermore, my project is as follows:
my_project/lib/maven-ant-tasks-2.0.7.jar
my_project/build.xml
my_project/pom.xml
repository/
my_parent_pom/pom.xml
The following sequence of commands shows the problems (I haven't
listed
Hi Hilco,
Le mercredi 29 août 2007, Hilco Wijbenga a écrit :
Hi all,
I ran into something strange while using the Maven Ant Tasks (2.0.7).
My Ant build now includes a POM which refers to a parent POM.
If I have the parent POM available in my local repository everything
works fine
Hi all,
I ran into something strange while using the Maven Ant Tasks (2.0.7).
My Ant build now includes a POM which refers to a parent POM.
If I have the parent POM available in my local repository everything
works fine. If not, then the build fails because it can't download the
parent POM
://jira.codehaus.org/browse/MANTTASKS-85
You'll find the modified tasks at
http://codehaus.org/~hboutemy/maven-ant-tasks-2.0.7-MANTTASKS-85.jar
Can you check that it fixes your problem?
Then it should be released in 2.0.8.
Hervé
Le vendredi 10 août 2007, Mykel Alvis a écrit :
Hervé,
Sorry it took
/MANTTASKS-85
You'll find the modified tasks at
http://codehaus.org/~hboutemy/maven-ant-tasks-2.0.7-MANTTASKS-85.jar
Can you check that it fixes your problem?
Then it should be released in 2.0.8.
Hervé
Le vendredi 10 août 2007, Mykel Alvis a écrit :
Hervé,
Sorry it took so long to get back to you
-
custom = true
# Jarfile name of the maven ant tasks. Occasionally updates
maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
# Local file location of maven ant tasks jar
maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.task.jar}
# repo username for scp
repository.username
/
/target
build.properties
-
custom = true
# Jarfile name of the maven ant tasks. Occasionally updates
maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
# Local file location of maven ant tasks jar
maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks
. Occasionally updates
maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
# Local file location of maven ant tasks jar
maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.tas
k.jar} # repo username for scp
repository.username=localbuild
# localtion of local private key
-
custom = true
# Jarfile name of the maven ant tasks. Occasionally updates
maven.ant.task.jar=maven-ant-tasks-2.0.7.jar
# Local file location of maven ant tasks jar
maven.ant.task.url=http://sirdsite/installs/maven-ant-tasks/${maven.ant.t
as
k.jar
Problemet med settings.xml ser no ut til å vere fiksa i Maven Ant Tasks
2.0.7 - frå releasenotes:
[MANTTASKS-6 http://jira.codehaus.org/browse/MANTTASKS-6] - ant artifact
doesn't read settings.xml
Frode
2007/7/6, Jason van Zyl [EMAIL PROTECTED]:
The Apache Maven team would like to announce
The Apache Maven team would like to announce the availability of the
Maven Ant Tasks 2.0.7.
You can find the binaries here:
http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-
tasks-2.0.7.jar
You can find the release notes here:
http://jira.codehaus.org/secure/ReleaseNote.jspa
wrote:
The Apache Maven team would like to announce the availability of the
Maven Ant Tasks 2.0.7.
You can find the binaries here:
http://www.apache.org/dyn/closer.cgi/maven/binaries/maven-ant-tasks-2.0.7.jar
You can find the release notes here:
http://jira.codehaus.org/secure/ReleaseNote.jspa
22 matches
Mail list logo