Re: [cross-project-issues-dev] Statement of intent to move platform.ua to Lucene 6.1 for M4

[Marc-André Laperle]

Yes it's perfectly clear, thank you! So we will build the index with 4.7 for 
Oxygen simrel and users of Eclipse 4.6 installing our plugins will have an 
additional 1-2 secs delay.


Marc-Andre


From: cross-project-issues-dev-boun...@eclipse.org 
 on behalf of Sopot Cela 

Sent: Friday, November 18, 2016 8:36:10 AM
To: Cross project issues
Subject: Re: [cross-project-issues-dev] Statement of intent to move platform.ua 
to Lucene 6.1 for M4

Pre-built indexes with Lucene 3.5 (what Eclipse 4.6 has) will not be consumable 
with Eclipse 4.7 M4 and later. However the content will be promptly re-indexed 
by Lucene 6.1 on the first search so there will be no loss of search results. 
The only thing is the 1-2 seconds (reasonable time for reasonable indexes on my 
machine) you have to wait for the re-indexing to be performed only on first 
search. The procedure to provide a brand new pre-built index is exactly the 
same as before with the ant task, you just have to use a recent enough build to 
do the indexing. This is what is being used now to provide the PDE, JDT and 
Platform pre-built indexes as part of the normal build.

Eclipse 4.6 of course has Lucene 3.5 so that will not be able to read the new 
Lucene 6.1 indexes.

Is that clear enough? Feel free to get back to me if it's not.

Sopot

- Oorspronkelijk bericht -
> Van: "Marc-André Laperle" 
> Aan: cross-project-issues-dev@eclipse.org
> Verzonden: Vrijdag 18 november 2016 14:13:17
> Onderwerp: Re: [cross-project-issues-dev] Statement of intent to  move
> platform.ua to Lucene 6.1 for M4
>
>
>
> Hi Sopot ,
>
>
>
>
> If I understand correctly, the pre-built index is not forward (or backward)
> compatible? For example, if I build the index for a documentation plugin
> with Eclipse 4.6, the index won't work with Eclipse 4.7 and vice versa? In
> this case, for Oxygen, it's probably preferable to build indexes always with
> 4.7 even if a documentation plugin is intended to be also installed in
> Eclipse 4.6 (some projects many compatibility with some older Eclipse
> versions). Eclipse 4.6 users will get a performance hit but that should be
> the only consequence. Let me know if I misunderstood.
>
>
>
>
>
> Regards,
>
>
> Marc-Andre
>
> From: cross-project-issues-dev-boun...@eclipse.org
>  on behalf of Sopot Cela
> 
> Sent: Friday, November 18, 2016 6:36:17 AM
> To: cross-project-issues-dev@eclipse.org
> Subject: Re: [cross-project-issues-dev] Statement of intent to move
> platform.ua to Lucene 6.1 for M4
> Hello,
>
> As stated below, the code in platform.ua was moved to consume Lucene 6.1 API.
> See the closing comment
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=466829#c34 for a short
> summary.
>
> I urge the other projects to move to this newer Lucene also and I'm open to
> assist if there is any question or issue in doing so. Feel free to add me on
> CC on the respective bugs if assistance is needed.
>
> Best regards,
> Sopot
>
> - Oorspronkelijk bericht -
> > Van: "Sopot Cela" 
> > Aan: cross-project-issues-dev@eclipse.org
> > Verzonden: Woensdag 2 november 2016 16:39:39
> > Onderwerp: Statement of intent to move platform.ua to Lucene 6.1 for M4
> >
> > Hello,
> >
> > In bug 466829 I am targeting to move the code (all of it is in internal
> > packages) in platform.ua which presently uses Lucene 3.x to Lucene 6.1. The
> > CQs were filed and approved. The Orbit work is being handled in sync with
> > the code work. I'll update again here as progress is made.
> >
> > If your project makes use of Lucene please plan accordingly to update to
> > the
> > latest version for Oxygen.
> >
> > Please raise any concern/issue you might have with the move.
> >
> > Best regards,
> > Sopot
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Statement of intent to move platform.ua to Lucene 6.1 for M4

[Sopot Cela]

Pre-built indexes with Lucene 3.5 (what Eclipse 4.6 has) will not be consumable 
with Eclipse 4.7 M4 and later. However the content will be promptly re-indexed 
by Lucene 6.1 on the first search so there will be no loss of search results. 
The only thing is the 1-2 seconds (reasonable time for reasonable indexes on my 
machine) you have to wait for the re-indexing to be performed only on first 
search. The procedure to provide a brand new pre-built index is exactly the 
same as before with the ant task, you just have to use a recent enough build to 
do the indexing. This is what is being used now to provide the PDE, JDT and 
Platform pre-built indexes as part of the normal build.

Eclipse 4.6 of course has Lucene 3.5 so that will not be able to read the new 
Lucene 6.1 indexes.

Is that clear enough? Feel free to get back to me if it's not.

Sopot

- Oorspronkelijk bericht -
> Van: "Marc-André Laperle" 
> Aan: cross-project-issues-dev@eclipse.org
> Verzonden: Vrijdag 18 november 2016 14:13:17
> Onderwerp: Re: [cross-project-issues-dev] Statement of intent to  move
> platform.ua to Lucene 6.1 for M4
> 
> 
> 
> Hi Sopot ,
> 
> 
> 
> 
> If I understand correctly, the pre-built index is not forward (or backward)
> compatible? For example, if I build the index for a documentation plugin
> with Eclipse 4.6, the index won't work with Eclipse 4.7 and vice versa? In
> this case, for Oxygen, it's probably preferable to build indexes always with
> 4.7 even if a documentation plugin is intended to be also installed in
> Eclipse 4.6 (some projects many compatibility with some older Eclipse
> versions). Eclipse 4.6 users will get a performance hit but that should be
> the only consequence. Let me know if I misunderstood.
> 
> 
> 
> 
> 
> Regards,
> 
> 
> Marc-Andre
> 
> From: cross-project-issues-dev-boun...@eclipse.org
>  on behalf of Sopot Cela
> 
> Sent: Friday, November 18, 2016 6:36:17 AM
> To: cross-project-issues-dev@eclipse.org
> Subject: Re: [cross-project-issues-dev] Statement of intent to move
> platform.ua to Lucene 6.1 for M4
> Hello,
> 
> As stated below, the code in platform.ua was moved to consume Lucene 6.1 API.
> See the closing comment
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=466829#c34 for a short
> summary.
> 
> I urge the other projects to move to this newer Lucene also and I'm open to
> assist if there is any question or issue in doing so. Feel free to add me on
> CC on the respective bugs if assistance is needed.
> 
> Best regards,
> Sopot
> 
> - Oorspronkelijk bericht -
> > Van: "Sopot Cela" 
> > Aan: cross-project-issues-dev@eclipse.org
> > Verzonden: Woensdag 2 november 2016 16:39:39
> > Onderwerp: Statement of intent to move platform.ua to Lucene 6.1 for M4
> > 
> > Hello,
> > 
> > In bug 466829 I am targeting to move the code (all of it is in internal
> > packages) in platform.ua which presently uses Lucene 3.x to Lucene 6.1. The
> > CQs were filed and approved. The Orbit work is being handled in sync with
> > the code work. I'll update again here as progress is made.
> > 
> > If your project makes use of Lucene please plan accordingly to update to
> > the
> > latest version for Oxygen.
> > 
> > Please raise any concern/issue you might have with the move.
> > 
> > Best regards,
> > Sopot
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
> https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] setting mirror URL in the p2 repository

[Andreas Sewe]

Hi Lorenzo,

> as suggested here https://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL
> we set the mirror property in our artifacts.jar when releasing.
> 
> We do that by using org.eclipse.wtp.releng.tools.addRepoProperties
> as done in other projects, e.g., 
> https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/repositories/pom.xml
>
>  this has worked up to now, but after we moved to tycho 0.25, which
> also generates the .xml.xz zipped version, we noted that the mirror
> property is not set in the artifacts.xml.xz (but only in
> artifacts.jar).
> 
> Would mirroring still work?

No, if you follow our template (I wrote the Code Recommenders pom.xml)
then mirroring will not work when the client downloads the
artifacts.xml.xz. This is Code Recommenders' Bug 497546 [1].

