Re: Maven Indexer Changes

[Olivier Lamy]

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 do more. Here is a
> branch I did today:
> https://github.com/cstamas/maven-indexer/commits/fixes
>
> Basically, it has following changes:
> * Removed heavy uses of StringBuffer, replaced with StringBuilder
> * Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
> introduces API breakage (especially how you "acquire" IndexSearcher from
> context, needed to properly implement locking semantics)
> * Removed bottle warmer threads completely
> * Removed problematic locking around contexts as we rely now on Lucene
> * Using new SearcherManager (see
>
> http://blog.mikemccandless.com/2011/09/lucenes-searchermanager-simplifies.html
> )
> instead of doing all this manually + relying on those removed stuff above
> * Removed deprecated baggage
>
> Changes above renders issues MINDEXER-52 and alike actually a "non-issues".
>
>
> Please comment the changes.
>
>
>
> Thanks,
> ~t~
>

Re: Maven Indexer Changes

[Robert Scholte]

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û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 do more. Here  
is a

branch I did today:
https://github.com/cstamas/maven-indexer/commits/fixes

Basically, it has following changes:
* Removed heavy uses of StringBuffer, replaced with StringBuilder
* Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
introduces API breakage (especially how you "acquire" IndexSearcher from
context, needed to properly implement locking semantics)
* Removed bottle warmer threads completely
* Removed problematic locking around contexts as we rely now on Lucene
* Using new SearcherManager (see

http://blog.mikemccandless.com/2011/09/lucenes-searchermanager-simplifies.html
)
instead of doing all this manually + relying on those removed stuff  
above

* Removed deprecated baggage

Changes above renders issues MINDEXER-52 and alike actually a  
"non-issues".



Please comment the changes.



Thanks,
~t~


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Indexer Changes

[Tamás Cservenák]

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 700 BC according to
wikipedia) -- to roughly 233 years. So, in case you wear spectacles, would
you wear these today http://www.sptddog.com/sotp/18thcent.jpg ?


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.


Thanks,
~t~

On Wed, Aug 8, 2012 at 7:24 PM, Robert Scholte  wrote:

> 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û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 do more. Here is
>>> a
>>> branch I did today:
>>> https://github.com/cstamas/**maven-indexer/commits/fixes
>>>
>>> Basically, it has following changes:
>>> * Removed heavy uses of StringBuffer, replaced with StringBuilder
>>> * Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
>>> introduces API breakage (especially how you "acquire" IndexSearcher from
>>> context, needed to properly implement locking semantics)
>>> * Removed bottle warmer threads completely
>>> * Removed problematic locking around contexts as we rely now on Lucene
>>> * Using new SearcherManager (see
>>>
>>> http://blog.mikemccandless.**com/2011/09/lucenes-**
>>> searchermanager-simplifies.**html
>>> )
>>> instead of doing all this manually + relying on those removed stuff above
>>> * Removed deprecated baggage
>>>
>>> Changes above renders issues MINDEXER-52 and alike actually a
>>> "non-issues".
>>>
>>>
>>> Please comment the changes.
>>>
>>>
>>>
>>> Thanks,
>>> ~t~
>>>
>>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@maven.apache.**org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Maven Indexer Changes

[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 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 related to the version used by Maven,  
although some think they should use the same JDK.


JDK5's EOL was april 2008, I'm pretty sure Maven started requiring JDK5 a  
lot of months (years?) after this date.


Some time we should move to JDK6, but I don't think that time has come yet.

Robert

Op Wed, 08 Aug 2012 21:43:24 +0200 schreef Tamás Cservenák  
:



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 700 BC according to
wikipedia) -- to roughly 233 years. So, in case you wear spectacles,  
would

you wear these today http://www.sptddog.com/sotp/18thcent.jpg ?


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.


Thanks,
~t~

On Wed, Aug 8, 2012 at 7:24 PM, Robert Scholte   
wrote:



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û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 do more. Here  
is

a
branch I did today:
https://github.com/cstamas/**maven-indexer/commits/fixes

