[linuxtools-dev] Linuxtools docker nightly MD5 failures (was Fwd: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14)
Hi Linuxtools folks, Can someone in your area have a look at a CDT build failure I am having. I can reproduce this failure on my machine. CDT has lots of builds failing due to this issue. Thanks, Jonah ~~~ Jonah Graham Kichwa Coders Ltd. www.kichwacoders.com -- Forwarded message -- From: Date: 21 March 2018 at 01:03 Subject: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14 To: jo...@kichwacoders.com, marc.dum...@ericsson.com See <https://ci.eclipse.org/cdt/job/debug-remote-tests-master-gdb-8.1/14/display/redirect> -- [...truncated 448.20 KB...] [INFO] Computing target platform for MavenProject: org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml [INFO] Resolving dependencies of MavenProject: org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml [INFO] Resolving class path of MavenProject: org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml [INFO] Computing target platform for MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties [INFO] Resolving dependencies of MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties [INFO] Resolving class path of MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties [INFO] Computing target platform for MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties [INFO] Resolving dependencies of MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties [INFO] Resolving class path of MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties [INFO] Computing target platform for MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui:1.1.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/.polyglot.build.properties [INFO] Resolving dependencies of MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui:1.1.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/.polyglot.build.properties [INFO] Resolving class path of MavenProject: org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui:1.1.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/.polyglot.build.properties [INFO] Computing target platform for MavenProject: org.eclipse.cdt:org.eclipse.cdt.gnu.dsf:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.dsf-feature/.polyglot.build.properties [INFO] Resolving dependencies of MavenProject: org.eclipse.cdt:org.eclipse.cdt.gnu.dsf:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.dsf-feature/.polyglot.build.properties [INFO] Resolving class path of MavenProject: org.eclipse.cdt:org.eclipse.cdt.gnu.dsf:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.dsf-feature/.polyglot.build.properties [INFO] Computing target platform for MavenProject: org.eclipse.cdt:org.eclipse.cdt.gnu.multicorevisualizer:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.multicorevisualizer-feature/.polyglot.build.properties [INFO] Resolving dependencies of MavenProject: org.eclipse.cdt:org.eclipse.cdt.gnu.multicorevisualizer:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.multicorevisualizer-feature/.polyglot.build.properties [INFO] Resolving class path of MavenProject: org.eclipse.cdt:org.eclipse.cdt.gnu.multicorevisualizer:9.5.0-SNAPSHOT @ /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.multicorevisualizer-feature/.polyglot.build.properties [INFO] Com
Re: [linuxtools-dev] Linuxtools docker nightly MD5 failures (was Fwd: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14)
I have had a quick look, and both linuxtools-sonar and linuxtools-master jobs copy to the same location. Both builds ran at the same time last night so they both were copying at the same time to the downloads location, leading, I suspect, to a random collection of files. Thanks Jonah ~~~ Jonah Graham Kichwa Coders Ltd. www.kichwacoders.com On 21 March 2018 at 07:50, Jonah Graham wrote: > Hi Linuxtools folks, > > Can someone in your area have a look at a CDT build failure I am > having. I can reproduce this failure on my machine. CDT has lots of > builds failing due to this issue. > > Thanks, > Jonah > > > ~~~ > Jonah Graham > Kichwa Coders Ltd. > www.kichwacoders.com > > > > -- Forwarded message -- > From: > Date: 21 March 2018 at 01:03 > Subject: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14 > To: jo...@kichwacoders.com, marc.dum...@ericsson.com > > > See > <https://ci.eclipse.org/cdt/job/debug-remote-tests-master-gdb-8.1/14/display/redirect> > > -- > [...truncated 448.20 KB...] > [INFO] Computing target platform for MavenProject: > org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml > [INFO] Resolving dependencies of MavenProject: > org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml > [INFO] Resolving class path of MavenProject: > org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml > [INFO] Computing target platform for MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties > [INFO] Resolving dependencies of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties > [INFO] Resolving class path of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties > [INFO] Computing target platform for MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties > [INFO] Resolving dependencies of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties > [INFO] Resolving class path of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties > [INFO] Computing target platform for MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui:1.1.0-SNAPSHOT > @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/.polyglot.build.properties > [INFO] Resolving dependencies of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui:1.1.0-SNAPSHOT > @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/.polyglot.build.properties > [INFO] Resolving class path of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui:1.1.0-SNAPSHOT > @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.multicorevisualizer.ui/.polyglot.build.properties > [INFO] Computing target platform for MavenProject: > org.eclipse.cdt:org.eclipse.cdt.gnu.dsf:9.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.dsf-feature/.polyglot.build.properties > [INFO] Resolving dependencies of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.gnu.dsf:9.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.dsf-feature/.polyglot.build.properties > [INFO] Resolving class path of MavenProject: > org.eclipse.cdt:org.eclipse.cdt.gnu.dsf:9.5.0-SNAPSHOT @ > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.gnu.dsf-feature/.polyglot.build.properties > [INFO] Computing target platform
Re: [linuxtools-dev] Linuxtools docker nightly MD5 failures (was Fwd: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14)
Have a look at the console log, the pom.xml has an antrun to copy to download: from https://ci.eclipse.org/linuxtools/job/linuxtools-sonar/1535/consoleText [INFO] --- maven-antrun-plugin:1.8:run (deploy) @ org.eclipse.linuxtools.docker-site --- [INFO] Executing tasks main: [copy] Copying 88 files to /home/data/httpd/download.eclipse.org/linuxtools/updates-docker-nightly [INFO] Executed tasks [INFO] And at (almost exactly the same time) in https://ci.eclipse.org/linuxtools/job/linuxtools-master/2823/consoleText [INFO] --- maven-antrun-plugin:1.8:run (deploy) @ org.eclipse.linuxtools.docker-site --- [INFO] Executing tasks main: [copy] Copying 88 files to /home/data/httpd/download.eclipse.org/linuxtools/updates-docker-nightly [INFO] Executed tasks [INFO] ~~~ Jonah Graham Kichwa Coders Ltd. www.kichwacoders.com On 21 March 2018 at 09:10, Aleksandar Kurtakov wrote: > > > On Wed, Mar 21, 2018 at 10:05 AM, Jonah Graham > wrote: >> >> I have had a quick look, and both linuxtools-sonar and >> linuxtools-master jobs copy to the same location. > > > Sonar job copy files? How did you come to this ? I'm looking at the job > config and can't see any coping and it's mvn verify not install. It should > not copy IMHO. > >> >> Both builds ran at >> the same time last night so they both were copying at the same time to >> the downloads location, leading, I suspect, to a random collection of >> files. >> >> Thanks >> Jonah >> ~~~ >> Jonah Graham >> Kichwa Coders Ltd. >> www.kichwacoders.com >> >> >> On 21 March 2018 at 07:50, Jonah Graham wrote: >> > Hi Linuxtools folks, >> > >> > Can someone in your area have a look at a CDT build failure I am >> > having. I can reproduce this failure on my machine. CDT has lots of >> > builds failing due to this issue. >> > >> > Thanks, >> > Jonah >> > >> > >> > ~~~ >> > Jonah Graham >> > Kichwa Coders Ltd. >> > www.kichwacoders.com >> > >> > >> > >> > -- Forwarded message -- >> > From: >> > Date: 21 March 2018 at 01:03 >> > Subject: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14 >> > To: jo...@kichwacoders.com, marc.dum...@ericsson.com >> > >> > >> > See >> > <https://ci.eclipse.org/cdt/job/debug-remote-tests-master-gdb-8.1/14/display/redirect> >> > >> > -- >> > [...truncated 448.20 KB...] >> > [INFO] Computing target platform for MavenProject: >> > org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml >> > [INFO] Resolving dependencies of MavenProject: >> > org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml >> > [INFO] Resolving class path of MavenProject: >> > org.eclipse.cdt.features:org.eclipse.cdt.examples.dsf:9.5.0-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf/org.eclipse.cdt.examples.dsf-feature/pom.xml >> > [INFO] Computing target platform for MavenProject: >> > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties >> > [INFO] Resolving dependencies of MavenProject: >> > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties >> > [INFO] Resolving class path of MavenProject: >> > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb:5.5.0-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb/.polyglot.build.properties >> > [INFO] Computing target platform for MavenProject: >> > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.gdb.ui/.polyglot.build.properties >> > [INFO] Resolving dependencies of MavenProject: >> > org.eclipse.cdt:org.eclipse.cdt.dsf.gdb.ui:2.6.1-SNAPSHOT @ >> > >> > /jobs/genie.cdt/debug-remote-tests-master-gdb-8.1/workspace/dsf-gdb/org.eclipse.cdt.dsf.g
Re: [linuxtools-dev] Linuxtools docker nightly MD5 failures (was Fwd: Build failed in Jenkins: debug-remote-tests-master-gdb-8.1 #14)
On 21 March 2018 at 09:36, akurtakov wrote: > > > On Wed, Mar 21, 2018 at 11:31 AM, Jonah Graham > wrote: >> >> Have a look at the console log, the pom.xml has an antrun to copy to >> download: > > > Oops, thanks Jonah. I've removed the profile that enables this from sonar > job. Do you want me to rerun our master build? Yes please! ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] stable-7.1 branch created
Thanks Jeff, CDT currently uses http://download.eclipse.org/linuxtools/updates-docker-nightly/ I assume there is a new URL to use for CDT 9.6.0 that I am about to branch? Thanks Jonah ~~~ Jonah Graham Kichwa Coders Ltd. www.kichwacoders.com On Fri, 7 Dec 2018 at 15:53, Jeff Johnston wrote: > Just to let everyone know, the stable-7.1 branch has been cut from master > for the up-coming 2018-12 RC2 next week. Only critical or obvious changes > should be considered at this time and a bug must be opened. > > I have bumped up master to 7.2.0 and created a separate build job: > linuxtools-7.1 on Jenkins that uses the stable-7.1 branch. > > -- Jeff J. > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Old M* and RC* builds removed
Hi folks, Thanks for the notification. I am updating (semi?)active CDT 9.6 branches with this change <https://git.eclipse.org/r/#/c/137626/>. BTW, one of the side effects of the removal is that the simrel.build for old tags now no longer points to valid p2 repos. I imagine it is not just linuxtools that would prevent a build, but more of a heads up. Thanks Jonah ~~~ Jonah Graham Kichwa Coders Ltd. www.kichwacoders.com On Tue, 26 Feb 2019 at 12:05, Aleksandar Kurtakov wrote: > All old milestone and rc update sites are removed now from our downloads. > > -- > Alexander Kurtakov > Red Hat Eclipse Team > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Linux Tools 7.2.0 is released for Eclipse 2019-03
Hi folks, Can someone confirm or point me at the P2 URL for Linuxtools 7.2.0 please, especially Docker part as the CDT build for CDT9.7 <https://ci.eclipse.org/cdt/job/cdt-9.7/> is broken? The downloads <https://www.eclipse.org/linuxtools/downloads.php> and news <https://ci.eclipse.org/cdt/job/cdt-9.7/> pages currently only list up to 7.0.1. In addition the root directory on download <https://download.eclipse.org/linuxtools/> has a custom HTML so I can't browse there. Poking around in the downloads directory I see https://download.eclipse.org/linuxtools/update-docker-4.2.0/ seems to be the newest version for docker and https://download.eclipse.org/linuxtools/update-7.2.0/ is the other URL. Are those URLs correct? Thanks, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Wed, 20 Mar 2019 at 11:45, Jeff Johnston wrote: > The 7.2.0 release of Linux Tools is now available from our update site. > The release contains a few bug-fixes and includes a new interface for > future CDT support. > > The tag v7.2.0 maps to commit d4fd4bbc25063570da9c4ebfa1f8e6f8c6f26201 > and corresponds to build 5 in the Jenkin's linuxtools-7.2 job. > > -- Jeff J. > > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] extended read on
Hi linuxtools-devers, Can someone enable extendedRead in the permissions for https://ci.eclipse.org/linuxtools/job/linuxtools-master/ please? That will allow me to see exactly how you are building and hopefully help me to resolve some CDT build issues that you have already dealt with. A picture if it helps: [image: image.png] Thank you, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] extended read on
> > >> >> > Please try now. > Thank you! It works now. ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] [lsp4e-dev] Can we release soon?
I have contributed <https://git.eclipse.org/r/#/c/158771/> a snapshot
<https://download.eclipse.org/lsp4e/0.14.0-snapshots/S202003032032/> of
0.14.0
<https://projects.eclipse.org/projects/technology.lsp4e/releases/0.14.0>
for SimRel RC1 today (We can provide a new RC1 contribution before end of
the day tomorrow - I am not sure what LSP4E's +? day is)
I am concerned that there are 4 different versions of LSP4E in SimRel
referenced repos at the moment.
These projects contain the following versions in their P2 repos that are
contributing to SimRel:
LSP4E - 0.13.1.202003021135 - this is the version that will make it into
SimRel
Linuxtools - 0.13.1.202001301838
WildWebDeveloper - 0.13.0.201912071343
Corrosion - 0.11.0.201909021607
In addition, the above projects also contribute different versions of LSP4J:
LSP4J & LSP4E - 0.9.0.v20200229-1009
Linuxtools does not republish LSP4J
Wildwebdeveloper - 0.8.1.v20190925-0746
Corrosion - 0.8.0.v20190822-0801
With the API fluidity in LSP4J & LSP4E I don't know if/how other projects
contributing to SimRel are working properly. Perhaps Linuxtools, WWD,
Corrosion don't use any of the changed APIs, but at the moment they are
clearly compiling against old versions of LSP4E/J and are therefore subject
to class/linkage problems at runtime when installed from SimRel which will
include a different version of LSP4E/J than they compiled against.
(Note the same applies to org.eclipse.lsp4{e,j}.debug, but I haven't listed
the versions above)
Thanks,
Jonah
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
On Mon, 2 Mar 2020 at 07:23, Jonah Graham wrote:
>
>
> On Sun., Mar. 1, 2020, 13:53 Jonah Graham, wrote:
>
>> I have a Gerrit in progress to fix LSP4E for Lsp4j api changes. I'll do
>> that too.
>>
>
>
> Done. https://git.eclipse.org/r/c/158567/
>
>
>> Jonah
>>
>> On Sun., Mar. 1, 2020, 13:20 Mickael Istria, wrote:
>>
>>>
>>>
>>> On Fri, Feb 28, 2020 at 3:35 AM Jonah Graham
>>> wrote:
>>>
>>>> [0.9.0,0.10.0) would make sense - there won't be API changes between
>>>> 0.9.0 and 0.9.1 as that would be way to hard for adopters to manage IMHO.
>>>>
>>>
>>> Do you think we should change that ASAP, before next release?
>>> ___
>>> lsp4e-dev mailing list
>>> lsp4e-...@eclipse.org
>>> To change your delivery options, retrieve your password, or unsubscribe
>>> from this list, visit
>>> https://www.eclipse.org/mailman/listinfo/lsp4e-dev
>>>
>>
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] [lsp4e-dev] Can we release soon?
On Wed., Mar. 4, 2020, 05:37 Mickael Istria, wrote: > > > On Wed, Mar 4, 2020 at 3:23 AM Jonah Graham > wrote: > >> I have contributed <https://git.eclipse.org/r/#/c/158771/> a snapshot >> <https://download.eclipse.org/lsp4e/0.14.0-snapshots/S202003032032/> of >> 0.14.0 >> <https://projects.eclipse.org/projects/technology.lsp4e/releases/0.14.0> >> for SimRel RC1 today (We can provide a new RC1 contribution before end of >> the day tomorrow - I am not sure what LSP4E's +? day is) >> >> I am concerned that there are 4 different versions of LSP4E in SimRel >> referenced repos at the moment. >> >> These projects contain the following versions in their P2 repos that are >> contributing to SimRel: >> LSP4E - 0.13.1.202003021135 - this is the version that will make it into >> SimRel >> Linuxtools - 0.13.1.202001301838 >> WildWebDeveloper - 0.13.0.201912071343 >> Corrosion - 0.11.0.201909021607 >> > > That's exactly why I usually prefer releasing early and independently from > SimRel schedule: it makes it easier for projects to keep in sync and avoid > the "let's update everything to volatile S-Builds" rush before SimRel and > the need to move to the actual release just after. > That argument would carry more weight if all the projects listed above were contributing to simrel were at least on the most recent release version of LSP4E or newer. Perhaps I am also concerned for nothing, maybe LSP4E is perfectly API stable so that their won't be runtime linkage errors. To restate my previous objection - I am fine with releasing off cycle with simrel, just not arbitrarily changing previously announced release dates from some time in the future to tomorrow. Perhaps you could start the discussions now for when the next releases are going to be? We can discuss having a window so that things can change. When doing so please also don't underestimate the value of simrel for coordinating API changes across multiple projects. The nature of lsp4j trying to apply a schema fundamentally designed for JavaScript to a strongly typed language means that we are likely to have this in the future again. In the meantime, consumers of lsp4e/j should probably have version ranges on their dependencies. And lsp4e/j should make sure not to break provisional api in maintenance releases. Thanks, Jonah ___ > lsp4e-dev mailing list > lsp4e-...@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/lsp4e-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] New and Noteworthy for 7.6
Hello folks, I am updating the metadata for the C/C++ EPP package. It currently points to N&N for 7.5, but I believe you are providing 7.6? The https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn76 does not exist yet. Once created, please let me know and/or update the packages/org.eclipse.epp.package.cpp.feature/epp.website.xml <https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/packages/org.eclipse.epp.package.cpp.feature/epp.website.xml> Thanks, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] New and Noteworthy for 7.6
Thank Jeff. Done: https://git.eclipse.org/r/#/c/158874/ ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Thu, 5 Mar 2020 at 10:59, Jeff Johnston wrote: > Thanks for catching Jonah. The N&N page is now available. I'll leave it > to you to make the xml change. > > -- Jeff J. > > On Thu, Mar 5, 2020 at 9:35 AM Jonah Graham > wrote: > >> Hello folks, >> >> I am updating the metadata for the C/C++ EPP package. It currently points >> to N&N for 7.5, but I believe you are providing 7.6? The >> https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn76 does not exist >> yet. >> >> Once created, please let me know and/or update the >> packages/org.eclipse.epp.package.cpp.feature/epp.website.xml >> <https://git.eclipse.org/c/epp/org.eclipse.epp.packages.git/tree/packages/org.eclipse.epp.package.cpp.feature/epp.website.xml> >> >> Thanks, >> Jonah >> ~~~ >> Jonah Graham >> Kichwa Coders >> www.kichwacoders.com >> ___ >> linuxtools-dev mailing list >> linuxtools-dev@eclipse.org >> To change your delivery options, retrieve your password, or unsubscribe >> from this list, visit >> https://www.eclipse.org/mailman/listinfo/linuxtools-dev > > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Re-trigger build?
Yes you have to be a committer to retrigger build. The workaround you are probably aware of is to make a dummy edit and submit a new patch set. Fixing a copyright year is a good way to go. HTH, Jonah On Tue., May 19, 2020, 20:41 Homer, Tony, wrote: > Roland had told me that I should be able to re-trigger a build, but I > can’t find the option. > > >>I've re-triggered the job and it seems to be running. You can do so by > just clicking the retrigger button when logged in and viewing a > specific build. > > > > Maybe it’s because I’m not a committer on linuxtools? > > If I should be able to do it, can someone give me detailed steps to help > me find the option? > > > > Thanks! > > Tony > > > > P.S. https://ci.eclipse.org/linuxtools/job/linuxtools-gerrit/231/ > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] N&N for v8
Is the link to the N&N from PMI <https://projects.eclipse.org/projects/tools.linuxtools/releases/8.0.0> correct? https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn80 has nothing on it? Thanks, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] ASM 8 or 9?
Hello Linux tools folks, I have been continuing to unravel dependencies, especially about version constraints. Most of my work has been on JAXB because some uses cases of JAXB is failing since 2020-06. While doing so I came across another case which only affects Linuxtools' docker support. At the moment docker tooling depends on com.github.jnr set of bundles, which in turn depends on org.objectweb.asm. However the dependency only specifies a lower bound of 8.0.1 [1]. There is now a 9.x version in Orbit, but linuxtools builds against an older orbit. Does it matter to Linuxtools which version of ASM is pulled in? [1] https://git.eclipse.org/r/c/orbit/orbit-recipes/+/162989/2/github/jnr/com.github.jnr.ffi_2.1.12/osgi.bnd Thanks Jonah ~~~ ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] ASM 8 or 9?
Because of changes in simrel (Orbit p2 repo is directly available to simrel[1]) ASM 9 is being used by Linuxtools for 2020-12 M3 simrel and EPP, but ASM 8 is being used if you install linuxtools outside of Simrel. If ASM9 does not work, changing Linuxtools target platform alone won't change what ends up being resolved. We probably need to update the com.github.jnr.ffi bundle in Orbit and normally Orbit publishes its RC2 around the same time Linuxtools publishes its RC1. [1] https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/172825 Jonah On Wed., Nov. 25, 2020, 16:39 Jeff Johnston, wrote: > The orbit repo for Linux Tools wasn't updated since M1, but that was an > oversight. We can update for RC1 to use the latest and greatest orbit > (RC1). If there > are issues and we have to back-level any packages, I'll post here. > > -- Jeff J. > > On Wed, Nov 25, 2020 at 3:49 PM Jonah Graham > wrote: > >> Hello Linux tools folks, >> >> I have been continuing to unravel dependencies, especially about version >> constraints. Most of my work has been on JAXB because some uses cases of >> JAXB is failing since 2020-06. >> >> While doing so I came across another case which only affects Linuxtools' >> docker support. >> >> At the moment docker tooling depends on com.github.jnr set of bundles, >> which in turn depends on org.objectweb.asm. However the dependency only >> specifies a lower bound of 8.0.1 [1]. There is now a 9.x version in Orbit, >> but linuxtools builds against an older orbit. >> >> Does it matter to Linuxtools which version of ASM is pulled in? >> >> [1] >> https://git.eclipse.org/r/c/orbit/orbit-recipes/+/162989/2/github/jnr/com.github.jnr.ffi_2.1.12/osgi.bnd >> >> Thanks >> Jonah >> >> >> ~~~ >> ___ >> linuxtools-dev mailing list >> linuxtools-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >> > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] ASM 8 or 9?
That sounds good. Thanks Jeff. Jonah On Wed., Nov. 25, 2020, 21:24 Jeff Johnston, wrote: > > I have switched Linux Tools target to use the RC1 Orbit repo and to > specify the 9.0.0 versions of objectweb.asm. It was > specifying 8.1.0 for M3. Looking at a local build repository, there are > only objectweb.asm 9.0.0 plug-ins. Docker Tooling > is working in my testing. > > Is there something else needed or should that fix the issue foir RC1? > > -- Jeff J. > > On Wed, Nov 25, 2020 at 5:29 PM Jonah Graham > wrote: > >> Because of changes in simrel (Orbit p2 repo is directly available to >> simrel[1]) ASM 9 is being used by Linuxtools for 2020-12 M3 simrel and EPP, >> but ASM 8 is being used if you install linuxtools outside of Simrel. >> >> If ASM9 does not work, changing Linuxtools target platform alone won't >> change what ends up being resolved. We probably need to update >> the com.github.jnr.ffi bundle in Orbit and normally Orbit publishes its RC2 >> around the same time Linuxtools publishes its RC1. >> >> [1] https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/172825 >> >> Jonah >> >> >> On Wed., Nov. 25, 2020, 16:39 Jeff Johnston, wrote: >> >>> The orbit repo for Linux Tools wasn't updated since M1, but that was an >>> oversight. We can update for RC1 to use the latest and greatest orbit >>> (RC1). If there >>> are issues and we have to back-level any packages, I'll post here. >>> >>> -- Jeff J. >>> >>> On Wed, Nov 25, 2020 at 3:49 PM Jonah Graham >>> wrote: >>> >>>> Hello Linux tools folks, >>>> >>>> I have been continuing to unravel dependencies, especially about >>>> version constraints. Most of my work has been on JAXB because some uses >>>> cases of JAXB is failing since 2020-06. >>>> >>>> While doing so I came across another case which only affects >>>> Linuxtools' docker support. >>>> >>>> At the moment docker tooling depends on com.github.jnr set of bundles, >>>> which in turn depends on org.objectweb.asm. However the dependency only >>>> specifies a lower bound of 8.0.1 [1]. There is now a 9.x version in Orbit, >>>> but linuxtools builds against an older orbit. >>>> >>>> Does it matter to Linuxtools which version of ASM is pulled in? >>>> >>>> [1] >>>> https://git.eclipse.org/r/c/orbit/orbit-recipes/+/162989/2/github/jnr/com.github.jnr.ffi_2.1.12/osgi.bnd >>>> >>>> Thanks >>>> Jonah >>>> >>>> >>>> ~~~ >>>> ___ >>>> linuxtools-dev mailing list >>>> linuxtools-dev@eclipse.org >>>> To unsubscribe from this list, visit >>>> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >>>> >>> ___ >>> linuxtools-dev mailing list >>> linuxtools-dev@eclipse.org >>> To unsubscribe from this list, visit >>> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >>> >> ___ >> linuxtools-dev mailing list >> linuxtools-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >> > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] [cross-project-issues-dev] 2020-12 Release
Hello Linux tools folk,
I think your entry on https://projects.eclipse.org/releases/2020-12 is
incorrect. It says 8.0.0, but I think you are planning on 8.1.0 for 2020-12?
PS Please ping me or update the NewAndNoteworthy entries in epp.website.xml
in the EPP project.
Thanks,
Jonah
~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com
On Thu, 26 Nov 2020 at 15:45, Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:
> Greetings folks.
>
> Thanks for all of your hard work in assembling your contributions to the
> simultaneous release.
>
> I've created the master record ("release page") for the 2020-12
> simultaneous release <https://projects.eclipse.org/releases/2020-12>.
> Please have a look at the page and let me know what I've gotten wrong.
>
> I've started comparing it to the build aggrcon files and have noticed that
> a few projects appear to be contributing new releases but have not yet
> created release records. Please make sure that you've created the
> release record
> <https://www.eclipse.org/projects/handbook/#pmi-commands-release> before
> asking me to update the release page.
>
> Selecting the right release record has required some guesswork on my part.
> I did notice that some of the release records have dates that are later
> than the simultaneous release date. Please make the value in the release
> date field for your release record is no later than December 16/2020.
>
> There were a few records dated 2020-12-18 that (at least according to the
> aggrcon files) I believe that I have correctly guessed are participating in
> the release; there was at least one release dated much later in December
> that I wasn't sure about and instead opted to pick the previous release as
> the participating one.
>
> If your project's release date is more than one year later than the date
> of your project's last successful release review, then you must engage in a
> release review. The EMO will automatically start tracking your release
> review when you submit your IP Log for review. Note that you only need to
> submit your IP Log for review or request PMC approval for your release if
> you are engaging in a release review.
>
> Even if your project does not require a release review, you must still
> take care to ensure that all of the intellectual property included in your
> release has been property vetted by the IP due diligence process. If you
> require assistance, please contact the IP Team.
>
> Note that the IP Team consults the future release records as input into
> their prioritization. Please create your release records as early as
> possible (even if you have to shift the date later) to ensure that we have
> as much information as possible to assist with prioritization and improve
> our odds of getting the intellectual property that you care about cleared
> well in advance of your planned release date.
>
> Wayne
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation, Inc.
>
> Join us at our virtual event: EclipseCon 2020
> <https://www.eclipsecon.org/2020> - October 20-22
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-...@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
___
linuxtools-dev mailing list
linuxtools-dev@eclipse.org
To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Why does RPM Specfile Editor is not enabled ?
Hi Lidia, In Eclipse 2020-06 and later (4.16) there is a new option that is on by default that helps users in this case - https://www.eclipse.org/eclipse/news/4.16/platform.php#verify-jre-installation HTH, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Sun, 16 May 2021 at 18:41, Popescu, Lidia wrote: > Hello > > I figured out that latest linuxtools requires java 11. > My problem is fixed. I found appropriate versions >7.7.0 for eclipse v.4.15.0 >6.2.1 for eclipse oxigen 3a > > but why does I've been allowed to install latest > org.eclipse.linuxtools.rpm_8.2.0.202103091924.jar > <https://download.eclipse.org/linuxtools/update/features/org.eclipse.linuxtools.rpm_8.2.0.202103091924.jar> > and it tells that installation is successful. It's confusing. A less > advanced user may not figure this out. > > Thank you > Kind Regards > Lidia > -- > *From:* Popescu, Lidia > *Sent:* Sunday, May 16, 2021 1:47 PM > *To:* linuxtools-dev@eclipse.org > *Subject:* Why does RPM Specfile Editor is not enabled ? > > Hello forks, > > I am trying to find out why does the RPM Specfile Editor is not visible > after 'org.eclipse.linuxtools.rpm.ui.editor ' plugin installation on a > linux system, on both eclipse Eclipse Oxygen.3a (v.4.7.3a) & Eclipse > v.4.15.0 (2020-03-05). > > I successfully works on windows system, eclipse 2021-03. > But I don't think that eclipse version or OS matters as soon as it passed > installation process. > > I compared Configuration's tab and > >1. When it does not work, the option "open with SpeciFile Editor" is >not visible - It shows as [Installed] org.eclipse.linuxtools.rpm.ui.editor >(4.0.0.202103091924) "RPM Specfile Editor" [Installed] >2. When it works, it has [Active] state > >org.eclipse.linuxtools.rpm.ui.editor (4.0.0.202103091924) "RPM >Specfile Editor" [Active] > >So, what could prevent a plugin from being Active? What are the >dependencies, why it does not work? I am trying to debug the plugin to find >out, but maybe you could give me a quicker replay? > > > Thank you in advance > Kind Regards > Lidia Popescu > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Why does RPM Specfile Editor is not enabled ?
Hi Lidia, Sorry you have stumped me on that one. But I have a few guesses that may help you debug the issue: 1- Stick a breakpoint on org.eclipse.ui.internal.WorkbenchPage.openEditor(IEditorInput, String, boolean, int, IMemento, boolean) - that should help you track down in the stack trace where the decision was made. 2- The plug-in that contributes an item to the view normally has control over what happens when you double-click or open the file. However the Open With command is handled generically. That means a plug-in can force a specific editor on normal opens, but users can override by using Open with. 3- For a CDT contributed element, org.eclipse.cdt.internal.ui.util.EditorUtility.getEditorID(IEditorInput, Object) is in charge of figuring out which editor to use 4- org.eclipse.ui.ide.IDE.EDITOR_KEY is the persistent property (see org.eclipse.core.resources.IResource.getPersistentProperty(QualifiedName)) that keep track of overrides for a single file. I don't know where the global overrides are stored. I hope that helps you figure out the problem. It would be great if you could report back what the issue ended up being. Thanks Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Tue, 18 May 2021 at 18:48, Popescu, Lidia wrote: > Thanks Jonah, > > Do you know by accident what could be the reason that my selection is not > persistent ? I can't reproduce it in plaint eclipse. > > Open a file with Specfile Editor and check 'Use it for all *.test files'. > The icons in project explorer are properly displayed, but on file click it > still opens with previous default text editor. > Where should I look for investigating this? > > > > > Thank you > Kind Regards > Lidia > > ------ > *From:* linuxtools-dev on behalf of > Jonah Graham > *Sent:* Monday, May 17, 2021 1:51 AM > *To:* Linux Tools developer discussions > *Subject:* Re: [linuxtools-dev] Why does RPM Specfile Editor is not > enabled ? > > > [Please note: This e-mail is from an EXTERNAL e-mail address] > Hi Lidia, > > In Eclipse 2020-06 and later (4.16) there is a new option that is on by > default that helps users in this case - > https://www.eclipse.org/eclipse/news/4.16/platform.php#verify-jre-installation > > HTH, > Jonah > > ~~~ > Jonah Graham > Kichwa Coders > www.kichwacoders.com > > > On Sun, 16 May 2021 at 18:41, Popescu, Lidia > wrote: > > Hello > > I figured out that latest linuxtools requires java 11. > My problem is fixed. I found appropriate versions >7.7.0 for eclipse v.4.15.0 >6.2.1 for eclipse oxigen 3a > > but why does I've been allowed to install latest > org.eclipse.linuxtools.rpm_8.2.0.202103091924.jar > <https://download.eclipse.org/linuxtools/update/features/org.eclipse.linuxtools.rpm_8.2.0.202103091924.jar> > and it tells that installation is successful. It's confusing. A less > advanced user may not figure this out. > > Thank you > Kind Regards > Lidia > -- > *From:* Popescu, Lidia > *Sent:* Sunday, May 16, 2021 1:47 PM > *To:* linuxtools-dev@eclipse.org > *Subject:* Why does RPM Specfile Editor is not enabled ? > > Hello forks, > > I am trying to find out why does the RPM Specfile Editor is not visible > after 'org.eclipse.linuxtools.rpm.ui.editor ' plugin installation on a > linux system, on both eclipse Eclipse Oxygen.3a (v.4.7.3a) & Eclipse > v.4.15.0 (2020-03-05). > > I successfully works on windows system, eclipse 2021-03. > But I don't think that eclipse version or OS matters as soon as it passed > installation process. > > I compared Configuration's tab and > >1. When it does not work, the option "open with SpeciFile Editor" is >not visible - It shows as [Installed] org.eclipse.linuxtools.rpm.ui.editor >(4.0.0.202103091924) "RPM Specfile Editor" [Installed] >2. When it works, it has [Active] state > >org.eclipse.linuxtools.rpm.ui.editor (4.0.0.202103091924) "RPM >Specfile Editor" [Active] > >So, what could prevent a plugin from being Active? What are the >dependencies, why it does not work? I am trying to debug the plugin to find >out, but maybe you could give me a quicker replay? > > > Thank you in advance > Kind Regards > Lidia Popescu > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] Archived p2 repos broken
Hi folks, It appears that Linuxtools cleaned up the downloads area, but it has exposed a problem that some of the p2 repos are broken. At some point recently(?) https://download.eclipse.org/linuxtools/updates-docker-nightly-4.6/ was removed - so I wanted to update my older CDT ** build which relies on docker 4.6 to https://archive.eclipse.org/linuxtools/update-docker-4.6.0/ * Problem is that link has no content/artifacts files - but the plugins/features are there. Is there anything you can do? If not, can you tell me what you had done so that I can start putting in requests to webmaster to restore lost files from backups if possible? Thanks Jonah ** CDT 9.11 branch - the previous major release branch that many integrators are using. CDT itself only stopped verifying this branch in Nov 2021 -https://ci.eclipse.org/cdt/view/Main%20(old%20releases)/job/cdt-9.11/ * These are the URLs that look suspect (missing the metadata files): - https://archive.eclipse.org/linuxtools/update-7.5.0/ (this one also has an extra nesting level) - https://archive.eclipse.org/linuxtools/update-7.7.0/ - https://archive.eclipse.org/linuxtools/update-docker-4.5.1/ - https://archive.eclipse.org/linuxtools/update-docker-4.6.0/ - https://archive.eclipse.org/linuxtools/update-docker-4.7.0/ - https://archive.eclipse.org/linuxtools/update-docker-5.0.0/ (this one looks ok, but has a dodgy subdir that looks like the broken ones) - https://archive.eclipse.org/linuxtools/update-docker-5.1.0/ (same as 5.0.0) - https://archive.eclipse.org/linuxtools/update-docker-5.2.0/ (same as 5.0.0) ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Archived p2 repos broken
On Wed., Jan. 26, 2022, 12:43 Александър Куртаков, wrote: > > > On Wed, Jan 26, 2022 at 7:26 PM Jonah Graham > wrote: > >> Hi folks, >> >> It appears that Linuxtools cleaned up the downloads area, but it has >> exposed a problem that some of the p2 repos are broken. >> >> At some point recently(?) >> https://download.eclipse.org/linuxtools/updates-docker-nightly-4.6/ was >> removed - so I wanted to update my older CDT ** build which relies on >> docker 4.6 to https://archive.eclipse.org/linuxtools/update-docker-4.6.0/ >> * >> >> Problem is that link has no content/artifacts files - but the >> plugins/features are there. >> >> Is there anything you can do? If not, can you tell me what you had done >> so that I can start putting in requests to webmaster to restore lost files >> from backups if possible? >> > > Everything was done using "Move selected to archive.eclipse.org" . There > were multiple issues with the scripts so I guess some of them screwed it > https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/754 . I really > can't help more with that right now. > Thanks, I'll bring it up to helpdesk. Jonah > >> >> Thanks >> Jonah >> >> ** CDT 9.11 branch - the previous major release branch that many >> integrators are using. CDT itself only stopped verifying this branch in Nov >> 2021 - >> https://ci.eclipse.org/cdt/view/Main%20(old%20releases)/job/cdt-9.11/ >> >> * These are the URLs that look suspect (missing the metadata files): >> - https://archive.eclipse.org/linuxtools/update-7.5.0/ (this one also >> has an extra nesting level) >> - https://archive.eclipse.org/linuxtools/update-7.7.0/ >> - https://archive.eclipse.org/linuxtools/update-docker-4.5.1/ >> - https://archive.eclipse.org/linuxtools/update-docker-4.6.0/ >> - https://archive.eclipse.org/linuxtools/update-docker-4.7.0/ >> - https://archive.eclipse.org/linuxtools/update-docker-5.0.0/ (this one >> looks ok, but has a dodgy subdir that looks like the broken ones) >> - https://archive.eclipse.org/linuxtools/update-docker-5.1.0/ (same as >> 5.0.0) >> - https://archive.eclipse.org/linuxtools/update-docker-5.2.0/ (same as >> 5.0.0) >> >> ~~~ >> Jonah Graham >> Kichwa Coders >> www.kichwacoders.com >> ___ >> linuxtools-dev mailing list >> linuxtools-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >> > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Archived p2 repos broken
Hi Jeff, Please do unzip the files if you can - I requested that to webmaster on helpdesk, so you can close the issue there if it is resolved - https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/814 Thanks, Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Wed, 26 Jan 2022 at 18:38, Jeff Johnston wrote: > Hi Jonah, > > The archive system was very wonky when I used it. The good news is that > in all these cases, there should be a zip file of the original repo. For > example, > there is a linuxtools-docker-4.6.0.zip file in our archives. This file > has the original content.xml, etc... that is missing. > > I can unzip just the missing files if everybody is ok with that or I could > replace everything in the directory with the unzipped files to ensure > everything is correct. > > -- Jeff J. > > On Wed, Jan 26, 2022 at 12:35 PM Jonah Graham > wrote: > >> Hi folks, >> >> It appears that Linuxtools cleaned up the downloads area, but it has >> exposed a problem that some of the p2 repos are broken. >> >> At some point recently(?) >> https://download.eclipse.org/linuxtools/updates-docker-nightly-4.6/ was >> removed - so I wanted to update my older CDT ** build which relies on >> docker 4.6 to https://archive.eclipse.org/linuxtools/update-docker-4.6.0/ >> * >> >> Problem is that link has no content/artifacts files - but the >> plugins/features are there. >> >> Is there anything you can do? If not, can you tell me what you had done >> so that I can start putting in requests to webmaster to restore lost files >> from backups if possible? >> >> Thanks >> Jonah >> >> ** CDT 9.11 branch - the previous major release branch that many >> integrators are using. CDT itself only stopped verifying this branch in Nov >> 2021 - >> https://ci.eclipse.org/cdt/view/Main%20(old%20releases)/job/cdt-9.11/ >> >> * These are the URLs that look suspect (missing the metadata files): >> - https://archive.eclipse.org/linuxtools/update-7.5.0/ (this one also >> has an extra nesting level) >> - https://archive.eclipse.org/linuxtools/update-7.7.0/ >> - https://archive.eclipse.org/linuxtools/update-docker-4.5.1/ >> - https://archive.eclipse.org/linuxtools/update-docker-4.6.0/ >> - https://archive.eclipse.org/linuxtools/update-docker-4.7.0/ >> - https://archive.eclipse.org/linuxtools/update-docker-5.0.0/ (this one >> looks ok, but has a dodgy subdir that looks like the broken ones) >> - https://archive.eclipse.org/linuxtools/update-docker-5.1.0/ (same as >> 5.0.0) >> - https://archive.eclipse.org/linuxtools/update-docker-5.2.0/ (same as >> 5.0.0) >> >> ~~~ >> Jonah Graham >> Kichwa Coders >> www.kichwacoders.com >> ___ >> linuxtools-dev mailing list >> linuxtools-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >> > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
[linuxtools-dev] Change in org.eclipse.linuxtools.rpm?
Hi Jeff/Linux Tools Devs Has there been a change in linuxtools related to rpm support? Since the 2022-09 M2 contribution <https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/194996> of linux tools the EPP builds fail with this error: *12:30:46* org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-packaging-plugin:2.7.1:build-qualifier-aggregator (default-build-qualifier-aggregator) on project org.eclipse.epp.package.parallel.feature: Execution default-build-qualifier-aggregator of goal org.eclipse.tycho:tycho-packaging-plugin:2.7.1:build-qualifier-aggregator failed: Could not resolve feature org.eclipse.linuxtools.rpm_0.0.0; Path to dependency: see https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/2381/console for full error/stack trace I haven't spent much time trying to track down the problem in the hope that you may have an idea where I should start. AFAICT org.eclipse.linuxtools.rpm is in the staging repo. Thanks for any insight you can provide. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
Re: [linuxtools-dev] Change in org.eclipse.linuxtools.rpm?
Thanks Alex, As EPP was using Java 11 to build that seems like the probable cause. I have tried switching to Java 17 to build with now and will know in a couple of hours if that was the issue. Thanks again. Jonah ~~~ Jonah Graham Kichwa Coders www.kichwacoders.com On Wed, 3 Aug 2022 at 14:58, Александър Куртаков wrote: > Most probably caused by > https://github.com/eclipse-linuxtools/org.eclipse.linuxtools/commit/d521a86fd50cfd4dbd518520f9767d81be26395f > and something in the EPP build fails with Java 17 bundles. > > On Wed, Aug 3, 2022 at 7:41 PM Jonah Graham > wrote: > >> Hi Jeff/Linux Tools Devs >> >> Has there been a change in linuxtools related to rpm support? Since the >> 2022-09 M2 contribution >> <https://git.eclipse.org/r/c/simrel/org.eclipse.simrel.build/+/194996> >> of linux tools the EPP builds fail with this error: >> >> *12:30:46* org.apache.maven.lifecycle.LifecycleExecutionException: Failed to >> execute goal >> org.eclipse.tycho:tycho-packaging-plugin:2.7.1:build-qualifier-aggregator >> (default-build-qualifier-aggregator) on project >> org.eclipse.epp.package.parallel.feature: Execution >> default-build-qualifier-aggregator of goal >> org.eclipse.tycho:tycho-packaging-plugin:2.7.1:build-qualifier-aggregator >> failed: Could not resolve feature org.eclipse.linuxtools.rpm_0.0.0; Path to >> dependency: >> >> >> see >> https://ci.eclipse.org/packaging/job/simrel.epp-tycho-build/2381/console >> for full error/stack trace >> >> I haven't spent much time trying to track down the problem in the hope >> that you may have an idea where I should start. AFAICT >> org.eclipse.linuxtools.rpm is in the staging repo. >> >> Thanks for any insight you can provide. >> >> Jonah >> >> >> ~~~ >> Jonah Graham >> Kichwa Coders >> www.kichwacoders.com >> ___ >> linuxtools-dev mailing list >> linuxtools-dev@eclipse.org >> To unsubscribe from this list, visit >> https://www.eclipse.org/mailman/listinfo/linuxtools-dev >> > ___ > linuxtools-dev mailing list > linuxtools-dev@eclipse.org > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/linuxtools-dev > ___ linuxtools-dev mailing list linuxtools-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/linuxtools-dev
