i don't like the policy of changing the package name to make a tiny change
to binary compatibility. it makes it impossible to release often
but we're getting way off base. my question is the same as ben's which was
never answered. can we check in the patch for 209 and then release a new
version?
We could release an Alpha to make it clear that we are still working on
possibly important changes.
G
On Mon, Mar 2, 2015 at 2:46 PM, ianmca86 ianmc...@gmail.com wrote:
Perhaps we could at least get a milestone release (i.e. pre-RC)? I'd like
to see if I can submit a branch to jibx where I
On 2 March 2015 at 20:00, Leandro Reis lr...@adobe.com wrote:
Hi all,
I¹m working on a product that uses Commons IO via Jackrabbit Oak. In the
process of testing the launch of such product on Japanese Windows 2012
Server R2, I came across the following exception:
On 2 March 2015 at 21:33, Gary Gregory garydgreg...@gmail.com wrote:
I'm all for RERO if the release manager is willing.
RM willingness is only part of it.
RERO is all very well if:
- the API is stable; or
- frequent changes of package name/Maven coords are acceptable to consumers; or
- one
I'm all for RERO if the release manager is willing.
Gary
On Mon, Mar 2, 2015 at 12:37 PM, ianmca86 ianmc...@gmail.com wrote:
+1
no one has really answered ben's question yet. if bcel 209
https://issues.apache.org/jira/browse/BCEL-209 is committed could we
cut
a release? it seems like
+1 to releasing an Alpha or making 6.0-RC3 available via Maven. Compiling
it ourselves is a really painful solution. It means we also need to setup
our own public Maven repository or make other drastic changes to our
release engineering.
On Mon, Mar 2, 2015 at 3:03 PM, Gary Gregory
Le 03/03/2015 00:03, Gary Gregory a écrit :
We could release an Alpha to make it clear that we are still working on
possibly important changes.
But we would have to upload it to Maven Central to make it really
useful. If there is a consensus to do that I'm ok to cut a release soon.
Emmanuel
WRT Tangent: The thing with BC is that it's a Boolean property, not a
quantitative...
On Mon, Mar 2, 2015 at 2:21 PM, ianmca86 ianmc...@gmail.com wrote:
i don't like the policy of changing the package name to make a tiny change
to binary compatibility. it makes it impossible to release often
Le 02/03/2015 23:21, ianmca86 a écrit :
i don't like the policy of changing the package name to make a tiny change
to binary compatibility. it makes it impossible to release often
And users don't like having deep conflicting libraries in their
dependency tree :)
but we're getting way off
On Mon, Mar 2, 2015 at 2:07 PM, sebb seb...@gmail.com wrote:
On 2 March 2015 at 21:33, Gary Gregory garydgreg...@gmail.com wrote:
I'm all for RERO if the release manager is willing.
RM willingness is only part of it.
RERO is all very well if:
- the API is stable; or
- frequent changes of
Le 02/03/2015 22:33, Gary Gregory a écrit :
I'm all for RERO if the release manager is willing.
I tend to agree with RERO, but if the API is not ready I don't think
it's right to rush into a release, and the deeper I dig into BCEL the
more I'm bothered by the issues I find.
Once BCEL is back in
On Mon, Mar 2, 2015 at 2:44 PM, Emmanuel Bourg ebo...@apache.org wrote:
Le 02/03/2015 22:33, Gary Gregory a écrit :
I'm all for RERO if the release manager is willing.
I tend to agree with RERO, but if the API is not ready I don't think
it's right to rush into a release, and the deeper I
Perhaps we could at least get a milestone release (i.e. pre-RC)? I'd like
to see if I can submit a branch to jibx where I get them to use the latest
bcel code. jibx won't work with Java 8 because we're waiting on a bcel
release. It's hard to work on making jibx compatible with Java 8 as long as
yes, that would be perfect! (agreed it would have to go to maven)
thanks so much for taking the suggestion into consideration!
-ian
On Mon, Mar 2, 2015 at 3:08 PM, Emmanuel Bourg-3 [via Apache Commons]
ml-node+s680414n4673398...@n4.nabble.com wrote:
Le 03/03/2015 00:03, Gary Gregory a écrit
On 2 March 2015 at 21:53, sebb wrote:
On 2 March 2015 at 20:00, Leandro Reis lr...@adobe.com wrote:
Hi all,
I¹m working on a product that uses Commons IO via Jackrabbit Oak. In the
process of testing the launch of such product on Japanese Windows 2012
Server R2, I came across the following
2015-03-02 21:34 GMT+01:00 Oliver Heger oliver.he...@oliver-heger.de:
Am 02.03.2015 um 07:23 schrieb Benedikt Ritter:
2015-03-01 22:20 GMT+01:00 Oliver Heger oliver.he...@oliver-heger.de:
Am 01.03.2015 um 17:52 schrieb Benedikt Ritter:
2015-02-26 21:29 GMT+01:00 Oliver Heger
Am 02.03.2015 um 07:23 schrieb Benedikt Ritter:
2015-03-01 22:20 GMT+01:00 Oliver Heger oliver.he...@oliver-heger.de:
Am 01.03.2015 um 17:52 schrieb Benedikt Ritter:
2015-02-26 21:29 GMT+01:00 Oliver Heger oliver.he...@oliver-heger.de:
Hi Arthur,
I don't have any principle objections
Hi all,
I¹m working on a product that uses Commons IO via Jackrabbit Oak. In the
process of testing the launch of such product on Japanese Windows 2012
Server R2, I came across the following exception:
(java.io.UnsupportedEncodingException: Encoding windows-31j is not
supported yet (feel free to
+1
no one has really answered ben's question yet. if bcel 209
https://issues.apache.org/jira/browse/BCEL-209 is committed could we cut
a release? it seems like everyone is okay with the general approach taken
there
my company also is mandating all projects move to java 8 this month since
java
Hi!
I have a question about dbcp and pool.
Last two weeks I have examined heapdumps of Tomcat instances that is
used by my apps.
There is situation with BoneCP - it have a LOT of SQLWarnings at each
connection used by it.
With DBCP-app all is normal - there is no SQLWarnings.
Apps are not the
Heads up: No ASL header !!
--- Weitergeleitete Nachricht (Anfang)
Betreff: svn commit: r1663140 - in /commons/proper/lang/trunk/src:
changes/changes.xml
main/java/org/apache/commons/lang3/time/FastDateParser.java
test/java/org/apache/commons/lang3/time/FastDateParserSDFTest.java
On 3/1/15 2:24 PM, Антон Мацюк wrote:
Hi!
I have a question about dbcp and pool.
Last two weeks I have examined heapdumps of Tomcat instances that is
used by my apps.
There is situation with BoneCP - it have a LOT of SQLWarnings at each
connection used by it.
With DBCP-app all is normal -
22 matches
Mail list logo