Now, for us fixing this has rather low priority, as not many people
download Code Recommenders from its update site, now that it is included
out-of-the-box in many EPP packages. But your mileage may vary, of course.

For you I see 3 ways out:

1. Disable XZ compresison in the tycho-p2-repository-plugin and compress
in a separate step, after the tycho-eclipserun-plugin with
rg.eclipse.wtp.releng.tools.addRepoProperties has finished. Maybe the
truezip-maven-plugin [3] or a similar plugin can help here.

2. Push for Tycho Bug 341744 [4] being fixed in such a way that it does
not only support p2.statsURI but also p2.mirrorsURL.

3. Do not set the p2.mirrorsURL in the Tycho build at all, but only when
promoting it to its final resting place. See Bug 498360 [5].

Option 1 certainly requires the most work, but has the advantage that it
just might work right *now*. In the long run, however, I think option 3
is preferable. The build should *not* need to know where the repository
bits will be offered for download, in particular as this may change over
time, e.g., if you move things from download.eclipse.org to
archive.eclipse.org.

Hope that helps.

Andreas

[1] 
[2]

[3] 
[4] 
[5] 

-- 
Codetrails GmbH
The knowledge transfer company

Robert-Bosch-Str. 7, 64293 Darmstadt
Phone: +49-6151-276-7092
Mobile: +49-170-811-3791
http://www.codetrails.com/

Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940



signature.asc
Description: OpenPGP digital signature
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Statement of intent to move platform.ua to Lucene 6.1 for M4

[Marc-André Laperle]

Hi Sopot,


If I understand correctly, the pre-built index is not forward (or backward) 
compatible? For example, if I build the index for a documentation plugin with 
Eclipse 4.6, the index won't work with Eclipse 4.7 and vice versa? In this 
case, for Oxygen, it's probably preferable to build indexes always with 4.7 
even if a documentation plugin is intended to be also installed in Eclipse 4.6 
(some projects many compatibility with some older Eclipse versions). Eclipse 
4.6 users will get a performance hit but that should be the only consequence. 
Let me know if I misunderstood.


Regards,

Marc-Andre


From: cross-project-issues-dev-boun...@eclipse.org 
 on behalf of Sopot Cela 

Sent: Friday, November 18, 2016 6:36:17 AM
To: cross-project-issues-dev@eclipse.org
Subject: Re: [cross-project-issues-dev] Statement of intent to move platform.ua 
to Lucene 6.1 for M4

Hello,

As stated below, the code in platform.ua was moved to consume Lucene 6.1 API. 
See the closing comment 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466829#c34 for a short summary.

I urge the other projects to move to this newer Lucene also and I'm open to 
assist if there is any question or issue in doing so. Feel free to add me on CC 
on the respective bugs if assistance is needed.

Best regards,
Sopot

- Oorspronkelijk bericht -
> Van: "Sopot Cela" 
> Aan: cross-project-issues-dev@eclipse.org
> Verzonden: Woensdag 2 november 2016 16:39:39
> Onderwerp: Statement of intent to move platform.ua to Lucene 6.1 for M4
>
> Hello,
>
> In bug 466829 I am targeting to move the code (all of it is in internal
> packages) in platform.ua which presently uses Lucene 3.x to Lucene 6.1. The
> CQs were filed and approved. The Orbit work is being handled in sync with
> the code work. I'll update again here as progress is made.
>
> If your project makes use of Lucene please plan accordingly to update to the
> latest version for Oxygen.
>
> Please raise any concern/issue you might have with the move.
>
> Best regards,
> Sopot
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] setting mirror URL in the p2 repository

[Lorenzo Bettini]

Hi

as suggested here https://wiki.eclipse.org/Equinox/p2/p2.mirrorsURL we
set the mirror property in our artifacts.jar when releasing.

We do that by using org.eclipse.wtp.releng.tools.addRepoProperties as
done in other projects, e.g.,
https://git.eclipse.org/c/recommenders/org.eclipse.recommenders.git/tree/repositories/pom.xml

this has worked up to now, but after we moved to tycho 0.25, which also
generates the .xml.xz zipped version, we noted that the mirror property
is not set in the artifacts.xml.xz (but only in artifacts.jar).

Would mirroring still work?

If not, has anyone noticed this behavior?

thanks in advance
Lorenzo

-- 
Prof. Lorenzo Bettini, Computer Science, DISIA, Univ. Firenze
HOME: http://www.lorenzobettini.it
Xtext Book:
https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Statement of intent to move platform.ua to Lucene 6.1 for M4

[Sopot Cela]

Hello,

As stated below, the code in platform.ua was moved to consume Lucene 6.1 API. 
See the closing comment 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=466829#c34 for a short summary.

I urge the other projects to move to this newer Lucene also and I'm open to 
assist if there is any question or issue in doing so. Feel free to add me on CC 
on the respective bugs if assistance is needed.

Best regards,
Sopot

- Oorspronkelijk bericht -
> Van: "Sopot Cela" 
> Aan: cross-project-issues-dev@eclipse.org
> Verzonden: Woensdag 2 november 2016 16:39:39
> Onderwerp: Statement of intent to move platform.ua to Lucene 6.1 for M4
> 
> Hello,
> 
> In bug 466829 I am targeting to move the code (all of it is in internal
> packages) in platform.ua which presently uses Lucene 3.x to Lucene 6.1. The
> CQs were filed and approved. The Orbit work is being handled in sync with
> the code work. I'll update again here as progress is made.
> 
> If your project makes use of Lucene please plan accordingly to update to the
> latest version for Oxygen.
> 
> Please raise any concern/issue you might have with the move.
> 
> Best regards,
> Sopot
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] just a FYI - macOS Sierra causes issues

[Martin Lippert]

Hey!

Just FYI, I investigated an issue with macOS Sierra that affects all Eclipse 
packages. I am posting this here since I think this could affect potentially 
many users:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=507328

The bottom line is:
If you download Eclipse, extract the file, and start Eclipse.app on macOS 
Sierra without moving it to a different location, all your additional plugin 
installs and global settings will be lost each time you restart your machine 
(or more frequently).

The reason:
macOS Sierra Gatekeeper Path Randomization happens and moves the app bundle to 
a read-only private folder on your disc. This happens after every restart to a 
new randomized location. The launcher has therefore no idea how to find the old 
config area and creates a new one.

The workaround:
Move the Eclipse.app after extracting it to a different location on disc (using 
the Finder) or start the executable inside instead of the .app bundle.
(others mentioned in the bug)
Maybe this should be mentioned in the n&n doc, release notes, or FAQ.

Possible solution:
Create a signed DMG that forces people to move the app after opening the DMG.

Cheers,
-Martin



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Part of the websites down?

[Daniel Megert]

I also had trouble, but seems to be back now.

Dani



From:   Laurent Goubet 
To: Cross project issues 
Date:   18.11.2016 09:16
Subject:[cross-project-issues-dev] Part of the websites down?
Sent by:cross-project-issues-dev-boun...@eclipse.org



projects [1], hudson [2] and wiki [3] are all failing saying that "Oops, 
something went wrong and we're completely broken down." Anything currently 
ongoing on these services?
[1] http://projects.eclipse.org/
[2] https://hudson.eclipse.org/
[3] https://wiki.eclipse.org/

-- 
Laurent Goubet
Consultant
+33 2 51 13 51 42

7 Boulevard Ampère - Carquefou - France 
obeo.fr | twitter | linkedin[attachment "logo_obeo.png" deleted by Daniel 
Megert/Zurich/IBM] [attachment "laurent_goubet.vcf" deleted by Daniel 
Megert/Zurich/IBM] ___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe 
from this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Part of the websites down?

[Laurent Goubet]

projects [1], hudson [2] and wiki [3] are all failing saying that "Oops, 
something went wrong and we're completely broken down." Anything 
currently ongoing on these services?


[1] http://projects.eclipse.org/

[2] https://hudson.eclipse.org/

[3] https://wiki.eclipse.org/


--

*Laurent Goubet*
Consultant
+33 2 51 13 51 42



7 Boulevard Ampère - Carquefou - France
*obeo.fr*  | *twitter* 
 | *linkedin* 



<>___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev