I just read a thread over at the Dev list [1] which talked about these stub plugins. Could you run mvn help:effective-pom to see which deploy plugin version is resolved?
Hth, [1] http://www.nabble.com/Unintended-usage-of-core-plugin-stubs-td19633933.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, Sep 23, 2008 at 10:51 PM, smitherz <[EMAIL PROTECTED]> wrote: > > I just figured out I seem to be picking up this ... > [DEBUG] > org.apache.maven.plugins:maven-deploy-plugin:maven-plugin:0.1-stub-SNAPSHOT:runtime > (selected for runtime) > > Now, I have specified every plugin declared in my pom to release versions. > How do I get this one forced out? I have > ... > <plugin> > <artifactId>maven-deploy-plugin</artifactId> > <version>2.4</version> > </plugin> > ... > defined also. Seems to be ignoring it. > > Scott > > > smitherz wrote: >> >> Hi all, >> >> I am fairly new to maven but have had it working for almost a year with no >> real issues. Today I was trying to fix my >> build problem in continuum and found out it was maven or a plugin that has >> possibly changed behavior. >> >> I run a build on about 30 modules from continuum and use a command from >> continuum like... >> mvn -e -Ddeploylocation=file:///home/apache/ci_repo clean deploy >> >> Running the same maven command manually gets this same behavior as >> continuum does. >> I noticed that the last time the files in that tree were updated was the >> 9/19/2008. I also found that the jars I was >> successfully creating were in their respective workspace/target >> directories. They were no longer getting copied to >> the "-Ddeploylocation=" directory. Instead I am seeing this at the end of >> my build logs. >> >> ..... >> [INFO] [install:install] >> [INFO] [MAVEN-CORE-IT-LOG] Using output file path: >> target/install-install.txt >> [INFO] [MAVEN-CORE-IT-LOG] Creating output file: >> /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/install-install.txt >> [INFO] [MAVEN-CORE-IT-LOG] Created output file: >> /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/install-install.txt >> [INFO] [deploy:deploy] >> [INFO] [MAVEN-CORE-IT-LOG] Using output file path: >> target/deploy-deploy.txt >> [INFO] [MAVEN-CORE-IT-LOG] Creating output file: >> /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/deploy-deploy.txt >> [INFO] [MAVEN-CORE-IT-LOG] Created output file: >> /usr/local/AppServer/default_host/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/28/target/deploy-deploy.txt >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD SUCCESSFUL >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 4 minutes 16 seconds >> [INFO] Finished at: Tue Sep 23 12:33:32 EDT 2008 >> [INFO] Final Memory: 63M/233M >> [INFO] >> ------------------------------------------------------------------------ >> >> Those deploy-deploy.txt and install-install.txt files are all zero bytes. >> >> Help? I am at a loss as to what I need to adjust to get the previous >> behavior of the copy. My guess is that a plugin >> was updated and I got the new functions. I am trying to nail down my >> <version> info in my poms but it takes time. >> >> I am using Maven 2.0.8 and a 1.5 jdk. >> >> thanks, >> Scott >> >> > > -- > View this message in context: > http://www.nabble.com/deploy-goal-no-longer-deploying-tp19634893p19636766.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > 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]
