Hi all, thank you all very much for the warm welcome!
Am 03.11.2016 um 11:08 schrieb Jean-Baptiste Onofré: > One thing that I would like to do in Pax JDBC is to be compliant with > blueprint (in addition of ConfigAdmin). > Thanks to that we would be able to deal with "old" and "new" style > datasource service in Karaf. Is there an open issue for that? What would be required to make that happen? > Another thing I saw is the encryption support added in Pax JDBC 0.8.0. > It doesn't seem to work "out of the box", even when the jasypt service > is there. It's maybe just a documentation issue, but I would like to > investigate a little. I saw that ticket and wanted to have a look into it. There is no rush for a 0.10.0 - just wanted to get the discussion rolling (and also wanted to get rid of our internal "fork" for the jtds adapter ;) ) So, from what I read regarding the Jasypt it's you put the encrypted pw in ENC() inside the properties and then it should be decrypted with Jasypt, right? > No objection for a 0.10.0 release. > > On the other hand, I think we can consider 1.0.0 release after a 0.11.0. > > On Thursday, November 3, 2016 at 10:26:50 AM UTC+1, Sascha Vogt wrote: > [...] > Are there any objections to a release? Is there something that > should go > into a 0.10.0 before releasing it? Would anyone of the existing > committers be willing to do the release or should I request an account > for publishing myself? (I currently do not have an account at Sonatypes > OSS Nexus). Greetings -Sascha- -- -- ------------------ OPS4J - http://www.ops4j.org - [email protected] --- You received this message because you are subscribed to the Google Groups "OPS4J" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
