RE: [picocontainer-dev] Drop persistence-core?

Jörg Schaible <[email protected]>
Newsgroups gmane.comp.java.picocontainer.devel
Message-ID <[email protected]>
Mauro Talevi wrote:
> Michael Rimov wrote:
>>>> Brilliant use of profiles, Watson ;-)
>>> However, how will you release? We need two different artifacts.
>> 
>> I haven't a clue :)
>> 
>> I mean, we could use two different poms with different modules, but
>> the problem there is that we actually need different JDK's set up,
>> and I can't see how to do that without additional configuration
>> steps involved for the developers. (Setting properties for JDK
>> homes, etc). 
>> 
>> Any thoughts on how to do this yet allow newbie developers still
>> easily get a build with their source?
> 
> It's not difficult to support multiple artifacts for
> different jdks, eg
> core-jdk5, core-jdk6, etc ... much similar to the way we produce eg
> picocontainer-tck from the core test code.

This time it is, since the Java runtime is not compatible. Therefore you would have to use explicitly different JDKs for the build. Unfortunately I could not find a standalone version of JDBC 4, that might have been used building with JDK 5.

> But I was taking a step back and having a critical look at the
> persistence-core.  I'm wondering whether it adds much value, both the
> jdbc support and the exception handling.
> 
> I personally, don't use any of it - in JDK1.5/JPA-land it's
> so easy to
> use tools like hibernate, that provide out-of-the-box other enterprise
> features ...
> 
> Wanted to sound out if anybody was using it in production
> systems.  If
> not, we could move it to an example/tutorial module (or move it to
> sandbox) but not release it. 

Cannot say, never used it.

- Jörg

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.