On Thu, Aug 9, 2012 at 2:33 AM, Brett Porter wrote:
>
> On 09/08/2012, at 5:43 AM, Tamás Cservenák wrote:
>
>
>> In essence: not really needed for now, as Lucene 3.6.1 is fine on Java5,
>> and IOEx new constructor is used in very few places but we can go back
>> in time for 233 years for now.
Brett and others,
I rolled back MI to Java5, but I agree, due to API breakage I did bump the
version to 5.0.0-SNAPSHOT.
https://github.com/cstamas/maven-indexer/commits/fixes
As for "consumer" side code, few examples:
Maven Indexer Examples updated to represent needed changes (commented on
API
Ok. As I said, java6 is not a must. Will be undone and merge prepared.
Thanks,
~t~ mobile
On Aug 9, 2012 4:14 AM, "Chris Graham" wrote:
> Whilst Java6 may be soon coming to EOL, I am still supporting many large
> corporates on Java 1.4 - corporates do not necessarily move quickly - not
> if thei
Whilst Java6 may be soon coming to EOL, I am still supporting many large
corporates on Java 1.4 - corporates do not necessarily move quickly - not if
their solution works.
Just something to consider from the real world.
-Chris
Sent from my iPhone
On 09/08/2012, at 1:13 AM, Tamás Cservenák wr
On 09/08/2012, at 5:43 AM, Tamás Cservenák wrote:
> In short: Java6 EOL is coming in months now, users running 1.5 and below
> should really consider an upgrade.
> A bit longer: Java6 1st release happened in 2006, 6 years ago. In our
> profession, that is around 70 years old, 6 years corresponds
HI,
JDK6's EOL is Feb 2013
(http://www.oracle.com/technetwork/java/eol-135779.html), so it's near.
Markku
On 8.8.2012 23:46, Robert Scholte wrote:
In theory you're right about the timing, but the facts are different.
It seems like the larger the company, the slower the time. I've seen
compa
For what its worth, Java 6's EOL just got pushed out till Feb 2013:
https://blogs.oracle.com/henrik/entry/java_6_eol_h_h
Mark
On 9/08/2012, at 7:43 AM, Tamás Cservenák wrote:
> In short: Java6 EOL is coming in months now, users running 1.5 and below
> should really consider an upgrade.
Perso, in 2012 I don't see any issue being 1.6 required.
Especially for a component which is not used in core neither in any plugin.
2012/8/8 Robert Scholte :
> In theory you're right about the timing, but the facts are different. It
> seems like the larger the company, the slower the time. I've s
In theory you're right about the timing, but the facts are different. It
seems like the larger the company, the slower the time. I've seen
companies still using jdk1.4 because they had a lot of trouble to upgrade
to a newer version of an application server.
The version of this JDK is not rela
In short: Java6 EOL is coming in months now, users running 1.5 and below
should really consider an upgrade.
A bit longer: Java6 1st release happened in 2006, 6 years ago. In our
profession, that is around 70 years old, 6 years corresponds to -- for
example in optics (first known lenses are about 70
What's the reason for the "Bumped MI to Java6 level."?
Looks like a potential issue to me (assuming a lot of projects still use
java5)
-Robert
Op Wed, 08 Aug 2012 18:29:41 +0200 schreef Olivier Lamy :
Nice changes.
+1 to merge that.
Maybe some jiras entries to create :-)
--
Olivier
Le 7 ao
Nice changes.
+1 to merge that.
Maybe some jiras entries to create :-)
--
Olivier
Le 7 août 2012 23:21, "Tamás Cservenák" a écrit :
> Hi there,
>
> Olivier did a great job of releasing Maven Indexer 4.1.3 that bumped Lucene
> to 3.6.1.
>
> But, having Lucene 3.6.1 in MI makes us now possible to
It's something not needed when you are breastfeeding :p
Thanks,
~t~ mobile
On Aug 8, 2012 8:07 AM, "Kristian Rosenvold"
wrote:
> Exactly what is a "Bottle warmer thread" ?? I think I want one too ;)
>
> Kristian
>
>
> 2012/8/7 Tamás Cservenák :
> > Hi there,
> >
> > Olivier did a great job of re
Exactly what is a "Bottle warmer thread" ?? I think I want one too ;)
Kristian
2012/8/7 Tamás Cservenák :
> Hi there,
>
> Olivier did a great job of releasing Maven Indexer 4.1.3 that bumped Lucene
> to 3.6.1.
>
> But, having Lucene 3.6.1 in MI makes us now possible to do more. Here is a
> branc
Hi there,
Olivier did a great job of releasing Maven Indexer 4.1.3 that bumped Lucene
to 3.6.1.
But, having Lucene 3.6.1 in MI makes us now possible to do more. Here is a
branch I did today:
https://github.com/cstamas/maven-indexer/commits/fixes
Basically, it has following changes:
* Removed hea
15 matches
Mail list logo
