With m102, a project apps uses artifactId dcm-apps and uses
war plugin with the settings
maven.war.final.name: Foo.war
However, while war:war generates Foo.war, the war:deploy goal
chooses to rename it to ${pom.artifactId}.war
$ maven war:deply
war:deploy:
[echo] maven.repo.list
]: Problem with war:deploy
With m102, a project apps uses artifactId dcm-apps and
uses war plugin with the settings
maven.war.final.name: Foo.war
However, while war:war generates Foo.war, the war:deploy goal
chooses to rename it to ${pom.artifactId}.war
$ maven war:deply
I do not mind if war:deploy wants to append ${pom.currentVersion}
or SNAPSHOT to the deploted artifact on the remote repo; but
my issue is that it is changing the name of the artifact
from
${maven.war.final.name}.war
to
${pom.artifactId}.war
Thanks,
Rk
x77309
On Wed, 19 Oct 2005
Users List
Objet : RE: [m102]: Problem with war:deploy
I do not mind if war:deploy wants to append
${pom.currentVersion} or SNAPSHOT to the deploted artifact on
the remote repo; but my issue is that it is changing the name
of the artifact from
${maven.war.final.name}.war
Hi All,
I am getting this exception while running war:deploy goal (it also
happens on war:install)
I can deploy and install jars without any problem.
Maven 1.1-b1
war-plugin 1.6.1
artifact-plugin 1.6
war:install:
[echo] Installing...
Uploading to **-web-1.0-SNAPSHOT.war
running war:deploy goal (it also
happens on war:install)
I can deploy and install jars without any problem.
Maven 1.1-b1
war-plugin 1.6.1
artifact-plugin 1.6
war:install:
[echo] Installing...
Uploading to **-web-1.0-SNAPSHOT.war:
(11628K)
BUILD FAILED
in $MAVEN_HOME/plugins or ~/.maven/plugins.
- Brett
On 8/20/05, Vitaliy Geraymovych [EMAIL PROTECTED] wrote:
Hi All,
I am getting this exception while running war:deploy goal (it also
happens on war:install)
I can deploy and install jars without any problem.
Maven 1.1-b1
war-plugin 1.6.1
Subject: Re: war:deploy
This is the artifact strategy for Maven is for a project to produce one
artifact per project.
I assume the way you are doing this, you need to re-run maven to build the
others?
The preferred Maven approach is to create small subprojects (possibly just
with a POM and different
the
result to our repository using the copy tag. However when I switch to
using war:deploy it gets the source filename correct, but the target uses
the default name, e.g. tcw-fip-workflow-webservice-2.0.0.war
Am I doing something wrong, or is this just a feature / limitation / bug of
the war / artifact
) that extend the original.
These can then be built to publish each different project, or all can
be done at once via the reactor.
To keep your existing approach, you will probably need to override the
war:deploy goal and use the artifact tags manually to deploy with the
new final name.
We should support
it and release a new version. Let me know if you want
to bounce any more ideas around.
Cheers,
Brett
-Original Message-
From: Leif Nelson [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 November 2003 11:33 AM
To: Brett Porter
Subject: RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapshot
OK
looks good to me... will apply when I get a chance.
Thanks,
Brett
On Mon, 28 Jun 2004 15:09:56 -0600, Leif Nelson [EMAIL PROTECTED] wrote:
After 6 months... I wrote a small patch.. MPARTIFACT-22. I started with
the latest HEAD version of the artifact plugin in CVS. This adds the
... or any of the artifact:deploy. I've been getting lost in the
docs, but have not found information or an example that shows where I
say where I want the files to be deployed to... and is it going to
deploy to a maven repository? And what sort of transport is available
for this?
does
Hello,
I have a project where I would like to deploy the pom and the war. When I ran maven
pom:deploy or maven war:deploy they both said that no remote repository was set. This
seemed strange as the site and jar deploy both work. So I looked at the plugin.jelly
files for these plugins and saw
Which protocol are you using for deploying?
Michal
-Original Message-
From: Neil Blue [mailto:[EMAIL PROTECTED]
Sent: Monday, December 15, 2003 10:30 AM
To: Maven Users List
Subject: pom:deploy / war:deploy - won't deploy?
Hello,
I have a project where I would like to deploy
maven.repo.astrogrid.group=cvs
Good luck,
John
- Original Message -
From: Charles N. Harvey III [EMAIL PROTECTED]
To: Maven Users List [EMAIL PROTECTED]
Sent: Wednesday, December 10, 2003 9:02 PM
Subject: Re: war:deploy
Ok. I did need to read the documentation a little bit. I have been
through a lot
Hi,
I want to deploy my artifacts (jar, ear, war...) on out remote reposipory. We
use scp protocole with key authentification.
When I use jar:deploy, it is working fine (I think it is using my Putty
configuration).
When I use ear/war:deploy (which use artifact plugin) it is fail. I've got
Hello.
I am having a tough time with war:deploy. When I run it I get the following:
No remote repository was defined.
No remote repository was defined.
Which, is actually pretty clear. It means that I don't have a remote
repository defined in my project.xml. But I don't know where to define
, at 15:33:08 [GMT -0500] Charles N. Harvey III
wrote:
Hello.
I am having a tough time with war:deploy. When I run it I get the following:
No remote repository was defined.
No remote repository was defined.
Which, is actually pretty clear. It means that I don't have a remote
repository
Ok. I did need to read the documentation a little bit. I have been
through a lot of it over the past 5 days though. Ok, so I had
distributionDirectory set but I did not have distributionSite.
So I added distributionSite and still got the same error when I ran
war:deploy. There must
Brett Porter wrote:
Hi Leif,
(Sorry for CC'ing back to the list again, but they'll probably want to
review this)
Sounds like a good idea - perhaps a new protocol could be added to artifact
(scpexe:// ?) that uses the mentioned parameters. Alternatively, it might be
a branch of the existing
working on integration unit tests.
I think the artifact plugin is better designed and better featured, but not
complete enough to be used everywhere. It's close though. I'm a little
disappointed anyone calling war:deploy gets forced into it though...
Cheers,
Brett
Hi all-
I'm confused about deployments with maven rc1. I have the jar deployment
stuff working perfectly. Setting these properties:
maven.repo.central=myrepo.mycompany
maven.repo.central.directory=/www/maven-repo
maven.username=lnelson
maven.remote.group=users
maven.ssh.executable=plink
November 2003 11:19 AM
To: [EMAIL PROTECTED]
Subject: jar:deploy-snapshot vs. war:deploy-snapshot and
ear:deploy-snapshot
Hi all-
I'm confused about deployments with maven rc1. I have the
jar deployment
stuff working perfectly. Setting these properties:
maven.repo.central
ideas around.
Cheers,
Brett
-Original Message-
From: Leif Nelson [mailto:[EMAIL PROTECTED]
Sent: Thursday, 20 November 2003 11:33 AM
To: Brett Porter
Subject: RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapshot
OK. I looked in the cvs repository, and it seems
25 matches
Mail list logo