[UPDATE]
the clean goal runs smoothely all over the projects of the solution, the problem now while running the compile goal, below the error message:
[INFO] Total time: 19.427s
[INFO] Finished at: Fri Jun 29 11:46:28 WEST 2012
[INFO] Final Memory: 15M/306M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.npanday.plugins:maven-aspx-plugin:1.4.0-incubating:compile (default-compile) on project B3GMcsInterface: NPANDAY-900-006: Unable to Compile: Language = ASP, Vendor = null, ArtifactType = asp, Source Directory = C:\Users\CASA-WS001\Desktop\Gateway\ProjectName: NPANDAY-040-001: Could not execute: Command = cmd.exe /X /C "aspnet_compiler -v " /MyArtifactId" -p C:\Users\CASA-W~1\AppData\Local\Temp\maven-aspx-plugin-3088047295012139775\src -u -f C:\Users\CASA-W~1\AppData\Local\Temp\maven-aspx-plugin-3088047295012139775\dest -nologo -fixednames", Result = 1 -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR] mvn -rf :B3GMcsInterface
NPanday Execution Failed!, with exit code: 1
[END OF UPDATE]
i'm trying to make the build of simple web application using NPanday, i am using the incubating 1.4.0 plugin for VS2010, i have successfully built C# Console or Libraries Projects using maven, but when i tried to clean a web application i encounter this kind of error
Below is the error output.
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1.628s
[INFO] Finished at: Tue Jun 26 17:53:56 WET 2012
[INFO] Final Memory: 6M/16M
[INFO] ------------------------------------------------------------------------
[ERROR] Error resolving version for plugin 'npanday.plugin:maven-aspx-plugin' from the repositories [local (C:\Users\user1.m2\repository), central (http://repo.maven.apache.org/maven2)]: Plugin not found in any plugin repository -> [Help1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginVersionResolutionException
any help is appreciated.
Thank You.
The problem is the "npanday.plugin" in "npanday.plugin:maven-aspx-plugin"... It must be wrongly stated in one of the life cycles.
Things have moved to "org.apache.npanday.plugins": http://search.maven.org/#search%7Cga%7C1%7Ca%3A%22maven-aspx-plugin%22
Try using 1.5.0-SNAPSHOT from the following repository. It contains a mass of improvements! I'm using it in production.
<pluginRepositories>
<pluginRepository>
<releases>
<enabled>false</enabled>
</releases>
<id>npanday.snapshots</id>
<name>NPanday Snapshot Repository</name>
<url>http://vmbuild.apache.org/archiva/repository/npanday-snapshots</url>
</pluginRepository>
</pluginRepositories>
I think you have to use a repository manager and define a supplemental repository which contains the given dependencies / plugins.
Error is related plugins order in pom.xml:
If maven-compile-plugin is before maven-aspx-plugin, you get the error.
But if the order is maven-aspx-plugin and then maven-compile-plugin, mvn compile works
Snip of the correct pom.xml:
....
<plugins>
<plugin>
<groupId>org.apache.npanday.plugins</groupId>
<artifactId>maven-aspx-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<frameworkVersion>4.0</frameworkVersion>
</configuration>
</plugin>
<plugin>
<groupId>org.apache.npanday.plugins</groupId>
<artifactId>maven-compile-plugin</artifactId>
<version>1.4.0-incubating</version>
<extensions>true</extensions>
....
Related
Similar to the problem outlined here trying to build a the (newer) Artifactory OSS 7.46.11 fails on non-resolvable artifacts. Adding JCenter does not work anymore as a solution because JCenter is dead and apparently the read-only archive version also doesn't provide the artifactory-parent-pom artifact:
$ mvn --settings ~/.m2/settings-artifactory.xml -DdownloadSources=true -U clean install -P release
[INFO] Scanning for projects...
Downloading from jcenter: https://jcenter.bintray.com/org/artifactory/artifactory-parent-pom/7.x-SNAPSHOT/maven-metadata.xml
Downloading from jcenter: https://jcenter.bintray.com/org/artifactory/artifactory-parent-pom/7.x-SNAPSHOT/artifactory-parent-pom-7.x-SNAPSHOT.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.artifactory:artifactory-parent:7.x-SNAPSHOT: Could not find artifact org.artifactory:artifactory-parent-pom:pom:7.x-SNAPSHOT in jcenter (https://jcenter.bintray.com/) and 'parent.relativePath' points at wrong local POM # line 29, column 13
#
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.artifactory:artifactory-parent:7.x-SNAPSHOT (/home/siepkes/git/artifactory/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.artifactory:artifactory-parent:7.x-SNAPSHOT: Could not find artifact org.artifactory:artifactory-parent-pom:pom:7.x-SNAPSHOT in jcenter (https://jcenter.bintray.com/) and 'parent.relativePath' points at wrong local POM # line 29, column 13 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
~/.m2/settings-artifactory.xml looks like this:
<?xml version="1.0"?>
<settings>
<profiles>
<profile>
<id>artifactory</id>
<repositories>
<repository>
<id>jcenter</id>
<name>Bintray JCenter</name>
<url>https://jcenter.bintray.com/</url>
</repository>
</repositories>
</profile>
</profiles>
<activeProfiles>
<activeProfile>artifactory</activeProfile>
</activeProfiles>
</settings>
EDIT: This seems to be caused by long standing (since 2021) open issue RTFACT-26254.
Hi I tried to clone the repository and build the source as mentioned in the opendaylight wiki page. But the build is failing.
Link: https://wiki.opendaylight.org/view/OpenDaylight_Controller:Netconf:Testtool#Building_testtool
The following are the steps I followed:
Check out latest netconf repository from git
Dive into netconf/netconf/tools/netconf-testtool/ folder
Build testtool using mvn clean install command
The build fails with the following error trace:
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[FATAL] Non-resolvable parent POM for org.opendaylight.netconf:netconf-parent:1.5.0-SNAPSHOT: Could not find artifact org.opendaylight.mdsal:binding-parent:pom:0.13.0-SNAPSHOT and 'parent.relativePath' points at no local POM # org.opendaylight.netconf:netconf-parent:1.5.0-SNAPSHOT, /home/balakrishnan/netconf_simulator/netconf/netconf/netconf-parent/pom.xml, line 11, column 11
#
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.opendaylight.netconf:netconf-testtool:1.5.0-SNAPSHOT (/home/balakrishnan/netconf_simulator/netconf/netconf/tools/netconf-testtool/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM for org.opendaylight.netconf:netconf-parent:1.5.0-SNAPSHOT: Could not find artifact org.opendaylight.mdsal:binding-parent:pom:0.13.0-SNAPSHOT and 'parent.relativePath' points at no local POM # org.opendaylight.netconf:netconf-parent:1.5.0-SNAPSHOT, /home/balakrishnan/netconf_simulator/netconf/netconf/netconf-parent/pom.xml, line 11, column 11 -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2] http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
The build needs artifacts which your Maven setup doesn’t know about. You need to edit your settings.xml file; if you’re running in a Unix-style environment:
cp -n ~/.m2/settings.xml{,.orig}
wget -q -O - https://raw.githubusercontent.com/opendaylight/odlparent/master/settings.xml > ~/.m2/settings.xml
This will configure Maven to download OpenDaylight artifacts from the OpenDaylight Nexus repositories; you will then be able to build netconf-testtool directly.
You need to build the entire netconf project (ie mvn install) from the top-down.
I am trying to integrate jmeter with spring mvc. I have captured all the request using blazemeter and converted in .jmx file. I have placed this jmx file in test/jmeter folder. When I try to install, I am getting following error.
Executing test: Dagwidouthtml.jmx INFO 2016-07-06 14:10:59.229 [jmeter.e] (): Listeners will be started after enabling running version INFO 2016-07-06 14:10:59.230 [jmeter.e] (): To revert to the earlier behaviour, define jmeterengine.startlistenerslater=false [info] Completed Test: Dagwidouthtml.jmx [info] [info] Building JMeter Report(s)... [info] [info] Raw results: /home/trina/git/framework_loadTest/target/jmeter/report/Dagwidouthtml-160706.jtl [info] Test report: /home/trina/git/framework_loadTest/target/jmeter/report/Dagwidouthtml-160706.jtl-report.html [INFO] [INFO] Test Results: [INFO] [INFO] Tests Run: 1, Failures: 6, Errors: 0 [INFO] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 46.269 s [INFO] Finished at: 2016-07-06T14:11:10-04:00 [INFO] Final Memory: 44M/481M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal com.lazerycode.jmeter:jmeter-maven-plugin:1.4.1:jmeter (jmeter-tests) on project framework: There were test failures. See the jmeter logs for details. -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
So why you're posting Maven output here while it states the following:
There were test failures. See the jmeter logs for details
The log file is usually located at target/jmeter/logs/${yourscript}.log
Inspect the log file and if you won't be able to figure out the problem yourself.
The possible reason (apart from misconfiguration) I can think of is that jmeter-maven-plugin still depends on JMeter 2.13 so if you're trying to use features, introduced in JMeter 3.0 in your script - the failures are absolutely expected.
Also see documentation on JMeter Maven Plugin on Github - it is the most comprehensive source.
I downloaded the scalafx-ensemble project. When I run sbt in the project's folder I'm facing the following error:
[info] Set current project to scalafxEnsemble (in build file:/C:/dev/sample/scalafx-ensemble-master/)
[ERROR] Terminal initialization failed; falling back to unsupported
java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected
at jline.TerminalFactory.create(TerminalFactory.java:101)
at jline.TerminalFactory.get(TerminalFactory.java:159)
at sbt.JLine$.sbt$JLine$$terminal(LineReader.scala:87)
at sbt.JLine$.withTerminal(LineReader.scala:91)
at sbt.JLine$.usingTerminal(LineReader.scala:97)
at sbt.JLine$.createReader(LineReader.scala:103)
at sbt.FullReader.<init>(LineReader.scala:135)
at sbt.BasicCommands$$anonfun$shell$1.apply(BasicCommands.scala:149)
...
java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected
at sbt.JLine$$anonfun$usingTerminal$1.apply(LineReader.scala:98)
at sbt.JLine$$anonfun$usingTerminal$1.apply(LineReader.scala:97)
at sbt.JLine$.withTerminal(LineReader.scala:92)
at sbt.JLine$.usingTerminal(LineReader.scala:97)
at sbt.JLine$.createReader(LineReader.scala:103)
at sbt.FullReader.<init>(LineReader.scala:135)
at sbt.BasicCommands$$anonfun$shell$1.apply(BasicCommands.scala:149)
at sbt.BasicCommands$$anonfun$shell$1.apply(BasicCommands.scala:146)
at sbt.Command$$anonfun$command$1$$anonfun$apply$1.apply(Command.scala:31)
at sbt.Command$$anonfun$command$1$$anonfun$apply$1.apply(Command.scala:31)
at sbt.Command$.process(Command.scala:95)
at sbt.MainLoop$$anonfun$1$$anonfun$apply$1.apply(MainLoop.scala:100)
...
[error] java.lang.IncompatibleClassChangeError: Found class jline.Terminal, but interface was expected
[error] Use 'last' for the full log.
If I run sbt run I'm getting the following:
at scala.tools.nsc.typechecker.Typers$Typer.doTypedApply(Typers.scala:3193)
at scala.tools.nsc.typechecker.Typers$Typer.handleOverloaded$1(Typers.scala:3190)
at scala.tools.nsc.typechecker.Typers$Typer.doTypedApply(Typers.scala:3193)
at scala.tools.nsc.typechecker.Typers$Typer.handleOverloaded$1(Typers.scala:3190)
[error] (compile:compile) java.lang.StackOverflowError
[error] Total time: 9 s, completed Jan 6, 2014 4:47:49 PM
What am I doing wrong?
This is likely problem with outdated SBT launcher. Make sure that your SBT is v.0.13 or newer.
I fixed the path to jfxrt.jar in build.sbt from
System.getenv("JAVA_HOME") + "jre/lib/jfxrt.jar"
to
System.getenv("JAVA_HOME") + "/lib/jfxrt.jar"
which is correct for my system. With the change, sbt run works fine.
I have a maven 2 job configured in Jenkins, and under the Build I use
clean test release:prepare ...
in the goals options. Jenkins runs these goals sequenctiallay, and when test runs, it prints (and works nice):
[WARNING] [LAUNCHER] Using regular flashplayer tests
But when it tries to run prepare I get,
[INFO] [WARNING] [LAUNCHER] Using xvfb-run to launch headless tests
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [ERROR] BUILD ERROR
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Failed to launch Flash Player. Probably java was not able to find flashplayer.
[INFO] Make sure flashplayer is available on PATH
[INFO] or use -DflashPlayer.command=${flashplayer executable}
[INFO] Read more at: https://docs.sonatype.org/display/FLEXMOJOS/Running+unit+tests
So the same jobs, same jenkins, same job configuration, how can I make it work so that prepare also works like the clean goal?
I have also tried what the error suggest, that is, putting:
-Dflex.flashPlayer.command=/opt/player_10/flashplayer", "-DflashPlayer.command=/opt/player_10/flashplayer