search

Shubhamjain007 / openhab

Automatically exported from code.google.com/p/openhab
0 stars 0 forks source link

Error in Maven build #49

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Followed the procedure described on Wiki Page - IDESetup
2. Using Win7, Maven 3.0.3
3. Executing the mvn clean install

Following build problem 

[ERROR] Failed to execute goal 
org.fornax.toolsupport:fornax-oaw-m2-plugin:3.3.0-SNAPSHOT:run-workflow 
(default) on project org.openhab.model.item: Wo
rkflow execution failed. -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal 
org.fornax.toolsupport:fornax-oaw-m2-plugin:3.3.0-SNAPSHOT:run-workflow
 (default) on project org.openhab.model.item: Workflow execution failed.
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
        at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
        at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
        at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
        at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
        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:597)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
        at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
        at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
        at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Workflow execution 
failed.
        at org.fornax.toolsupport.maven2.WorkflowMojo.execute(WorkflowMojo.java:411)
        at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
        at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
        ... 19 more
[ERROR]
[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 <goals> -rf :org.openhab.model.item

Original issue reported on code.google.com by kirschne...@gmail.com on 17 Nov 2011 at 5:43

GoogleCodeExporter commented 8 years ago 
Hi,

Could you please run the mvn build with the -X option and see if it results in 
any more meaningful exception?

Thx,
Kai

Original comment by kai.openhab on 17 Nov 2011 at 7:53

GoogleCodeExporter commented 8 years ago 
There does not seem to be a general problem with the Maven build - I 
successfully ran one this morning on CloudBees: 
https://openhab.ci.cloudbees.com/job/openHAB/67/console

So I guess the problem is local to your machine. You might try to clean your 
local Maven repo and rerun the build. There is sometimes the case that a 
partially downloaded or broken jar is left in the local repo, which prevents 
successful builds.

Original comment by kai.openhab on 17 Nov 2011 at 10:54

GoogleCodeExporter commented 8 years ago 
I retried the same thing from an different site (without NTLM-proxy) and it 
works there. So i assume that the modeling stuff (Mojo...) is not compatible 
with the proxy.

Original comment by kirschne...@gmail.com on 18 Nov 2011 at 8:03