Re: Pipeline Global Library vars file naming convention

2016-06-01 Thread ludovic SMADJA
On our environment, the vars is camelCase without any problems. But we are using is as block : for example : JaliosPlugin{ mailrecipients : ludovic.sma...@jalios.com } Others elements are designed as classes and in our case are used with new operator , like : new com.jalios.build.MailNotifi

Re: Pipeline Global Library vars file naming convention

2016-05-31 Thread Sverre Moe
Well if it is a bug. I was not entirely sure as I have just begun using Pipeline. I will create a bug report of this problem. tirsdag 31. mai 2016 12.55.59 UTC+2 skrev Daniel Beck følgende: > > > > On 31.05.2016, at 12:01, Sverre Moe > > wrote: > > > > This naming does not work: > > vars/pack

Re: Pipeline Global Library vars file naming convention

2016-05-31 Thread Daniel Beck
> On 31.05.2016, at 12:01, Sverre Moe wrote: > > This naming does not work: > vars/packageInformation.groovy > > I get the following exception when calling a function > packageInformation.init() > java.lang.NullPointerException: Cannot invoke method init() on null object > > This works > vars

Pipeline Global Library vars file naming convention

2016-05-31 Thread Sverre Moe
This naming does not work: vars/packageInformation.groovy I get the following exception when calling a function packageInformation.init() java.lang.NullPointerException: Cannot invoke method init() on null object This works vars/packageinformation.groovy According to the instructions/tutorial o