Hi All,
I have identified the problem :
There is an entry in my pom.xml
<extensions>
<extension>
<groupId>org.apache.maven.wagon</groupId>
<artifactId>wagon-webdav</artifactId>
<version>1.0-beta-2</version>
</extension>
</extensions>
Which was causing the trouble. This was introduced inadvertently in the
pom.xml, which caused the problem.
Thanks again for your help!!!
Regards
Abhilash John
From: John, Abhilash
Sent: Tuesday, January 05, 2010 11:28 AM
To: [email protected]
Subject: RE: [Fornax-developer] Build Error in Hudson while building
Hi Andreas,
I have tried both the suggestions you mentioned below. (Wipe out workspace, and
moving maven 2.0.10). Interestingly, there are other projects using Sculptor in
the same CI server. Only in the newly set up projects, we are facing this
problem.
Regards
Abhilash John
From: Andreas Källberg [mailto:[email protected]]
Sent: Tuesday, January 05, 2010 3:25 AM
To: [email protected]
Subject: Re: [Fornax-developer] Build Error in Hudson while building
Hi,
I'm also using Hudson, but haven't seen that problem.
Though, I have had some strange problem where the symptom have been the same,
i.e. it works outside of hudson but not the other way around.
A couple of things you could test:
1) Empty the workspace folder of your job, i.e. let hudson do a clean checkout
of the job.
2) Upgrade to maven 2.0.10 (2.0.9 wasn't a good release)
Let us know how it goes.
.../Andreas
On Mon, Jan 4, 2010 at 1:03 PM, John, Abhilash <[email protected]> wrote:
Hi All,
I am using Sculptor v1.6 for my project. When I am doing the build in any of
the dev machines, I am able to build the project successfully. But, If I am
building via my CI Server (Hudson 1.339) -- with the same code, same pom-- the
build is failing with the following error.
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Cannot load or instantiate class
org.openarchitectureware.workflow.WorkflowRunner
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.IllegalArgumentException: Cannot load or instantiate class
org.openarchitectureware.workflow.WorkflowRunner
at
org.fornax.toolsupport.maven2.MojoWorkflowRunner.setWorkflowRunnerClass(MojoWorkflowRunner.java:72)
at
org.fornax.toolsupport.maven2.WorkflowMojo.execute(WorkflowMojo.java:280)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at
hudson.maven.agent.PluginManagerInterceptor.executeMojo(PluginManagerInterceptor.java:182)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at
org.apache.maven.lifecycle.LifecycleExecutorInterceptor.execute(LifecycleExecutorInterceptor.java:65)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
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.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at hudson.maven.agent.Main.launch(Main.java:165)
at hudson.maven.MavenBuilder.call(MavenBuilder.java:159)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:688)
at
hudson.maven.MavenModuleSetBuild$Builder.call(MavenModuleSetBuild.java:632)
at hudson.remoting.UserRequest.perform(UserRequest.java:104)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:270)
at
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18 seconds
If I remote log in to my CI server, and do a build from a command prompt, the
build is happening fine. The issue happens only while building using Hudson. (I
have the same settings.xml in both the CI server and my dev environment). Is
there any known issues with Hudson and Sculptor based projects?
Here is a bit of my dev environment.
JDK 1.6.13
Hudson Version 1.339
Maven 2.0.9
Sculptor 1.6.0
fornax-oaw-m2.version 3.0.1
maven-eclipse-plugin.version 2.5.1
Can you please advise me on this?
Regards
Abhilash John
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Fornax-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fornax-developer
