Issue Details (XML | Word | Printable)

Key: GALAXY-231
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Andrew Perepelytsya
Reporter: Mike Carr
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Galaxy

galaxy-maven-publish-plugin missing dependencies

Created: 30/Apr/08 09:40 AM   Updated: 07/May/08 01:29 PM
Component/s: Integration: Maven
Affects Version/s: 1.0-beta-3
Fix Version/s: 1.0-RC

Time Tracking:
Not Specified

File Attachments: 1. Text File debug.log (103 kB)
2. Zip Archive test-galaxy-plugin.zip (11 kB)

Environment: Windows XP, Fedora and Ubuntu Linux, Maven 2.0.8

Labels:
User impact: High


 Description  « Hide
From a clean machine (no galaxy components installed) I created a simple maven project (pom attached), mvn clean install first reported that it was missing abdera-client:

Missing:
----------
1) org.apache.abdera:abdera-client:jar:0.4.0-incubating

I manually installed that artifact to maven repository:

C:\code\test-galaxy-plugin>mvn install:install-file -DgroupId=org.apache.abdera
-DartifactId=abdera-client -Dversion=0.4.0-incubating -Dpackaging=jar -Dfile=C:
\Downloads\galaxy-integration-distribution-1.0-beta-3\abdera-client-0.4.0-incuba
ting.jar

I then receive an NoClassDefFoundError exception:
[INFO] [galaxypublish:execute {execution: publish-artifacts}]
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] org/apache/commons/httpclient/methods/RequestEntity
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.NoClassDefFoundError: org/apache/commons/httpclient/methods/RequestEnt
ity
at org.mule.galaxy.maven.publish.PublishMojo.execute(PublishMojo.java:18
9)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:539)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:480)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:459)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:311)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:278)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.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:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.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: 12 seconds
[INFO] Finished at: Wed Apr 30 07:34:12 PDT 2008
[INFO] Final Memory: 10M/19M
[INFO] ------------------------------------------------------------------------

On a previously build with a machine that was built from the galaxy trunk I received another NoClassDefFoundError exception about commons-logging.
(see http://forums.muleforge.org/thread.jspa?threadID=45&tstart=0)

mvn dependency:list
[INFO] [dependency:list]
[INFO]
[INFO] The following files have been resolved:
[INFO] junit:junit:jar:3.8.1:test



 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Mike Carr added a comment - 30/Apr/08 09:41 AM
maven debug log

Mike Carr added a comment - 30/Apr/08 09:42 AM
sample program

Dan Diephouse added a comment - 07/May/08 12:48 PM
An easy workaround for this is to add this to your plugin declaration:

<plugin>
...
<dependencies>
<dependency>
<groupId>commons-logging</groupId>
<artifactId>commons-logging-api</artifactId>
<version>1.0.4</version>
</dependency>
</dependencies>
</plugin>


Andrew Perepelytsya added a comment - 07/May/08 01:29 PM
Ah, the joys of clogging... Unfortunately, Dan's workaround isn't ideal, but may work in most cases still. We specifically avoided using clogging libs directly, as they're problematic in more complex classloader setups.

Gave the module some love and made it comply galaxy's conventions on logging libs, now using jcl-over-slf4j->log4j bridge, which is safe.

http://fisheye.muleforge.org/changelog/galaxy/?cs=829
http://fisheye.muleforge.org/changelog/galaxy/?cs=830

Thanks for reporting and making it easier to fix with a sample project, Mike