> On Apr 6, 2018, at 10:14 PM, Gary Gregory <[email protected]> wrote: > > Hi Rob, > > My experience is that japicmp does not work (throws an exception) with > recent Java versions unless it is the latest version. I am sorry for being > vague but I know I've had to set it to the most recent version (the one in > commons-parent 46-SNAPSHOT) in order to get some Commons components to > build.
I’m familiar with that warning exception that sebb helped fix. Now it requires an actual built artifact for doing the comparison. I suppose we could set it up so that it runs after “package”, but some projects seem to generate the site before any artifacts get generated. (I suppose I should read more on the subtitles of the maven build lifecycle). But if we’re not too concerned with japicmp, then I’d be happy to build a release candidate tomorrow some time. -Rob > > FWIW, I'd like to see a release of Commons Lang, Configuration, and > Collections. So maybe you can use of of these as a test bed. > > Cheers, > Gary > >> On Fri, Apr 6, 2018 at 8:09 PM, Rob Tompkins <[email protected]> wrote: >> >> >> >>> On Apr 6, 2018, at 8:23 PM, Gary Gregory <[email protected]> wrote: >>> >>> Hi Rob: >>> >>> Thank you for pushing out the release of our build and release plugins. >>> >>> Are you planning on pushing out commons-parent 46? >> >> Yes. That was my plan. I’ve been fiddling with japicmp to try to actually >> get it working. Do we have a project where it’s actually working properly? >> >>> >>> Thank you, >>> Gary >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