Basically, it has following changes:
* Removed heavy uses of StringBuffer, replaced with StringBuilder
* Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
introduces API breakage (especially how you "acquire" IndexSearcher  
from

context, needed to properly implement locking semantics)
* Removed bottle warmer threads completely
* Removed problematic locking around contexts as we rely now on Lucene
* Using new SearcherManager (see

http://blog.mikemccandless.**com/2011/09/lucenes-**
searchermanager-simplifies.**html
)
instead of doing all this manually + relying on those removed stuff  
above

* Removed deprecated baggage

Changes above renders issues MINDEXER-52 and alike actually a
"non-issues".


Please comment the changes.



Thanks,
~t~




--**--**-
To unsubscribe, e-mail:  
dev-unsubscribe@maven.apache.**org

For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Surefire Plugin version 2.12.2

[Olivier Lamy]

+1

2012/8/7 Kristian Rosenvold :
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18712&styleName=Text&projectId=10541
>
> A couple of improvements worth noting:
>
> Of general interest is the fix of
> http://jira.codehaus.org/browse/SUREFIRE-894, which should be able to
> save a little build time for users of
> forkmode="once" in multimodule builds. Users with multiple
> surefire/failsafe executions in forkMode once may experience notable
> gains.
>
> http://jira.codehaus.org/browse/SUREFIRE-887 is also interesting, you
> may want to read the closing comments on that issue.
>
> We have added maven 2.2.1 runs to jenkins. Although a few IT's are
> still not green, I have individually verified that this are IT's that
> rely on m3's higher precision in
> pom evalutation/execution, so we need to find some way to ignore these
> tests for 2.2.1; I do not consider this a problem.
>
>
> There are still lots of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQuery=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-122/
>
>  Staging site: (Sync pending)
>  http://maven.apache.org/surefire/staging/ (Links to sub-sites work
>  when transfered to production)
>
>  http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.2/
>  http://maven.apache.org/plugins/maven-surefire-plugin-2.12.2/
>  http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.2/
>
> Guide to testing staged releases:
>
> http://maven.apache.org/guides/development/guide-testing-releases.html
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> And here's my +1
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Relase Apache Parent Pom 11

[Olivier Lamy]

My +1

2012/8/5 Olivier Lamy :
> Hi,
> I'd like to release Apache Parent 11.
> Staging repository is here:
> https://repository.apache.org/content/repositories/orgapacheapache-120/
> Staged documentation: http://maven.apache.org/pom/asf-11/
>
> Diff from previous release:
> http://svn.apache.org/viewvc/maven/pom/tags/apache-11/pom.xml?r1=HEAD&r2=1154610&diff_format=h
>
> Vote open for 72H.
>
> [+1]
> [0]
> [-1]
>
> Thanks
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT][VOTE] Relase Apache Parent Pom 11

[Olivier Lamy]

Hi,
The vote has passed with the following result:
+1 (binding): Hervé Boutemy, Kristian Rosenvold, Stephen Connolly,
Vincent Siveton, Wayne Fay, Olivier Lamy
+1 (non binding): Tony Chemit

I will continue the release process.

-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Release request for maven-installer-plugin

[Felix Mayerhuber]

Hi,

I don't want to seem unpolite, but I write again since I got no response 
and thought the mail got maybe lost. Is there a release for the maven 
installer plugin in the near future planned?


Kind regards,
Felix

Am 2012-08-01 09:47, schrieb Felix Mayerhuber:

Hi @all,

I hope I'm in the correct list for this question. When is the release of
the maven installer plugin version 2.4 planned? I would need at least
the fix for MINSTALL-73.

Kind regards,
Felix







-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Indexer Changes

