Hi, Jörg,
On Wed, Jun 5, 2013 at 1:42 PM, Jörg Schaible
wrote:
>
> This is here not possible, since we provide *implementations* that
> implement
> the affected interfaces. E.g. Statement interface has more methods which
> have arguments of types that are not even present in the older JDBC versi
Hi Jochen,
Jochen Wiedmann wrote:
> On Tue, Jun 4, 2013 at 11:29 AM, sebb wrote:
>
>> DBCP is complicated to release, because the source has to be
>> pre-processed in order to build additional versions of the code.
>> (unlike the rest of Java, JDBC is not generally upwards compatible).
>>
>
>
On Tue, Jun 4, 2013 at 11:29 AM, sebb wrote:
> DBCP is complicated to release, because the source has to be
> pre-processed in order to build additional versions of the code.
> (unlike the rest of Java, JDBC is not generally upwards compatible).
>
Alternative proposal (worked for me in the past
Le 04/06/2013 16:23, Jörg Schaible a écrit :
> IMHO it is. If you do not have a matching -sources.jar, it will be
> cumbersome to debug a problem for any client. Note, that the -sources.jar
> would contain the filtered stuff, while the source distribution (-src.zip)
> would contain the original
Emmanuel Bourg wrote:
> Le 04/06/2013 15:45, Phil Steitz a écrit :
>
>> Such a tool would be useful if it could automatically generate
>> taggable sources. This is what the comment markers and ant filter
>> tasks in the current setup do.
>
> I don't think a tool based on bytecode manipulation c
Le 04/06/2013 16:01, Phil Steitz a écrit :
> Are you guys OK with me plowing forward with the setup I described
> yesterday
+1
Emmanuel Bourg
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands
Hi Phil,
Phil Steitz wrote:
[snip]
>> For the release you can now activate the appropriate JDK profile, provide
>> the versions with the command line and possibly we can additionally add
>> an enforcer rule to avoid errors.
>
> If maven can do the filtering to help create the source branches /
Le 04/06/2013 15:45, Phil Steitz a écrit :
> Such a tool would be useful if it could automatically generate
> taggable sources. This is what the comment markers and ant filter
> tasks in the current setup do.
I don't think a tool based on bytecode manipulation could produce the
corresponding sou
On 6/4/13 3:16 AM, Jörg Schaible wrote:
> sebb wrote:
>
>> DBCP is complicated to release, because the source has to be
>> pre-processed in order to build additional versions of the code.
>> (unlike the rest of Java, JDBC is not generally upwards compatible).
>>
>> The source code in SVN is for the
On 6/4/13 2:29 AM, sebb wrote:
> DBCP is complicated to release, because the source has to be
> pre-processed in order to build additional versions of the code.
> (unlike the rest of Java, JDBC is not generally upwards compatible).
>
> The source code in SVN is for the latest JDBC version we suppor
On 6/4/13 4:10 AM, Emmanuel Bourg wrote:
> Le 04/06/2013 13:03, sebb a écrit :
>
>> Are you sure?
>> Sounds like a lot more work than what we have currently.
> I like the idea. It's more work but the scope could be wider than DBCP.
> I guess any project implementing JDBC classes could be interested
Hi Sebb,
sebb wrote:
> On 4 June 2013 11:16, Jörg Schaible wrote:
>> sebb wrote:
>>
>>> DBCP is complicated to release, because the source has to be
>>> pre-processed in order to build additional versions of the code.
>>> (unlike the rest of Java, JDBC is not generally upwards compatible).
>>>
>
Le 04/06/2013 13:03, sebb a écrit :
> Are you sure?
> Sounds like a lot more work than what we have currently.
I like the idea. It's more work but the scope could be wider than DBCP.
I guess any project implementing JDBC classes could be interested by a
tool filtering JDBC methods and producing j
On 4 June 2013 11:43, Romain Manni-Bucau wrote:
> Hi
>
> Modules would make sense too (instead of classifier).
I don't think so, because the builds all need different compilers and libraries.
Also Maven modules are tricky to get right for site builds and seems
overkill here.
> That said using a
Hi
Modules would make sense too (instead of classifier). That said using asm
to generate classes for older versions would be simple enough to get a
single artifact with N impl in different packages.
Le 4 juin 2013 12:39, "sebb" a écrit :
> On 4 June 2013 11:16, Jörg Schaible wrote:
> > sebb wro
On 4 June 2013 11:16, Jörg Schaible wrote:
> sebb wrote:
>
>> DBCP is complicated to release, because the source has to be
>> pre-processed in order to build additional versions of the code.
>> (unlike the rest of Java, JDBC is not generally upwards compatible).
>>
>> The source code in SVN is for
sebb wrote:
> DBCP is complicated to release, because the source has to be
> pre-processed in order to build additional versions of the code.
> (unlike the rest of Java, JDBC is not generally upwards compatible).
>
> The source code in SVN is for the latest JDBC version we support, and
> can be b
DBCP is complicated to release, because the source has to be
pre-processed in order to build additional versions of the code.
(unlike the rest of Java, JDBC is not generally upwards compatible).
The source code in SVN is for the latest JDBC version we support, and
can be built and deployed using M
18 matches
Mail list logo
