Hi Patrick,

I went ahead and fixed it (TOMEE-3848). Thanks for reporting the issue
in the first place! It is very much appreciated.

The fix will be contained in the next TomEE 8 release.

Background: We missed a change in the transient dependency of openejb-
quartz-shade in the version update in 2020, so our exclusions did not
match.

Gruß
Richard

Am Donnerstag, dem 03.03.2022 um 05:36 +0000 schrieb Zowalla, Richard:
> Hi Patrick,
> 
> could you create an issue https://issues.apache.org/ with this
> finding?
> This would help us track it (and it does not get lost in the mailing
> list).
> 
> Thanks in advance,
> Richard
> 
> 
> Am Dienstag, dem 01.03.2022 um 12:55 +0100 schrieb Jean-Louis
> Monteiro:
> > Thanks for reporting.
> > I don't think it's on purpose. But I need to check unless Jon
> > remembers on
> > top of his head.
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> > 
> > 
> > On Tue, Mar 1, 2022 at 11:55 AM Patrick Merz
> > <[email protected]> wrote:
> > 
> > > Hi *,
> > > 
> > > I have the following question:
> > > 
> > > starting with Apache TomEE version 8.0.6 the lib directory
> > > contains
> > > not
> > > only the quartz-openejb-shade-2.2.4.jar, but also the quartz jar
> > > itself,
> > > quartz-2.2.4.jar.
> > > All previous TomEE versions did not come with a quartz jar.
> > > Therefor we
> > > had to deploy a corresponding quartz.jar by ourself in order to
> > > use
> > > classes
> > > like org.quartz.core.QuartzScheduler etc.
> > > We followed the guideline by Jonathan Gallimore
> > > https://www.mail-archive.com/[email protected]/msg17392.html
> > > 
> > > Now both the openejb-shaded quartz as well as the original quartz
> > > is
> > > packaged with Apache TomEE 8.0.6 onwards.
> > > It looks like this is related to
> > > https://issues.apache.org/jira/browse/TOMEE-2947, resolved by
> > > https://github.com/apache/tomee/pull/742.
> > > 
> > > Was this change intended, so applications based on TomEE do not
> > > need to
> > > deploy quartz.jar in the future?
> > > 
> > > Please advice.
> > > 
> > > Thanks and ciao
> > > Patrick
> > > 
> > > 
> > > 

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to