Re: [papyrus-rt-dev] Question about the build

[Ernesto Posse <eposse@xxxxxxxxxxxxx>]

Hi. I think you are probably referring to the master pom, at least the hudson Master-All build (https://hudson.eclipse.org/papyrus-rt/job/Papyrus-RT-Master-All/configure) sets eclipse.release, although I am confused about that too, since I do not see any mention of the eclipse.release property in that pom or its immediate (sub)modules, and I don't see where to other poms (core, common, profile, tooling) are included in this. What am I missing here?

Anyway, regardless, since Celine's changes have not been merged to the master branch yet, we are still using our own separate codegen+rts pom and build, and in this one, the profile activation is on the PAPYRUS_UPDATE_SITE property, not on eclipse.release. You can see that in releng/codegen/pom.xml. This is where we define the eclipse.targetrelease property (which I think Celine added when she also added the codegen-specific target platforms) and the tycho configuration I mentioned. You are right that we need to unify these properties, but that was what Celine's unified build was all about, no? 

Nevertheless, it seems to be working now, but it is ugly, because I had to add the following to the release target platform (in fact to all TPs):

location "https://hudson.eclipse.org/papyrus/job/Papyrus-Neon-Extra/lastSuccessfulBuild/artifact/repository/" eclipse-papyrus-neon-extra {

  org.eclipse.papyrus.infra.gmfdiag.elk.feature.feature.group lazy

}

location "http://download.eclipse.org/elk/updates/releases/0.1.0/" eclipse-elk {

  org.eclipse.elk.sdk.feature.feature.group lazy

}

The location for the new ELK integration in Papyrus is not yet available at the "real" location (http://download.eclipse.org/modeling/mdt/papyrus/updates/nightly/neon/extra/) so I had to use the url from the latest successful build.

I've sent an e-mail to Remi and Quentin who is supposed to work on ELK integration, but Remi is now on vacations and Quentin has not answered. So for now it will have to do.

But I'm still bewildered by the error I described in my original message. It doesn't make sense to me.

At least the CodegenRTS build works now, but I'm mystified with the fact that the codegen nightly build has been failing. Even more strange, I just triggered it manually and it succeeded. So there seems to be a problem building automatically at that particular time (11:30pm). Very weird. The console output suggests that the problem occurs when we run our tests and try to install the features.

On Wed, Aug 17, 2016 at 9:27 AM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Ernesto,

The selection of the specific TP module in the Maven build is determined by profile activation on the “eclipse.release” property, not “eclipse.targetrelease”.

So, in your Hudson build configuration, I think you need to set the “eclipse.release” property to activate the correct profile.  Perhaps your codegen POM should reuse this property instead of setting its own “eclipse.targetrelease” property?

HTH,

Christian

On 12 August, 2016 at 13:06:18, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:

Hi. I have a question about the build, which perhaps someone can help me with. Currently, for the codegen build we are using the Papyrus releases update site as a dependency, but we will soon need to use the nightly. There are three codegen target platforms, for releases, milestones and nightly. The codegen pom has three corresponding profiles which activate each of these TPs. The profiles are activated with a Hudson job parameter called PAPYRUS_UPDATE_SITE. Additionally, the codegen pom includes this property:

<eclipse.targetrelease>neon.papyrusrelease</eclipse.targetrelease>

which seems to be used in the configuration of the org.eclipse.tycho:target-platform-configuration plugin which specifies:

<target>

<artifact>

<groupId>org.eclipse.papyrusrt</groupId>

<artifactId>org.eclipse.papyrusrt.codegen.targetplatform.${eclipse.targetrelease}</artifactId>

<version>${target.version}</version>

</artifact>

</target>

The problem I have is that if I set PAPYRUS_UPDATE_SITE to nightly, and change the property eclipse.targetrelease to 

<eclipse.targetrelease>neon.papyrusnightly</eclipse.targetrelease>

then the build fails with this:

[ERROR] Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse.papyrusrt:org.eclipse.papyrusrt.codegen.targetplatform.neon.papyrusnightly:target:0.7.2-SNAPSHOT -> [Help 1]
org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: Could not resolve target platform specification artifact org.eclipse.papyrusrt:org.eclipse.papyrusrt.codegen.targetplatform.neon.papyrusnightly:target:0.7.2-SNAPSHOT

Note that if the PAPYRUS_UPDATE_SITE is set to release, there is no problem, so the problem seems to be with the tycho configuration. Why does it fail to resolve the nigthly codegen TP if it is there, under releng/codegen/targetplatform and its pom has the correct group and artifact ids?

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

<modelVersion>4.0.0</modelVersion>

<parent>

<artifactId>org.eclipse.papyrusrt.codegen.targetplatform</artifactId>

<groupId>org.eclipse.papyrusrt</groupId>

<version>0.7.2-SNAPSHOT</version>

</parent>

<artifactId>org.eclipse.papyrusrt.codegen.targetplatform.neon.papyrusnightly</artifactId>

<packaging>eclipse-target-definition</packaging>

<name>org.eclipse.papyrusrt.codegen.targetplatform.neon.papyrusnightly</name>

<description>This plug-in contains the target definition for Codegen Papyrus-RT in Neon</description>

<groupId>org.eclipse.papyrusrt</groupId>

<version>0.7.2-SNAPSHOT</version>

</project>

Any ideas?

Thanks

--

Ernesto Posse

Zeligsoft

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev