[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] How to build plugin-based products with platform-specific fragments?
|
Tried it again, it doesn't work if I remove the fragment plugin.
If I am using the button add required plugins <plugin
id="org.eclipse.swt.win32.win32.x86" fragment="true"/>
is always added.
Removing it doesn't include it in the build. Furthermore other os/archs
aren't build correctly too.
Placing the plugins like the following works:
<plugin id="org.eclipse.swt.win32.win32.x86" fragment="true"/>
<plugin id="org.eclipse.swt.win32.win32.x86_64" fragment="true"/>
So the statement "Tycho no longer needs (and in fact ignores) the
ws/os/arch attributes in product files."
is correct but you need to put all fragments into the product configuration.
But I don't understand why the system can't use the environment
configurations.
In my opinion it would be a great update.
Am 20.03.2013 16:36, schrieb Christian Schulz:
Hmm...
I hope Tobias Oberlies will read our messages. I have added his message.
Okay it seems that the plugin based product supports the behaviour I
want.
@Tobias:
"Tycho no longer needs (and in fact ignores) the ws/os/arch attributes
in product files."
In my case I have to specify the attributes otherwise the fragments
aren't added. :/
Date: Mon, 18 Mar 2013 09:58:26 +0000
From: "Oberlies, Tobias"<tobias.oberlies@xxxxxxx>
To: Tycho user list<tycho-user@xxxxxxxxxxx>
Subject: Re: [tycho-user] How to build plugin-based products with
platform-specific fragments?
Message-ID:
<D9B0E18147535141AFBBA24DCD46D8F5070F474E@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"
I just noticed that the FAQ you referred had two parts, and the second
part has become obsolete:
Sincehttps://bugs.eclipse.org/bugs/show_bug.cgi?id=342890 has been
fixed, Tycho no longer needs (and in fact ignores) the ws/os/arch
attributes in product files.
You obviously still need to specify the ws/os/arch you want to build
for in the target-platform-configuration.
Now that this has been simplified, "How to build plugin-based products
with platform-specific fragments" should no longer be an FAQ, so I
deleted the entry from the FAQ wiki page.
Regards
Tobias
Am 20.03.2013 16:27, schrieb Justin Georgeson:
I guess I don't know why listing features vs plugins in the product
file makes a difference. As long as you have the native fragments for
all platforms resolvable and have all the platform environments
enabled, the feature should include all of them. The troubles I
described were when building the native fragment plugins, not when
building the features.
-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx
[mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Christian Schulz
Sent: Wednesday, March 20, 2013 10:23 AM
To: Tycho user list
Subject: Re: [tycho-user] How to build plugin-based products with
platform-specific fragments?
So in general it was a bad idea to switch to a feature based product? :/
How can I achieve to get the fragments packaged too?
At the moment I only see the possibility to switch back.
Perhaps I miss something out.
Am 20.03.2013 16:14, schrieb Justin Georgeson:
The problem I ran into with specifying all the platform environments
is that if I was on linux building a reactor which included the
native fragment bundles it would fail on the windows fragments
because the platform filter for those fragments (windows) didn't
apply to the OS (linux).
-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx
[mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Christian Schulz
Sent: Wednesday, March 20, 2013 10:10 AM
To: Tycho user list
Subject: Re: [tycho-user] How to build plugin-based products with
platform-specific fragments?
Hello Justin,
thanks for the explaination.
In my case the SWT fragments are missing.
The plugin based way was easy with including all plugins and
relation to the os/ws.
But it isn't the recommened way. So I switched to the feature based
product, because it should handle all on it own with a valid
environment configuration in the pom.xml.
I have following configuration for the environments:
<plugin>
<groupId>org.eclipse.tycho</groupId>
<artifactId>target-platform-configuration</artifactId>
<version>${tycho.version}</version>
<configuration>
<resolver>p2</resolver>
<pomDependencies>consider</pomDependencies>
<environments>
<environment>
<os>linux</os>
<ws>gtk</ws>
<arch>x86</arch>
</environment>
...
</configuration>
</plugin>
I thought it is enough to define something like that and tycho will
use the fragments, whcih are needed by the environment.
But it seems not to work.
In general I got some problems with the feature based product.
I got after successful build following exception:
java.lang.RuntimeException: Application "org.eclipse.ui.ide.workbench"
could not be found in the registry
I had to include as dependency org.eclipse.ui.ide.application. I
don't know why, but it works after it.
Perhaps I have something wrong in the tycho configuration or similar.
Cheers,
Chris
Am 20.03.2013 15:30, schrieb Justin Georgeson:
We have feature-based products with lots of native code to compile
into fragments. Our aggregator has profiles like linux-repo and
win-repo and the reactor includes all the plugins (host plugins,
fragment plugins, test plugins) and a special platform-specific
projects for a feature and a repository. These platform builds only
enable the tycho-platform-configuration environment that they're
building. So at the end of this reactor each platform build machine
has a P2 repo of the native fragments. We copy the windows fragment
p2 repo to the linux machine, then build a profile that includes
those platform-fragment p2 repos and the reactor has our shippable
features and products. And this feature/product reactor has all
tycho-platform-configuration environments enabled.
It means we're duplicating the compilation of the Java code on each
platform but I couldn't see an easy way to avoid that.
-----Original Message-----
From: tycho-user-bounces@xxxxxxxxxxx
[mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Christian Schulz
Sent: Wednesday, March 20, 2013 8:15 AM
To: tycho-user@xxxxxxxxxxx
Subject: Re: [tycho-user] How to build plugin-based products with
platform-specific fragments?
Hello,
now I have switched to a feature based product, but now I am facing
the same problem.
The platform-specific fragments are missing.
I had setted up the environments like described in my previous mail.
What is going wrong?
Cheers,
Chris
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
---------------------------------------------------------------------
- This e-mail, including any attached files, may contain confidential
and privileged information for the sole use of the intended
recipient. Any review, use, distribution, or disclosure by others
is strictly prohibited. If you are not the intended recipient (or
authorized to receive information for the intended recipient),
please contact the sender by reply e-mail and delete all copies of
this message.
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
