[m102]: 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
war:deploy:
[echo] maven.repo.list is set - using artifact deploy mode
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying: /vob/nm_dcm/apps/project.xml--dcm/poms/dcm-apps-1.0.pom
Deploying: /vob/nm_dcm/apps/project.xml.md5--dcm/poms/dcm-apps-1.0.pom.md5
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying: /vob/nm_dcm/apps/../target/dcm.war--dcm/wars/dcm-apps-1.0.war
Deploying:
/vob/nm_dcm/apps/../target/dcm.war.md5--dcm/wars/dcm-apps-1.0.war.md5
How can I force war:deploy goal from changing the name of the
deployed artifact?
Thanks,
Rk
x77309
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m102]: Problem with war:deploy
In fact I'm not sure you can deploy on a maven repository an artifact without a
version. It's the fundation of the repository.
Arnaud
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 19 octobre 2005 22:09
À : Maven Users List
Objet : [m102]: 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
war:deploy:
[echo] maven.repo.list is set - using artifact deploy mode
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying:
/vob/nm_dcm/apps/project.xml--dcm/poms/dcm-apps-1.0.pom
Deploying:
/vob/nm_dcm/apps/project.xml.md5--dcm/poms/dcm-apps-1.0.pom.md5
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying:
/vob/nm_dcm/apps/../target/dcm.war--dcm/wars/dcm-apps-1.0.war
Deploying:
/vob/nm_dcm/apps/../target/dcm.war.md5--dcm/wars/dcm-apps-1.0.war.md5
How can I force war:deploy goal from changing the name of the
deployed artifact?
Thanks,
Rk
x77309
-
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]
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
to
${pom.artifactId}.war
Thanks,
Rk
x77309
On Wed, 19 Oct 2005, Arnaud HERITIER wrote:
In fact I'm not sure you can deploy on a maven repository an artifact without
a version. It's the fundation of the repository.
Arnaud
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoy? : mercredi 19 octobre 2005 22:09
? : Maven Users List
Objet : [m102]: 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
war:deploy:
[echo] maven.repo.list is set - using artifact deploy mode
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying:
/vob/nm_dcm/apps/project.xml--dcm/poms/dcm-apps-1.0.pom
Deploying:
/vob/nm_dcm/apps/project.xml.md5--dcm/poms/dcm-apps-1.0.pom.md5
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying:
/vob/nm_dcm/apps/../target/dcm.war--dcm/wars/dcm-apps-1.0.war
Deploying:
/vob/nm_dcm/apps/../target/dcm.war.md5--dcm/wars/dcm-apps-1.0.war.md5
How can I force war:deploy goal from changing the name of the
deployed artifact?
Thanks,
Rk
x77309
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m102]: Problem with war:deploy
Ok. I don't know if it can be considered as a bug.
It's the default naming of an artifact (${pom.artifactId}.${type}) in the
repository (jars, ears, ...).
Arnaud
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 19 octobre 2005 23:43
À : Maven 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
to
${pom.artifactId}.war
Thanks,
Rk
x77309
On Wed, 19 Oct 2005, Arnaud HERITIER wrote:
In fact I'm not sure you can deploy on a maven repository
an artifact without a version. It's the fundation of the repository.
Arnaud
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mercredi 19
octobre 2005 22:09 À : Maven Users List Objet : [m102]:
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
war:deploy:
[echo] maven.repo.list is set - using artifact deploy mode
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying:
/vob/nm_dcm/apps/project.xml--dcm/poms/dcm-apps-1.0.pom
Deploying:
/vob/nm_dcm/apps/project.xml.md5--dcm/poms/dcm-apps-1.0.pom.md5
Will deploy to 1 repository(ies): omitted
Deploying to repository: omitted
Deploying:
/vob/nm_dcm/apps/../target/dcm.war--dcm/wars/dcm-apps-1.0.war
Deploying:
/vob/nm_dcm/apps/../target/dcm.war.md5--dcm/wars/dcm-apps-1.0.war.m
d5
How can I force war:deploy goal from changing the name of the
deployed artifact?
Thanks,
Rk
x77309
- 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]
-
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]
m[1] Exception on war:deploy/war:install
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: (11628K) BUILD FAILED java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(L java/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.j ava:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.jav a:57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInst all(DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(De faultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java :160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.jav a:180) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.jav a:102) .(snip). File.. C:\Documents and Settings\***\.maven\cache\maven-artifact-plugi -1.5.2\plugin.jelly Element... artifact:artifact-install Line.. 62 Column 9 org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V Total time : 2 minutes 34 seconds Finished at : Friday, August 19, 2005 10:46:28 AM EDT Any help greatly appreciated. Thanks, Vitaliy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m[1] Exception on war:deploy/war:install
You need artifact 1.6. I know you said you were using it, but the error message says 1.5.2 - check that you don't still have 1.5.2 JAR 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 artifact-plugin 1.6 war:install: [echo] Installing... Uploading to **-web-1.0-SNAPSHOT.war: (11628K) BUILD FAILED java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(L java/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.j ava:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.jav a:57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInst all(DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(De faultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java :160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.jav a:180) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.jav a:102) .(snip). File.. C:\Documents and Settings\***\.maven\cache\maven-artifact-plugi -1.5.2\plugin.jelly Element... artifact:artifact-install Line.. 62 Column 9 org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V Total time : 2 minutes 34 seconds Finished at : Friday, August 19, 2005 10:46:28 AM EDT Any help greatly appreciated. Thanks, Vitaliy - 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]
Re: m[1] Exception on war:deploy/war:install
Thanks, that solved the issue. I forgot to download new plugin on our CruiseControl box. Vitaliy On 8/19/05, Brett Porter [EMAIL PROTECTED] wrote: You need artifact 1.6. I know you said you were using it, but the error message says 1.5.2 - check that you don't still have 1.5.2 JAR 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 artifact-plugin 1.6 war:install: [echo] Installing... Uploading to **-web-1.0-SNAPSHOT.war: (11628K) BUILD FAILED java.lang.NoSuchMethodError: org.apache.maven.project.Dependency.setProperties(L java/util/List;)V at org.apache.maven.artifact.PomRewriter.getRewrittenModel(PomRewriter.j ava:124) at org.apache.maven.artifact.PomRewriter.getRewrittenPom(PomRewriter.jav a:57) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.handleInst all(DefaultArtifactDeployer.java:174) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.install(De faultArtifactDeployer.java:143) at org.apache.maven.artifact.deployer.DeployBean.install(DeployBean.java :160) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.jav a:180) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.jav a:102) .(snip). File.. C:\Documents and Settings\***\.maven\cache\maven-artifact-plugi -1.5.2\plugin.jelly Element... artifact:artifact-install Line.. 62 Column 9 org.apache.maven.project.Dependency.setProperties(Ljava/util/List;)V Total time : 2 minutes 34 seconds Finished at : Friday, August 19, 2005 10:46:28 AM EDT Any help greatly appreciated. Thanks, Vitaliy - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: war:deploy
Thanks Brett - I've raised a JIRA issue.
I have considered changing to using multiple small Maven projects for this,
just haven't had the chance to experiment yet
James
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: 28 August 2004 01:28
To: Maven Users List
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 properties) 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 using war.final.name to publish the artifact, so if you
want to raise an issue in JIRA, that'd be great.
Cheers,
Brett
On Fri, 27 Aug 2004 08:41:07 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I've finally got round to moving my build over to using the xxx:deploy
goals. This works a treat for jars, but I'm having an issue with
wars.
The build can produce various different builds of the war, which
contain different config settings for the environment it will run in.
To distinguish these builds I include the environment name by
manipulating the appropriate property:
postGoal name=war:init
j:set
var=maven.war.final.namefip-workflow-${maven.tcw.env}.war/j:set
/postGoal
This all works for building the war and under my old build I just
copied 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 plugin?
thanks
James
--
--
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of
the Barclays Group. Replies to this email may be monitored by the
Barclays Group for operational or business reasons.
--
--
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
war:deploy
I've finally got round to moving my build over to using the xxx:deploy
goals. This works a treat for jars, but I'm having an issue with wars.
The build can produce various different builds of the war, which contain
different config settings for the environment it will run in. To
distinguish these builds I include the environment name by manipulating the
appropriate property:
postGoal name=war:init
j:set
var=maven.war.final.namefip-workflow-${maven.tcw.env}.war/j:set
/postGoal
This all works for building the war and under my old build I just copied 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 plugin?
thanks
James
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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 properties) 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 using war.final.name to publish the artifact, so if
you want to raise an issue in JIRA, that'd be great.
Cheers,
Brett
On Fri, 27 Aug 2004 08:41:07 +0100, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
I've finally got round to moving my build over to using the xxx:deploy
goals. This works a treat for jars, but I'm having an issue with wars.
The build can produce various different builds of the war, which contain
different config settings for the environment it will run in. To
distinguish these builds I include the environment name by manipulating the
appropriate property:
postGoal name=war:init
j:set
var=maven.war.final.namefip-workflow-${maven.tcw.env}.war/j:set
/postGoal
This all works for building the war and under my old build I just copied 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 plugin?
thanks
James
For more information about Barclays Capital, please
visit our web site at http://www.barcap.com.
Internet communications are not secure and therefore the Barclays
Group does not accept legal responsibility for the contents of this
message. Although the Barclays Group operates anti-virus programmes,
it does not accept responsibility for any damage whatsoever that is
caused by viruses being passed. Any views or opinions presented are
solely those of the author and do not necessarily represent those of the
Barclays Group. Replies to this email may be monitored by the Barclays
Group for operational or business reasons.
-
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]
RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapsh ot
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 scpexe:// protocol to the artifact plugin. Provides eqivalent funcionality to the old maven.ssh.executable and maven.scp.executable properties. Here's an example build.properties entry, using this. maven.repo.list=t1 maven.repo.t1=scpexe://t1.somewhere.com maven.repo.t1.directory=/www/maven maven.repo.t1.username=myname maven.repo.t1.group=mygroup maven.repo.t1.ssh.executable=plink maven.repo.t1.ssh.args=-C maven.repo.t1.scp.executable=pscp maven.repo.t1.scp.args=-C --Leif At 06:45 PM 11/19/2003, you 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 protocl based on another property - however, I think the new protocol idea is better. Michal, do you have any current thoughts on the direction of artifact? Your changes would be welcome - just submit a patch to JIRA when you are done and I'll commit 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. I looked in the cvs repository, and it seems that the artifact plugin hasn't been touched in a while... (2-3 months). If I fixed it up to work with maven.ssh.executable and maven.scp.executable, would that help? Or, is this already on someone's task list.. Thanks again, --Leif At 11:26 AM 11/20/2003 +1100, you wrote: Your analysis is correct. Artifact needs to be more friendly to SSH, jar:deploy should use artifact. The reason it hasn't moved is because of the fact that artifact still needs more work. Cheers, Brett -Original Message- From: Leif Nelson [mailto:[EMAIL PROTECTED] Sent: Thursday, 20 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=myrepo.mycompany maven.repo.central.directory=/www/maven-repo maven.username=lnelson maven.remote.group=users maven.ssh.executable=plink maven.scp.executable=pscp Well, I tried to start using ear war deployment. And, it didn't work. After some research, I found that these plugins use the artifact plugin to do their deployments. So, I added all these properties to support this: maven.repo.list=myrepo maven.repo.myrepo=scp://myrepo.mycompany maven.repo.myrepo.directory=/www/maven-repo maven.repo.myrepo.username=lnelson maven.repo.myrepo.privatekey=/private/private-key maven.repo.myrepo.passphrase=mypassphrase # YUCKY! Want to use pageant! maven.repo.myrepo.group=users But, It seems that these plugins do the SAME thing, but the artifact plugin won't work with putty and pageant. It requires me to provide my private key and passphrase (and it can't read the putty private keys). So, am I missing something here? How do I deploy wars ears using putty (pscp) and pageant? That's the most convenient! It looks like the artifact plugin uses JCraft ( http://www.jcraft.com/jsch/index.html ) which doesn't support the idea of ssh-agents. Thanks, --Leif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Leif Nelson [EMAIL PROTECTED] Lawrence Livermore National Laboratory (406) 863-9187 ICQ: 9389793 Yahoo: nelson9087 Fax: (406) 863-9030 AIM: nelson9087 Jabber: [EMAIL PROTECTED] Leif Nelson [EMAIL PROTECTED] Lawrence Livermore National Laboratory (406) 863-9187 ICQ: 9389793 Yahoo: nelson9087 Fax: (406) 863-9030 AIM: nelson9087 Jabber: [EMAIL PROTECTED]
Re: RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapsh ot
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 scpexe:// protocol to the artifact plugin. Provides eqivalent funcionality to the old maven.ssh.executable and maven.scp.executable properties. Here's an example build.properties entry, using this. maven.repo.list=t1 maven.repo.t1=scpexe://t1.somewhere.com maven.repo.t1.directory=/www/maven maven.repo.t1.username=myname maven.repo.t1.group=mygroup maven.repo.t1.ssh.executable=plink maven.repo.t1.ssh.args=-C maven.repo.t1.scp.executable=pscp maven.repo.t1.scp.args=-C --Leif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to setup for war:deploy...
... 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 anyone have an example of the settings that effect the deploy, or a pointer to where this is documented? Thanks. - Glenn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
pom:deploy / war:deploy - won't deploy?
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 they used the atifact plugin. Looking at the docs for this I added a new set of maven.repo.x setting to my project.propeties files. Now I don't get the error of no repositories and everything seems to run fine, but no files are deployed to the remote site. Is this the correct way to setup a pom and war deploy, and if so does this currently work. Thanks Neil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploy / war:deploy - won't deploy?
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 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 they used the atifact plugin. Looking at the docs for this I added a new set of maven.repo.x setting to my project.propeties files. Now I don't get the error of no repositories and everything seems to run fine, but no files are deployed to the remote site. Is this the correct way to setup a pom and war deploy, and if so does this currently work. Thanks Neil - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Chcesz zobaczyc? http://link.interia.pl/f177d - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war:deploy
Hi Charlie, For some reason that isn't clear to me, the war plugin seems to look in a different place to the jar plugin when determining where to deploy the artifact. You need to add something like the following to your project.properties file: #deployment - settings for artifact / war. # see http://nagoya.apache.org/eyebrowse/[EMAIL PROTECTED]msgNo=8046 # and http://maven.apache.org/reference/plugins/artifact/examples.html maven.repo.list=astrogrid maven.repo.astrogrid=file:///var/www/www/ maven.repo.astrogrid.directory=maven maven.repo.astrogrid.username=maven 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 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 be something else I am missing. I'll keep checking out the reference section, hopefully something will jump out at me. Charlie Jefferson K. French wrote: You want distributionSite and distributionDirectory. Here is documentation on the POM: http://maven.apache.org/reference/project-descriptor.html. There is a lot of documentation at the Maven site: http://maven.apache.org/. Look under the Reference tab on the left. Jeff On Wed, 10 Dec 2003, 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 defined in my project.xml. But I don't know where to define the remote repository. I have repository but that is where in cvs it is located. Am I supposed to define remoteRepository? I can't find a lick of documentation on this anywhere. Any help at all would be greatly appreciated. - 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]
ear/war:deploy problem
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 this exception : com.jcraft.jsch.JSchException: invaid privatekey: C:\win32app\ssh\maven_private.PPK at com.jcraft.jsch.Identity.init(Unknown Source) at com.jcraft.jsch.JSch.addIdentity(Unknown Source) at org.apache.maven.deploy.deployers.GenericSshDeployer.init(GenericSshDeployer.java:163) My build.properties contain : # For jar:deploy maven.ssh.executable=C:\\win32app\\ssh\\plink.exe maven.scp.executable=C:\\win32app\\ssh\\pscp.exe maven.username=maven maven.repo.central=remote-maven-01 maven.repo.central.directory=/var/www/html/maven-repository maven.remote.group=apache # For artifact:deploy maven.repo.list=remote-maven-01 maven.repo.gieoracle1=scp://remote-maven-01 maven.repo.gieoracle1.username=maven maven.repo.gieoracle1.directory=/var/www/html/maven-repository maven.repo.gieoracle1.group=apache maven.repo.gieoracle1.privatekey=C:\\win32app\\ssh\\maven_private.PPK maven.repo.gieoracle1.passphrase= Any idea ? Thx, -emmanuel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
war:deploy
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 the remote repository. I have repository but that is where in cvs it is located. Am I supposed to define remoteRepository? I can't find a lick of documentation on this anywhere. Any help at all would be greatly appreciated. Charlie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war:deploy
You want distributionSite and distributionDirectory. Here is documentation on the POM: http://maven.apache.org/reference/project-descriptor.html. There is a lot of documentation at the Maven site: http://maven.apache.org/. Look under the Reference tab on the left. Jeff On Wed, 10 Dec 2003, 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 defined in my project.xml. But I don't know where to define the remote repository. I have repository but that is where in cvs it is located. Am I supposed to define remoteRepository? I can't find a lick of documentation on this anywhere. Any help at all would be greatly appreciated. -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: war:deploy
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 be something else I am missing. I'll keep checking out the reference section, hopefully something will jump out at me. Charlie Jefferson K. French wrote: You want distributionSite and distributionDirectory. Here is documentation on the POM: http://maven.apache.org/reference/project-descriptor.html. There is a lot of documentation at the Maven site: http://maven.apache.org/. Look under the Reference tab on the left. Jeff On Wed, 10 Dec 2003, 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 defined in my project.xml. But I don't know where to define the remote repository. I have repository but that is where in cvs it is located. Am I supposed to define remoteRepository? I can't find a lick of documentation on this anywhere. Any help at all would be greatly appreciated. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapsh ot
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 protocl based on another property - however, I think the new protocol idea is better. Michal, do you have any current thoughts on the direction of artifact? Your changes would be welcome - just submit a patch to JIRA when you are done and I'll commit it and release a new version. Let me know if you want to bounce any more ideas around. There is a special type of deployer in maven-artifact plugin called External, which was supposed to be used for executing arbitrary user defined programs (like putty). This deployer is half-finished. A new protocol sounds like a good idea. Leif: Patches and documentation are always welcomed :) If we have solution based on external programs which supports SSH (SCP) which works both on Windows and Linux, we can think about switching from deploy plugins like to artifact plugin. Generaly I am trying to provide pure java, ready to use out-of-the box solution. So my vision is: if there is Java libaray which does the same trick as external program - it should be used. I am progressing with Artifact Transport Libaray called Wagon which probably will be used in future verions of Maven( after 1.0). It should be moved to Apache CVS repo in a matter of days. The main problem with artifact plugin is that it is poorly tested. I wonder how many people are actually using it and what kind of experinces they have with it... Wagon has alredy much more unit tests and I am working on integration unit tests. regards Michal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapsh ot
There is a special type of deployer in maven-artifact plugin called External, which was supposed to be used for executing arbitrary user defined programs (like putty). This deployer is half-finished. A new protocol sounds like a good idea. Leif: Patches and documentation are always welcomed :) That sounds like the best approach. If we have solution based on external programs which supports SSH (SCP) which works both on Windows and Linux, we can think about switching from deploy plugins like to artifact plugin. Great! Generaly I am trying to provide pure java, ready to use out-of-the box solution. An admirable goal, but in the case of this SSH library, it is too hard to configure and not as feature rich, where executing external apps is easy and works well most of the time. It'd just be nice not to have to ask windows people to download cygwin, putty, or whatever. Giving both options as discussed is the best of both worlds. The main problem with artifact plugin is that it is poorly tested. I wonder how many people are actually using it and what kind of experinces they have with it... Wagon has alredy much more unit tests and I am 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
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=myrepo.mycompany maven.repo.central.directory=/www/maven-repo maven.username=lnelson maven.remote.group=users maven.ssh.executable=plink maven.scp.executable=pscp Well, I tried to start using ear war deployment. And, it didn't work. After some research, I found that these plugins use the artifact plugin to do their deployments. So, I added all these properties to support this: maven.repo.list=myrepo maven.repo.myrepo=scp://myrepo.mycompany maven.repo.myrepo.directory=/www/maven-repo maven.repo.myrepo.username=lnelson maven.repo.myrepo.privatekey=/private/private-key maven.repo.myrepo.passphrase=mypassphrase # YUCKY! Want to use pageant! maven.repo.myrepo.group=users But, It seems that these plugins do the SAME thing, but the artifact plugin won't work with putty and pageant. It requires me to provide my private key and passphrase (and it can't read the putty private keys). So, am I missing something here? How do I deploy wars ears using putty (pscp) and pageant? That's the most convenient! It looks like the artifact plugin uses JCraft ( http://www.jcraft.com/jsch/index.html ) which doesn't support the idea of ssh-agents. Thanks, --Leif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapsh ot
Your analysis is correct. Artifact needs to be more friendly to SSH, jar:deploy should use artifact. The reason it hasn't moved is because of the fact that artifact still needs more work. Cheers, Brett -Original Message- From: Leif Nelson [mailto:[EMAIL PROTECTED] Sent: Thursday, 20 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=myrepo.mycompany maven.repo.central.directory=/www/maven-repo maven.username=lnelson maven.remote.group=users maven.ssh.executable=plink maven.scp.executable=pscp Well, I tried to start using ear war deployment. And, it didn't work. After some research, I found that these plugins use the artifact plugin to do their deployments. So, I added all these properties to support this: maven.repo.list=myrepo maven.repo.myrepo=scp://myrepo.mycompany maven.repo.myrepo.directory=/www/maven-repo maven.repo.myrepo.username=lnelson maven.repo.myrepo.privatekey=/private/private-key maven.repo.myrepo.passphrase=mypassphrase # YUCKY! Want to use pageant! maven.repo.myrepo.group=users But, It seems that these plugins do the SAME thing, but the artifact plugin won't work with putty and pageant. It requires me to provide my private key and passphrase (and it can't read the putty private keys). So, am I missing something here? How do I deploy wars ears using putty (pscp) and pageant? That's the most convenient! It looks like the artifact plugin uses JCraft ( http://www.jcraft.com/jsch/index.html ) which doesn't support the idea of ssh-agents. Thanks, --Leif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: deploy-snapshot vs. war:deploy-snapshot and ear:deploy-snapsh ot
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 protocl based on another property - however, I think the new protocol idea is better. Michal, do you have any current thoughts on the direction of artifact? Your changes would be welcome - just submit a patch to JIRA when you are done and I'll commit 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. I looked in the cvs repository, and it seems that the artifact plugin hasn't been touched in a while... (2-3 months). If I fixed it up to work with maven.ssh.executable and maven.scp.executable, would that help? Or, is this already on someone's task list.. Thanks again, --Leif At 11:26 AM 11/20/2003 +1100, you wrote: Your analysis is correct. Artifact needs to be more friendly to SSH, jar:deploy should use artifact. The reason it hasn't moved is because of the fact that artifact still needs more work. Cheers, Brett -Original Message- From: Leif Nelson [mailto:[EMAIL PROTECTED] Sent: Thursday, 20 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=myrepo.mycompany maven.repo.central.directory=/www/maven-repo maven.username=lnelson maven.remote.group=users maven.ssh.executable=plink maven.scp.executable=pscp Well, I tried to start using ear war deployment. And, it didn't work. After some research, I found that these plugins use the artifact plugin to do their deployments. So, I added all these properties to support this: maven.repo.list=myrepo maven.repo.myrepo=scp://myrepo.mycompany maven.repo.myrepo.directory=/www/maven-repo maven.repo.myrepo.username=lnelson maven.repo.myrepo.privatekey=/private/private-key maven.repo.myrepo.passphrase=mypassphrase # YUCKY! Want to use pageant! maven.repo.myrepo.group=users But, It seems that these plugins do the SAME thing, but the artifact plugin won't work with putty and pageant. It requires me to provide my private key and passphrase (and it can't read the putty private keys). So, am I missing something here? How do I deploy wars ears using putty (pscp) and pageant? That's the most convenient! It looks like the artifact plugin uses JCraft ( http://www.jcraft.com/jsch/index.html ) which doesn't support the idea of ssh-agents. Thanks, --Leif - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Leif Nelson [EMAIL PROTECTED] Lawrence Livermore National Laboratory (406) 863-9187 ICQ: 9389793 Yahoo: nelson9087 Fax: (406) 863-9030 AIM: nelson9087 Jabber: [EMAIL PROTECTED]
