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
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
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
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
Yonik Seeley wrote:
> Not sure I understand the use of "forked" here.
>
> Solr needed CSV handing. Rather than just roll our own, I looked at
> commons-csv and put a *lot* of time and effort into improving it. I
> didn't have time to follow through with a complete release of
> commons-csv, so w
Not sure I understand the use of "forked" here.
Solr needed CSV handing. Rather than just roll our own, I looked at
commons-csv and put a *lot* of time and effort into improving it. I
didn't have time to follow through with a complete release of
commons-csv, so we just included a snapsot in Solr
On 6 March 2012 01:50, sebb wrote:
> On 6 March 2012 01:12, 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 packa
Le 06/03/2012 02:50, sebb a écrit :
Are you sure?
I think so, but I wish I'm wrong. Look into the jar, the package is
org.apache.commons.csv and the pom.xml file included in META-INF is
exactly the one of Commons CSV, the groupId/artifactId isn't even changed.
http://repo1.maven.org/maven2
On 6 March 2012 01:12, 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 :(
Are you sure?
Maven Centr
The only thing to do is to release [csv] out of the sandbox, when ready,
and let Solr clean up its own mess.
Gary
On Mon, Mar 5, 2012 at 8:23 PM, James Carman
wrote:
> This is very bothersome, with all the trouble we go through to maintain
> compatibility. Frustrating indeed.
> On Mar 5, 2012 8
This is very bothersome, with all the trouble we go through to maintain
compatibility. Frustrating indeed.
On Mar 5, 2012 8:13 PM, "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 i
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/apache/solr/solr-commons-csv/3.5.0
22 matches
Mail list logo