[Olivier Lamy]

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 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 related to the version used by Maven,
> although some think they should use the same JDK.
>
> JDK5's EOL was april 2008, I'm pretty sure Maven started requiring JDK5 a
> lot of months (years?) after this date.
>
> Some time we should move to JDK6, but I don't think that time has come yet.
>
> Robert
>
> Op Wed, 08 Aug 2012 21:43:24 +0200 schreef Tamás Cservenák
> :
>
>
>> 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 700 BC according to
>> wikipedia) -- to roughly 233 years. So, in case you wear spectacles, would
>> you wear these today http://www.sptddog.com/sotp/18thcent.jpg ?
>>
>>
>> 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.
>>
>>
>> Thanks,
>> ~t~
>>
>> On Wed, Aug 8, 2012 at 7:24 PM, Robert Scholte 
>> wrote:
>>
>>> 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û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 do more. Here
> is
> a
> branch I did today:
>
> https://github.com/cstamas/**maven-indexer/commits/fixes
>
> Basically, it has following changes:
> * Removed heavy uses of StringBuffer, replaced with StringBuilder
> * Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
> introduces API breakage (especially how you "acquire" IndexSearcher
> from
> context, needed to properly implement locking semantics)
> * Removed bottle warmer threads completely
> * Removed problematic locking around contexts as we rely now on Lucene
> * Using new SearcherManager (see
>
> http://blog.mikemccandless.**com/2011/09/lucenes-**
>
> searchermanager-simplifies.**html
> )
> instead of doing all this manually + relying on those removed stuff
> above
> * Removed deprecated baggage
>
> Changes above renders issues MINDEXER-52 and alike actually a
> "non-issues".
>
>
> Please comment the changes.
>
>
>
> Thanks,
> ~t~
>

>>> --**--**-
>>> To unsubscribe, e-mail:
>>> dev-unsubscribe@maven.apache.**org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Indexer Changes

[Mark Derricutt]

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.

Re: [VOTE] Release Maven Surefire Plugin version 2.12.2

[Hervé BOUTEMY]

+1

Hervé

Le mardi 7 août 2012 03:03:18 Kristian Rosenvold a écrit :
> Hi,
> 
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18712&styleName=Tex
> t&projectId=10541
> 
> A couple of improvements worth noting:
> 
> Of general interest is the fix of
> http://jira.codehaus.org/browse/SUREFIRE-894, which should be able to
> save a little build time for users of
> forkmode="once" in multimodule builds. Users with multiple
> surefire/failsafe executions in forkMode once may experience notable
> gains.
> 
> http://jira.codehaus.org/browse/SUREFIRE-887 is also interesting, you
> may want to read the closing comments on that issue.
> 
> We have added maven 2.2.1 runs to jenkins. Although a few IT's are
> still not green, I have individually verified that this are IT's that
> rely on m3's higher precision in
> pom evalutation/execution, so we need to find some way to ignore these
> tests for 2.2.1; I do not consider this a problem.
> 
> 
> There are still lots of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jql
> Query=project+%3D+SUREFIRE+AND+resolution+%3D+Unresolved+ORDER+BY+updated+DE
> SC
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-122/
> 
>  Staging site: (Sync pending)
>  http://maven.apache.org/surefire/staging/ (Links to sub-sites work
>  when transfered to production)
> 
>  http://maven.apache.org/plugins/maven-failsafe-plugin-2.12.2/
>  http://maven.apache.org/plugins/maven-surefire-plugin-2.12.2/
>  http://maven.apache.org/plugins/maven-surefire-reports-plugin-2.12.2/
> 
> Guide to testing staged releases:
> 
> http://maven.apache.org/guides/development/guide-testing-releases.html
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 
> And here's my +1
> 
> Kristian
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

svnpubsub and rewrite rule

[Hervé BOUTEMY]

I need help.

In order to provide instructions [1] to publish release documentation with 
svnpubsub, I'm trying to use httpd rewrite rule instead of svn symlink, since 
it should be easier to maintain.

I'm trying to write a sample rule [2] to have latest clean plugin release [3] 
accessible as default [4].
But for the moment, it does not work, I get a 404.

Is there a rewrite rule master out here who could make this work?

Regards,

Hervé


[1] http://maventest.apache.org/developers/release/maven-plugin-release.html

[2] http://svn.apache.org/viewvc?rev=1370574&view=rev

