History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: CARGO-266
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Vincent Massol
Reporter: Vincent Massol
Votes: 0
Watchers: 0
Operations

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

Fails to start Resin because of classpath issue when using individual Cargo jars

Created: 01/Feb/06 11:29 AM   Updated: 30/Mar/06 04:25 AM
Component/s: Maven2
Affects Version/s: 0.1-maven2
Fix Version/s: 0.2-maven2

Time Tracking:
Not Specified


 Description  « Hide
Tthe Cargo Maven2 plugin fails to start Resin. If you check the logs you'll see a: java.lang.NoClassDefFoundError: org/codehaus/cargo/container/spi/util/DefaultServerRun

This happens if you're using individual Cargo jars. However there's also a bug if you use the core uberjar with Resin (see CARGO-265).

The problem with the individual jars is that the ResinRun class used to start Resin is calling the DefaultServerRun class which is located in another jar (in the core util jar) and the way it is currently implemented the core util jar is not passed to the classpath used to start the Resin container.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Vincent Massol - 01/Feb/06 12:15 PM
Fixed