Re: Configuring build with maven 3.3.9

nevermind - fixed by upgrading maven invoker plugin to current version, which doesn't use mvn.bat. Apologies for the noise.  -Marshall Schor On 9/21/2017 4:07 PM, Marshall Schor wrote: > ping? we're continuing to get this on Windows builds. > > latest one: > >

Re: Configuring build with maven 3.3.9

ping? we're continuing to get this on Windows builds. latest one: -Marshall On 9/19/2017 3:28 PM, Marshall Schor wrote: > Hi, > > Looks like there still may be a small issue.  > Running our build on a Windows system

Re: Configuring build with maven 3.3.9

Hi, Looks like there still may be a small issue.  Running our build on a Windows system now starts and runs, until it gets to an "integration test".   The integration test runs 'maven within maven"; we use it to test new maven plugins.    This test fails with the message: Maven invocation fa

Re: Configuring build with maven 3.3.9

Thanks, Gav! That seemed to do the trick... -Marshall On 9/14/2017 6:28 PM, Gav wrote: > Hi, > > All of the 'Latest' options for 'Ant,Maven'Java' etc are configured to work > for both Linux and Windows, have been for a while. > > Maven 3.3.9 used to be 'Latest' until 3.5.0 was released when tha

Re: Configuring build with maven 3.3.9

Hi, All of the 'Latest' options for 'Ant,Maven'Java' etc are configured to work for both Linux and Windows, have been for a while. Maven 3.3.9 used to be 'Latest' until 3.5.0 was released when that took over the symlinking for Latest. So 3.3.9 used to work for both, then stopped. As there are s

Configuring build with maven 3.3.9

Hi, We have a build which needs maven 3.3.9. I see in the Jenkins pulldown menu for configuring builds, there are 2 picks for maven 3.3.9:   - one is labeled "Maven 3.3.9"   - one is labeled "Maven 3.3.9 (Windows)" We are using the first ("Maven 3.3.9").  Our build is not set to restrict wher