Closed cuchaz closed 7 years ago
Look like a bug indeed. Both Jacoco and Sonar plugin are bundled within Jerkar so normally it should run as is.
Looking further, it's a bug on unix script only (that explain why I didn't cacth it).
For windows CP is set "COMMAND="%JAVA_CMD%" %JERKAR_OPTS% -cp "%LOCAL_BUILD_DIR%%JERKAR_HOME%libs\ext\*;%JERKAR_HOME%org.jerkar.core-all.jar" org.jerkar.tool.Main %*"
For unix this is :
-cp "$LOCAL_BUILD_DIR$JERKAR_HOME/libs/ext/*:$JERKAR_HOME/libs/builtins/*:$JERKAR_HOME/org.jerkar.core.jar" org.jerkar.tool.Main "$@"
(line 161)
It should bereplace by something like
-cp "$LOCAL_BUILD_DIR$JERKAR_HOME/libs/ext/*:$JERKAR_HOME/org.jerkar.core-all.jar" org.jerkar.tool.Main "$@"
As I don't have any easy way to run it on unixfor testing, please can you make the fix ?
Yeah, that definitely works, thanks! I'll send a PR with the fix.
I'm trying to write a plugin for jerkar, but I'm having trouble using it in my build script. It appears that plugins are not added to the build classpath? Here's a minimial working example:
build script:
output for
jerkar doTest
:I noticed the "Jerkar Classpath" section shows the plugins correctly, but the "Compiling 1 source files using options" -cp flag only lists the core jar.
How can I make sure the plugins are on the build classpath? Do I need to add something to my build script to tell jerkar to include the plugins? Or is this a bug?