+1 to all said. I could even help.
-0 to waiting until we have a clear idea about the rest of Jakarta as
this is likely to never happen. Maybe a clearer idea will form after
commons leaves Jakarta.
Oliver
2007/4/3, Henri Yandell [EMAIL PROTECTED]:
On 4/2/07, Phil Steitz [EMAIL PROTECTED]
Hello,
i am using Commons-VFS 1.0 across Ivy dependency management
(http://incubator.apache.org/ivy/). I am trying to write a file using ftp
located in a directory named repository
I got the following exception:
org.apache.commons.vfs.FileSystemException: Could not create folder
On Mon, 2007-03-26 at 15:51 +0200, Oleg Kalnichevski wrote:
On Fri, 2007-03-23 at 19:56 +0100, Boris Unckel wrote:
Hello,
I have seen the recent discussions on JCL 2.0.0 and a version without
autodiscovery.
Someone stated to stop any further development (with good reasons
behind)
On Tue, 2007-04-03 at 22:51 +1200, Simon Kitching wrote:
On Mon, 2007-03-26 at 15:51 +0200, Oleg Kalnichevski wrote:
On Fri, 2007-03-23 at 19:56 +0100, Boris Unckel wrote:
Hello,
I have seen the recent discussions on JCL 2.0.0 and a version without
autodiscovery.
Someone stated
On 4/3/07, Henri Yandell [EMAIL PROTECTED] wrote:
I think the end should be nigh for Jakarta (those on private@ will
have seen a thread in which I side-topic'd with the feeling that the
end should be nigh for Jakarta). Previously I've suggested that
Commons should flatten into Jakarta and that
2007/4/3, nicolas de loof [EMAIL PROTECTED]:
Peux tu compter ça dans ton budget :
http://www.camif.fr/wwwSurf/pages/multimedia/OffreDuJour.asp?REFERENCE=883272
Ca serait pas mal au fond du placard de l'entrée ?
Yeah whatever you say :-P
Peux tu compter ça dans ton budget :
http://www.camif.fr/wwwSurf/pages/multimedia/OffreDuJour.asp?REFERENCE=883272
Ca serait pas mal au fond du placard de l'entrée ?
Phil Steitz wrote:
Yeah, assuming the m2's work. Its probably best in each case to post
something like
[foo] moving to m2
and make sure that nobody screams, all are OK with the pom can get the
build to work, etc., before moving the associated nightly and
deprecating the m1 build (to be
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-jsl-test has an issue affecting its community
integration.
Hello Simon,
Simon Kitching wrote:
Would you both mind explaining what benefits you see in a new JCL
implementation that cannot be obtained via java.util.logging?
this is possible already today with x4juli, it does have a JCL native
implementation.
I'm no fan of the j.u.l design, but it
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-fmt-test has an issue affecting its community
integration.
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at [EMAIL PROTECTED]
Project commons-jelly-tags-fmt-test has an issue affecting its community
integration.
[
https://issues.apache.org/jira/browse/FILEUPLOAD-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jochen Wiedmann resolved FILEUPLOAD-132.
Resolution: Fixed
I understand that you want the global HTTP request headers,
Would you guys be open to a patch to implement a periodic cleanup of
abandoned connections
the following logic can cause abandoned connections to sit around
forever, just because you are not hitting the max in the pool.
Using a DB like postgres that creates a process for each connection,
this
On 4/2/07, Henri Yandell [EMAIL PROTECTED] wrote:
On 4/2/07, Phil Steitz [EMAIL PROTECTED] wrote:
snip/
+0 for waiting to do this until we have a clear idea of where the rest
of the Jakarta subprojects are going.
Once we go TLP, I imagine a few would head in our direction, whereas
until we
I've got a question: If we have commons.apache.org, what will be the
difference to jakarta.apache.org, apart from the missing projects? Why
do we expect that c.a.p will work, although we assume that j.a.p
didn't?
Thanks,
Jochen
--
My cats know that I am a loser who goes out for hunting every
j:new casts objects to java.lang.String
---
Key: JELLY-275
URL: https://issues.apache.org/jira/browse/JELLY-275
Project: Commons Jelly
Issue Type: Bug
Components: core / taglib.core
Affects
[
https://issues.apache.org/jira/browse/COLLECTIONS-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Kestle updated COLLECTIONS-247:
---
Description:
As requested on
On 4/3/07, Oliver Zeigermann [EMAIL PROTECTED] wrote:
+1 to all said. I could even help.
-0 to waiting until we have a clear idea about the rest of Jakarta as
this is likely to never happen. Maybe a clearer idea will form after
commons leaves Jakarta.
I guess that's one way to force the
On 4/3/07, Jochen Wiedmann [EMAIL PROTECTED] wrote:
I've got a question: If we have commons.apache.org, what will be the
difference to jakarta.apache.org, apart from the missing projects? Why
do we expect that c.a.p will work, although we assume that j.a.p
didn't?
I had three answers to this
Author: tcurdt
Date: Tue Apr 3 13:44:40 2007
New Revision: 525273
URL: http://svn.apache.org/viewvc?view=revrev=525273
Log:
first try failed
Removed:
jakarta/commons/proper/jci/tags/1.0-RC1/
-
To unsubscribe, e-mail:
A group of people that care about the same things under one umbrella, with it's
own power of making
decisions. Jakarta isn't that, c.a.o will for commons.
Mvgr,
Martin
Jochen Wiedmann wrote:
I've got a question: If we have commons.apache.org, what will be the
difference to jakarta.apache.org,
Author: tcurdt
Date: Tue Apr 3 13:56:39 2007
New Revision: 525275
URL: http://svn.apache.org/viewvc?view=revrev=525275
Log:
[maven-release-plugin] prepare release 1.0-RC1
Modified:
jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml
Author: tcurdt
Date: Tue Apr 3 13:56:56 2007
New Revision: 525276
URL: http://svn.apache.org/viewvc?view=revrev=525276
Log:
[maven-scm] copy for tag 1.0-RC1
Added:
jakarta/commons/proper/jci/tags/1.0-RC1/
- copied from r524960, jakarta/commons/proper/jci/trunk/
Author: tcurdt
Date: Tue Apr 3 13:57:13 2007
New Revision: 525277
URL: http://svn.apache.org/viewvc?view=revrev=525277
Log:
[maven-release-plugin] prepare for next development iteration
Modified:
jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml
[
https://issues.apache.org/jira/browse/JELLY-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486496
]
Andre Huertas commented on JELLY-275:
-
I created a little work around for this (but I'm new to this so I'm not
Author: psteitz
Date: Tue Apr 3 14:35:43 2007
New Revision: 525289
URL: http://svn.apache.org/viewvc?view=revrev=525289
Log:
Updated site, pom for 1.2.2 release.
Modified:
jakarta/commons/proper/dbcp/trunk/project.xml
jakarta/commons/proper/dbcp/trunk/xdocs/navigation.xml
Modified:
+1 for c.a.o, since I think it is right thing for commons.
Jakarta PMC Chair hat on
I really regret this step is necessary and is the beginning of the end of
Jakarta. Even though this
process started earlier than this proposal, this process will make the end of
Jakarta unavoidable. I
always
So I got further. So it looks like this
mvn -Prc release:prepare
mvn -Prc release:perform -Dgpg.passphrase=... -Darguments=-
Dgpg.passphrase=...
almost does the job. Builds and prepares the whole thing. Even does
the upload BUT
...I cannot find the artifacts in the remote repo (but in
On 4/3/07, Luc Maisonobe [EMAIL PROTECTED] wrote:
Phil Steitz wrote:
Yeah, assuming the m2's work. Its probably best in each case to post
something like
[foo] moving to m2
and make sure that nobody screams, all are OK with the pom can get the
build to work, etc., before moving the
[
https://issues.apache.org/jira/browse/JELLY-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486524
]
Paul Libbrecht commented on JELLY-275:
--
Andre,
this really looks like a bug.
I believe that on should rather
Author: tcurdt
Date: Tue Apr 3 15:54:52 2007
New Revision: 525319
URL: http://svn.apache.org/viewvc?view=revrev=525319
Log:
next try
Removed:
jakarta/commons/proper/jci/tags/1.0-RC1/
-
To unsubscribe, e-mail: [EMAIL
Author: tcurdt
Date: Tue Apr 3 16:01:17 2007
New Revision: 525321
URL: http://svn.apache.org/viewvc?view=revrev=525321
Log:
[maven-release-plugin] prepare release 1.0-RC1
Modified:
jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml
Author: tcurdt
Date: Tue Apr 3 16:01:34 2007
New Revision: 525322
URL: http://svn.apache.org/viewvc?view=revrev=525322
Log:
[maven-scm] copy for tag 1.0-RC1
Added:
jakarta/commons/proper/jci/tags/1.0-RC1/
- copied from r524960, jakarta/commons/proper/jci/trunk/
Author: tcurdt
Date: Tue Apr 3 16:01:48 2007
New Revision: 525323
URL: http://svn.apache.org/viewvc?view=revrev=525323
Log:
[maven-release-plugin] prepare for next development iteration
Modified:
jakarta/commons/proper/jci/trunk/compilers/eclipse/pom.xml
Hi, Torsten,
On 4/4/07, Torsten Curdt [EMAIL PROTECTED] wrote:
it looks like the repository from the profile is not getting
selected. Instead the artifacts are getting copied in the default
as far as I remember, -Prc was for uploading a snapshot release.
You've got to use -Prelease.
Jochen
The Jakarta Commons team is pleased to announce the release of version
1.2.2 of the commons-DBCP component. Commons DBCP is a database
connection pool.
The 1.2.2 release is a maintenance release, including numerous bug
fixes, upgrade to commons-pool 1.3, and elimination of the dependency
on
[
https://issues.apache.org/jira/browse/DBCP-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Phil Steitz resolved DBCP-68.
-
Resolution: Fixed
1.2.2 has (at last) been released.
[dbcp] Commons Collection dependency version clash
39 matches
Mail list logo
