-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run cargo/jboss without war deployment #147
Comments
Have you tried if it works if you use the CargoBasePlugin? Here is a few things that might brake the list of deployables. gradle-cargo-plugin/src/main/groovy/com/bmuschko/gradle/cargo/util/ProjectInfoHelper.groovy Lines 28 to 35 in b2c9c21
Here i do not know if a default file object will be returned or null. If it's a default file object then a invalid file will be added to the list. gradle-cargo-plugin/src/main/groovy/com/bmuschko/gradle/cargo/CargoPlugin.groovy Lines 122 to 133 in b2c9c21
Is definently broken, it will add an item even though you do not want it to, it will even fallback to an invalid file if you define a path to a file that doesn't exist. |
#181 should fix this |
I have a use case to run integration tests on a JAR project which interacts with a jboss based web application. The goal is to fire up jboss instance that's preconfigured with war files, etc before running integration junit tests, run the tests, then stop jboss after the tests have been completed. Right now i'm running "gradle cargoStartLocal" with the following snippet
cargo{ local{ homeDir=file("$rootDir/jboss") } containerId='jboss61x' port = 8888 }
And I'm running into the "Cannot get property 'cannonicalPath' on a null object, thrown by LocalCargoContainerTask.validateConfiguration, line 138.
Is this a supported configuration or anything I can do to force it to work this way?
The text was updated successfully, but these errors were encountered: