Author: bayard
Date: Sat Sep 9 23:01:04 2006
New Revision: 441916
URL: http://svn.apache.org/viewvc?view=revrev=441916
Log:
Maven-2 pom for IO so I can mvn install the snapshot locally into my .m2 and
use it with finder
Added:
jakarta/commons/proper/io/trunk/pom.xml
Added:
Author: bayard
Date: Sat Sep 9 23:13:41 2006
New Revision: 441918
URL: http://svn.apache.org/viewvc?view=revrev=441918
Log:
Finder is also going to want to use CLI, so creating an m2 pom for it as well
Added:
jakarta/commons/proper/cli/trunk/pom.xml
Added:
So I'm using [cli] in [finder] to see if I can mimic the command line
interface for the unix find command. I'm using the cli2 version - lots
of thought, but very painful to use. Here are the 30 lines of code to
add a single option:
code
public static void main(String[] args) throws
Author: bayard
Date: Sun Sep 10 00:40:29 2006
New Revision: 441922
URL: http://svn.apache.org/viewvc?view=revrev=441922
Log:
Adding dependency on commons-cli for the purpose of a command line find
implementation, and a Find class to put said implementation in, though it
barely has anything in
Author: bayard
Date: Sun Sep 10 00:55:54 2006
New Revision: 441924
URL: http://svn.apache.org/viewvc?view=revrev=441924
Log:
Update the text section - though not with much of value. Need to talk about the
classes here.
Modified:
jakarta/commons/proper/lang/trunk/xdocs/userguide.xml
Author: bayard
Date: Sun Sep 10 00:56:35 2006
New Revision: 441925
URL: http://svn.apache.org/viewvc?view=revrev=441925
Log:
Killing the 'next version' part of the user guide. It's the wrong place for
that kind of information I think
Modified:
Author: bayard
Date: Sun Sep 10 01:04:17 2006
New Revision: 441929
URL: http://svn.apache.org/viewvc?view=revrev=441929
Log:
Fixed javadoc typo as mentioned in #LANG-258
Modified:
jakarta/commons/proper/lang/trunk/src/java/org/apache/commons/lang/enum/ValuedEnum.java
[
http://issues.apache.org/jira/browse/LANG-258?page=comments#action_12433677 ]
Henri Yandell commented on LANG-258:
Fixed the doSomething javado typo in r441929. Will go with 2.2.
Enum JavaDoc: 1) outline 5.0 native Enum migration 2) warn
Any thoughts on this issue?
https://issues.apache.org/jira/browse/LANG-262
Says that the cEnumClasses Hashmap in the Enum class is keeping a
ClassLoader from being garbage collected and that switching it to a
WeakHashMap should fix it.
Seems fair to me, and an easy fix for 2.2; but not
Author: olegk
Date: Sun Sep 10 04:14:12 2006
New Revision: 441940
URL: http://svn.apache.org/viewvc?view=revrev=441940
Log:
HTTPCLIENT-597
Modified:
jakarta/commons/proper/httpclient/trunk/release_notes.txt
Modified: jakarta/commons/proper/httpclient/trunk/release_notes.txt
URL:
Hey guys
An interesting discussion here. I'll try to address some of the points
raised and give my take on the issue.
* As far as [net] specifically is concerned, there are very few things
that 1.5 makes possible that you really can't do on 1.3 (One of these is
asynchronous I/O and a
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.
Failed build logs:
http://people.apache.org/~psteitz/commons-nightlies/20060910/finder.log
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Continuing the discussion:
1. Regex support is in 1.4. It's only because we were trying to stay 1.2/1.3
compatible that we couldn't use it. That's a small point. I doubt we want to
have (say) a 1.4.2 branch that requires 1.4 after having supported 1.2/1.3 for
all these years, if our
On 9/9/06, Steve Cohen [EMAIL PROTECTED] wrote:
snip/
I am not ready to vote yet on this until there is a discussion about what this
release means. Will commons-net-2.0 become the official release, with
previous versions relegated to backward compatibility support? If so, this
may be
Henri Yandell wrote:
So I'm using [cli] in [finder] to see if I can mimic the command line
interface for the unix find command. I'm using the cli2 version - lots
of thought, but very painful to use. Here are the 30 lines of code to
add a single option:
snip/
Must learn more about the CLI API
On 9/10/06, Steve Cohen [EMAIL PROTECTED] wrote:
Continuing the discussion:
1. Regex support is in 1.4. It's only because we were trying to stay 1.2/1.3
compatible that we couldn't use it. That's a small point. I doubt we want to
have (say) a 1.4.2 branch that requires 1.4 after having
I agree with the major points that Steve has made below. I would think
that a logical way to go (at least for [net]} would be :
* Version 2.0 (JDK 5.0+) becomes the main development branch, and the
focal point for new features;
* Version 1.x continues to be supported, in that fixes and new
Hello,
As mentioned a few times on this list, I have proposed to donate the
Mantissa (http://www.spaceroots.org/software/mantissa/index.html) code
to Apache and continue maintaining it here along with commons math.
Almost everything has been both designed and coded by me, so I was able
to
I think we are in agreement. I would be available to do some of the backporting
work if we go down this path.
Does anyone have anything to say about making the site a dual site (something
like Tomcat does)? How difficult is that? Does Maven 2 aid in such a process,
can it build a site from
May I point out, that tools like retroweaver or retrotranslator can be
used to write code with most 1.5 features while still compiling for
1.4? I don't know whether this applies to the commons-net project, but
for most projects I know, this should still be fine.
Jochen
It looks like the Minpack license is a BSD license with an extended
warranty and liability section. I'll ping the legal-discuss mailing
list about it, but it looks fine to me. Just some government
boilerplate tacked onto a BSD license I think.
The Hairer license is as you say, a BSD-like
How does that work exactly? Can we happily write 1.5 stuff and then
let the user take the 1.5 jar and retroweave it before using it, or do
we have to integrate retroweaver into our builds (though not our
sources I hope?)?
Hen
On 9/10/06, Jochen Wiedmann [EMAIL PROTECTED] wrote:
May I point
You'd integrate it into your builds. However, this doesn't help with
missing APIs (though I believe retrotranslator does take care of some
of these). It's a pretty good solution for providing JDK 5 binaries
for JDK 1.4.
However, I don't think this addresses the issue being faced - and it
Brett Porter wrote:
Didn't collections go through this
(backwards-incompatible API change, not a JDK5-ification) Îin the past
for 3.0? Any experiences that can be learned from there?
[collections] 3.0 has been FUDed with the backwards incompatible tag
ever since it was released, but it was
Some interesting points have been made so far. I believe I should
restate my proposal based on feedback (especially as the original was
written just after a weeks holiday...):
[PROPOSAL]
Whenever a project performs a backwards incompatible API change, two
things must happen:
a) the major
oops! Thanks for the clarification - I'd never had any problems
myself, but I thought I'd gotten that indication from the release
notes/web site. Long while ago now, obviously my memory isn't so good.
- Brett
On 11/09/2006, at 7:55 AM, Stephen Colebourne wrote:
Brett Porter wrote:
Didn't
Henri Yandell wrote :
It looks like the Minpack license is a BSD license with an extended
warranty and liability section. I'll ping the legal-discuss mailing
list about it, but it looks fine to me. Just some government
boilerplate tacked onto a BSD license I think.
Thanks. I'm not subscribed
29 matches
Mail list logo
