Re: [cross-project-issues-dev] LSP4E: A Problem Waiting to Happen?

2019-12-08 Thread Eike Stepper 

Am 08.12.2019 um 13:17 schrieb Stephan Herrmann:

thanks for nagging :)

While we are at it, is anybody using validation from the aggregation editor??
Reason for asking: whenever I try that, it aborts with this message:

Unable to load repository 
https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository
Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/
Build failed! Exception was org.eclipse.core.runtime.CoreException: Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/

I use it with OpenJDK 1.8.0 and it validates without errors.

Cheers
/Eike


http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper



___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "The software you installed requires [...] nodejs >= 6"

2019-12-08 Thread Jonah Graham 
On Sun, 8 Dec 2019 at 14:05, Aleksandar Kurtakov 
wrote:

> On Sun, Dec 8, 2019 at 5:43 PM Jonah Graham 
> wrote:
>
>> Does anyone recognize the attached error message? It comes up whenever I
>> open the cdt.target file recently, but I haven't tracked down which project
>> contributes this.
>> Hey Jonah,
>>
> 1. Please file a bug against p2 to request that
> touchpoint.natives.checkAndPromptNativePackage has better message to make
> it clear which bundle requires it. Add me on CC this is a topic of interest
> for me so I'll try to find time for it.
>

Done. Bug 558006 


> 2. It reminds of smth we added in the Dockerfile ls based editor (
> https://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/commit/containers/org.eclipse.linuxtools.docker.editor.ls/META-INF/p2.inf?id=5fe85e48934bfd7ff0758af378e0565f21b052b4).
> So do you have nodejs installed? Or maybe nodejs package name is different
> under debian? If there is package with name nodejs name installed and it's
> version is greater than 6 it should be a bug in p2 touchpoint handling.
>

It is indeed the dockerfile ls editor's p2.inf that is doing it. I do have
node on my system, on my path, not from the nodejs package in Ubuntu 18.04
LTS because it is relatively old (v8) and I have many versions installed
and managed with my .bashrc setting the PATH. The language server
integration is working for Docker, so my user experience there is good.

HTH,
Jonah
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "The software you installed requires [...] nodejs >= 6"

2019-12-08 Thread Aleksandar Kurtakov 
On Sun, Dec 8, 2019 at 5:43 PM Jonah Graham  wrote:

> Hi folks,
>
> Does anyone recognize the attached error message? It comes up whenever I
> open the cdt.target file recently, but I haven't tracked down which project
> contributes this.
>
> Full message:
>
> -
> Install Native Software Packages
>
> The software you installed requires the following OS packages to be
> installed:
> nodejs >= 6
> nodejs >= 6
>
> You can install those by executing the following command:
>sudo apt-get install nodejs nodejs
> -
>
> I want to file an appropriate bug, but not sure who with.
>

Hey Jonah,
1. Please file a bug against p2 to request that
touchpoint.natives.checkAndPromptNativePackage has better message to make
it clear which bundle requires it. Add me on CC this is a topic of interest
for me so I'll try to find time for it.
2. It reminds of smth we added in the Dockerfile ls based editor (
https://git.eclipse.org/c/linuxtools/org.eclipse.linuxtools.git/commit/containers/org.eclipse.linuxtools.docker.editor.ls/META-INF/p2.inf?id=5fe85e48934bfd7ff0758af378e0565f21b052b4).
So do you have nodejs installed? Or maybe nodejs package name is different
under debian? If there is package with name nodejs name installed and it's
version is greater than 6 it should be a bug in p2 touchpoint handling.



>
> Jonah
>
>
>
> ~~~
> Jonah Graham
> Kichwa Coders
> www.kichwacoders.com
> ___
> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



-- 
Alexander Kurtakov
Red Hat Eclipse Team
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] "The software you installed requires [...] nodejs >= 6"

2019-12-08 Thread Ed Merks 

Jonah,

Yes, that drives me a bit crazy.   It doesn't just come up once but 
again and again. :-(


I assume it's coming from some LSP integration like was the case for 
this problem:


https://bugs.eclipse.org/bugs/show_bug.cgi?id=550163

But I *really *like using the generic editor editing HTML so I live with 
an annoyance for that case...


Regards,
Ed

On 08.12.2019 16:42, Jonah Graham wrote:

Hi folks,

Does anyone recognize the attached error message? It comes up whenever 
I open the cdt.target file recently, but I haven't tracked down which 
project contributes this.


Full message:

-
Install Native Software Packages

The software you installed requires the following OS packages to be 
installed:

nodejs >= 6
nodejs >= 6

You can install those by executing the following command:
   sudo apt-get install nodejs nodejs
-

I want to file an appropriate bug, but not sure who with.

Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com 

___
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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] LSP4E: A Problem Waiting to Happen?

2019-12-08 Thread Ed Merks 

Stephan,

Yes, this annoys me as well.  The problem goes away if I change the URI 
to http instead of https and it goes away if I create an installation 
that runs with Java 12 instead of Java 8...


So it appears to be an issue related to certificate handling versus the 
root certificates in the Java runtime.  Perhaps the root certificate of 
archive.eclipse.org is somehow different from the one for 
download.eclipse.org...  Just a theory...


Regards,
Ed


On 08.12.2019 13:17, Stephan Herrmann wrote:

thanks for nagging :)

While we are at it, is anybody using validation from the aggregation 
editor??

Reason for asking: whenever I try that, it aborts with this message:

Unable to load repository 
https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository 

Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/ 

Build failed! Exception was org.eclipse.core.runtime.CoreException: 
Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/ 




yes, my browser can see that repository. Is p2 not ready to read from 
archive.e.o? Is the repo broken by any terms?


anybody else seeing this?
Stephan 

___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] "The software you installed requires [...] nodejs >= 6"

2019-12-08 Thread Jonah Graham 
Hi folks,

Does anyone recognize the attached error message? It comes up whenever I
open the cdt.target file recently, but I haven't tracked down which project
contributes this.

Full message:

-
Install Native Software Packages

The software you installed requires the following OS packages to be
installed:
nodejs >= 6
nodejs >= 6

You can install those by executing the following command:
   sudo apt-get install nodejs nodejs
-

I want to file an appropriate bug, but not sure who with.

Jonah



~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] LSP4E: A Problem Waiting to Happen?

2019-12-08 Thread Ed Willink 

Hi

Yes I think I saw something similar a few weeks ago, when I needed to do 
a feature-affecting change for MoDisco.


But mostly I never use the aggregator tooling since it breaks EMF [1]

Once a tool has bitten you a few times, you remember to avoid it like 
the plague.


Usually my changes are for repo-name/feature range only and so are much 
better done with a text editor.


    Regards

        Ed Willink

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=527164

On 08/12/2019 12:17, Stephan Herrmann wrote:

thanks for nagging :)

While we are at it, is anybody using validation from the aggregation 
editor??

Reason for asking: whenever I try that, it aborts with this message:

Unable to load repository 
https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository
Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/
Build failed! Exception was org.eclipse.core.runtime.CoreException: 
Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/ 




yes, my browser can see that repository. Is p2 not ready to read from 
archive.e.o? Is the repo broken by any terms?


anybody else seeing this?
Stephan

On 08.12.19 10:23, Ed Merks wrote:

Hi,

It's me the nagger again. I know many of you are editing your 
*.aggrcon manually.  This is mildly annoying.  When I edit using the 
editor and save my changes, all the files being edited manually change.


I can and do revert all these, but it's annoying.

Unfortunately this approach also makes it easy (and likely) to 
overlook problems in the consistency of the overall simrel.aggr 
resource.


In addition, the recommended process for contributing is to point 
your contribution at a specific update site:


https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#The_best_format_and_process_for_contributing_to_Sim._Release 



When you don't do this, your contribution will potentially change 
dynamically, which might be convenient for you, but it is problematic 
from an overall consistency point of view.  It's also less than idea 
if your specific site updates its content dynamically...


Why do I harp about this?  I'm quite sure that lsp4e intends to 
contribute the 0.13.0 release for 2019-12:


https://projects.eclipse.org/projects/technology.lsp4e/releases/0.13.0

But look closely at what the editor tells us:


While the "dynamically changing" repo (I can only assume that this is 
the case) does contain version 1.30.0, this is *not *what's 
contributed to the the 2019-12 release train.  Somewhere (and I have 
no clue from where) the 0.12.0 version is found and that's what's on 
the train:


https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/releases/2019-12/http___download.eclipse.org_releases_2019-12_201912061000/org.eclipse.lsp4e_0.12.0.201909270706.html 



I'm quite sure this is not the intent so I've opened this Bugzilla:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=557998

Regards,
Ed


___
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://www.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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] LSP4E: A Problem Waiting to Happen?

2019-12-08 Thread Stephan Herrmann 

thanks for nagging :)

While we are at it, is anybody using validation from the aggregation editor??
Reason for asking: whenever I try that, it aborts with this message:

Unable to load repository 
https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository
Unable to load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/
Build failed! Exception was org.eclipse.core.runtime.CoreException: Unable to 
load repository 
p2:https://archive.eclipse.org/webtools/downloads/drops/R3.2/C3.2.0/I-C3.2.0-20100614204142/repository/



yes, my browser can see that repository. Is p2 not ready to read from 
archive.e.o? Is the repo broken by any terms?


anybody else seeing this?
Stephan

On 08.12.19 10:23, Ed Merks wrote:

Hi,

It's me the nagger again. I know many of you are editing your *.aggrcon 
manually.  This is mildly annoying.  When I edit using the editor and save my 
changes, all the files being edited manually change.


I can and do revert all these, but it's annoying.

Unfortunately this approach also makes it easy (and likely) to overlook problems 
in the consistency of the overall simrel.aggr resource.


In addition, the recommended process for contributing is to point your 
contribution at a specific update site:


https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#The_best_format_and_process_for_contributing_to_Sim._Release

When you don't do this, your contribution will potentially change dynamically, 
which might be convenient for you, but it is problematic from an overall 
consistency point of view.  It's also less than idea if your specific site 
updates its content dynamically...


Why do I harp about this?  I'm quite sure that lsp4e intends to contribute the 
0.13.0 release for 2019-12:


https://projects.eclipse.org/projects/technology.lsp4e/releases/0.13.0

But look closely at what the editor tells us:


While the "dynamically changing" repo (I can only assume that this is the case) 
does contain version 1.30.0, this is *not *what's contributed to the the 2019-12 
release train.  Somewhere (and I have no clue from where) the 0.12.0 version is 
found and that's what's on the train:


https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/releases/2019-12/http___download.eclipse.org_releases_2019-12_201912061000/org.eclipse.lsp4e_0.12.0.201909270706.html

I'm quite sure this is not the intent so I've opened this Bugzilla:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=557998

Regards,
Ed


___
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://www.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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] LSP4E: A Problem Waiting to Happen?

2019-12-08 Thread Ed Merks 

Hi,

It's me the nagger again. I know many of you are editing your *.aggrcon 
manually.  This is mildly annoying.  When I edit using the editor and 
save my changes, all the files being edited manually change.


I can and do revert all these, but it's annoying.

Unfortunately this approach also makes it easy (and likely) to overlook 
problems in the consistency of the overall simrel.aggr resource.


In addition, the recommended process for contributing is to point your 
contribution at a specific update site:


https://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build#The_best_format_and_process_for_contributing_to_Sim._Release

When you don't do this, your contribution will potentially change 
dynamically, which might be convenient for you, but it is problematic 
from an overall consistency point of view.  It's also less than idea if 
your specific site updates its content dynamically...


Why do I harp about this?  I'm quite sure that lsp4e intends to 
contribute the 0.13.0 release for 2019-12:


https://projects.eclipse.org/projects/technology.lsp4e/releases/0.13.0

But look closely at what the editor tells us:


While the "dynamically changing" repo (I can only assume that this is 
the case) does contain version 1.30.0, this is *not *what's contributed 
to the the 2019-12 release train.  Somewhere (and I have no clue from 
where) the 0.12.0 version is found and that's what's on the train:


https://download.eclipse.org/oomph/archive/reports/download.eclipse.org/releases/2019-12/http___download.eclipse.org_releases_2019-12_201912061000/org.eclipse.lsp4e_0.12.0.201909270706.html

I'm quite sure this is not the intent so I've opened this Bugzilla:

  https://bugs.eclipse.org/bugs/show_bug.cgi?id=557998

Regards,
Ed

___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev