Hi Ricardo,
sorry for the delay, have been busy at work lately. Nice that you want to
contribute to CLI. Help is always welcome. There hasn't been activity in
that component for a while (Gary explained the reasons on the other
thread). However there has been a discussion about 1.3 [1] and what com
On Tue, Jun 4, 2013 at 6:01 PM, Ricardo Espírito Santo <
ricardoespsa...@gmail.com> wrote:
> Hi Gary,
>
> Thanks for your reply!
>
> I kinda was expecting that answer but I'm sort of curious as to what
> happens to a project that gets no love from anyone for a long while?
>
> The reason I'm asking
Hi Gary,
Thanks for your reply!
I kinda was expecting that answer but I'm sort of curious as to what
happens to a project that gets no love from anyone for a long while?
The reason I'm asking this is that I have been buzzing around the commons
projects for a few days trying to find something I c
Hi,
No one is "in charge" of any Commons component. The community develops and
supports Commons as each participant and member sees fit.
Gary
On Tue, Jun 4, 2013 at 4:33 PM, Ricardo Espírito Santo <
ricardoespsa...@gmail.com> wrote:
> Is there anyone in charge of this project?
>
> Thanks,
> Ri
Is there anyone in charge of this project?
Thanks,
Ricardo Espírito Santo
On 4 June 2013 16:08, William Speirs wrote:
> Gary, thanks for the info. That is an unbelievable number of steps required
> to cut a release. I see you're working on Windows, but I'm going to try and
> throw something together (probably in Python as I'm trying learn it)
> focused on Linux. If you
On 4 June 2013 13:08, Benedikt Ritter wrote:
> Hi Bill,
>
>
> 2013/6/4 William Speirs
>
>> My confusion, it says in those directions to remove the -SNAPSHOT from the
>> version. That's exactly what I did. So then I shouldn't submit that to
>> trunk? I thought you were supposed to get everything s
On 4 June 2013 13:19, Gary Gregory wrote:
> On Tue, Jun 4, 2013 at 8:08 AM, Benedikt Ritter wrote:
>
>> Hi Bill,
>>
>>
>> 2013/6/4 William Speirs
>>
>> > My confusion, it says in those directions to remove the -SNAPSHOT from
>> the
>> > version. That's exactly what I did. So then I shouldn't sub
On 4 June 2013 12:54, William Speirs wrote:
> My confusion, it says in those directions to remove the -SNAPSHOT from the
> version. That's exactly what I did. So then I shouldn't submit that to
> trunk? I thought you were supposed to get everything setup in trunk then
> simply svn copy that to you
On Mon, Jun 3, 2013 at 9:25 PM, William Speirs wrote:
> I would like to release commons-dbutils 1.6
>
> commons-dbutils 1.6 RC1 is available for review here:
> http://people.apache.org/~wspeirs/commons-dbutils-1.6-RC1/ (svn
> revision r1489259)
>
> Details of changes since 1.5 are in the release
On Tue, Jun 4, 2013 at 11:08 AM, William Speirs wrote:
> Gary, thanks for the info. That is an unbelievable number of steps required
> to cut a release. I see you're working on Windows, but I'm going to try and
> throw something together (probably in Python as I'm trying learn it)
> focused on Li
Wouldn't it be better to use something like http://www.gradle.org/ to write
up the build process?
Ricardo Espírito Santo
On 4 June 2013 16:08, William Speirs wrote:
> Gary, thanks for the info. That is an unbelievable number of steps required
> to cut a release. I see you're working on Windows
Gary, thanks for the info. That is an unbelievable number of steps required
to cut a release. I see you're working on Windows, but I'm going to try and
throw something together (probably in Python as I'm trying learn it)
focused on Linux. If you could make it work on Windows as well, that'd be
huge
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
On 6/3/13 12:06 PM, Thomas Neidhart wrote:
> On 06/03/2013 04:10 PM, Phil Steitz wrote:
>> On 6/3/13 4:18 AM, Thomas Neidhart wrote:
>>> Hi,
>>>
>>> to start working on the Monte Carlo engine (see MATH-463) I would like to
>>> break this thing up in multiple pieces. One thing that could be added
>>
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
On Tue, Jun 4, 2013 at 8:08 AM, Benedikt Ritter wrote:
> Hi Bill,
>
>
> 2013/6/4 William Speirs
>
> > My confusion, it says in those directions to remove the -SNAPSHOT from
> the
> > version. That's exactly what I did. So then I shouldn't submit that to
> > trunk? I thought you were supposed to
Hi Bill,
2013/6/4 William Speirs
> My confusion, it says in those directions to remove the -SNAPSHOT from the
> version. That's exactly what I did. So then I shouldn't submit that to
> trunk? I thought you were supposed to get everything setup in trunk then
> simply svn copy that to your tag.
>
My confusion, it says in those directions to remove the -SNAPSHOT from the
version. That's exactly what I did. So then I shouldn't submit that to
trunk? I thought you were supposed to get everything setup in trunk then
simply svn copy that to your tag.
If I were to start working on a python script
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
The current DBCP versioning scheme is a bit odd.
1.3.x is for JDBC 3
1.4.x is for JDBC 4
They have the same original code base, so 1.4 is not later than 1.3
It might make more sense to use Maven classifiers to distinguish the
different builds.
Then there would be a single release version, and M
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
http://commons.apache.org/releases/prepare.html#Manual_Method
On 4 June 2013 11:56, William Speirs wrote:
> Is there documentation about this somewhere? What should I have done?
>
> Thanks...
>
> Bill-
> On Jun 4, 2013 5:02 AM, wrote:
>
>> Author: sebb
>> Date: Tue Jun 4 09:02:02 2013
>> New Re
Is there documentation about this somewhere? What should I have done?
Thanks...
Bill-
On Jun 4, 2013 5:02 AM, wrote:
> Author: sebb
> Date: Tue Jun 4 09:02:02 2013
> New Revision: 1489347
>
> URL: http://svn.apache.org/r1489347
> Log:
> Only tags should use non-SNAPSHOT versions please
>
> Mod
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
35 matches
Mail list logo
