Re: [ALL] Create a pom parent 41 release

2016-07-26 Thread Chas Honton
Unfortunately no. Report plugins cannot have dependencies changed. Chas > On Jul 25, 2016, at 10:06 PM, Gary Gregory wrote: > > Now that BCEL 6.0 is out, can the parent POM make Clirr use BCEL 6? > > Gary > >> On Mon, Jul 25, 2016 at 8:03 PM, Charles Honton wrote: >> >> Any objections to c

Re: [ALL] Create a pom parent 41 release

2016-07-26 Thread Matt Sicker
That would certainly be nice. On 26 July 2016 at 00:06, Gary Gregory wrote: > Now that BCEL 6.0 is out, can the parent POM make Clirr use BCEL 6? > > Gary > > On Mon, Jul 25, 2016 at 8:03 PM, Charles Honton wrote: > > > Any objections to creating a release for pom parent 41? > > This currently

Re: [ALL] Create a pom parent 41 release

2016-07-25 Thread Gary Gregory
Now that BCEL 6.0 is out, can the parent POM make Clirr use BCEL 6? Gary On Mon, Jul 25, 2016 at 8:03 PM, Charles Honton wrote: > Any objections to creating a release for pom parent 41? > This currently has one change; two new profiles that enable clirr or > japicmp for binary compatibility rep

Re: [ALL] Create a pom parent 41 release

2016-07-25 Thread Gary Gregory
Go for it. Gary On Mon, Jul 25, 2016 at 8:03 PM, Charles Honton wrote: > Any objections to creating a release for pom parent 41? > This currently has one change; two new profiles that enable clirr or > japicmp for binary compatibility reports. > > chas >

[ALL] Create a pom parent 41 release

2016-07-25 Thread Charles Honton
Any objections to creating a release for pom parent 41? This currently has one change; two new profiles that enable clirr or japicmp for binary compatibility reports. chas - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.