On Feb 6, 2008 5:02 AM, Henri Yandell <[EMAIL PROTECTED]> wrote:
> I buy your argument for huge changes, ie) collections-generics is very
> much a different product. I don't buy it for small API changes and
> removal of deprecation. Your argument would imply that we should never
> deprecate (as we
my fault, I introduced a dependency cycle in Gump which should be
fixed now.
sorry for the noise
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
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-collections has an issue affecting its community integration.
This issue
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-xmlio has an issue affecting its community integration.
This issue affect
On Feb 5, 2008 5:27 AM, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> On 05.02.2008, at 06:44, Henri Yandell wrote:
> > For Collections it makes sense as there's a big API change planned.
> > For the others, I think they should charge in and see what kind of
> API
> > changes are required. If w
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-threading has an issue affecting its community integration.
This issue af
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-openpgp has an issue affecting its community integration.
This issue affe
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-launcher has an issue affecting its community integration.
This issue aff
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-jjar has an issue affecting its community integration.
This issue affects
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-http has an issue affecting its community integration.
This issue affects
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-attributes has an issue affecting its community integration.
This issue 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-io has an issue affecting its community integration.
This issue affects 1
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-daemon has an issue affecting its community integration.
This issue affec
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-codec has an issue affecting its community integration.
This issue affect
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-lang has an issue affecting its community integration.
This issue affects
> From: Stephen Colebourne [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 2:19 PM
> To: Jakarta Commons Developers List
> Subject: Re: [io] 2.0 Moving to minimum of JDK 1.5
>
> Simon Kitching wrote:
> > Stephen Colebourne <[EMAIL PROTECTED]> schrieb:
> >>> On Feb 4, 2008 8:47 PM,
Looks cool IMO +1
cheers
--
Torsten
On 05.02.2008, at 22:14, Niall Pemberton wrote:
On Feb 5, 2008 8:40 PM, Niall Pemberton <[EMAIL PROTECTED]>
wrote:
On Feb 5, 2008 9:51 AM, Torsten Curdt <[EMAIL PROTECTED]> wrote:
On 05.02.2008, at 02:34, Niall Pemberton wrote:
The ant plugin I've been
Simon Kitching wrote:
Stephen Colebourne <[EMAIL PROTECTED]> schrieb:
On Feb 4, 2008 8:47 PM, Niall Pemberton <[EMAIL PROTECTED]>
From memory the preference was to move to a new package name - how
about "org.apache.commons.io2"?
To avoid confusion with version numbers, we could choose [
On Feb 5, 2008 6:09 PM, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, February 05, 2008 9:52 AM
> > To: Jakarta Commons Developers List
> > Subject: Re: [io] 2.0 Moving to minimum of JDK 1.5
> >
> > On Feb 5, 2008 5:49 PM, Gary Gregor
FYI:
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Thomas Watson
Sent: Dienstag, 05. Februar 2008 19:52
To: Orbit Developer discussion
Subject: Re: [orbit-dev] FW: Support for OSGi
The thread at
http://dev.eclipse.org/mhonarc/lists/orbit-dev/msg
On Feb 5, 2008 8:40 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> On Feb 5, 2008 9:51 AM, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> >
> > On 05.02.2008, at 02:34, Niall Pemberton wrote:
> >
> > > The ant plugin I've been playing with in the Sandbox provides a way to
> > > generate custom JIRA i
On Feb 5, 2008 9:51 AM, Torsten Curdt <[EMAIL PROTECTED]> wrote:
>
> On 05.02.2008, at 02:34, Niall Pemberton wrote:
>
> > The ant plugin I've been playing with in the Sandbox provides a way to
> > generate custom JIRA issue tracking pages and download pages for
> > components:
> >
> > http://commo
On Tue, 2008-02-05 at 19:33 +, Niall Pemberton wrote:
> On Feb 5, 2008 7:26 PM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> > Hello
> >
> > I've got a strange behavior of Eclipse when using maven to configure my
> > environment. The .classpath includes the project root as a source folder to
>
On Feb 5, 2008 7:26 PM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Hello
>
> I've got a strange behavior of Eclipse when using maven to configure my
> environment. The .classpath includes the project root as a source folder to
> match the commons-parent-7.pom .
>
> This has the side effect that t
Hello
I've got a strange behavior of Eclipse when using maven to configure my
environment. The .classpath includes the project root as a source folder to
match the commons-parent-7.pom .
This has the side effect that the "new class" wizard appends "src.main.java."
to the extended class in imports
> From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, February 05, 2008 9:52 AM
> To: Jakarta Commons Developers List
> Subject: Re: [io] 2.0 Moving to minimum of JDK 1.5
>
> On Feb 5, 2008 5:49 PM, Gary Gregory <[EMAIL PROTECTED]> wrote:
> > Should we come up with a general package na
On Feb 5, 2008 5:49 PM, Gary Gregory <[EMAIL PROTECTED]> wrote:
> Should we come up with a general package naming convention for all commons
> projects and Java 5?
>
> Either:
>
> org.apache.commons.io2
> org.apache.commons.lang2
> org.apache.commons.[project]2
>
> Or:
>
> org.apache.commons2.io
>
Should we come up with a general package naming convention for all commons
projects and Java 5?
Either:
org.apache.commons.io2
org.apache.commons.lang2
org.apache.commons.[project]2
Or:
org.apache.commons2.io
org.apache.commons2.lang
org.apache.commons2.[project]
Where the minimum requirement
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-jaxme has an issue affecting its community
integration.
This
I just fixed commons-httpclient to include the NOTICE.txt in META-INF
commons-betwixt 0.5 and commons-jxpath 1.2 source distribution in
http://archive.apache.org/dist/commons/betwixt/source/ does not contain the
required NOTICE...
I've added it manually to fix the source.jars
commons-pool 1.0 is
Niall Pemberton <[EMAIL PROTECTED]> schrieb:
> I don't see why people are voting -1 on all of this when its only
> certain jars in question. IMO those that have an AL 2.0 and NOTICE
> file are good to go. Those with missing bits should be -1 (betwixt
> 0.5, httpclient 3.1, jxpath 1.2, pool 1.0
Stephen Colebourne <[EMAIL PROTECTED]> schrieb:
> > On Feb 4, 2008 8:47 PM, Niall Pemberton <[EMAIL PROTECTED]>
>> From memory the preference was to move to a new package name - how
>> about "org.apache.commons.io2"?
To avoid confusion with version numbers, we could choose [io-two]:
org.ap
On Feb 5, 2008 10:30 AM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> According to previous discution, the maven -sources.jar bundles that haven't
> yet been deployed on maven "central" repository require a PMC vote.
>
> They are just a repackaging of the original -src.zip source distribution,
> an
On Feb 5, 2008 2:58 PM, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Most public artifacts on maven "central" have no such cource bundles, even
> recent ones when built with maven. see commons-httpclient 3.1 :-/
In that case, commons-httpclient is
- not using a Maven 2 build
- either not using t
The issue is not to produce those source bundles, but to get them from
project dependencies from public repositories.
Most public artifacts on maven "central" have no such cource bundles, even
recent ones when built with maven. see commons-httpclient 3.1 :-/
The issue discussed here is to repacka
On Feb 5, 2008 2:27 PM, Stephen Colebourne <[EMAIL PROTECTED]> wrote:
> To avoid confusion with version numbers, we could choose [io-two]:
> org.apache.commons.io-two
I do not understand why that's less confusing if you have commons-io
version 3 in package org.apache.commons-io-two?
Jochen
-
On Tue, 5 Feb 2008, Simon Kitching <[EMAIL PROTECTED]> wrote:
> In my experience these weird execute bits are quite common; if a
> unix text file gets this bit set on it for some reason, then svn add
> will helpfully set the executable flag.
Many times the Cygwin svn client is to blame, it seems
2008/2/5, sebb <[EMAIL PROTECTED]>:
>
> Maven could/should be changed to use -src.zip if -sources.jar is
> missing ... seems to me that would be much less effort overall.
I do not know where you do see the problem with Maven. The projects
using M2 builds with the commons-parent POM *and* building
Because some IDEs already support source zips.
There are also far fewer IDEs than there are missing source jars.
S///
On 05/02/2008, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> Yeah ...I can also not see how that is LESS effort.
>
> cheers
> --
> Torsten
>
>
> On 05.02.2008, at 13:48, nicolas de l
> On Feb 4, 2008 8:47 PM, Niall Pemberton <[EMAIL PROTECTED]>
>> From memory the preference was to move to a new package name - how
>> about "org.apache.commons.io2"?
To avoid confusion with version numbers, we could choose [io-two]:
org.apache.commons.io-two
On 05.02.2008, at 06:44, Henri Ya
sebb <[EMAIL PROTECTED]> schrieb:
> I'm working on a Perl script to check that SVN properties have sensible
> values.
>
> I've tried it against some Commons projects, and found a few with
> rather odd settings, for example the following files are all flagged
> as svn:executable:
>
> Commons
Yeah ...I can also not see how that is LESS effort.
cheers
--
Torsten
On 05.02.2008, at 13:48, nicolas de loof wrote:
Right,
maven SHOULD support those source distribution bundles,
eclipse, netbeans and idea SHOULD support them also
all of them SHOULD support heterogeneous folders (src/java,
Eclipse already does - I'm using the source zips for various commons jars..
No idea about whether Netbeans or Idea support them.
On 05/02/2008, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Right,
>
> maven SHOULD support those source distribution bundles,
> eclipse, netbeans and idea SHOULD suppo
Should I raise JIRA issues for these (I can provide scripts to reset
the properties) or should I just fix them in trunk?
Good finding ...just fix them IMO
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addi
Right,
maven SHOULD support those source distribution bundles,
eclipse, netbeans and idea SHOULD support them also
all of them SHOULD support heterogeneous folders (src/java, src/main/java,
src/share ...) in such archives.
... much less effort ?
Nico.
2008/2/5, sebb <[EMAIL PROTECTED]>:
>
> Ma
I'm working on a Perl script to check that SVN properties have sensible values.
I've tried it against some Commons projects, and found a few with
rather odd settings, for example the following files are all flagged
as svn:executable:
Commons-Lang
src/java/org/apache/commons/lang/mutable/Mutable.j
Maven could/should be changed to use -src.zip if -sources.jar is
missing ... seems to me that would be much less effort overall.
S///
On 05/02/2008, nicolas de loof <[EMAIL PROTECTED]> wrote:
> Only -sources.jar are downloaded by maven and added to IDE for
> source-debugging.
>
> Existing src-dist
Only -sources.jar are downloaded by maven and added to IDE for
source-debugging.
Existing src-dists require users to manually do the unzip & jar I've done
2008/2/5, sebb <[EMAIL PROTECTED]>:
>
> -1, for the following reasons:
>
> - these are new distributions and all new distributions must contai
Right,
Nico.
2008/2/5, Torsten Curdt <[EMAIL PROTECTED]>:
>
> I suggest we cancel/postpone the vote until we hear back from the board.
> I've just sent the mail.
>
> cheers
> --
> Torsten
>
>
> -
> To unsubscribe, e-mail: [EMAIL P
-1, for the following reasons:
- these are new distributions and all new distributions must contain
NOTICE and LICENSE files; not all of them do.
- at least one of the repackaged jars does not correspond with the
release src.zip file
Why not just upload the existing source zip or tgz files?
No re
I suggest we cancel/postpone the vote until we hear back from the board.
I've just sent the mail.
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-0: I do not agree that a "re-packaging" does not qualify as a
distribution. But I am no lawyer. Therefore, I won't block.
--
Look, that's why there's rules, understand? So that you think before
you break 'em.
-- (Terry Pratchett, Thief of Time)
-
Thought the agreement was to check with the board/legal about the
license files first? Or did I miss that?
cheers
--
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
+100 ... enough ? ;-)
[EMAIL PROTECTED] wrote:
> According to previous discution, the maven -sources.jar
> bundles that haven't
> yet been deployed on maven "central" repository require a PMC vote.
>
> They are just a repackaging of the original -src.zip source
> distribution, and are NOT conside
According to previous discution, the maven -sources.jar bundles that haven't
yet been deployed on maven "central" repository require a PMC vote.
They are just a repackaging of the original -src.zip source distribution,
and are NOT considered as a new release of the considered apache commons
compon
On 05.02.2008, at 06:44, Henri Yandell wrote:
On Feb 4, 2008 8:47 PM, Niall Pemberton <[EMAIL PROTECTED]>
wrote:
We've discussed moving to a minimum of JDK 1.5 for IO 2.0
previously -
theres also an JIRA report here:
http://issues.apache.org/jira/browse/IO-140
From memory the preference
On 05.02.2008, at 02:34, Niall Pemberton wrote:
The ant plugin I've been playing with in the Sandbox provides a way to
generate custom JIRA issue tracking pages and download pages for
components:
http://commons.apache.org/sandbox/commons-build-plugin/
If we add it to the commons-parent, then
57 matches
Mail list logo
