Re: svn commit: r1843135 - /db/torque/torque4/trunk/pom.xml

[Jeffery Painter <je...@jivecast.com>]

Reverse that... torque-4.1 is still referencing the older fulcrum
components.  We probably want to release the updated fulcrum components
that torque relies on first, then do a torque-4.1 release, then update
fulcrum/security to take advantage of the latest version of torque :-)

-
Jeff


On 10/09/2018 12:33 PM, Jeffery Painter wrote:
> Hi Thomas,
>
> I didn't spend much more time on it, but I think there may have been
> some issues when updating fulcrum components to use mockito 2.22 and
> torque was still using an older version... but who knows, I will dig in
> soon and do as you suggest :-)
>
> -
> Jeff
>
>
> On 10/09/2018 12:30 PM, Thomas Vandahl wrote:
>> Hi Jeff,
>>
>> On 08.10.18 14:42, Jeffery Painter wrote:
>>> I am not sure why those changes failed in Jenkins... everything looked
>>> fine on my end.  There were some complaints about some of the Java8
>>> updates after making the dependency updates in the jenkins log file, but
>>> nothing that looked fatal to me.
>> There are a couple of cases where Jenkins does things differently. I had
>> to exclude two tests in the generator which passed locally and failed on
>> Jenkins. The tremendous amount of log output is related to the fact that
>> Cobertura doesn't know about Java8 syntax, however.
>>
>>> I have reverted changes just on the parent pom and see if Jenkins
>>> complains again.  Is there a way for me to test the jenkins build params
>>> locally before pushing code to the repo?
>> I'd suggest to change the dependencies one by one, commit and see how it
>> goes. You should be able to log into Jenkins with your Apache
>> credentials and do some research on the build details.
>>
>> Bye, Thomas
>>
>

-- 
Jeff Painter

CEO and Founder of JiveCast
Software and analytics, made together
https://jivecast.com

301 Fayetteville St. Unit 2301, Raleigh, NC 27601
(919) 533-9024