Err, I meant 'mvn install', with no '-DskiTests' as per danielbeck's advice.

On Friday, August 22, 2014 11:53:02 AM UTC-4, Jacob Vallejo wrote:
>
> Thanks for the help Jesse! I did end up trying 'mvn build' (I believe it 
> was - thanks to danielbeck for that - from the root level) and that worked. 
> I'm not sure if that worked properly though. I'll give this try today and 
> see if I can run my fork locally with everything working. I'll send along a 
> PR if it does work as expected.
>
>
> On Thursday, August 21, 2014 5:06:23 PM UTC-4, Jesse Glick wrote:
>>
>> On Thu, Aug 21, 2014 at 1:24 PM, Jacob Vallejo 
>> <[email protected]> wrote: 
>> > I'm working on adding a BatchScriptStep (in the same style as 
>> ShellStep) to 
>> > the workflow-plugin to run scripts on Windows 
>>
>> Great! 
>>
>> > As of now I'm using mvn compile and mvn 
>> > test to compile and test respectively. The compile step fails with an 
>> error 
>> > in the cps compiling step: Failure to find 
>> > org.jenkins-ci.plugins.workflow:workflow-support. 
>>
>> From root level, try: 
>>
>> mvn -DskipTests clean install 
>>
>> > I'd really like to get this compiling and be able to test this locally 
>> > (hpi:run style if possible). 
>>
>> After doing a build of everything, you can use 
>>
>> mvn -f aggregator hpi:run 
>>
>> to test. If you are using an IDE with support for this kind of thing, 
>> you can get the usual hpi:run features for sources in any of the 
>> plugins in the suite: 
>>
>> · Edit src/main/resources/**, save, and reload the page to see changes 
>> immediately. 
>> · Edit src/main/java/**, save, and rerun hpi:run (or use JPDA hot 
>> swap) to see code changes without a Maven rebuild. 
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to