Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] please test staged Tycho 2.0.0 
Le 11/08/2020 à 18:17, Johan Compagner a écrit :

and you have the toolchain plugin in the pom.xml?
I didn't. I have added it (https://git.eclipse.org/c/emf-transaction/org.eclipse.emf.transaction.git/commit/?id=23fe0e4fcfa0942536cb694731a6c4d753f5d90f), but both locally and on the JIPP it still fails (https://ci.eclipse.org/emfservices/job/emf-transaction-master/63/).
The logs when running mvn -X has this section which seems related (see https://ci.eclipse.org/emfservices/job/emf-transaction-master/63/PLATFORM=2020-09,jdk=openjdk-jdk13-latest,label=migration/consoleText for the full log):
[INFO] Computing target platform for MavenProject: org.eclipse.emf.transaction.plugins:org.eclipse.emf.transaction:1.9.1-SNAPSHOT @ /home/pcdavid/src/maintenance/git/org.eclipse.emf.transaction/o$ [DEBUG] Using execution environment 'JavaSE-1.8' configured in Bundle-RequiredExecutionEnvironment (first entry) [DEBUG] Adding target definition file "/home/pcdavid/src/maintenance/git/org.eclipse.emf.transaction/org.eclipse.emf.transaction.target/2020-06.target" 
[DEBUG] Resolving target definition content...
[...]
[DEBUG] Added 3 locally built units to the target platform
[INFO] Resolving dependencies of MavenProject: org.eclipse.emf.transaction.plugins:org.eclipse.emf.transaction:1.9.1-SNAPSHOT @ /home/pcdavid/src/maintenance/git/org.eclipse.emf.transaction/org.e$ [DEBUG] Using execution environment 'JavaSE-13' configured in current execution environment [DEBUG] Adding target definition file "/home/pcdavid/src/maintenance/git/org.eclipse.emf.transaction/org.eclipse.emf.transaction.target/2020-06.target" [DEBUG] Target definition content cache miss: All entries differ, but there are entries which only differ in one parameter: [execution environment] 
[DEBUG] Resolving target definition content...
[...]
[ERROR] Cannot resolve target definition: [ERROR] Software being installed: org.eclipse.sdk.ide 4.17.0.I20200811-1800 [ERROR] Missing requirement: org.apache.lucene.analyzers-common 8.4.1.v20200122-1459 requires 'osgi.ee; (&(osgi.ee=JavaSE)(version=1.8))' but it could not be found [ERROR] Cannot satisfy dependency: org.eclipse.help.feature.group 2.3.300.v20200811-1800 depends on: org.eclipse.equinox.p2.iu; org.apache.lucene.analyzers-common [8.4.1.v20200122-1459,8.4.1.v20200122-1459] [ERROR] Cannot satisfy dependency: org.eclipse.platform.feature.group 4.17.0.v20200811-1800 depends on: org.eclipse.equinox.p2.iu; org.eclipse.help.feature.group [2.3.300.v20200811-1800,2.3.300.v20200811-1800] [ERROR] Cannot satisfy dependency: org.eclipse.sdk.feature.group 4.17.0.v20200811-1828 depends on: org.eclipse.equinox.p2.iu; org.eclipse.platform.feature.group [4.17.0.v20200811-1800,4.17.0.v20200811-1800] [ERROR] Cannot satisfy dependency: org.eclipse.sdk.ide 4.17.0.I20200811-1800 depends on: org.eclipse.equinox.p2.iu; org.eclipse.sdk.feature.group [4.17.0.v20200811-1828,4.17.0.v20200811-1828] [ERROR] 

Si it starts the target resolution by saying
[DEBUG] Using execution environment 'JavaSE-1.8' configured in Bundle-RequiredExecutionEnvironment (first entry) 

then a little later a similar message says it is now using Java 13:
[DEBUG] Using execution environment 'JavaSE-13' configured in current execution environment
I'll spare you the details of the constraints p2 fails to solve (visible in the full logs), except that it ends with this, which may or may not be related: 

...
Unable to satisfy dependency from tycho-ee-1597230437822 0.0.0.1597230437822 to org.eclipse.equinox.p2.iu; a.jre.javase [13.0.0,13.0.0].; Unable to satisfy dependency from tycho-1597230437894 0.0.0.1597230437894 to org.eclipse.equinox.p2.iu; a.jre.javase [13.0.0,13.0.0].; 
No solution found because the problem is unsatisfiable.]
When using Java 14 to build (https://ci.eclipse.org/emfservices/job/emf-transaction-master/63/PLATFORM=2020-09,jdk=openjdk-jdk14-latest,label=migration/consoleText), it works, although there is a similar switch, which seems to happen for every plug-in: 

[INFO] Computing target platform for MavenProject: org.eclipse.emf.transaction.plugins:org.eclipse.emf.workspace:1.5.1-SNAPSHOT @ /home/jenkins/agent/workspace/emf-transaction-master/PLATFORM/2020-09/jdk/openjdk-jdk14-latest/label/migration/org.eclipse.emf.workspace/pom.xml
[DEBUG] Using execution environment 'JavaSE-1.8' configured in Bundle-RequiredExecutionEnvironment (first entry)
[DEBUG] Adding target definition file "/home/jenkins/agent/workspace/emf-transaction-master/PLATFORM/2020-09/jdk/openjdk-jdk14-latest/label/migration/org.eclipse.emf.transaction.target/2020-09.target"
[DEBUG] Added 980 units, the content of the target definition file, to the target platform
[DEBUG] Registered artifact repository org.eclipse.tycho.repository.registry.facade.RepositoryBlackboardKey(uri=file:/resolution-context-artifacts@%252Fhome%252Fjenkins%252Fagent%252Fworkspace%252Femf-transaction-master%252FPLATFORM%252F2020-09%252Fjdk%252Fopenjdk-jdk14-latest%252Flabel%252Fmigration%252Forg.eclipse.emf.workspace)
[DEBUG] Added 0 locally built units to the target platform
[INFO] Resolving dependencies of MavenProject: org.eclipse.emf.transaction.plugins:org.eclipse.emf.workspace:1.5.1-SNAPSHOT @ /home/jenkins/agent/workspace/emf-transaction-master/PLATFORM/2020-09/jdk/openjdk-jdk14-latest/label/migration/org.eclipse.emf.workspace/pom.xml
[DEBUG] Using execution environment 'JavaSE-14' configured in current execution environment
[DEBUG] Adding target definition file "/home/jenkins/agent/workspace/emf-transaction-master/PLATFORM/2020-09/jdk/openjdk-jdk14-latest/label/migration/org.eclipse.emf.transaction.target/2020-09.target"
[DEBUG] Added 980 units, the content of the target definition file, to the target platform
[DEBUG] Registered artifact repository org.eclipse.tycho.repository.registry.facade.RepositoryBlackboardKey(uri=file:/resolution-context-artifacts@%252Fhome%252Fjenkins%252Fagent%252Fworkspace%252Femf-transaction-master%252FPLATFORM%252F2020-09%252Fjdk%252Fopenjdk-jdk14-latest%252Flabel%252Fmigration%252Forg.eclipse.emf.workspace)
[DEBUG] Added 0 locally built units to the target platform

This is all using Tycho 1.7.0.

When switching to Tycho 2.0, still using Java 13 to run, I get:

[DEBUG] Toolchain JDK[/home/pcdavid/.sdkman/candidates/java/9.0.4-open] doesn't match required property: id
[DEBUG] Toolchain JDK[/home/pcdavid/.sdkman/candidates/java/10.0.2-open] doesn't match required property: id
[DEBUG] Toolchain JDK[/home/pcdavid/.sdkman/candidates/java/11.0.6-open] doesn't match required property: id
[DEBUG] Toolchain JDK[/home/pcdavid/.sdkman/candidates/java/12.0.2-open] doesn't match required property: id
[DEBUG] Toolchain JDK[/home/pcdavid/.sdkman/candidates/java/13.0.2.hs-adpt] doesn't match required property: id
[DEBUG] Toolchain JDK[/home/pcdavid/.sdkman/candidates/java/14.0.0-open] doesn't match required property: id
[ERROR] Internal error: org.eclipse.tycho.core.ee.UnknownEnvironmentException: Unknown OSGi execution environment: 'JavaSE-13' -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: org.eclipse.tycho.core.ee.UnknownEnvironmentException: Unknown OSGi execution environment: 'JavaSE-13'

Tycho 1.7.0 does not complain anywhere about these.
On Tue, 11 Aug 2020 at 16:20, Pierre-Charles David <pierre-charles.david@xxxxxxx <mailto:pierre-charles.david@xxxxxxx>> wrote: 

    Le 11/08/2020 à 15:48, Johan Compagner a écrit :
    > do you have a toolchains.xml file?
    >
    > <toolchains>
    >   <!-- JDK toolchains -->
    >   <toolchain>
    >        <type>jdk</type>
    >        <provides>
    > <id>JavaSE-1.8</id>
    >        </provides>
    >        <configuration>
    > <jdkHome>c:/javatools/jdk18/</jdkHome>
    >        </configuration>
    >   </toolchain>
    > </toolchains>
    >
    > i guess that is still needed right?
    > If we want to let tycho run with any kind of java (11 or higher)
    > but still compile with or against a BREE of java 8?


    Locally I have one, which seems correct. It points to the path for a
    real OpenJDK 1.8.0:

    ~% grep -C5 JavaSE-1.8 ~/.m2/toolchains.xml
    <toolchains xmlns="http://maven.apache.org/TOOLCHAINS/1.1.0";
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
    xsi:schemaLocation="http://maven.apache.org/TOOLCHAINS/1.1.0
    http://maven.apache.org/xsd/toolchains-1.1.0.xsd";>
       <toolchain>
         <type>jdk</type>
         <provides>
           <id>JavaSE-1.8</id>
         </provides>
         <configuration>
    <jdkHome>/home/pcdavid/.sdkman/candidates/java/8.0.242-open</jdkHome>
         </configuration>
       </toolchain>
    ~% /home/pcdavid/.sdkman/candidates/java/8.0.242-open/bin/java
    -version
    openjdk version "1.8.0_242"
    OpenJDK Runtime Environment (build 1.8.0_242-b08)
    OpenJDK 64-Bit Server VM (build 25.242-b08, mixed mode)

    I don't know how the JIRO servers are setup in this regard though,
    but I
    see the same behavior there as locally. I don't think I changed
    anything
    related to that on the EMF Services Jenkins [1] (using the
    "migration"
    image).

    [1] https://ci.eclipse.org/emfservices/

    Oh, and I forgot to mention, both locally and on the JIPP this is
    using
    "Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)".

    _______________________________________________
    tycho-user mailing list
    tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
    To unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/tycho-user



--
Johan Compagner
Servoy

_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tycho-user

Back to the top