RE: Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin'
Thanks for the response. I resolved this issue by disabling access to the maven central plugin repo (http://repo1.maven.org/maven2/) and allowing my local repo to use a older version of the plugin like 2.0. Also, I'm currently using maven 2.0.7. Is this issue resolved for higher versions? Thanks, Venkat -Original Message- From: Vincent Siveton [mailto:vincent.sive...@gmail.com] Sent: Wednesday, March 04, 2009 3:29 PM To: Maven Users List Subject: Re: Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin' Hi Weird issue... maven-reporting-impl is defined in the pom! Several ideas: - rerun with maven 2.0.10 - run mvn -up - remove your local repo - be sure that the pom/jar in your repo managers are valids. Cheers, Vincent 2009/3/4, Krishnamurthi, Venkat : > Thanks for the response. This is the output with -e switch: > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error getting > reports from the plugin > 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find > the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in > the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:694) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:642) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:517) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) > 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:585) > at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find > the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in > the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:571) > at > org.apache.maven.plugin.DefaultPluginManager.getReport(DefaultPluginManager.java:495) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.getReports(DefaultLifecycleExecutor.java:683) > ... 18 more > Caused by: > org.codehaus.plexus.component.repository.exception.ComponentLookupException: > Unable to lookup component > 'org.apache.maven.plugin.Mojoorg.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license', > it could not be created > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:335) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:440) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:562) > ... 20 more > Caused by: > org.codehaus.plexus.component.factory.ComponentInstantiationException: Could > not instanciate component: role: 'null', implementation: > 'org.apache.maven.report.projectinfo.LicenseReport' > at > org.codehaus.plexus.component.factory.java.JavaComponentFactory.makeException(JavaComponentFactory.java:77) > at > org.codehaus.plexus.component.factory.java.JavaComponentFactory.new
RE: Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin'
188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$100(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195) at org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255) at org.codehaus.plexus.component.factory.java.JavaComponentFactory.newInstance(JavaComponentFactory.java:30) ... 26 more [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Wed Mar 04 13:27:51 EST 2009 [INFO] Final Memory: 44M/559M [INFO] Thanks, Venkat -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Wednesday, March 04, 2009 1:25 PM To: Maven Users List Subject: Re: Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin' [INFO] For more information, run Maven with the -e switch Could you try this and see if it gives any more information? With regards, Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Wed, Mar 4, 2009 at 5:42 PM, Krishnamurthi, Venkat wrote: > [INFO] For more information, run Maven with the -e switch - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Error getting reports from plugin:'org.apache.maven.plugins:maven-project-info-reports-plugin'
Hi, I'm getting the following error for all maven based projects that I have: Downloading: http://gcatfs1d.ny.ssltc.com:1/repository/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.pom - this realm = app0.child-container[org.apache.maven.plugins:maven-project-info-reports-plugin] urls[0] = file:/opt/zint/.m2/repository/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar urls[1] = file:/opt/zint/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar Number of imports: 4 import: org.codehaus.classworlds.en...@4891bb28 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@c51bc9e7 import: org.codehaus.classworlds.en...@bece5185 this realm = plexus.core urls[0] = file:/xenv/Maven/X/2.0.7/lib/maven-core-2.0.7-uber.jar Number of imports: 4 import: org.codehaus.classworlds.en...@4891bb28 import: org.codehaus.classworlds.en...@f8e44ca4 import: org.codehaus.classworlds.en...@c51bc9e7 import: org.codehaus.classworlds.en...@bece5185 - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' org/apache/maven/reporting/AbstractMavenReport [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 30 seconds [INFO] Finished at: Wed Mar 04 11:33:24 EST 2009 [INFO] Final Memory: 45M/550M [INFO] Please help me resolve this issue. Thanks, Venkat -Original Message- From: Nord, James [mailto:jn...@nds.com] Sent: Wednesday, March 04, 2009 11:35 AM To: Maven Users List Subject: RE: [maven-eclipse-plugin] Define compiler options in POM Can you not change the eclipse worksapce settings instead of the per project ones. Then when the settings get clobbered you will still be using the defaults - but the defaults are what you wanted. /James > -Original Message- > From: Daniele Dellafiore [mailto:ilde...@gmail.com] > Sent: 04 March 2009 14:19 > To: Maven Users List > Subject: Re: [maven-eclipse-plugin] Define compiler options in POM > > That is easy, I am talking about all the others: > > org.eclipse.jdt.core.compiler.problem.annotationSuperInterface=warning > org.eclipse.jdt.core.compiler.problem.autoboxing=warning > org.eclipse.jdt.core.compiler.problem.deprecation=warning > org.eclipse.jdt.core.compiler.problem.deprecationInDeprecatedC > ode=disabled > > and so on... > > On Wed, Mar 4, 2009 at 3:13 PM, Todd Thiessen > wrote: > > maven-compiler-plugin > > > > > >maven-compiler-plugin > > > > 1.5 > > 1.5 > > > > > > > > --- > > Todd Thiessen > > > > > >> -Original Message- > >> From: Daniele Dellafiore [mailto:ilde...@gmail.com] > >> Sent: Wednesday, March 04, 2009 9:10 AM > >> To: Maven Users List > >> Subject: [maven-eclipse-plugin] Define compiler options in POM > >> > >> Hi all. > >> > >> Hi have this issue: every time I run mvn eclipse:eclipse the > >> .settings folder of the project is cleaned and I lose my project > >> specific compiler settings. I would like to keep them or > at least be > >> able to define them in the POM. > >> > >> What solution do you suggest? I have not found any on the web... > >> > >> -- > >> Daniele Dellafiore > >> http://blog.ildella.net/ > >> > >> > - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > -- > Daniele Dellafiore > http://blog.ildella.net/ > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > ** This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone oth
RE: Specifying jdk version for maven-javadoc-plugin
Yeah. We have to have both jdk5 and jdk6. Only very few projects in cruisecontrol use jdk.. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2008 1:41 PM To: Maven Users List Subject: Re: Specifying jdk version for maven-javadoc-plugin Err, point at JDK6. ;-) Wayne On Fri, Sep 12, 2008 at 10:40 AM, Wayne Fay <[EMAIL PROTECTED]> wrote: > Is there a reason you cannot simply update the JAVA_HOME to point it at JDK5? > > Wayne > > On Fri, Sep 12, 2008 at 7:23 AM, Krishnamurthi, Venkat > <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I'm using jdk 1.6 for the maven compiler plugin. But JAVA_HOME env is >> set to jdk 1.5. So during the site phase, generating javadoc goal fails. >> It's because it still uses jdk 1.5. Is there a way to specify the jdk >> version to be used for the maven-javadoc-plugin and also following >> plugins: >> >> maven-pmd-plugin >> cobertura-maven-plugin >> >> Thanks, >> Venkat >> >> - >> 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]
Specifying jdk version for maven-javadoc-plugin
Hi, I'm using jdk 1.6 for the maven compiler plugin. But JAVA_HOME env is set to jdk 1.5. So during the site phase, generating javadoc goal fails. It's because it still uses jdk 1.5. Is there a way to specify the jdk version to be used for the maven-javadoc-plugin and also following plugins: maven-pmd-plugin cobertura-maven-plugin Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with dependencies report generation during site:site
Thanks for your feedback Dennis.. We were able to resolve this issue, when we commented out this particular dependency: > > com.sun > tools > 1.5 > system > ${java.home}/../lib/tools.jar > > However, we are unable to diagnose the exact cause for this. Is this because of the or elements that are not readable by the Maven Project Info Reports Plugin? Thanks, Venkat -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Saturday, August 02, 2008 7:34 AM To: Maven Users List Subject: Re: Problem with dependencies report generation during site:site I tried your POM. Here are my findings: [WARNING] While downloading javax.xml:jaxws-api:2.0 This artifact has been relocated to javax.xml.ws:jaxws-api:2.0. suggests that you should change the groupId for that dependency. The following jars are not available in the central repo, so I had to comment them out to be able to build: com.sun.xml jaxb-impl 2.0 com.sun.xml jaxws-rt 2.0 javax.jws jsr181-api 1.0 I have not seen the exception you had, but the stack trace indicates that one of the jars are not readable for the Maven Project Info Reports Plugin, when it is creating the Dependencies report. Since I don't get the error I suspect that it is one of the three above. Krishnamurthi, Venkat wrote: > Thanks a lot for your help! Please find the pom.xml below > > http://maven.apache.org/POM/4.0.0"; > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 > http://maven.apache.org/maven-v4_0_0.xsd";> > 4.0.0 > > asap > quasi > jar > 2.0-SNAPSHOT > Quantum Project > > > > > > > > > com.sun.xml > jaxb-impl > 2.0 > > > > javax.xml > jsr173 > 1.0 > > > > com.sun.xml > jaxws-rt > 2.0 > > > > javax.jms > jms > 1.1 > > > > javax.jws > jsr181-api > 1.0 > > > > javax.xml > jaxb-api > 2.0 > > > > javax.xml > jaxws-api > 2.0 > > > > javax.transaction > jta > 1.0.1B > > > > com.sun > tools > 1.5 > system > ${java.home}/../lib/tools.jar > > > > > ${artifactId}-${version}-${label} > > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.5 > 1.5 > > org/**/*.java > > > > > > org.apache.maven.plugins > maven-assembly-plugin > > > distribution-bin > package > > assembly > > > src > > > etc/qas-bin-assembly.xml > > etc/xenv-assembly.xml > > > > ${artifactId}-${version}-${label} > > ${artifactId}-${version}-${label} > > > > > > > > > > > -Original Message- > From: Dennis Lundberg [mailto:[EMAIL PROTECTED] > Sent: Friday, August 01, 2008 3:20 PM > To: Maven Users List > Subject: Re: Problem with dependencies report generation during > site:site > > If you supply us with a POM we might be able to help you. > > > Krishnamurthi, Venkat wrote: >> Hi, >> >> I'm using maven 2.0.7 and I'm getting the following error during >> dependencies report generation stage of site:site: >> >> >> >> >> Maven Site Plugin >> >> [INFO] Generating "Dependencies" report
RE: Problem with dependencies report generation during site:site
Thanks a lot for your help! Please find the pom.xml below http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 asap quasi jar 2.0-SNAPSHOT Quantum Project com.sun.xml jaxb-impl 2.0 javax.xml jsr173 1.0 com.sun.xml jaxws-rt 2.0 javax.jms jms 1.1 javax.jws jsr181-api 1.0 javax.xml jaxb-api 2.0 javax.xml jaxws-api 2.0 javax.transaction jta 1.0.1B com.sun tools 1.5 system ${java.home}/../lib/tools.jar ${artifactId}-${version}-${label} org.apache.maven.plugins maven-compiler-plugin 1.5 1.5 org/**/*.java org.apache.maven.plugins maven-assembly-plugin distribution-bin package assembly src etc/qas-bin-assembly.xml etc/xenv-assembly.xml ${artifactId}-${version}-${label} ${artifactId}-${version}-${label} -Original Message- From: Dennis Lundberg [mailto:[EMAIL PROTECTED] Sent: Friday, August 01, 2008 3:20 PM To: Maven Users List Subject: Re: Problem with dependencies report generation during site:site If you supply us with a POM we might be able to help you. Krishnamurthi, Venkat wrote: > Hi, > > I'm using maven 2.0.7 and I'm getting the following error during > dependencies report generation stage of site:site: > > > > > Maven Site Plugin > > [INFO] Generating "Dependencies" report. > > [INFO] > -- > -- > > [ERROR] FATAL ERROR > > [INFO] > -- > -- > > [INFO] null > > [INFO] > -- > -- > > [INFO] Trace > java.lang.NullPointerException > > at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:165) > at > org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClas > se > sAnalysis.java:92) at > org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDe > pe > ndencyDetails(Dependencies.java:285) at > org.apache.maven.report.projectinfo.dependencies.renderer.Dependencies > Re nderer.renderSectionDependencyFileDetails(Depende > > nciesRenderer.java:426) > > at > org.apache.maven.report.projectinfo.dependencies.renderer.Dependencies > Re > nderer.renderBody(DependenciesRenderer.java:233) at > org.apache.maven.reporting.AbstractMavenReportRenderer.render(Abstract > Ma > venReportRenderer.java:65) at > org.apache.maven.report.projectinfo.DependenciesReport.executeReport(D > ep > endenciesReport.java:228) at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenR > ep > ort.java:90) at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Re > po > rtDocumentRenderer.java:139) at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(D > ef > aultSiteRenderer.java:269) at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(Default > Si > teRenderer.java:101) at > org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) > > at > org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) > > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugin > Ma > nager.java:447) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defau > lt > LifecycleExecutor.java:539) at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif &g
Problem with dependencies report generation during site:site
Hi, I'm using maven 2.0.7 and I'm getting the following error during dependencies report generation stage of site:site: Maven Site Plugin [INFO] Generating "Dependencies" report. [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.bcel.classfile.ClassParser.parse(ClassParser.java:165) at org.apache.maven.shared.jar.classes.JarClassesAnalysis.analyze(JarClasse sAnalysis.java:92) at org.apache.maven.report.projectinfo.dependencies.Dependencies.getJarDepe ndencyDetails(Dependencies.java:285) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderSectionDependencyFileDetails(Depende nciesRenderer.java:426) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderBody(DependenciesRenderer.java:233) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa venReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Dep endenciesReport.java:228) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep ort.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Repo rtDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Def aultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSi teRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Please help me resolve this issue. Thanks, venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
2.0.8 also throws the same exception. Please let me know if there are any solutions to this issue: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:526) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:234) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMave nProjectFromRepository(RepositoryUtils.java:316) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.j ava:623) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderBody(DependenciesRenderer.java:274) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa venReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Dep endenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep ort.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Repo rtDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Def aultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSi teRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 2 minutes 44 seconds [INFO] Finished at: Tue Jul 29 14:16:03 EDT 2008 [INFO] Final Memory: 80M/547M [INFO] Thanks, Venkat -Original Message- From: Krishnamurthi, Venkat [CMB-IT] Sent: Tuesday, July 29, 2008 5:56 PM To: Maven Users List Subject: RE: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) Currently I'm using 2.0.7. It has been working fine till today. I'm facing the same problem with 2.0.8 as well. -Original Message- From: Martin [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2008 5:37 PM To: Maven Users List Subject: Re: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) You must be working with RepositoryUtils on an older unsupported version What happens when you upgrade to 2.08? Martin - Original Message ----- From: "Krishnamurthi, Venkat " <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Tuesday, July 29, 2008 4:04 PM Subject: RE: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) Hi, Can someone please explain what this error means? [INFO] --
RE: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
Currently I'm using 2.0.7. It has been working fine till today. I'm facing the same problem with 2.0.8 as well. -Original Message- From: Martin [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 29, 2008 5:37 PM To: Maven Users List Subject: Re: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) You must be working with RepositoryUtils on an older unsupported version What happens when you upgrade to 2.08? Martin - Original Message ----- From: "Krishnamurthi, Venkat " <[EMAIL PROTECTED]> To: "Maven Users List" Sent: Tuesday, July 29, 2008 4:04 PM Subject: RE: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) Hi, Can someone please explain what this error means? [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:526) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:234) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMave nProjectFromRepository(RepositoryUtils.java:316) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.j ava:623) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderBody(DependenciesRenderer.java:274) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa venReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Dep endenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep ort.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Repo rtDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Def aultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSi teRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 2 minutes 44 seconds [INFO] Finished at: Tue Jul 29 14:16:03 EDT 2008 [INFO] Final Memory: 80M/547M [INFO] Thanks, Venkat -Original Message- From: Krishnamurthi, Venkat [CMB-IT] Sent: Tuesday, July 29, 2008 2:31 PM To: Maven Users List Subject: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) Hi, I'm getting the following exception during the site phase: [INFO] -
RE: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
Hi, Can someone please explain what this error means? [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:526) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:234) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMave nProjectFromRepository(RepositoryUtils.java:316) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.j ava:623) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderBody(DependenciesRenderer.java:274) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa venReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Dep endenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep ort.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Repo rtDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Def aultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSi teRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 2 minutes 44 seconds [INFO] Finished at: Tue Jul 29 14:16:03 EDT 2008 [INFO] Final Memory: 80M/547M [INFO] Thanks, Venkat -Original Message- From: Krishnamurthi, Venkat [CMB-IT] Sent: Tuesday, July 29, 2008 2:31 PM To: Maven Users List Subject: Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) Hi, I'm getting the following exception during the site phase: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:526) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:234) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMave nProjectFromRepository(RepositoryUtils.java:31
Null Pointer Exception at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:92)
Hi, I'm getting the following exception during the site phase: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:92) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(Defau ltArtifactResolver.java:73) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromReposit ory(DefaultMavenProjectBuilder.java:526) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository( DefaultMavenProjectBuilder.java:234) at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMave nProjectFromRepository(RepositoryUtils.java:316) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderSectionDependencyRepositoryLocations(DependenciesRenderer.j ava:623) at org.apache.maven.report.projectinfo.dependencies.renderer.DependenciesRe nderer.renderBody(DependenciesRenderer.java:274) at org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMa venReportRenderer.java:65) at org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Dep endenciesReport.java:239) at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRep ort.java:90) at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(Repo rtDocumentRenderer.java:139) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Def aultSiteRenderer.java:269) at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSi teRenderer.java:101) at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 2 minutes 44 seconds [INFO] Finished at: Tue Jul 29 14:16:03 EDT 2008 [INFO] Final Memory: 80M/547M [INFO] Please help me resolve this issue, Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Error deploying to a remote respository using scm
This is the output of ssh2 -V: ssh2: SSH Tectia Server 4.4.8 on i686-pc-linux-gnu Build: 21 Crypto library version: SSH Cryptographic Library, version 1.2.6 FIPS certification mode: DISABLED Product: SSH Tectia Server (A) License type: commercial Thanks, Venkat -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 7:36 PM To: Maven Users List Subject: Re: Error deploying to a remote respository using scm The stack trace says very clearly: Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed to authenticate. (or you have too old ssh2 installed, check with ssh2 -V) So, what does "ssh2 -V" say? Wayne On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote: > Hi, > > I'm trying to deploy a snapshot jar to a remote repository. I followed > the instructions given here: > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ss > h- > external.html > > However, when I execute mvn deploy, I get the following error: > > [INFO] [deploy:deploy] > [INFO] Retrieving previous build number from scp_snapshot [WARNING] > repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' > could not be retrieved from repository: scp_snapshot due to an error: > Exit code: 78 - warning: Authentication failed. > Disconnected (local); connection lost (Connection closed by remote > host.). > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > to authenticate. (or you have too old ssh2 installed, check with ssh2 > -V) > > [INFO] Repository 'scp_snapshot' will be blacklisted > Uploading: > scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-SNA > PS > HOT.jar > [INFO] > -- > -- > [ERROR] BUILD ERROR > [INFO] > -- > -- [INFO] Error deploying artifact: Error executing command for > transfer > > Exit code 74 - warning: Authentication failed. > Disconnected (local); connection lost (Connection closed by remote > host.). > Disconnect reason 10, exit code = 74 > > My pom.xml has the following distributionManagement: > > > > > false > scp_snapshot > SCP Snapshot Repository > scpexe://eqp2fcc:1080/scp_snapshot > default > > > > Also, I added the following to my settings.xml > > > > scp_snapshot > my_username > my_password > > > > Please help me resolve this issue. > > > Thanks, > Venkat > > - > 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: Error deploying to a remote respository using scm
There was an issue with my server path in the last case (I included port no.). Now I removed the port number and gave the path from root. Now, I get the following error: [INFO] [deploy:deploy] [INFO] Retrieving previous build number from scp_inhouse_snapshot [WARNING] repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' could not be retrieved from repository: scp_snapshot due to an error: Exit code: 78 - You are authorized to use this System for approved business purposes only. Use for any other purpose is prohibited. All transactional records, reports, e-mail, software, and other data generated by or residing upon this System are the property of the Company and may be used by the Company for any purpose. Authorized and unauthorized activities may be monitored. Keyboard-interactive: PAM authentication Keyboard-interactive: PAM authentication Keyboard-interactive: PAM authentication warning: Authentication failed. Disconnected (local); no more authentication methods available (No further authentication methods available.). Disconnect reason 14, exit code = 78scp: warning: ssh2 client failed to authenticate. (or you have too old ssh2 installed, check with ssh2 -V) [INFO] Repository 'scp_snapshot' will be blacklisted Uploading: scpexe://eqz2pff:/demo/maven2_repositories/scp_snapshot/demo/demo/1.0-SN APSHOT/demo-1.0-SNAPSHOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Error executing command for transfer Exit code 78 - You are authorized to use this System for approved business purposes only. Use for any other purpose is prohibited. All transactional records, reports, e-mail, software, and other data generated by or residing upon this System are the property of the Company and may be used by the Company for any purpose. Authorized and unauthorized activities may be monitored. Keyboard-interactive: PAM authentication Keyboard-interactive: PAM authentication Keyboard-interactive: PAM authentication warning: Authentication failed. Disconnected (local); no more authentication methods available (No further authentication methods available.). Disconnect reason 14, exit code = 78 Thanks for your help. Best Regards, Venkat -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Thursday, June 05, 2008 9:56 AM To: Maven Users List Subject: Re: Error deploying to a remote respository using scm In additional to that, I am trying any way I can to deploy site docs: I keep getting this error: *[INFO] [site:deploy] The authenticity of host '208.96.48.200' can't be established. RSA key fingerprint is 15:6f:d1:60:05:21:dd:43:4b:4d:d6:9e:4f:3b:aa:e4. Are you sure you wan*t to continue connecting? (yes/no): I have create a ppk and key from putty, and have added this to my pom.xml site.internal site.internal ${siteUrl} And here is my settings.xml site.internal [username] [password] 664 755 c:/ssh/internal-private.ppk plink pscp ... scp://208.0.50.1/:/var/www/html/site I have spent all day on this, and can't find anything that fixes this issue. On Thu, Jun 5, 2008 at 6:49 AM, Krishnamurthi, Venkat < [EMAIL PROTECTED]> wrote: > Hi, > > I get the same error when I execute ssh2 -V on my windows XP machine: > > C:\ssh2 -V > 'ssh2' is not recognized as an internal or external command, operable > program or batch file. > > Please help me resolve this. > > Thanks, > Venkat > > -Original Message- > From: Mick Knutson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 04, 2008 7:40 PM > To: Maven Users List > Subject: Re: Error deploying to a remote respository using scm > > on XP, I use that command adn get: > > *C:\opt\baselogic>ssh2 -V > 'ssh2' is not recognized as an internal or external command, operable > program or batch file. > > C:\opt\baselogic>ssh -V > 'ssh' is not recognized as an internal or external command, operable > program or batch file. > > C:\opt\baselogic> > * > > Then when I try to deploy with scpexe it does the same thing. > > > > On Wed, Jun 4, 2008 at 4:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > The stack trace says very clearly: > > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > > to authenticate. (or you have too old ssh2 installed, check with > > ssh2 > > -V) > > > > So, what does "ssh2 -V" say? > > > > Wayne > > > > On Wed, Jun 4, 2008 at 5:12 PM,
RE: Error deploying to a remote respository using scm
Hi, I get the same error when I execute ssh2 -V on my windows XP machine: C:\ssh2 -V 'ssh2' is not recognized as an internal or external command, operable program or batch file. Please help me resolve this. Thanks, Venkat -Original Message- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Wednesday, June 04, 2008 7:40 PM To: Maven Users List Subject: Re: Error deploying to a remote respository using scm on XP, I use that command adn get: *C:\opt\baselogic>ssh2 -V 'ssh2' is not recognized as an internal or external command, operable program or batch file. C:\opt\baselogic>ssh -V 'ssh' is not recognized as an internal or external command, operable program or batch file. C:\opt\baselogic> * Then when I try to deploy with scpexe it does the same thing. On Wed, Jun 4, 2008 at 4:36 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > The stack trace says very clearly: > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > to authenticate. (or you have too old ssh2 installed, check with ssh2 > -V) > > So, what does "ssh2 -V" say? > > Wayne > > On Wed, Jun 4, 2008 at 5:12 PM, Krishnamurthi, Venkat > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I'm trying to deploy a snapshot jar to a remote repository. I > > followed the instructions given here: > > > > http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy- > > ssh- > > external.html > > > > However, when I execute mvn deploy, I get the following error: > > > > [INFO] [deploy:deploy] > > [INFO] Retrieving previous build number from scp_snapshot [WARNING] > > repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' > > could not be retrieved from repository: scp_snapshot due to an error: > > Exit code: 78 - warning: Authentication failed. > > Disconnected (local); connection lost (Connection closed by remote > > host.). > > Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed > > to authenticate. (or you have too old ssh2 installed, check with > > ssh2 -V) > > > > [INFO] Repository 'scp_snapshot' will be blacklisted > > Uploading: > > scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-S > > NAPS > > HOT.jar > > [INFO] > > > > > > [ERROR] BUILD ERROR > > [INFO] > > > > [INFO] Error deploying artifact: Error executing command for > > transfer > > > > Exit code 74 - warning: Authentication failed. > > Disconnected (local); connection lost (Connection closed by remote > > host.). > > Disconnect reason 10, exit code = 74 > > > > My pom.xml has the following distributionManagement: > > > > > > > > > > false > > scp_snapshot > > SCP Snapshot Repository > > scpexe://eqp2fcc:1080/scp_snapshot > > default > > > > > > > > Also, I added the following to my settings.xml > > > > > > > > scp_snapshot > > my_username > > my_password > > > > > > > > Please help me resolve this issue. > > > > > > Thanks, > > Venkat > > > > > > - 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] > > -- --- Thank You... Mick Knutson BASE Logic, inc. Website: http://baselogic.com Blog: http://baselogic.com/blog BLiNC Magazine: http://blincmagazine.com Linked IN: http://linkedin.com/in/mickknutson DJ Mick: http://djmick.com MySpace: http://myspace.com/mickknutson Tahoe: http://tahoe.baselogic.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Error deploying to a remote respository using scm
Hi, I'm trying to deploy a snapshot jar to a remote repository. I followed the instructions given here: http://maven.apache.org/plugins/maven-deploy-plugin/examples/deploy-ssh- external.html However, when I execute mvn deploy, I get the following error: [INFO] [deploy:deploy] [INFO] Retrieving previous build number from scp_snapshot [WARNING] repository metadata for: 'snapshot demo:demo:1.0-SNAPSHOT' could not be retrieved from repository: scp_snapshot due to an error: Exit code: 78 - warning: Authentication failed. Disconnected (local); connection lost (Connection closed by remote host.). Disconnect reason 10, exit code = 74scp: warning: ssh2 client failed to authenticate. (or you have too old ssh2 installed, check with ssh2 -V) [INFO] Repository 'scp_snapshot' will be blacklisted Uploading: scpexe://eqp2fcc:1080/scp_snapshot/demo/demo/1.0-SNAPSHOT/demo-1.0-SNAPS HOT.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error deploying artifact: Error executing command for transfer Exit code 74 - warning: Authentication failed. Disconnected (local); connection lost (Connection closed by remote host.). Disconnect reason 10, exit code = 74 My pom.xml has the following distributionManagement: false scp_snapshot SCP Snapshot Repository scpexe://eqp2fcc:1080/scp_snapshot default Also, I added the following to my settings.xml scp_snapshot my_username my_password Please help me resolve this issue. Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Overriding parent's distribution management
Hi, I'm trying to override a parent pom's distribution management through the child's pom. (Deploy the artifacts in different directories). When I tried adding a element in the child pom, it is still picking up the details from the parent's pom. Please help me resolve this issue. Thanks and Regards, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Root directory of the assembly
Hi, How do I set the root directory of the assembly in my own assembly descriptor? Can it be set outside the project's directory. Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven-assembly-plugin
Thanks John. That worked. Is there a way to override the location which is currently {basedir}/target/finalName-.dir/lib to any other directory outside this project's directory. Thanks and Regards, Venkat -Original Message- From: John Casey [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 16, 2008 10:45 AM To: Maven Users List Subject: Re: Maven-assembly-plugin To change the format for the dependency artifacts, add something like the following to the dependencySet: ${artifact.artifactId}.${artifact.extension} For other options to fine-tune your assembly configuration, see: http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html -john On Wed, Apr 16, 2008 at 10:32 AM, Krishnamurthi, Venkat < [EMAIL PROTECTED]> wrote: > > > > Hi, > > I used the following assembly descriptor to create an assembly > directory with my project's jar and all the jars that are it's dependencies: > > >distribution > >dir > >false > > >target > > >*.jar > > > > > >/lib >false >runtime > > > > > > However, all the jars that are copied inside lib/ had the version > numbers attached to them. Is there a way to filter out these version > numbers and just have the jars. > > Also, if I want to create this assembly directory at a location > outside this projects's target directory, where do I specify that path. > > > Thanks and Regards, > Venkat > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- John Casey --- Maven Developer (http://maven.apache.org) --- Blog: http://www.ejlife.net/blogs/buildchimp - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven-assembly-plugin
Hi, I used the following assembly descriptor to create an assembly directory with my project's jar and all the jars that are it's dependencies: distribution dir false target *.jar /lib false runtime However, all the jars that are copied inside lib/ had the version numbers attached to them. Is there a way to filter out these version numbers and just have the jars. Also, if I want to create this assembly directory at a location outside this projects's target directory, where do I specify that path. Thanks and Regards, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven-assembly-plugin
Hi, I used the following assembly descriptor to create an assembly directory with my project's jar and all the jars that are it's dependencies: distribution dir false target *.jar /lib false runtime However, all the jars that are copied inside lib/ had the version numbers attached to them. Is there a way to filter out these version numbers and just have the jars. Also, if I want to create this assembly directory at a location outside this projects's target directory, where do I specify that path. Thanks and Regards, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven2 assembly plug-in
Hi, I'm trying to use maven-assembly plugin. Should I add it in a separate assembly.xml or can I have it as a part of pom.xml. If I add it in pom.xml, I get the following error: Parse error reading POM. Reason: Unrecognised tag: 'assembly' (position: START_TAG seen ...\n\t... @170:12) for project Thanks, Venkat -Original Message- From: tadamski [mailto:[EMAIL PROTECTED] Sent: Monday, April 14, 2008 2:39 PM To: users@maven.apache.org Subject: Re: maven2 assembly plug-in within the configuration tags where you setup the assembly plugin, use the name Urooj Khan wrote: > > Sorry if this is a repost... Not sure if the first one got out... > > > > -- Forwarded message -- > From: Urooj Khan <[EMAIL PROTECTED]> > Date: Thu, 27 Mar 2008 20:04:24 -0400 > Subject: maven2 assembly plug-in > To: users@maven.apache.org > > i'm using the assembly plug-in to create an assembly in the form of a > directory which contains my jar file which is created by maven and it > also contains a lib directory with all the jar files that are > dependencies of this build > > this is what my assembly xml looks like > > > dist > > dir > > false > > > target > > > *.jar > > > > > > /lib > false > runtime > > > > > > when i run $>mvn clean package assembly:assembly > > i get my ${project}.jar in the target directory and i also get a > directory called ${project.build.dir} inside the target directory. > this directory contains my ${project}.jar and a /lib directory with > all the dependency jars... > > i want to rename ${project.build.dir} that maven creates to just > ${project}.dir > > any idea how i can do that? > > please help. > > thanks. > > -uk > > -- > Sent from Gmail for mobile | mobile.google.com > > Urooj Khan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/maven2-assembly-plug-in-tp16342889s177p16685501.ht ml 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]
RE: Using antrun plugin
I want this dependency as a run-time dependency. I'm using the antrun plugin to launch the application. Thanks, Venkat -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, April 11, 2008 5:18 PM To: Maven Users List Subject: Re: Using antrun plugin You should probably just add the jar as a dependency in your pom, just like any other dependency, and then it will be included in the compile classpath assuming you set the scope properly. Wayne On 4/11/08, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote: > > Hi, > > I'm trying to append an additional jar to "maven.compile.classpath" > while using the antrun plugin. > > > > refid="maven.compile.classpath"/> > > > How do I add a maven snapshot build jar (or any other external) to > this classpath? > > Thanks, > Venkat > > > > - > 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]
Using antrun plugin
Hi, I'm trying to append an additional jar to "maven.compile.classpath" while using the antrun plugin. How do I add a maven snapshot build jar (or any other external) to this classpath? Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing multiple files in the local repository using mvn install?
Hi, Is there a way to install multiple jars in the local repository using the mvn install:install-file command? Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing multiple files in the local repository using mvn istall?
Hi, Is there a way to install multiple jars in the local repository using the mvn install:install-file command? Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven ignores my archetype selection
Thanks! -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 4:01 PM To: Maven Users List Subject: Re: Maven ignores my archetype selection On Mon, Feb 25, 2008 at 1:51 PM, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote: > That works. Thanks! However, maven does not pick up the URL's > specified under or in settings.xml. > How do we address that issue? It's a known issue: http://jira.codehaus.org/browse/ARCHETYPE-59 . Issues 81 and 89 may also be relevant. This isn't just an Archetype problem, the Stage plugin suffers from the same thing. If there is no "project" (== pom.xml in the current directory) then Maven does not "see" your settings.xml file. -- Wendy - 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: Maven ignores my archetype selection
That works. Thanks! However, maven does not pick up the URL's specified under or in settings.xml. How do we address that issue? -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 3:29 PM To: Maven Users List Subject: Re: Maven ignores my archetype selection On Mon, Feb 25, 2008 at 1:21 PM, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote: > But the archetype I'm trying to use is in an inhouse remote repository. > I have specified that in my settings.xml. However, Maven is still > unable to pick that up from settings.xml. > I also tried -DarchetypeRepository=. The 2.0-alpha-2 release was supposed to restore backwards compatibility, and the parameter used to be -DremoteRepositories=... . Does that work? Old docs: http://maven.apache.org/plugins/maven-archetype-plugin-1.0-alpha-7/creat e-mojo.html -- Wendy - 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: Maven ignores my archetype selection
That works!!! Thanks a lot!! -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 3:29 PM To: Maven Users List Subject: Re: Maven ignores my archetype selection On Mon, Feb 25, 2008 at 1:21 PM, Krishnamurthi, Venkat <[EMAIL PROTECTED]> wrote: > But the archetype I'm trying to use is in an inhouse remote repository. > I have specified that in my settings.xml. However, Maven is still > unable to pick that up from settings.xml. > I also tried -DarchetypeRepository=. The 2.0-alpha-2 release was supposed to restore backwards compatibility, and the parameter used to be -DremoteRepositories=... . Does that work? Old docs: http://maven.apache.org/plugins/maven-archetype-plugin-1.0-alpha-7/creat e-mojo.html -- Wendy - 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: Maven ignores my archetype selection
Hi Kalle, I'm running into a similar problem. But the archetype I'm trying to use is in an inhouse remote repository. I have specified that in my settings.xml. However, Maven is still unable to pick that up from settings.xml. I also tried -DarchetypeRepository=. When I executed: I get the following error log: mvn archetype:create -DarchetypeGroupId=com.myorg.2008 -DarchetypeArtifactId=custom-archetype -DarchetypeVersion=1.0-SNAPSHOT -DgroupId=Custom-Venkat -DartifactId=Sample-Venkat [INFO] Scanning for projects... [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [org.apache.maven.plugins:maven-archetype-plugin:1.0-alpha-7:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on => 'false'. [INFO] Setting property: resource.loader => 'classpath'. [INFO] Setting property: resource.manager.logwhenfound => 'false'. [INFO] ** [INFO] Starting Jakarta Velocity v1.4 [INFO] RuntimeInstance initializing. [INFO] Default Properties File: org/apache/velocity/runtime/defaults/velocity.properties [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime.resource.ResourceManagerImpl) [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader [INFO] ClasspathResourceLoader : initialization starting. [INFO] ClasspathResourceLoader : initialization complete. [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource.ResourceCacheImpl) [INFO] Default ResourceManager initialization complete. [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [INFO] Created: 20 parsers. [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org.apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'VM_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be global in scope if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [archetype:create] [INFO] Defaulting package to group ID: Custom-Venkat [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: com.myorg.2008 ArtifactId: custom-archetype Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.myorg.2008 -DartifactId=custom-archetype \ -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.myorg.2008 -DartifactId=custom-archetype \ -Dversion=1.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file \ -Durl=[url] -DrepositoryId=[id] com.myorg.2008:custom-archetype:jar:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Mon Feb 25 15:08:54 EST 2008 [INFO] Final Memory: 8M/358M [INFO] Thanks, Venkat -Original Message- From: Kalle Korhonen [mailto:[EMAIL PROTECTED] Sent: Thursday, February 21, 2008 6:19 PM To: Maven Users List Subject: Re: Maven ignores my archetype selection Tom, I already replied to your comment you left at http://docs.codehaus.org/display/TRAILS/Quick+Start with the same informatoin others have provided: use