commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niall Pemberton" <niall.pember...@gmail.com>
Subject Re: [IO] Planning IO 1.4 release
Date Sun, 06 Jan 2008 20:26:15 GMT
On Jan 6, 2008 6:18 PM, sebb <sebbaz@gmail.com> wrote:
>
> On 06/01/2008, Dennis Lundberg <dennisl@apache.org> wrote:
> > Henri Yandell wrote:
> > > On Jan 5, 2008 5:51 PM, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> > >> I would like to get an IO 1.4 release out in the near future. Looking
> > >> thru the issues tagged for 1.4 I would suggest the following:
> > >>
> > >> 1) Resolve the following issues, which all have patches except IO-149
> > >> which is trivial
> > >>   IO-149 - Make FilenameUtils.EXTENSION_SEPARATOR public
> > >>   IO-105 - Add a FileUtils.copyDirectoryStructure method
> > >>   IO-152 - Add ByteArrayOutputStream.readFrom(InputStream)
> > >>   IO-135 - Add convenience deleteQuietly to FileUtils
> > >
> > > +1
> > >
> > >> 2) Move the following issues to post-1.4
> > >>   IO-137 - Added method for getting InputStream from
> > >> ByteArrayOutputStream & IOUtils avoiding unnecessary array allocation
> > >> and copy
> > >>   IO-51  - Throttled input and output stream classes
> > >>   IO-77 - add a convenience FileUtils.move(File src, File dest)
> > >
> > > +1 on IO-77 being post-1.4 as it lacks unit tests.
> > >
> > > I think we should deal with IO-137 as it's a minor enhancement and
> > > comes with tests. I'll volunteer to look at that.
> > >
> > > IO-51 has tests, so worth a look at if that can be done before the
> > > others are resolved. ie) punt to post-1.4 iff it's the last one left.
> > >
> > >> 3) Upgrade to commons-parent-6 pom.xml which looks like the release
> > >> will be approved shortly
> > >>
> > >> Thoughts on this?
> > >
> > > Delete the M1 build, and maybe Ant given that the build.xml is M1 generated.
> >
> > For the Logging release I documented in RELEASE-NOTES.txt that the M1
> > build was deprecated and that it will be removed in a future release. If
> > it is still working that can be a smooth transition. Deprecate it and
> > remove it in the next release, or just remove it straight away.
> >
> > There is an Ant plugin for M2 as well. I haven't used it myself, but I
> > could have a go at it, if we think it'd be good to still have a basic
> > Ant build around.
> >
> > > And IO-148 + IO-127?
> > >
> > > Hen
> >
>
> I could not work out from the current web-site which versions of Java
> are supported.

Theres a note about it in the release notes:

http://svn.apache.org/repos/asf/commons/proper/io/trunk/RELEASE-NOTES.txt

> Seems to me this should be added to the dependencies page.

I've always thought that, but thats maven generated don't know how we
could do that?

> Also, the current dependencies page lists junit as a run-time
> dependency, which seems wrong.

Again thats a m1 issue. With m2 it does a better job with the
<scope>test</scope> on the generated page.

> IClasses need documentation on whether they are thread-safe or not.

Better docs are always nice but it needs someone to step up and do it.
If someone does then great, otherwise it [IO-134] should get moved to
post-1.4 IMO

Niall

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message