oops
Damn it.
J
On 10/23/06, Jerome Lacoste [EMAIL PROTECTED] wrote:
Hi,
I'd like to release the first alpha release of the webstart plugin.
Plugin has been almost unchanged since before the summer. I intend to
change some things before 1.0, but there's clearly a need for an
official non
Hi,
I'd like to release the first alpha release of the webstart plugin.
Plugin has been almost unchanged since before the summer. I intend to
change some things before 1.0, but there's clearly a need for an
official non-snapshot release of the plugin.
The latest snapshot was just deployed
On 6/21/06, Phil Steitz [EMAIL PROTECTED] wrote:
On 6/21/06, jerome lacoste [EMAIL PROTECTED] wrote:
Hi,
I've submitted a patch some days ago and am waiting for comments (DBCP-175).
In the mean time, I've had a look at the status of DBCP. Some notes:
- no release since 2004
Your plan sounds very good. Only question is why not using Jira in the
first place to target issues?
Because we started planning this release before the Jira migration ;-)
Probably a good idea to just do it all in Jira now. Feel free to
jump in.
Probably can't do much with Jira in terms of
Hi,
I've submitted a patch some days ago and am waiting for comments (DBCP-175).
In the mean time, I've had a look at the status of DBCP. Some notes:
- no release since 2004
- there are 10+ issues marked UNRESOLVED but with a Resolved status in
Jira. Could be cleaned up.
- althought I don't
[ http://issues.apache.org/jira/browse/DBCP-175?page=all ]
Jerome Lacoste updated DBCP-175:
Attachment: DBCP-175-2.txt
New version of the second patch that allows to run multiple init statements.
The patch now includes a change
[ http://issues.apache.org/jira/browse/DBCP-189?page=all ]
Jerome Lacoste updated DBCP-189:
Attachment: DBCP-189.txt
Patch that implements the requested changes. Only unit tested. Didn't add a
regression test.
[dbcp] Threads do not get a Connection
[ http://issues.apache.org/jira/browse/DBCP-175?page=all ]
Jerome Lacoste updated DBCP-175:
Attachment: DBCP-175-1.txt
DBCP-175-2.txt
DBCP-175-1.txt is a version of the change that is similar to the original
request. It allows one
the second one that would allow to have more than
one initialization statements. Do we want to go that way?
Please review/comment,
Thanks!
Jerome Lacoste
http://issues.apache.org/jira/browse/DBCP-175
-
To unsubscribe, e-mail: [EMAIL
On 6/17/06, Kenneth Xu [EMAIL PROTECTED] wrote:
Hello,
I apologize if this is a stupid question. I know there is an archive but I
didn't find a way to search it. I have tried to request for info and FAQ but
none available.
[EMAIL PROTECTED]
[EMAIL PROTECTED]
Thanks in advance!
On 6/16/06, Jochen Wiedmann [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
As I understand it, by the time you call getInputStream(), the user's POST
request is already entirely in the server's memory space, or it has been
written to disk. This data isn't consumed when you read() it, so
On 1/24/06, Brett Porter [EMAIL PROTECTED] wrote:
jerome lacoste wrote:
The refactoring ended up here:
http://moca.dynalias.com/~jerome/projects/exec2/
(Unfortunately it seems like I messed up apache access rights, but I
should make this code available tomorrow).
Let us know, I'll
On 1/24/06, Brett Porter [EMAIL PROTECTED] wrote:
jerome lacoste wrote:
I'm big on interfaces for defining and maintaining a simple public
contract of the API,
They help to some extent, but if you are going to use interface just
to define your public contract, I think it might be an overuse
Niklas, Brett, Trygve all,
Things were stagnating a little bit end of last year. I am happy to
see that things are in motion again.
Last interesting initiative was Brett's idea to start with an API
sketch. I think it is a good start but it's only solving the start
Process feature. That's
On 1/13/06, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
Back in September 05 (wow, is it really 2006 already? :) Jerome sent a
comprehensive vision for exec. I found myself agreeing with most
everything in there (I'll reply to a couple of specifics shortly).
Message ID from then: [EMAIL
On 1/17/06, Niklas Gustavsson [EMAIL PROTECTED] wrote:
Hi
jerome lacoste wrote:
I had some changes in mind compared to my original design proposal, to
make it simpler.
So I am willing to help you design test this API/implementation and
make sure it works with CruiseControl.
Great
On 1/13/06, Brett Porter [EMAIL PROTECTED] wrote:
Hi,
Back in September 05 (wow, is it really 2006 already? :) Jerome sent a
comprehensive vision for exec. I found myself agreeing with most
everything in there (I'll reply to a couple of specifics shortly).
Message ID from then: [EMAIL
Proposed architecture
- Launchers: exist as today
- OS functionality
- ProcessLauncher, (our ProcessBuilder)
- Execute (or Executor?): Flexible, we use it to tie together the
various concepts in the execute() call (stream management, process
management, process building, etc...)
-
On 10/9/05, Niklas Gustavsson [EMAIL PROTECTED] wrote:
Hi
We regard to my other patches, they can be discarded if we go for a
rewrite (through refactorings). Trygve: in particular the serializable
patch is not critical. Was just there to maintain the functionality of
the old API, as I
[Sorry for the long mail. I hope I was clear enough this time]
This complements/summarizes the couple of mails I sent this week-end,
trying to give a better description of the vision I have for
commons-exec.
I don't want to impose anything. A library like commons-exec is
something I have been
Proposal
to me commons-exec is slightly over-engineered. As is, clients will
have to resort to strange things and rewrite somewhat complex helper
classes to do simple things.
I propose to change the API.
Vision: Make commons-exec a reusable Library that is available to all
SDK,
Hi,
I did the first step at integrating commons-exec into CruiseControl.
It's not in the trunk yet [1]. I am not using all the functionality
(Exec) and we still have some duplicated code that could be fixed if
commons-exec was a little bit more flexible (i.e. add some interfaces
where
I am also voluntary to produce documentation for the package (as said
to Brett and Trygve yesterday), help redesign things if these small
redesigns are allowed, making sure if will be used fully in
CruiseControl and why not help ant migration when it comes.
Some notes below on that regard:
On 9/23/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
On Fri, 2005-09-23 at 10:36 +0700, Kev Jackson wrote:
Hi,
I've been looking at the use of commons logging in exec. Coming from
ant dev, it would be nice to refactor ant to use the commons-exec
package, but Ant has it's own logging
On 8/6/05, Niklas Gustavsson [EMAIL PROTECTED] wrote:
Hi Jerome
Thanks for a lot of really good feedback and ideas! I will come back to
some of the other stuff later on, but first I think we need to discuss
on of the points you bring up:
jerome lacoste wrote:
* run on the oldest SDK
Thanks a lot to Eric for pointing me to this thread.
As he said, I started a similar project some weeks ago and put some
notes to share on http://www.coffeebreaks.org/blogs/?p=8. I would have
preferred more feedback from the jakarta guys before going further.
Looks like my wishes are coming true
26 matches
Mail list logo
