Thanks Brett! I did the update, built the artifact plugin, installed it and ran a war:deploy-snapshot
There is no joy in Mudville. [EMAIL PROTECTED] OmniManager]$ maven war:deploy-snapshot __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Attempting to download commons-discovery-SNAPSHOT.jar. Attempting to download wagon-provider-api-1.0-alpha-3-SNAPSHOT.jar. build:start: war:init: war:war-resources: [copy] Copying 1 file to /opt/omnimanager/builds/OmniManager/target/OmniManager/WEB-INF java:prepare-filesystem: java:compile: [echo] Compiling to /opt/omnimanager/builds/OmniManager/target/classes [echo] ========================================================== NOTE: Targetting JVM 1.4, classes will not run on earlier JVMs ========================================================== [javac] Compiling 2 source files to /opt/omnimanager/builds/OmniManager/target/classes java:jar-resources: test:prepare-filesystem: test:test-resources: test:compile: test:test: war:webapp: [echo] Assembling webapp OmniManager war:war: [echo] Building WAR OmniManager [jar] Building jar: /opt/omnimanager/builds/OmniManager/target/OmniManager- 0.8.0.war war:deploy-snapshot: [echo] Deploying as snapshot... [echo] maven.repo.list is set - using artifact deploy mode Will deploy to 1 repository(ies): omnimanagerdev Deploying to repository: omnimanagerdev .................... (16K) .................... (0K) .................... (0K) .................... (16K) .................... (0K) .................... (0K) .................... (0K) .................... (0K) .................... (0K) Will deploy to 1 repository(ies): omnimanagerdev Deploying to repository: omnimanagerdev .................... (29511K) .................... (0K) .................... (0K) ..............SSH_MSG_DISCONNECT: 2 Corrupted MAC on input. Read end dead Failed to deploy to: omnimanagerdev Reason: org.apache.maven.wagon.TransferFailedException: Error occured while deploying 'omnimanager/wars/OmniManager-20050421.191106.war' to remote repository: scp://omnimanagerdev org.apache.maven.wagon.TransferFailedException: Error occured while deploying 'omnimanager/wars/OmniManager-20050421.191106.war' to remote repository: scp://omnimanagerdev at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:324) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deployFiles( DefaultArtifactDeployer.java:399) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.doDeploy( DefaultArtifactDeployer.java:356) at org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploySnapshot (DefaultArtifactDeployer.java:176) at org.apache.maven.artifact.deployer.DeployBean.deploySnapshot( DeployBean.java:151) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java :39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java :230) at org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java :145) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.OtherwiseTag.doTag(OtherwiseTag.java :87) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233) at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:84) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.commons.jelly.impl.DynamicTag.doTag(DynamicTag.java:125) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag( MavenGoalTag.java:79) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction (MavenGoalTag.java:110) at com.werken.werkz.Goal.fire(Goal.java:639) at com.werken.werkz.Goal.attain(Goal.java:575) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:488) at org.apache.maven.cli.App.main(App.java:1239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java :39) at sun.reflect.DelegatingMethodAccessorImpl.invoke( DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Caused by: org.apache.maven.wagon.TransferFailedException: PUT request for: [EMAIL PROTECTED] to OmniManager-0.8.0.warfailed at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:196) at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:303) ... 36 more Caused by: java.io.IOException: Read end dead at java.io.PipedInputStream.receive(PipedInputStream.java:138) at java.io.PipedInputStream.receive(PipedInputStream.java:176) at java.io.PipedOutputStream.write(PipedOutputStream.java:129) at org.apache.maven.wagon.AbstractWagon.transfer(AbstractWagon.java:228) at org.apache.maven.wagon.AbstractWagon.putTransfer(AbstractWagon.java:188) ... 37 more BUILD FAILED File...... /home/maven/.maven/cache/maven-artifact-plugin-1.5-SNAPSHOT /plugin.jelly Element... artifact:artifact-deploy-snapshot Line...... 178 Column.... 13 Unable to deploy to any repositories Total time: 1 minutes 14 seconds Finished at: Thu Apr 21 14:11:55 CDT 2005 On 4/20/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > argh... my mistake. I didn't build clean. Fixed and committed. > > - Brett > > On 4/21/05, Mykel Alvis <[EMAIL PROTECTED]> wrote: > > Did I miss something? I have to download files from SVN by hand while > I'm > > here at the office, so if you changed anything but project.xml let me > know. > > > > > > java:compile: > > [echo] Compiling to > > /opt/omgs/plugins/artifact/target/classes > > [javac] Compiling 5 source files to > > /opt/omgs/plugins/artifact/target/classes > > > /opt/omgs/plugins/artifact/src/main/org/apache/maven/artifact/deployer/UploadMeter.java:32: > > org.apache.maven.artifact.deployer.UploadMeter is not > > abstract and does not override abstract method > > transferInitiated(org.apache.maven.wagon.events.TransferEvent) > > in org.apache.maven.wagon.events.TransferListener > > public class UploadMeter implements TransferListener > > ^ > > 1 error > > > > BUILD FAILED > > > > > > > > On 4/20/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > > > patience :) > > > > > > They are all there now. If you get a 404, it's because ibiblio has a > > > cache that takes a while to expire, and Maven 1.0.2 isn't sending a > > > no-cache header. Manually download anything missing... > > > > > > The file has also been updated in svn. > > > > > > HTH, > > > Brett > > > > > > On 4/21/05, Mykel Alvis <[EMAIL PROTECTED]> wrote: > > > > Thanks, Brett > > > > I noticed that there's an http-lightweight but the dep is on http. > > > > Is that another correction for the project.xml or is it a different > > dep? > > > > > > > > > > > > On 4/20/05, Brett Porter <[EMAIL PROTECTED] > wrote: > > > > > > > > > > ok, the groupID should be org.apache.maven.wagon, not maven. I've > > > > > fixed it, will commit when the machine is working again. > > > > > > > > > > I'm copying the missing dependencies now, so if you make the above > > > > > change and try again in 5 minutes, it should work. > > > > > > > > > > - Brett > > > > > > > > > > On 4/21/05, Mykel Alvis <[EMAIL PROTECTED] > wrote: > > > > > > SNAPSHOTS they are. > > > > > > > > > > > > Updating the project.xml to include SNAPSHOT for all the wagon > deps > > > > gives > > > > > > me FNFs on only the following. > > > > > > They are not in the maven repo. > > > > > > > > > > > > wagon-provider-api-1.0-alpha-3-SNAPSHOT.jar <- > > there > > > > IS > > > > > > an alpha-2-SNAPSHOT > > > > > > wagon-ssh-external-1.0-alpha-2-SNAPSHOT.jar <- No > > > > such > > > > > > creature > > > > > > > > > > > > This may not be correct. Maybe everything doesn't need a > -SNAPSHOT > > > > > > appended to its version. > > > > > > from modified project.xml > > > > > > ---------------------------------------- > > > > > > <dependency> > > > > > > <groupId>maven</groupId> > > > > > > <artifactId>wagon-provider-api</artifactId> > > > > > > <version>1.0-alpha-3-SNAPSHOT</version> > > > > > > </dependency> > > > > > > <dependency> > > > > > > <groupId>maven</groupId> > > > > > > <artifactId>wagon-http</artifactId> > > > > > > <version>1.0-alpha-2-SNAPSHOT</version> > > > > > > </dependency> > > > > > > <dependency> > > > > > > <groupId>maven</groupId> > > > > > > <artifactId>wagon-ftp</artifactId> > > > > > > <version>1.0-alpha-2-SNAPSHOT</version> > > > > > > </dependency> > > > > > > <dependency> > > > > > > <groupId>maven</groupId> > > > > > > <artifactId>wagon-ssh</artifactId> > > > > > > <version>1.0-alpha-2-SNAPSHOT </version> > > > > > > </dependency> > > > > > > <dependency> > > > > > > <groupId>maven</groupId> > > > > > > <artifactId>wagon-ssh-external</artifactId> > > > > > > <version>1.0-alpha-2-SNAPSHOT</version> > > > > > > </dependency> > > > > > > <dependency> > > > > > > <groupId>maven</groupId> > > > > > > <artifactId>wagon-file</artifactId> > > > > > > <version>1.0-alpha-2-SNAPSHOT</version> > > > > > > </dependency> > > > > > > </dependencies> > > > > > > > > > > > > > > > > > > On 4/20/05, Mykel Alvis < [EMAIL PROTECTED]> wrote: > > > > > > > Yep. They're there...as SNAPSHOTS (doh!) When I surf to > > > > > > > http://www.ibiblio.org/maven/maven/jars/ > > > > > > > I see a file called > > > > wagon-file-1.0-alpha-2-SNAPSHOT.jar > > > > > > > But the file from the project, per project.xml and from output > of > > > > maven -X > > > > > > is wagon-file-1.0-alpha-2.jar > > > > > > > > > > > > > > -- snip -- > > > > > > > Received status code: 404 > > > > > > > File not found on one of the repos > > > > > > > java.io.FileNotFoundException: > > > > > > > > > > > > http://www.ibiblio.org/maven/maven/jars/wagon-file-1.0-alpha-2.jar > > > > > > > -- snip -- > > > > > > > > > > > > > > Do I need to change the version to xxx-SNAPSHOT? > > > > > > > > > > > > > > > > > > > > > > > > > > > > On 4/20/05, Brett Porter < [EMAIL PROTECTED] > wrote: > > > > > > > > On 4/21/05, Mykel Alvis <[EMAIL PROTECTED]> wrote: > > > > > > > > > My question is how to get maven1 to download those > > dependencies as > > > > > > part of > > > > > > > > > attaining the plugin:install goal. > > > > > > > > > > > > > > > > I don't understand why the main ones aren't working... they > are > > in > > > > the > > > > > > > > right place. > > > > > > > > > > > > > > > > For the others, you might need to put them in place until I > can > > move > > > > > > > > them across. > > > > > > > > > > > > > > > > > Do I need to surf to the spot, download the jars manually, > and > > > > > > manually > > > > > > > > > place them in my repository? That seems a little > > "counter-maven". > > > > > > > > > More specifically, should I have installed the plugin > plugin > > first > > > > so > > > > > > that > > > > > > > > > it would recognize the maven2 repository structure? Would > that > > > > help? > > > > > > > > > > > > > > > > No, m1 can't read the m2 repo yet. > > > > > > > > > > > > > > > > - Brett > > > > > > > > > > > > > > > > > > On 4/20/05, Brett Porter < [EMAIL PROTECTED] > wrote: > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://www.ibiblio.org/maven/org.apache.maven.wagon/jars/ > > > > > > > > > > > > > > > > > > > > Most of them seem to be there... I'll look into the > others, > > but > > > > you > > > > > > > > > > can get them from: > > > > > > > > > > > > > > > > > > > > > > > > > > > > http://www.ibiblio.org/maven2/org/apache/maven/wagon/ > > > > > > > > > > > > > > > > > > > > Either jsch should be fine... I'll probably update the > SVN > > > > version > > > > > > later > > > > > > > > > > on. > > > > > > > > > > > > > > > > > > > > Thanks, > > > > > > > > > > Brett > > > > > > > > > > > > > > > > > > > > On 4/21/05, Mykel Alvis < [EMAIL PROTECTED]> wrote: > > > > > > > > > > > Also, apparently there's a dependency on jsch-0.1.14in > > the > > > > plugin > > > > > > > > > > > Earlier you mentioned to change to 0.1.17 of jsch. I > was > > > > wondering > > > > > > if > > > > > > > > > > that > > > > > > > > > > > was still necessary/a good idea? > > > > > > > > > > > > > > > > > > > > > > On 4/20/05, Mykel Alvis < [EMAIL PROTECTED] > > wrote: > > > > > > > > > > > > > > > > > > > > > > > > Brett, > > > > > > > > > > > > I've gotten a distro from svn and tried the > > plugin:install. > > > > > > > > > > > > The following dependencies are apparently not > available > > to > > > > me. > > > > > > > > > > > > Wrong repo or something else? > > > > > > > > > > > > > > > > > > > > > > > > > > wagon-provider-api-1.0-alpha-3-SNAPSHOT.jar > > > > > > > > > > > > wagon-http-1.0-alpha-2.jar > > > > > > > > > > > > wagon-ftp-1.0-alpha-2.jar > > > > > > > > > > > > wagon-ssh-1.0-alpha-2.jar > > > > > > > > > > > > wagon-ssh-external-1.0-alpha-2.jar > > > > > > > > > > > > wagon-file-1.0-alpha-2.jar > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > > > > > >
