So how would we feel with 'openejb-shade-[quartz]' ? And eventually bring all
shade jars in line with that naming?
I'm happy to do the maven stuff either way.
Andy
--
View this message in context:
http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p486.html
Sent from the OpenEJB
I agree. Just checked in for a build something that works for me - We can
rename stuff later.
Andy.
--
View this message in context:
http://openejb.979440.n4.nabble.com/Quartz-next-tp4666498p488.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.
The TomEE Maven plugin is still moving forward with more new features.
Enhanced lightweight http serveur to support servlet deployments. Useful
for testing.
2013/12/10 Bjorn Danielsson bjorn-apa...@lists.cuspycode.com
User experience of out-of-the-box performance is better in general.
For
Hello everybody,
I think its worth mentioning that now you can with 1.6.0 describe
operation parameters in JMX really easy.
https://issues.apache.org/jira/browse/TOMEE-1024
Best Regards
Alexander
Am 10.12.2013 04:17, schrieb David Blevins:
I want to crank out the announcement for the 1.6.0
Hmm
I have not enough time to say no but till try to justify my opinion (i like
product-openejb-shade (or shaded))
It really makes diff easy and if product and shade are together by mistake
in assemblies you see it quickly sorting by name. Last point for libraries
which were not shaded in
On Dec 10, 2013, at 2:40 PM, David Blevins david.blev...@gmail.com wrote:
As far as where the shaded project lives, I'm cool with whatever as long as
it doesn't:
- break Intellij so we can still compile with a plain Intellij import and not
having to go through any magic to compile/run