[3] http://maventest.apache.org/plugins/maven-clean-plugin-2.5/

[4] http://maventest.apache.org/plugins/maven-clean-plugin/

Re: Maven Indexer Changes

[Markku Saarela]

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 
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 related to the version used by Maven, 
although some think they should use the same JDK.


JDK5's EOL was april 2008, I'm pretty sure Maven started requiring 
JDK5 a lot of months (years?) after this date.


Some time we should move to JDK6, but I don't think that time has come 
yet.


Robert

Op Wed, 08 Aug 2012 21:43:24 +0200 schreef Tamás Cservenák 
:



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 700 BC according to
wikipedia) -- to roughly 233 years. So, in case you wear spectacles, 
would

you wear these today http://www.sptddog.com/sotp/18thcent.jpg ?


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.


Thanks,
~t~

On Wed, Aug 8, 2012 at 7:24 PM, Robert Scholte  
wrote:



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û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 do more. 
Here is

a
branch I did today:
https://github.com/cstamas/**maven-indexer/commits/fixes 



Basically, it has following changes:
* Removed heavy uses of StringBuffer, replaced with StringBuilder
* Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
introduces API breakage (especially how you "acquire" 
IndexSearcher from

context, needed to properly implement locking semantics)
* Removed bottle warmer threads completely
* Removed problematic locking around contexts as we rely now on 
Lucene

* Using new SearcherManager (see

http://blog.mikemccandless.**com/2011/09/lucenes-**
searchermanager-simplifies.**html 


)
instead of doing all this manually + relying on those removed 
stuff above

* Removed deprecated baggage

Changes above renders issues MINDEXER-52 and alike actually a
"non-issues".


Please comment the changes.



Thanks,
~t~



--**--**- 

To unsubscribe, e-mail: 
dev-unsubscribe@maven.apache.**org

For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Indexer Changes

[Brett Porter]

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 to -- for
> example in optics (first known lenses are about 700 BC according to
> wikipedia) -- to roughly 233 years. So, in case you wear spectacles, would
> you wear these today http://www.sptddog.com/sotp/18thcent.jpg ?

LOL.

> 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.

I don't have a problem with updating it if there's something useful to take 
advantage of, knowing the user-base of the library. In other libraries, we 
don't need to upgrade just for the sake of it, of course.

Perhaps with this requirement, and the API breakage you indicated, the version 
could bump to 5.0.0-SNAPSHOT? I like the semantic versioning rules (semver.org).

- Brett

--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven Indexer Changes

[Chris Graham]

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  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 to -- for
> example in optics (first known lenses are about 700 BC according to
> wikipedia) -- to roughly 233 years. So, in case you wear spectacles, would
> you wear these today http://www.sptddog.com/sotp/18thcent.jpg ?
> 
> 
> 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.
> 
> 
> Thanks,
> ~t~
> 
> On Wed, Aug 8, 2012 at 7:24 PM, Robert Scholte  wrote:
> 
>> 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û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 do more. Here is
 a
 branch I did today:
 https://github.com/cstamas/**maven-indexer/commits/fixes
 
 Basically, it has following changes:
 * Removed heavy uses of StringBuffer, replaced with StringBuilder
 * Version bumped to 4.5.0-SNAP (from 4.1.4-SNAP) as changes below
 introduces API breakage (especially how you "acquire" IndexSearcher from
 context, needed to properly implement locking semantics)
 * Removed bottle warmer threads completely
 * Removed problematic locking around contexts as we rely now on Lucene
 * Using new SearcherManager (see
 
 http://blog.mikemccandless.**com/2011/09/lucenes-**
 searchermanager-simplifies.**html
 )
 instead of doing all this manually + relying on those removed stuff above
 * Removed deprecated baggage
 
 Changes above renders issues MINDEXER-52 and alike actually a
 "non-issues".
 
 
 Please comment the changes.
 
 
 
 Thanks,
 ~t~
 
>>> 
>> --**--**-
>> To unsubscribe, e-mail: 
>> dev-unsubscribe@maven.apache.**org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>> 
>> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org