Howdy, Some more issues:
1. dependency prob by jmeter, reverted to its prev version. 2. (as you pointed out earlier) there is a static binding issue with sl4j. First question, why did this suddenly appear? Didn’t feel like mucking so I added sl4j's simple jar, which fixed the error and allowed log statements to work. But now they’re formatted differently. No longer picking up the log4j config. Scratching head. Not a showstopper. We can fix it later. But the third issue stops me: 3. fortress realm can’t find 1.0-RC42 core jar earlier deployed. This means my m2 settings.xml needs a statement pointing to the staging repo. I did setup that file per the instructions on our website but didn’t include the pointer to the staging repo. With 1 & 2’s necessary changes to the pom I’ll need to re-deploy core’s content to correct the release. I suppose I could change the versions in core and realm to 1.0-RC42, and run mvn install locally to get past #3, but that would be a BAD programmer. Shawn > On Mar 2, 2016, at 6:01 AM, Emmanuel Lécharny <[email protected]> wrote: > > Le 02/03/16 11:52, Emmanuel Lécharny a écrit : >> Hi guys, >> >> I have cleaned-up the realm pom.xml, in order to run the release. >> >> There are 52 files without the license header : > > Problem solved. It was way more an issue with the way teh rat-plugin was > declared than files with missing headers. > > FTR, I successfully cut the realm release. > > On my way for web and rest ! >
