Eclipse Community Forums: e(fx)clipse » Neon and 2.4.0 site target linux 64 bit problem

Home » Eclipse Projects » e(fx)clipse » Neon and 2.4.0 site target linux 64 bit problem

Neon and 2.4.0 site target linux 64 bit problem [message #1737118]

Tue, 05 July 2016 16:52

Eclipse User

I was working with e(fx)clipse 2.3.0 and Mars 4.5.2 with no issues. I moved to 2.4.0 and 4.6.0 today. I mirrored the targets. The runnable target works fine but when I run the Maven-Tycho build (which depends on the p2 site target) it states:
Missing requirement: toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64 1.1.400.v20160518-1444 requires 'bundle org.eclipse.equinox.launcher.gtk.linux.x86_64 1.1.400.v20160518-1444' but it could not be found

Notice the blank space between x86_64 and 1.1.400. The jar for this platform executable is present except it has an underscore where the blank space currently is. I tried renaming the bundle so it has the space but the same error message is produced. I renamed it again to its original name.

I took linux gtk x86_64 out of the build and left the linux gtk x86 and the win32 win32 x86_64 environments in the build. The build completes successfully and the zip files have executables that launch.

I also tried this using the remote site (instead of a local mirror) but I get :
Missing requirement: toolingwin32.win32.x86_64org.eclipse.core.runtime 1.0.0 requires 'bundle org.eclipse.core.runtime 3.12.0.v20160606-1342' but it could not be found

Here is my config pom:

<?xml version="1.0" encoding="UTF-8"?>
<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>
	<groupId>my.group.id</groupId>
	<artifactId>my.group.id.artifact.id</artifactId>
	<version>1.0.0-SNAPSHOT</version>
	<packaging>pom</packaging>
	<properties>
		<tycho.version>0.25.0</tycho.version>
		<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<!-- 		<efxclipse.target>file:/${git.repo}/TEX/build-site-target/efxclipse-2.4.0/</efxclipse.target> -->
<!-- 		<eclipse.target>file:/${git.repo}/TEX/build-site-target/eclipse-4.6.0/</eclipse.target> -->
		<efxclipse.target>http://download.eclipse.org/efxclipse/runtime-released/2.4.0/site/</efxclipse.target>
		<eclipse.target>http://download.eclipse.org/releases/neon</eclipse.target>
	</properties>

	<repositories>
		<repository>
			<id>eclipse 4.6.0</id>
			<url>${eclipse.target}</url>
			<layout>p2</layout>
		</repository>
		<repository>
			<id>e(fx)clipse 2.4.0</id>
			<url>${efxclipse.target}</url>
			<layout>p2</layout>
		</repository>
	</repositories>

	<build>
		<plugins>
			<plugin>
				<groupId>org.eclipse.tycho</groupId>
				<artifactId>tycho-maven-plugin</artifactId>
				<version>${tycho.version}</version>
				<extensions>true</extensions>
			</plugin>

			<plugin>
				<groupId>org.eclipse.tycho</groupId>
				<artifactId>target-platform-configuration</artifactId>
				<version>${tycho.version}</version>
				<configuration>
					<environments>
<!-- 						<environment> -->
<!-- 							<os>linux</os> -->
<!-- 							<ws>gtk</ws> -->
<!-- 							<arch>x86</arch> -->
<!-- 						</environment> -->
						<environment>
							<os>linux</os>
							<ws>gtk</ws>
							<arch>x86_64</arch>
						</environment>
<!-- 						<environment> -->
<!-- 							<os>win32</os> -->
<!-- 							<ws>win32</ws> -->
<!-- 							<arch>x86_64</arch> -->
<!-- 						</environment> -->
					</environments>
				</configuration>
			</plugin>
		</plugins>
	</build>
</project>

This is my script to mirror the repo. This worked just fine for the 4.5.2 and 2.3.0 targets:

<project name="Mirror" default="mirrorRepos">
	<!-- The P2 repository location to mirror -->
	<property name="efxclipseRepository" value="http://download.eclipse.org/efxclipse/runtime-released/2.4.0/site" />
	<property name="eclipseRepository" value="http://download.eclipse.org/releases/neon" />
	<!-- The location to place the mirrored repository (root location) -->
	<property name="baseP2RepoHome" value="C:/TEMP/target" />
	<property name="baseEclipseP2RepoHome" value="${baseP2RepoHome}" />
	<!-- Defines each p2 destination with a version identifier. -->
	<property name="eclipseReleaseNameVer" value="eclipse-4.6.0" />
	<property name="efxclipseReleaseNameVer" value="efxclipse-2.4.0" />

	<target name="mirrorRepos" description="Builds the entire p2 mirror set.">
		<antcall target="createMirror" />
	</target>

	<target name="createMirror" description="Mirrors the Eclipse 4.6.0 launcher feature and efxclispe 2.4.0 repository items. Turns them into runnables">
		<p2.mirror source="${eclipseRepository}" verbose="true" log="C:/TEMP/p2NeonMirror.log" validate="true" destination="file://${baseEclipseP2RepoHome}/site/${eclipseReleaseNameVer}" >
			<iu id="org.eclipse.equinox.executable.feature.group" />
		</p2.mirror>
		<p2.mirror source="${efxclipseRepository}" verbose="true" log="C:/TEMP/p2FXMirror.log" validate="true" destination="file://${baseEclipseP2RepoHome}/site/${efxclipseReleaseNameVer}" >
 			<iu id="org.eclipse.fx.target.feature.feature.group" />
		</p2.mirror>
		<p2.repo2runnable>
		  <repository location="file://${baseEclipseP2RepoHome}/runnable/${eclipseReleaseNameVer}" />
		  <source>
		    <repository location="file://${baseEclipseP2RepoHome}/site/${eclipseReleaseNameVer}" />
		  </source>
		</p2.repo2runnable>
		<p2.repo2runnable>
		  <repository location="file://${baseEclipseP2RepoHome}/runnable/${efxclipseReleaseNameVer}" />
		  <source>
		    <repository location="file://${baseEclipseP2RepoHome}/site/${efxclipseReleaseNameVer}" />
		  </source>
		</p2.repo2runnable>
	</target>
</project>

Thanks for any help you can provide.

[Updated on: Wed, 06 July 2016 13:32] by Moderator

Re: Neon and 2.4.0 site target linux 64 bit problem [message #1737157 is a reply to message #1737118]

Wed, 06 July 2016 03:44

Eclipse User

Hi John,

Can you file a bug for that. I'll try to track that down. Is your
application a pure e4 and JavaFX app or a SWT-JavaFX mixed one?

Tom

On 05.07.16 22:52, John Bodkin wrote:
> I was working with e(fx)clipse 2.3.0 and Mars 4.5.2 with no issues. I
> moved to 2.4.0 and 4.6.0 today. I mirrored the targets. The runnable
> target works fine but when I run the Maven-Tycho build (which depends on
> the p2 site target) it states:
> Missing requirement:
> toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64
> 1.1.400.v20160518-1444 requires 'bundle
> org.eclipse.equinox.launcher.gtk.linux.x86_64 1.1.400.v20160518-1444'
> but it could not be found
>
> Notice the blank space between x86_64 and 1.1.400. The jar for this
> platform executable is present except it has an underscore where the
> blank space currently is. I tried renaming the bundle so it has the
> space but the same error message is produced. I renamed it again to its
> original name.
>
> I took linux gtk x86_64 out of the build and left the linux gtk x86 and
> the win32 win32 x86_64 environments in the build. The build completes
> successfully and the zip files have executables that launch.
>
> I also tried this using the remote site (instead of a local mirror) but
> I get :
> Missing requirement: toolingwin32.win32.x86_64org.eclipse.core.runtime
> 1.0.0 requires 'bundle org.eclipse.core.runtime 3.12.0.v20160606-1342'
> but it could not be found
>
> Here is my config pom:
>
> <?xml version="1.0" encoding="UTF-8"?>
> <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>
> <groupId>my.group.id</groupId>
> <artifactId>my.group.id.artifact.id</artifactId>
> <version>1.0.0-SNAPSHOT</version>
> <packaging>pom</packaging>
> <properties>
> <tycho.version>0.25.0</tycho.version>
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> 
> 
>
> <efxclipse.target>http://download.eclipse.org/efxclipse/runtime-released/2.4.0/site/</efxclipse.target>
>
>
> <eclipse.target>http://download.eclipse.org/releases/neon</eclipse.target>
> </properties>
>
> <repositories>
> <repository>
> <id>eclipse 4.6.0</id>
> <url>${eclipse.target}</url>
> <layout>p2</layout>
> </repository>
> <repository>
> <id>e(fx)clipse 2.4.0</id>
> <url>${efxclipse.target}</url>
> <layout>p2</layout>
> </repository>
> </repositories>
>
> <build>
> <plugins>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-maven-plugin</artifactId>
> <version>${tycho.version}</version>
> <extensions>true</extensions>
> </plugin>
>
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>target-platform-configuration</artifactId>
> <version>${tycho.version}</version>
> <configuration>
> <environments>
> 
> 
> 
> 
> 
> <environment>
> <os>linux</os>
> <ws>gtk</ws>
> <arch>x86_64</arch>
> </environment>
> 
> 
> 
> 
> 
> </environments>
> </configuration>
> </plugin>
> </plugins>
> </build>
> </project>
>
>
>
> This is my script to mirror the repo. This worked just fine for the
> 4.5.2 and 2.3.0 targets:
>
> <project name="Mirror" default="mirrorRepos">
> 
> <property name="efxclipseRepository"
> value="http://download.eclipse.org/efxclipse/runtime-released/2.4.0/site" />
>
> <property name="eclipseRepository"
> value="http://download.eclipse.org/releases/neon" />
> 
> <property name="baseP2RepoHome" value="C:/TEMP/target" />
> <property name="baseEclipseP2RepoHome" value="${baseP2RepoHome}" />
> 
> <property name="eclipseReleaseNameVer" value="eclipse-4.6.0" />
> <property name="efxclipseReleaseNameVer" value="efxclipse-2.4.0" />
>
> <target name="mirrorRepos" description="Builds the entire p2 mirror
> set.">
> <antcall target="createMirror" />
> </target>
>
> <target name="createMirror" description="Mirrors the Eclipse 4.6.0
> launcher feature and efxclispe 2.4.0 repository items. Turns them into
> runnables">
> <p2.mirror source="${eclipseRepository}" verbose="true"
> log="C:/TEMP/p2NeonMirror.log" validate="true"
> destination="file://${baseEclipseP2RepoHome}/site/${eclipseReleaseNameVer}"
>>
> <iu id="org.eclipse.equinox.executable.feature.group" />
> </p2.mirror>
> <p2.mirror source="${efxclipseRepository}" verbose="true"
> log="C:/TEMP/p2FXMirror.log" validate="true"
> destination="file://${baseEclipseP2RepoHome}/site/${efxclipseReleaseNameVer}"
>>
> <iu id="org.eclipse.fx.target.feature.feature.group" />
> </p2.mirror>
> <p2.repo2runnable>
> <repository
> location="file://${baseEclipseP2RepoHome}/runnable/${eclipseReleaseNameVer}"
> />
> <source>
> <repository
> location="file://${baseEclipseP2RepoHome}/site/${eclipseReleaseNameVer}" />
> </source>
> </p2.repo2runnable>
> <p2.repo2runnable>
> <repository
> location="file://${baseEclipseP2RepoHome}/runnable/${efxclipseReleaseNameVer}"
> />
> <source>
> <repository
> location="file://${baseEclipseP2RepoHome}/site/${efxclipseReleaseNameVer}"
> />
> </source>
> </p2.repo2runnable>
> </target>
> </project>
>
>
>
> Thanks for any help you can provide.

Re: Neon and 2.4.0 site target linux 64 bit problem [message #1737161 is a reply to message #1737157]

Wed, 06 July 2016 03:51

Eclipse User

BTW for the lookup the jar name is not relevant but the information in
the artifacts.jar/contents.jar.

Since 2.4.0 we also bundle the native-launcher into our target maybe
there's a mismatch now?

Tom

On 06.07.16 09:44, Tom Schindl wrote:
> Hi John,
>
> Can you file a bug for that. I'll try to track that down. Is your
> application a pure e4 and JavaFX app or a SWT-JavaFX mixed one?
>
> Tom
>
> On 05.07.16 22:52, John Bodkin wrote:
>> I was working with e(fx)clipse 2.3.0 and Mars 4.5.2 with no issues. I
>> moved to 2.4.0 and 4.6.0 today. I mirrored the targets. The runnable
>> target works fine but when I run the Maven-Tycho build (which depends on
>> the p2 site target) it states:
>> Missing requirement:
>> toolingorg.eclipse.equinox.launcher.gtk.linux.x86_64
>> 1.1.400.v20160518-1444 requires 'bundle
>> org.eclipse.equinox.launcher.gtk.linux.x86_64 1.1.400.v20160518-1444'
>> but it could not be found
>>
>> Notice the blank space between x86_64 and 1.1.400. The jar for this
>> platform executable is present except it has an underscore where the
>> blank space currently is. I tried renaming the bundle so it has the
>> space but the same error message is produced. I renamed it again to its
>> original name.
>>
>> I took linux gtk x86_64 out of the build and left the linux gtk x86 and
>> the win32 win32 x86_64 environments in the build. The build completes
>> successfully and the zip files have executables that launch.
>>
>> I also tried this using the remote site (instead of a local mirror) but
>> I get :
>> Missing requirement: toolingwin32.win32.x86_64org.eclipse.core.runtime
>> 1.0.0 requires 'bundle org.eclipse.core.runtime 3.12.0.v20160606-1342'
>> but it could not be found
>>
>> Here is my config pom:
>>
>> <?xml version="1.0" encoding="UTF-8"?>
>> <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>
>> <groupId>my.group.id</groupId>
>> <artifactId>my.group.id.artifact.id</artifactId>
>> <version>1.0.0-SNAPSHOT</version>
>> <packaging>pom</packaging>
>> <properties>
>> <tycho.version>0.25.0</tycho.version>
>> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
>> 
>> 
>>
>> <efxclipse.target>http://download.eclipse.org/efxclipse/runtime-released/2.4.0/site/</efxclipse.target>
>>
>>
>> <eclipse.target>http://download.eclipse.org/releases/neon</eclipse.target>
>> </properties>
>>
>> <repositories>
>> <repository>
>> <id>eclipse 4.6.0</id>
>> <url>${eclipse.target}</url>
>> <layout>p2</layout>
>> </repository>
>> <repository>
>> <id>e(fx)clipse 2.4.0</id>
>> <url>${efxclipse.target}</url>
>> <layout>p2</layout>
>> </repository>
>> </repositories>
>>
>> <build>
>> <plugins>
>> <plugin>
>> <groupId>org.eclipse.tycho</groupId>
>> <artifactId>tycho-maven-plugin</artifactId>
>> <version>${tycho.version}</version>
>> <extensions>true</extensions>
>> </plugin>
>>
>> <plugin>
>> <groupId>org.eclipse.tycho</groupId>
>> <artifactId>target-platform-configuration</artifactId>
>> <version>${tycho.version}</version>
>> <configuration>
>> <environments>
>> 
>> 
>> 
>> 
>> 
>> <environment>
>> <os>linux</os>
>> <ws>gtk</ws>
>> <arch>x86_64</arch>
>> </environment>
>> 
>> 
>> 
>> 
>> 
>> </environments>
>> </configuration>
>> </plugin>
>> </plugins>
>> </build>
>> </project>
>>
>>
>>
>> This is my script to mirror the repo. This worked just fine for the
>> 4.5.2 and 2.3.0 targets:
>>
>> <project name="Mirror" default="mirrorRepos">
>> 
>> <property name="efxclipseRepository"
>> value="http://download.eclipse.org/efxclipse/runtime-released/2.4.0/site" />
>>
>> <property name="eclipseRepository"
>> value="http://download.eclipse.org/releases/neon" />
>> 
>> <property name="baseP2RepoHome" value="C:/TEMP/target" />
>> <property name="baseEclipseP2RepoHome" value="${baseP2RepoHome}" />
>> 
>> <property name="eclipseReleaseNameVer" value="eclipse-4.6.0" />
>> <property name="efxclipseReleaseNameVer" value="efxclipse-2.4.0" />
>>
>> <target name="mirrorRepos" description="Builds the entire p2 mirror
>> set.">
>> <antcall target="createMirror" />
>> </target>
>>
>> <target name="createMirror" description="Mirrors the Eclipse 4.6.0
>> launcher feature and efxclispe 2.4.0 repository items. Turns them into
>> runnables">
>> <p2.mirror source="${eclipseRepository}" verbose="true"
>> log="C:/TEMP/p2NeonMirror.log" validate="true"
>> destination="file://${baseEclipseP2RepoHome}/site/${eclipseReleaseNameVer}"
>>>
>> <iu id="org.eclipse.equinox.executable.feature.group" />
>> </p2.mirror>
>> <p2.mirror source="${efxclipseRepository}" verbose="true"
>> log="C:/TEMP/p2FXMirror.log" validate="true"
>> destination="file://${baseEclipseP2RepoHome}/site/${efxclipseReleaseNameVer}"
>>>
>> <iu id="org.eclipse.fx.target.feature.feature.group" />
>> </p2.mirror>
>> <p2.repo2runnable>
>> <repository
>> location="file://${baseEclipseP2RepoHome}/runnable/${eclipseReleaseNameVer}"
>> />
>> <source>
>> <repository
>> location="file://${baseEclipseP2RepoHome}/site/${eclipseReleaseNameVer}" />
>> </source>
>> </p2.repo2runnable>
>> <p2.repo2runnable>
>> <repository
>> location="file://${baseEclipseP2RepoHome}/runnable/${efxclipseReleaseNameVer}"
>> />
>> <source>
>> <repository
>> location="file://${baseEclipseP2RepoHome}/site/${efxclipseReleaseNameVer}"
>> />
>> </source>
>> </p2.repo2runnable>
>> </target>
>> </project>
>>
>>
>>
>> Thanks for any help you can provide.
>

Re: Neon and 2.4.0 site target linux 64 bit problem [message #1737227 is a reply to message #1737157]

Wed, 06 July 2016 09:29

Eclipse User

it is pure e4 and JavaFX app

Re: Neon and 2.4.0 site target linux 64 bit problem [message #1737231 is a reply to message #1737227]

Wed, 06 July 2016 09:49

Eclipse User

So why do you reference the 4.6.0 repo? Can you remove that one?

Tom

On 06.07.16 15:29, John Bodkin wrote:
> it is pure e4 and JavaFX app

Re: Neon and 2.4.0 site target linux 64 bit problem [message #1737232 is a reply to message #1737161]

Wed, 06 July 2016 09:54

Eclipse User

I removed the <eclipse.target> from the config pom and it compiled successfully through Maven-Tycho. Produced a zip and a working executable for all platforms.

I doubt it matters but the neon versions on the executables is 1.1.400 and the executables in 2.4.0 are 1.1.300.

Thanks again for the assist.

[Updated on: Wed, 06 July 2016 13:32] by Moderator

Re: Neon and 2.4.0 site target linux 64 bit problem [message #1737237 is a reply to message #1737232]

Wed, 06 July 2016 10:01

Eclipse User

Well yes our target platform in the 2.4.0 release still contains Mars.1
(Mars.2 has had a regression) and we did not had time to upgrade our
target to neon for the 2.4.0 release.

The nightly builds for 3.0.0 just today was modified to use Neon.1.

Tom

On 06.07.16 15:54, John Bodkin wrote:
> I removed the <eclipse.target> from the config pom and it compiled
> successfully through Maven-Tycho. Produced a zip and a working
> executable for all platforms.
>
> I doubt it matters but the neon versions on the executables is 1.1.400
> and the executables in 2.4.0 are 1.1.300.
> Thanks again for the assist.

Previous Topic:	e(fx)clipse for Java 9
Next Topic:	OS X bundle provided at http://efxclipse.bestsolution.at/ not working

Goto Forum:

-=] Back to Top [=-

Current Time: Sat Jul 19 22:02:34 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter