Hi Seb!
>> +
>> + 2.12
>
> Commons Parent 23 has
>
> 2.9
>
> Would it work to override this instead?
yeah! didn't notice it, it does!
>> + maven-surefire-report-plugin
>> + ${surefire.version}
>> +
>> + true
>> +
>
> The config section is not in CP23.
Ralph Goers wrote:
>
> On Mar 6, 2012, at 8:51 PM, sebb wrote:
>
>> On 7 March 2012 01:43, James Carman wrote:
>>> I still think it should be renamed, but I think I lost that battle.
>>
>> Given the "release" by Solr, perhaps now would be a good time to
>> revisit that discussion.
>>
>> It wo
Le 06/03/2012 18:42, Emmanuel Bourg a écrit :
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers, a CSV AP
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 gene...@gump.apache.org.
Project commons-vfs2-test has an issue affecting its community integration.
This i
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 gene...@gump.apache.org.
Project commons-proxy-test has an issue affecting its community integration.
This
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 gene...@gump.apache.org.
Project commons-configuration-test has an issue affecting its community
integrati
Hi,
>> If you like the Wiki system and you want to lead the work, then use your
>> favorite tool.
>>
I've tried to play around with the Wiki system, and it certainly is
*not* my favorite tool... So another idea would be to keep the report
on the refactoring as a page in the website of Commons-Mat
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 gene...@gump.apache.org.
Project commons-scxml-test has an issue affecting its community integration.
This
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "LinearPackageInterfaceSimplification" page has been changed by
SebastienBrisard:
http://wiki.apache.org/commons/LinearPackageInterfaceSimplification?action=diff&rev1=4&rev2=5
=
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "LinearPackageInterfaceSimplification" page has been changed by
SebastienBrisard:
http://wiki.apache.org/commons/LinearPackageInterfaceSimplification?action=diff&rev1=3&rev2=4
=
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "LinearPackageInterfaceSimplification" page has been changed by
SebastienBrisard:
http://wiki.apache.org/commons/LinearPackageInterfaceSimplification?action=diff&rev1=2&rev2=3
On Mar 6, 2012, at 8:51 PM, sebb wrote:
> On 7 March 2012 01:43, James Carman wrote:
>> I still think it should be renamed, but I think I lost that battle.
>
> Given the "release" by Solr, perhaps now would be a good time to
> revisit that discussion.
>
> It would solve any package name clashe
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "LinearPackageInterfaceSimplification" page has been changed by
SebastienBrisard:
http://wiki.apache.org/commons/LinearPackageInterfaceSimplification?action=diff&rev1=1&rev2=2
=
Maybe time to add a Base64(int mode) constructor! Yay, room for 32
true/false bitwise fields!
Sorry I can't respond inline to the email like a normal person. Bad habit.
yours,
Julius
On Tue, Mar 6, 2012 at 11:40 AM, sebb wrote:
> On 6 March 2012 19:33, Gary Gregory wrote:
>> What about pa
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 gene...@gump.apache.org.
Project commons-lang3-test has an issue affecting its community integration.
This
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 gene...@gump.apache.org.
Project commons-digester3 has an issue affecting its community integration.
This i
Let's start a separate thread for naming then.
Gary
On Mar 6, 2012, at 20:43, James Carman wrote:
> I still think it should be renamed, but I think I lost that battle.
> It's not just for comma-separated values. I'd rather us come up with
> a more generic name. I'm +1 for moving it out of the
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 gene...@gump.apache.org.
Project commons-io-test has an issue affecting its community integration.
This iss
On 7 March 2012 01:43, James Carman wrote:
> I still think it should be renamed, but I think I lost that battle.
Given the "release" by Solr, perhaps now would be a good time to
revisit that discussion.
It would solve any package name clashes without needing to call it
csv2 or whatever.
> It's
I still think it should be renamed, but I think I lost that battle.
It's not just for comma-separated values. I'd rather us come up with
a more generic name. I'm +1 for moving it out of the sandbox. It
needs a bit of polish before a release, though, IMHO.
On Tue, Mar 6, 2012 at 12:42 PM, Emmanu
+1
Niall
On Tue, Mar 6, 2012 at 5:42 PM, Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CS
>
>That's not the right conclusion.
>If there had been arguments against including , you
>would have
>gotten a response. :-)
You are totally right Gilles , I apologize for jumping to that conclusion.
>
>The central point is: It's is not primarily other people that have
>to be
>interested in a f
Hello Leandro.
> >>
> >> Thanks for your suggestion ! I Downloaded the sources and i will
> >check them soon. If I am correct , Maxima is implemented in Lisp
> >(or CLisp) but I guess it could be feasible , once they had been
> >analyzed and studied , to translate those algorithms into Java.
>
On 6 March 2012 22:35, wrote:
> Author: ggregory
> Date: Tue Mar 6 22:35:30 2012
> New Revision: 1297767
>
> URL: http://svn.apache.org/viewvc?rev=1297767&view=rev
> Log:
> Set the 1.4 release date. I should have done this before the release.
Surely we don't normally put release dates in releas
On 6 March 2012 21:50, wrote:
> Author: ggregory
> Date: Tue Mar 6 21:50:04 2012
> New Revision: 1297741
>
> URL: http://svn.apache.org/viewvc?rev=1297741&view=rev
> Log:
> Add JIRA report for all versions so you can see what has been fixed no matter
> what version you are updating from.
There
>>
>> Thanks for your suggestion ! I Downloaded the sources and i will
>> check them soon. If I am correct , Maxima is implemented in Lisp
>(or
>> CLisp) but I guess it could be feasible , once they had been
>analyzed
>> and studied , to translate those algorithms into Java.
>
>Maxima is GPL lic
On Tuesday, March 06, 2012 at 3:20 AM, Sébastien Brisard
wrote:
>
>>
>> Thanks for your suggestion ! I Downloaded the sources and i will
>check them soon. If I am correct , Maxima is implemented in Lisp
>(or CLisp) but I guess it could be feasible , once they had been
>analyzed and studied
Le 06/03/2012 22:09, Gary Gregory a écrit :
Let's not hesitate to go to Java 6 if it helps.
Gary
I do consider Java 6. I'm pondering if Commons CSV can be plugged with
JAXB to implement the bean parsing.
Emmanuel Bourg
smime.p7s
Description: S/MIME Cryptographic Signature
Could you please open a ticket in our bug tracking system [1], so that
this report does not get lost?
BTW: Please note that iss...@commons.apache.org is used only for
automatically generated mail notifications. The mailing list you should
use for postings like this is dev@commons.apache.org.
Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers, a CSV API looks incomplete to m
+1
On 6 March 2012 19:35, Dennis Lundberg wrote:
> +1
>
> On 2012-03-06 18:42, Emmanuel Bourg wrote:
>> Commons CSV is approaching a releasable state. Considering the general
>> interest in this component I think it's time to promote it to Commons
>> proper.
>>
>> There are a few points I'd like
On 6 March 2012 19:33, Gary Gregory wrote:
> What about passing in a "boolean strict" to the constructor of the codecs?
What does strict mean? See my comment:
https://issues.apache.org/jira/browse/CODEC-95#comment-12986951
If we do add another parameter (which is not popular with others), at
le
Le 06/03/2012 15:01, Ralph Goers a écrit :
> I don't recall if a board report is required or not, but I would send one
> even if it isn't required. Obviously, the Solr team doesn't understand what
> they have done. However, if Solr considers CSV "good enough" to use in their
> application then
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "LinearPackageInterfaceSimplification" page has been changed by
SebastienBrisard:
http://wiki.apache.org/commons/LinearPackageInterfaceSimplification
New page:
= Simplification of
+1
On 2012-03-06 18:42, Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers, a CSV A
What about passing in a "boolean strict" to the constructor of the codecs?
Gary
On Tue, Mar 6, 2012 at 2:07 PM, Julius Davies wrote:
> Hi,
>
>
> CODEC-95 talked about these issues, too (in this case with Base64).
>
> https://issues.apache.org/jira/browse/CODEC-95
>
>
> Personally, I would prefer
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MathWishList" page has been changed by SebastienBrisard:
http://wiki.apache.org/commons/MathWishList?action=diff&rev1=73&rev2=74
= Commons-Math Wish List =
A list of feature r
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MathWishList" page has been changed by SebastienBrisard:
http://wiki.apache.org/commons/MathWishList?action=diff&rev1=72&rev2=73
= Commons-Math Wish List =
A list of feature r
Hi,
CODEC-95 talked about these issues, too (in this case with Base64).
https://issues.apache.org/jira/browse/CODEC-95
Personally, I would prefer to see some new "strict" classes defined,
and to preserve the garbage-in/garbage-out behaviour on the current
existing classes.
Here are the new c
On 03/06/2012 06:42 PM, Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers, a CSV AP
+1
Unfortunately I cannot offer help, I am totally out of time
On Tue, Mar 6, 2012 at 6:42 PM, Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few poin
On Tue, Mar 6, 2012 at 7:42 PM, Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons
> proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers,
+1
On Mar 6, 2012, at 6:42 PM, Emmanuel Bourg wrote:
> Commons CSV is approaching a releasable state. Considering the general
> interest in this component I think it's time to promote it to Commons proper.
>
> There are a few points I'd like to address before a release:
> - Handle CSV headers,
I'm not an committer, but I've been monitoring the CSV project for a
couple of years and I'm really happy to see it trying to emerge from
the sandbox. If it does go to release, I will be dropping OpenCsv and
switching to it for my projects both personal and professional.
Please accept my virtual +
Commons CSV is approaching a releasable state. Considering the general
interest in this component I think it's time to promote it to Commons
proper.
There are a few points I'd like to address before a release:
- Handle CSV headers, a CSV API looks incomplete to me without this
- Examine the fea
On 6 March 2012 09:15, wrote:
> Author: simonetripodi
> Date: Tue Mar 6 09:15:10 2012
> New Revision: 1297393
>
> URL: http://svn.apache.org/viewvc?rev=1297393&view=rev
> Log:
> explicit use of the surefire-report plugin to aggregate test results
>
> Modified:
> commons/proper/chain/trunk/pom
On 6 March 2012 12:52, Gary Gregory wrote:
> On Mar 6, 2012, at 6:47, sebb wrote:
>
>> The errors are occuring because some testCases are leaving an item in
>> the registry.
>> If the next test is one that checks for an empty registry at the end,
>> it will fail.
>>
>> It's very easy to check tha
On 6 March 2012 14:33, Torsten Curdt wrote:
> Added my thought to this issue. MIght be better than here where they
> are not reading.
> Let's hope they come around.
I think we should consider changing the package name/Maven id for the
first official release of CSV.
This would force end-users (in
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 gene...@gump.apache.org.
Project commons-exec-test has an issue affecting its community integration.
This i
Added my thought to this issue. MIght be better than here where they
are not reading.
Let's hope they come around.
cheers,
Torsten
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-
I don't recall if a board report is required or not, but I would send one even
if it isn't required. Obviously, the Solr team doesn't understand what they
have done. However, if Solr considers CSV "good enough" to use in their
application then it is definitely time to do a release of CSV.
Ralp
The Solr team isn't listening, the issue was closed as "Won't Fix",
*sighs*...
https://issues.apache.org/jira/browse/SOLR-3204
Emmanuel Bourg
Le 06/03/2012 02:12, Emmanuel Bourg a écrit :
Hi,
This is actually a bad joke for all of us binary compatibility lovers. I
just noticed that Solr for
On Mar 6, 2012, at 6:47, sebb wrote:
> The errors are occuring because some testCases are leaving an item in
> the registry.
> If the next test is one that checks for an empty registry at the end,
> it will fail.
>
> It's very easy to check that the registry is always left empty by
> adding an @A
The errors are occuring because some testCases are leaving an item in
the registry.
If the next test is one that checks for an empty registry at the end,
it will fail.
It's very easy to check that the registry is always left empty by
adding an @After method - I tried this and the code then fails f
On Tue, Mar 06, 2012 at 12:15:20AM +0100, Emmanuel Bourg wrote:
> I ran Cobertura and uploaded the result here:
>
> http://people.apache.org/~ebourg/math/cobertura
>
> It took more than 4 hours to complete on my Core 2 Duo, ouch!
Thanks for the effort! :-)
> At the
> end JavaNCSS complained abo
Emmanuel Bourg wrote:
>Le 06/03/2012 10:26, ma...@apache.org a écrit :
>
>> The right way for solr to do this would be to package rename csv the
>same way Tomcat does for encode.
>
>Yes that's what I suggested. How do you do this in Tomcat? Did you copy
>
>and rename the packages manually, or do
Hi Emmanuel,
Emmanuel Bourg wrote:
> Le 06/03/2012 10:26, ma...@apache.org a écrit :
>
>> The right way for solr to do this would be to package rename csv the same
>> way Tomcat does for encode.
>
> Yes that's what I suggested. How do you do this in Tomcat? Did you copy
> and rename the package
Le 06/03/2012 10:26, ma...@apache.org a écrit :
The right way for solr to do this would be to package rename csv the same way
Tomcat does for encode.
Yes that's what I suggested. How do you do this in Tomcat? Did you copy
and rename the packages manually, or do you have a tool that automates
Hi Emmanuel,
Emmanuel Bourg wrote:
> Le 06/03/2012 08:52, Jörg Schaible a écrit :
>
>> All that we can do now is to put a big red warning at commons-cvs
>> homepage:
>>
>> == %< ==
>> CAUTION: If you use Apache Solr you run implicitly an incompatible
>> version of commons-csv th
ma...@apache.org wrote:
>Emmanuel Bourg wrote:
>
>>Le 06/03/2012 08:52, Jörg Schaible a écrit :
>>
>>> All that we can do now is to put a big red warning at commons-cvs
>>homepage:
>>>
>>> == %< ==
>>> CAUTION: If you use Apache Solr you run implicitly an incompatible
>>version
>
Emmanuel Bourg wrote:
>Le 06/03/2012 08:52, Jörg Schaible a écrit :
>
>> All that we can do now is to put a big red warning at commons-cvs
>homepage:
>>
>> == %< ==
>> CAUTION: If you use Apache Solr you run implicitly an incompatible
>version
>> of commons-csv that may affect yo
Emmanuel Bourg wrote:
>Hi,
>
>This is actually a bad joke for all of us binary compatibility lovers.
>I
>just noticed that Solr forked Commons CSV and released it as a separate
>
>artifact, but kept the org.apache.commons.csv package unchanged :(
>
>http://www.jarvana.com/jarvana/inspect/org/apa
Le 06/03/2012 08:52, Jörg Schaible a écrit :
All that we can do now is to put a big red warning at commons-cvs homepage:
== %< ==
CAUTION: If you use Apache Solr you run implicitly an incompatible version
of commons-csv that may affect your application. We have to refuse any he
Hi Yonik,
The issue is not the "fork", that's perfectly fine and your help is
really appreciated. The issue is that it was released without renaming
the package, leading to classpath conflicts when Commons CSV is released
officially.
I opened an issue for Solr:
https://issues.apache.org/jir
64 matches
Mail list logo
