Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Buckminster dev » Headless (JUnit) launching
Headless (JUnit) launching [message #483832] Thu, 03 September 2009 09:42 Go to next message
Achim Demelt is currently offline Achim DemeltFriend
Messages: 160
Registered: July 2009
Senior Member
It seems that with Helios M2 we'll have all prerequisites for headless JUnit
launching available. I'll be ready to check in the Buckminster JUnit command
shortly after.

I have two questions, though:

1) If we build Galileo SR1 from trunk, I'd better not include the new bundle
in the o.e.buckminster.pde.headless feature, right? Otherwise I'll break the
build because of the 3.6 dependencies.

2) With a little extra effort --- and I mean _really_ little extra effort, <
4hrs --- I could provide not only JUnit launching, but _any_ kind of
launching from the headless workspace. Plain Java and OSGi launching will
come out-of-the-box. Launching any other kind of launch config will only
require that the respective LaunchConfigurationDelegates are installed in
the Buckminster headless host. What do think about that?

Regards,
Achim
Re: Headless (JUnit) launching [message #483839 is a reply to message #483832] Thu, 03 September 2009 10:08 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
Hi Achim,
Congratulations to the approval of all your hard work with the separation. I've been following the
dialog on Bugzilla and I know that this has been a significant effort.

Achim Demelt wrote:
> It seems that with Helios M2 we'll have all prerequisites for headless JUnit
> launching available. I'll be ready to check in the Buckminster JUnit command
> shortly after.
>
> I have two questions, though:
>
> 1) If we build Galileo SR1 from trunk, I'd better not include the new bundle
> in the o.e.buckminster.pde.headless feature, right? Otherwise I'll break the
> build because of the 3.6 dependencies.

We usually branch on demand. The demand arises when 3.6 diverges in such a way that API changes or
dependencies to 3.6 functionality are introduced. This is a good example of that. The
o.e.buckminster.pde.headless feature must be branched off to the Platform-3.5.x branch. So feel free
to create that branch.

Incidentally, we already have a CQUERY that will look into the Platform-3.5.x branch first and give
any components found there higher priority during resolution. That's the query to use when we do
continued work for the Galileo SR1 release.

The buckminster-dev.cquery and dogfood.rmap should change slightly also. As a quick fix I suggest
that you make buckminster-dev.cquery point to another rmap where you change the eclipse repos to the
ones where the milestones are staged.

Going forward, we need to provide a property that controls what Eclipse repository to use as input
for the target platform so that all work can share the same rmap. I'm doing some heavy experimenting
setting up the TP + Workspace in one go using a MSPEC import, it looks really promising and I expect
that the rmap refinement will come as a result of that work.

> 2) With a little extra effort --- and I mean _really_ little extra effort, <
> 4hrs --- I could provide not only JUnit launching, but _any_ kind of
> launching from the headless workspace. Plain Java and OSGi launching will
> come out-of-the-box. Launching any other kind of launch config will only
> require that the respective LaunchConfigurationDelegates are installed in
> the Buckminster headless host. What do think about that?
>
Sounds awesome. I'm all for it.

Regards,
Thomas Hallgren
Re: Headless (JUnit) launching [message #483851 is a reply to message #483839] Thu, 03 September 2009 11:34 Go to previous messageGo to next message
Achim Demelt is currently offline Achim DemeltFriend
Messages: 160
Registered: July 2009
Senior Member
I filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=288453 for the generic
launching facility. And I think code coverage with EclEmma is also within
reach, so I also filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=288455.

I'll now work with Chris to finish the PDE launching separation. After that,
I'll tackle the Buckminster commands.

Cheers,
Achim

Thomas Hallgren wrote:

> Hi Achim,
> Congratulations to the approval of all your hard work with the separation.
> I've been following the dialog on Bugzilla and I know that this has been a
> significant effort.
>
> Achim Demelt wrote:
>> It seems that with Helios M2 we'll have all prerequisites for headless
>> JUnit launching available. I'll be ready to check in the Buckminster
>> JUnit command shortly after.
>>
>> I have two questions, though:
>>
>> 1) If we build Galileo SR1 from trunk, I'd better not include the new
>> bundle in the o.e.buckminster.pde.headless feature, right? Otherwise I'll
>> break the build because of the 3.6 dependencies.
>
> We usually branch on demand. The demand arises when 3.6 diverges in such a
> way that API changes or dependencies to 3.6 functionality are introduced.
> This is a good example of that. The o.e.buckminster.pde.headless feature
> must be branched off to the Platform-3.5.x branch. So feel free to create
> that branch.
>
> Incidentally, we already have a CQUERY that will look into the
> Platform-3.5.x branch first and give any components found there higher
> priority during resolution. That's the query to use when we do continued
> work for the Galileo SR1 release.
>
> The buckminster-dev.cquery and dogfood.rmap should change slightly also.
> As a quick fix I suggest that you make buckminster-dev.cquery point to
> another rmap where you change the eclipse repos to the ones where the
> milestones are staged.
>
> Going forward, we need to provide a property that controls what Eclipse
> repository to use as input for the target platform so that all work can
> share the same rmap. I'm doing some heavy experimenting setting up the TP
> + Workspace in one go using a MSPEC import, it looks really promising and
> I expect that the rmap refinement will come as a result of that work.
>
>> 2) With a little extra effort --- and I mean _really_ little extra
>> effort, < 4hrs --- I could provide not only JUnit launching, but _any_
>> kind of launching from the headless workspace. Plain Java and OSGi
>> launching will come out-of-the-box. Launching any other kind of launch
>> config will only require that the respective LaunchConfigurationDelegates
>> are installed in the Buckminster headless host. What do think about that?
>>
> Sounds awesome. I'm all for it.
>
> Regards,
> Thomas Hallgren
Re: [buckminster-dev] Re: Headless (JUnit) launching [message #483857 is a reply to message #483851] Thu, 03 September 2009 11:52 Go to previous messageGo to next message
Oisin Hurley is currently offline Oisin HurleyFriend
Messages: 204
Registered: July 2009
Senior Member
I have to second Thomas' congratulations, Achim! It has been a lot of work
and getting the necessary approval and buy-in from the team is a great
achievement. Well done!

--oh
Re: [buckminster-dev] Re: Headless (JUnit) launching [message #483888 is a reply to message #483857] Thu, 03 September 2009 13:38 Go to previous messageGo to next message
Achim Demelt is currently offline Achim DemeltFriend
Messages: 160
Registered: July 2009
Senior Member
Thanks for the kudos! It's good to see that the Eclipse ecosystem is healthy
enough to enable such contributions.

Achim

Oisin Hurley wrote:

> I have to second Thomas' congratulations, Achim! It has been a lot of work
> and getting the necessary approval and buy-in from the team is a great
> achievement. Well done!
>
> --oh
Re: Headless (JUnit) launching [message #483907 is a reply to message #483832] Thu, 03 September 2009 14:41 Go to previous messageGo to next message
Carsten Reckord is currently offline Carsten ReckordFriend
Messages: 139
Registered: July 2009
Senior Member
Hi Achim,

Great work! We are using the Buckminster JUnit Command and refactored JDT and PDE from Google Code for a few weeks already and they are
working great. I assume the JUnit version in the google svn is not quite up-to-date? I've made a few changes against it, mostly some logging
in the TestListener and catching some configuration and launching errors in the command itself, should you be interested in a patch.

Two questions of my own, though:

1) Are there any plans/has there been any discussion about providing JUnit support as an actor instead of/in addition to a command?

2) Do you have a good way to deal with platform-specific settings in your launch configurations? We would've really liked to have launch
configurations that we can use both on our development boxes and on the ci server, so we can be reasonably sure that the tests we execute
locally are configured the same as on the server. However that's a bit problematic in light of platform-specific plugins like swt and
filesystem. Right now we provide a template launch configuration that contains all platform-specific plugins from all platforms and copy
that to create new configurations. Do you have a better idea to handle that? We don't want to use "All plug-ins and features" in the unit
tests, because we want to isolate the tests and plug-ins under test as much as possible during unit-testing. And "Add required plug-ins"
only adds requirements for my current platform.

Best regards,
Carsten

On 03.09.2009 11:42, Achim Demelt wrote:
> It seems that with Helios M2 we'll have all prerequisites for headless JUnit
> launching available. I'll be ready to check in the Buckminster JUnit command
> shortly after.
>
> I have two questions, though:
>
> 1) If we build Galileo SR1 from trunk, I'd better not include the new bundle
> in the o.e.buckminster.pde.headless feature, right? Otherwise I'll break the
> build because of the 3.6 dependencies.
>
> 2) With a little extra effort --- and I mean _really_ little extra effort, <
> 4hrs --- I could provide not only JUnit launching, but _any_ kind of
> launching from the headless workspace. Plain Java and OSGi launching will
> come out-of-the-box. Launching any other kind of launch config will only
> require that the respective LaunchConfigurationDelegates are installed in
> the Buckminster headless host. What do think about that?
>
> Regards,
> Achim
Re: Headless (JUnit) launching [message #483947 is a reply to message #483907] Thu, 03 September 2009 17:44 Go to previous messageGo to next message
Achim Demelt is currently offline Achim DemeltFriend
Messages: 160
Registered: July 2009
Senior Member
Carsten,

comments below.

> Hi Achim,
>
> Great work! We are using the Buckminster JUnit Command and refactored JDT
> and PDE from Google Code for a few weeks already and they are working
> great. I assume the JUnit version in the google svn is not quite
> up-to-date? I've made a few changes against it, mostly some logging in the
> TestListener and catching some configuration and launching errors in the
> command itself, should you be interested in a patch.
>

You're correct. The code at Google's SVN repo is terribly outdated. I have a
new version waiting to be checked into the Eclipse repository. In
particular, the new version writes XML output that is very similar to what
the regular JUnit Ant task produces. This output can be correctly parsed by
Bamboo and hopefully Hudson, too.

I'd be interested in your changes so that I can compare them to the changes
that I've made. Can you please file a bug in the Google Code project and
attach a patch with your changes?

> Two questions of my own, though:
>
> 1) Are there any plans/has there been any discussion about providing JUnit
> support as an actor instead of/in addition to a command?
>

There are no discussions or plans that I am aware of. Personally, I think
that launching is a workspace-related thing and as such, a command is the
best way to handle this. I may be wrong, though...

> 2) Do you have a good way to deal with platform-specific settings in your
> launch configurations? We would've really liked to have launch
> configurations that we can use both on our development boxes and on the ci
> server, so we can be reasonably sure that the tests we execute locally are
> configured the same as on the server. However that's a bit problematic in
> light of platform-specific plugins like swt and filesystem. Right now we
> provide a template launch configuration that contains all
> platform-specific plugins from all platforms and copy that to create new
> configurations. Do you have a better idea to handle that? We don't want to
> use "All plug-ins and features" in the unit tests, because we want to
> isolate the tests and plug-ins under test as much as possible during
> unit-testing. And "Add required plug-ins" only adds requirements for my
> current platform.
>

That's a good question. Honestly, I currently have no platform-dependent
bundles in my test launch configs. Off the top of my head I'd say that you
can safely run the configuration containing all platform-specific bundles.
Equinox should filter out any bundles that are not allowed to run on the
current platform. Have you tried that?

Cheers,
Achim

> Best regards,
> Carsten
>
> On 03.09.2009 11:42, Achim Demelt wrote:
>> It seems that with Helios M2 we'll have all prerequisites for headless
>> JUnit launching available. I'll be ready to check in the Buckminster
>> JUnit command shortly after.
>>
>> I have two questions, though:
>>
>> 1) If we build Galileo SR1 from trunk, I'd better not include the new
>> bundle in the o.e.buckminster.pde.headless feature, right? Otherwise I'll
>> break the build because of the 3.6 dependencies.
>>
>> 2) With a little extra effort --- and I mean _really_ little extra
>> effort, < 4hrs --- I could provide not only JUnit launching, but _any_
>> kind of launching from the headless workspace. Plain Java and OSGi
>> launching will come out-of-the-box. Launching any other kind of launch
>> config will only require that the respective LaunchConfigurationDelegates
>> are installed in the Buckminster headless host. What do think about that?
>>
>> Regards,
>> Achim
Re: Headless (JUnit) launching [message #483979 is a reply to message #483947] Thu, 03 September 2009 19:57 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
On 09/03/2009 07:44 PM, Achim Demelt wrote:

>> 1) Are there any plans/has there been any discussion about providing JUnit
>> support as an actor instead of/in addition to a command?
>>
>
> There are no discussions or plans that I am aware of. Personally, I think
> that launching is a workspace-related thing and as such, a command is the
> best way to handle this. I may be wrong, though...
>
One possible scenario where an actor would be handy is if you want run tests as part of a Buckminster perform. The JUnit
test action would be dependent on the eclipse.build action and run prior to assembling features, sites, etc. One nice
thing about that would be that the prerequisites, execution, and the results of the test would become part of the actual
build workflow.

We have an executor actor today, capable of running a shell or a bat script. Perhaps a 'launcher' actor could be created
that can do that and more?

Carsten, if you feel that there's a need for an actor like that, please enter an enhancement request in the bugzilla and
let's continue the discussion there.

Regards,
Thomas Hallgren
Re: Headless (JUnit) launching [message #484094 is a reply to message #483947] Fri, 04 September 2009 09:26 Go to previous messageGo to next message
Carsten Reckord is currently offline Carsten ReckordFriend
Messages: 139
Registered: July 2009
Senior Member
Hi Achim,

On 03.09.2009 19:44, Achim Demelt wrote:
>> Great work! We are using the Buckminster JUnit Command and refactored JDT
>> and PDE from Google Code for a few weeks already and they are working
>> great. I assume the JUnit version in the google svn is not quite
>> up-to-date? I've made a few changes against it, mostly some logging in the
>> TestListener and catching some configuration and launching errors in the
>> command itself, should you be interested in a patch.
>>
>
> You're correct. The code at Google's SVN repo is terribly outdated. I have a
> new version waiting to be checked into the Eclipse repository. In
> particular, the new version writes XML output that is very similar to what
> the regular JUnit Ant task produces. This output can be correctly parsed by
> Bamboo and hopefully Hudson, too.
>
> I'd be interested in your changes so that I can compare them to the changes
> that I've made. Can you please file a bug in the Google Code project and
> attach a patch with your changes?

Done. Issue #1 ;)

>> Two questions of my own, though:
>>
>> 1) Are there any plans/has there been any discussion about providing JUnit
>> support as an actor instead of/in addition to a command?
>>
>
> There are no discussions or plans that I am aware of. Personally, I think
> that launching is a workspace-related thing and as such, a command is the
> best way to handle this. I may be wrong, though...
>
>> 2) Do you have a good way to deal with platform-specific settings in your
>> launch configurations? We would've really liked to have launch
>> configurations that we can use both on our development boxes and on the ci
>> server, so we can be reasonably sure that the tests we execute locally are
>> configured the same as on the server. However that's a bit problematic in
>> light of platform-specific plugins like swt and filesystem. Right now we
>> provide a template launch configuration that contains all
>> platform-specific plugins from all platforms and copy that to create new
>> configurations. Do you have a better idea to handle that? We don't want to
>> use "All plug-ins and features" in the unit tests, because we want to
>> isolate the tests and plug-ins under test as much as possible during
>> unit-testing. And "Add required plug-ins" only adds requirements for my
>> current platform.
>>
>
> That's a good question. Honestly, I currently have no platform-dependent
> bundles in my test launch configs. Off the top of my head I'd say that you
> can safely run the configuration containing all platform-specific bundles.
> Equinox should filter out any bundles that are not allowed to run on the
> current platform. Have you tried that?

That's what we're doing right now. It works, but has a tendency to break if one is not very careful. For some reason, the Launch dialog
tends to alter the configuration just by opening and launching it. Although Delta packs are installed on all machines, that tends to break
the config for the other platform. Launching without the dialog (from Buckminster or the Favorites) works good, though.


Regards,
Carsten
Re: Headless (JUnit) launching [message #484106 is a reply to message #484094] Fri, 04 September 2009 10:28 Go to previous messageGo to next message
Achim Demelt is currently offline Achim DemeltFriend
Messages: 160
Registered: July 2009
Senior Member
>>
>> I'd be interested in your changes so that I can compare them to the
>> changes that I've made. Can you please file a bug in the Google Code
>> project and attach a patch with your changes?
>
> Done. Issue #1 ;)
>

Thanks for that. There are some parts that I consider including in the final
version. For IP reasons, I must ask you to attach the same patch to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=243293. Sorry for that, I
should have though of that before. But if I'm going to check in code based
on your suggestions, I have to make sure that you submitted that code via
Bugzilla.

>> That's a good question. Honestly, I currently have no platform-dependent
>> bundles in my test launch configs. Off the top of my head I'd say that
>> you can safely run the configuration containing all platform-specific
>> bundles. Equinox should filter out any bundles that are not allowed to
>> run on the current platform. Have you tried that?
>
> That's what we're doing right now. It works, but has a tendency to break
> if one is not very careful. For some reason, the Launch dialog tends to
> alter the configuration just by opening and launching it. Although Delta
> packs are installed on all machines, that tends to break the config for
> the other platform. Launching without the dialog (from Buckminster or the
> Favorites) works good, though.
>

I played around a bit with multi-platform launch configs. On my machine,
this works without any problems. Opening the launch config and running it
does not change the plug-in configuration.

Which version of Eclipse are you using?

Regards,
Achim
[buckminster-dev] product export [message #484408 is a reply to message #484106] Mon, 07 September 2009 12:07 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dieter.cailliau.barco.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA2FB3.BF495364
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I'm trying to use buckminster to export an eclipse product, but it's not =
clear to me how to do it.=20
1) there's the mailapp tutorial where i copied the product.ant and =
cspex, put this is not giving me an executable file anywhere.
2) using site.p2 there is a binaries folder with zips containing =
executables + swt lib for each platform, but when i extract the one i =
need and run it, it complains it can not find its companion jar.=20


DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

------_=_NextPart_001_01CA2FB3.BF495364
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IhMMAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEADwAAAHByb2R1 Y3QgZXhwb3J0AMMF
AQWAAwAOAAAA2QcJAAcADgAHABIAAQAYAQEggAMADgAAANkHCQAHAA4ABwAS AAEAGAEBCYABACEA
AAA2NThGQUQ2MDE2REU5QTRFQkY5ODE0QUZGQzFDQTRFMQCEBwEDkAYAXAkA ADkAAAADACYAAAAA
AAMANgAAAAAAQAA5AGRTSb+zL8oBHgA9AAEAAAABAAAAAAAAAAIBRwABAAAA MgAAAGM9QkU7YT1S
VFQ7cD1CQVJDTztsPUtORE1FWDAxLTA5MDkwNzEyMDcxOFotNzMxNzcAAAAe AEkAAQAAADEAAABb
YnVja21pbnN0ZXItZGV2XSBSZTogSGVhZGxlc3MgKEpVbml0KSBsYXVuY2hp bmcAAAAAQABOAIBz
s35KLcoBHgBaAAEAAAAkAAAAYnVja21pbnN0ZXItZGV2LWJvdW5jZXNAZWNs aXBzZS5vcmcAAgFb
AAEAAABlAAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAYnVja21pbnN0ZXIt ZGV2LWJvdW5jZXNA
ZWNsaXBzZS5vcmcAU01UUABidWNrbWluc3Rlci1kZXYtYm91bmNlc0BlY2xp cHNlLm9yZwAAAAAC
AVwAAQAAACkAAABTTVRQOkJVQ0tNSU5TVEVSLURFVi1CT1VOQ0VTQEVDTElQ U0UuT1JHAAAAAB4A
XQABAAAADQAAAEFjaGltIERlbWVsdAAAAAACAV4AAQAAAEEAAAAAAAAAgSsf pL6jEBmdbgDdAQ9U
AgAAAABBY2hpbSBEZW1lbHQAU01UUABhLmRlbWVsdEBleHhjZWxsZW50LmRl AAAAAAIBXwABAAAA
HAAAAFNNVFA6QS5ERU1FTFRARVhYQ0VMTEVOVC5ERQAeAGYAAQAAAAUAAABT TVRQAAAAAB4AZwAB
AAAAJAAAAGJ1Y2ttaW5zdGVyLWRldi1ib3VuY2VzQGVjbGlwc2Uub3JnAB4A aAABAAAABQAAAFNN
VFAAAAAAHgBpAAEAAAAXAAAAYS5kZW1lbHRAZXh4Y2VsbGVudC5kZQAAHgBw AAEAAAAPAAAAcHJv
ZHVjdCBleHBvcnQAAAIBcQABAAAAGwAAAAHKLUq2WHmLJSt84ki7jN/IZF0h VkAAmgeclgAeAHQA
AQAAABwAAABidWNrbWluc3Rlci1kZXZAZWNsaXBzZS5vcmcAHgAaDAEAAAAR AAAAQ2FpbGxpYXUs
IERpZXRlcgAAAAAeAB0OAQAAAA8AAABwcm9kdWN0IGV4cG9ydAAAAgEJEAEA AAD1AQAA8QEAAL4C
AABMWkZ1o0DxhwMACgByY3BnMTI14jIDQ3RleAVBAQMB9/8KgAKkA+QHEwKA D/MAUARWPwhVB7IR
JQ5RAwECAGNo4QrAc2V0MgYABsMRJfYzBEYTtzASLBEzCO8J97Y7GB8OMDUR IgxgYwBQMwsJAWQz
NhZQC6YgSUAnbSB0cnkLgGeRHSBvIHUUECBiGtD0a20LgHMOsAXAHaEOwNpw F8EgA5EFkGwFIB3h
ynADYGQa0HQsHgEFQMhpdCcEIG5vBUAfsI5lCsEdoQeAIGhvB+BtHaFkHbAg 8C4K4wqAMeopHSBo
BJBlIREjsSIA8wtwC2BwcB0gIMAFsAcxnCB3I8Ig4CFwb3AIkHZkJCMgJS4A cB9SJlBj7HNwDsAg
kHAgwSOwBADjIOAhJGdpdh1iIhEfcp54BZAgwAGgIZAgZgMQ1SmieSWDLiMk MiOQHdDnHWIAkA6w
LnAUQCOzKKJ+YR4AC4AKwAiQBCACEGzHBIElcCDwaCB6H9El8V8CMAtxHWIp +AQgKyxgd/sFQB/A
Yi4hBcAhoBPQIBD3C2AAMAWwbSCUJYEDoCXg/Q7BcgDQKEId8AIgJcI0APMm QSdycnUy8SCBIPAl
8f5tC1MokSFhA5EhQiqgJ4EvIPAvIjWwAHBpAiAgagsKwCMGfTjQAAAAHgA1 EAEAAAA+AAAAPDAy
OEFFOEE3QzA0RUUxNDg4OUJFOTlFNTQ1MEJFMzJEMDM2RUJBQkJAa25kbWV4 MDEuYmFyY28uY29t
PgAAAB4AORABAAAApQAAADxoN28zMXEkNGI4JDFAYnVpbGQuZWNsaXBzZS5v cmc+IDxoN29ram4k
YTcyJDFAYnVpbGQuZWNsaXBzZS5vcmc+IDxoN292OWwkcGMzJDFAYnVpbGQu ZWNsaXBzZS5vcmc+
IDxoN3FtZnAkOGM1JDFAYnVpbGQuZWNsaXBzZS5vcmc+IDxoN3FxNTYkb3Vn JDFAYnVpbGQuZWNs
aXBzZS5vcmc+AAAAAB4ARxABAAAADwAAAG1lc3NhZ2UvcmZjODIyAAALAPIQ AQAAAB8A8xABAAAA
JgAAAHAAcgBvAGQAdQBjAHQAIABlAHgAcABvAHIAdAAuAEUATQBMAAAAAAAL APYQAAAAAEAABzBV
wsjUsi/KAUAACDAeGE6/sy/KAQMA3j+vbwAAAwDxPwkEAAAeAPg/AQAAABEA AABDYWlsbGlhdSwg
RGlldGVyAAAAAAIB+T8BAAAARAAAAAAAAADcp0DIwEIQGrS5CAArL+GCAQAA AAAAAAAvTz1CQVJD
Ty9PVT1BRzAwMS9DTj1SRUNJUElFTlRTL0NOPURJRUMAHgD6PwEAAAAVAAAA U3lzdGVtIEFkbWlu
aXN0cmF0b3IAAAAAAgH7PwEAAAAeAAAAAAAAANynQMjAQhAatLkIACsv4YIB AAAAAAAAAC4AAAAD
AP0/5AQAAAMAGUAAAAAAAwAaQAAAAAADAB1AAAAAAAMAHkAAAAAAHgAwQAEA AAAFAAAARElFQwAA
AAAeADFAAQAAAAUAAABESUVDAAAAAB4AMkABAAAAJAAAAGJ1Y2ttaW5zdGVy LWRldi1ib3VuY2Vz
QGVjbGlwc2Uub3JnAB4AM0ABAAAAFwAAAGEuZGVtZWx0QGV4eGNlbGxlbnQu ZGUAAB4AOEABAAAA
BQAAAERJRUMAAAAAHgA5QAEAAAACAAAALgAAAAMAdkD/////CwApAAAAAAAL ACMAAAAAAAMABhBL
cU4RAwAHEFQBAAADABAQAAAAAAMAERABAAAAHgAIEAEAAABlAAAASU1UUllJ TkdUT1VTRUJVQ0tN
SU5TVEVSVE9FWFBPUlRBTkVDTElQU0VQUk9EVUNULEJVVElUU05PVENMRUFS VE9NRUhPV1RPRE9J
VDEpVEhFUkVTVEhFTUFJTEFQUFRVVE9SSQAAAAACAX8AAQAAAD4AAAA8MDI4 QUU4QTdDMDRFRTE0
ODg5QkU5OUU1NDUwQkUzMkQwMzZFQkFCQkBrbmRtZXgwMS5iYXJjby5jb20+ AAAA/FQ=

------_=_NextPart_001_01CA2FB3.BF495364--
Re: [buckminster-dev] product export [message #484453 is a reply to message #484408] Mon, 07 September 2009 14:10 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi Dieter,

The site.p2 action only creates a p2 repository. For a product you
should invoke the create.product or create.product.zip action. Those
will invoke the p2 director on the repository created by site.p2 to
create the actual product.

Best regards,
Johannes

Cailliau, Dieter schrieb:
> I'm trying to use buckminster to export an eclipse product, but it's not clear to me how to do it.
> 1) there's the mailapp tutorial where i copied the product.ant and cspex, put this is not giving me an executable file anywhere.
> 2) using site.p2 there is a binaries folder with zips containing executables + swt lib for each platform, but when i extract the one i need and run it, it complains it can not find its companion jar.
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
RE: [buckminster-dev] product export [message #484470 is a reply to message #484453] Mon, 07 September 2009 15:27 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dieter.cailliau.barco.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA2FCF.B7CAF243
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

The create.product you're talking about: is it the one specified in =
buckminster.cspex that actually calls the product.ant file (from the =
mailapp example), or is it some action that is specified "inside =
buckminster" (via <property key=3D"buildFileId" =
value=3D"buckminster.pdetasks"/>)? When i do it like in the mailapp i =
have no executable.




-----Original Message-----
From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
Sent: Mon 7/09/2009 16:10
To: buckminster-dev@eclipse.org
Subject: Re: [buckminster-dev] product export
=20
Hi Dieter,

The site.p2 action only creates a p2 repository. For a product you=20
should invoke the create.product or create.product.zip action. Those=20
will invoke the p2 director on the repository created by site.p2 to=20
create the actual product.

Best regards,
Johannes

Cailliau, Dieter schrieb:
> I'm trying to use buckminster to export an eclipse product, but it's =
not clear to me how to do it.=20
> 1) there's the mailapp tutorial where i copied the product.ant and =
cspex, put this is not giving me an executable file anywhere.
> 2) using site.p2 there is a binaries folder with zips containing =
executables + swt lib for each platform, but when i extract the one i =
need and run it, it complains it can not find its companion jar.=20
>=20
>=20
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message =
is privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.
_______________________________________________
buckminster-dev mailing list
buckminster-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/buckminster-dev




DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

------_=_NextPart_001_01CA2FCF.B7CAF243
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IiEPAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEAJQAAAFJFOiBb YnVja21pbnN0ZXIt
ZGV2XSBwcm9kdWN0IGV4cG9ydACfDQEFgAMADgAAANkHCQAHABEAGwAgAAEA PQEBIIADAA4AAADZ
BwkABwARABsAIAABAD0BAQmAAQAhAAAAMTFDOTYyMTcwRDgzNjI0NjkwNkE4 MEZERTBGOEY2MjMA
BQcBA5AGABQOAAA5AAAAAwAmAAAAAAADADYAAAAAAEAAOQBD8sq3zy/KAR4A PQABAAAABQAAAFJF
OiAAAAAAAgFHAAEAAAAyAAAAYz1CRTthPVJUVDtwPUJBUkNPO2w9S05ETUVY MDEtMDkwOTA3MTUy
NzMyWi03NDU1OQAAAB4ASQABAAAAJQAAAFJlOiBbYnVja21pbnN0ZXItZGV2 XSBwcm9kdWN0IGV4
cG9ydAAAAABAAE4AAFhCBMUvygEeAFoAAQAAACQAAABidWNrbWluc3Rlci1k ZXYtYm91bmNlc0Bl
Y2xpcHNlLm9yZwACAVsAAQAAAGUAAAAAAAAAgSsfpL6jEBmdbgDdAQ9UAgAA AABidWNrbWluc3Rl
ci1kZXYtYm91bmNlc0BlY2xpcHNlLm9yZwBTTVRQAGJ1Y2ttaW5zdGVyLWRl di1ib3VuY2VzQGVj
bGlwc2Uub3JnAAAAAAIBXAABAAAAKQAAAFNNVFA6QlVDS01JTlNURVItREVW LUJPVU5DRVNARUNM
SVBTRS5PUkcAAAAAHgBdAAEAAAAPAAAASm9oYW5uZXMgVXR6aWcAAAIBXgAB AAAAOwAAAAAAAACB
Kx+kvqMQGZ1uAN0BD1QCAAAAAEpvaGFubmVzIFV0emlnAFNNVFAAbWFpbEBq dXR6aWcuZGUAAAIB
XwABAAAAFAAAAFNNVFA6TUFJTEBKVVRaSUcuREUAHgBmAAEAAAAFAAAAU01U UAAAAAAeAGcAAQAA
ACQAAABidWNrbWluc3Rlci1kZXYtYm91bmNlc0BlY2xpcHNlLm9yZwAeAGgA AQAAAAUAAABTTVRQ
AAAAAB4AaQABAAAADwAAAG1haWxAanV0emlnLmRlAAAeAHAAAQAAACEAAABb YnVja21pbnN0ZXIt
ZGV2XSBwcm9kdWN0IGV4cG9ydAAAAAACAXEAAQAAABsAAAAByi/Fo2wl8/rC LEpC+5u9nJgyfnpx
AAJX8mMAHgB0AAEAAAAcAAAAYnVja21pbnN0ZXItZGV2QGVjbGlwc2Uub3Jn AB4AGgwBAAAAEQAA
AENhaWxsaWF1LCBEaWV0ZXIAAAAAHgAdDgEAAAAhAAAAW2J1Y2ttaW5zdGVy LWRldl0gcHJvZHVj
dCBleHBvcnQAAAAAAgEJEAEAAAArBgAAJwYAAE4KAABMWkZ16aJTNgMACgBy Y3BnMTI14jIDQ3Rl
eAVBAQMB9/8KgAKkA+QHEwKAD/MAUARWPwhVB7IRJQ5RAwECAGNo4QrAc2V0 MgYABsMRJfYzBEYT
tzASLBEzCO8J97Y7GB8OMDURIgxgYwBQMwsJAWQzNhZQC6YgVEhoZSAFAGVh DrAuWnADYGQa0AVA
eQhgJyUYICABkGxrC4BnIOMBoAhgdDogBAAfcAVAznQdAQIgHRBzcAWQBpAt CJBkH3ADoGIa0Gtt
RQuAcw6wci5jIGF4Lx/RHWAfAB3wdQdAbHnfHSAi4QQgH+IdpS4AcAVA9SCw bB0QKANSH9MAwAMQ
kGFwcCAOwGFtC1C4ZSksIBAFwB+EcwNwex0QIqFpAiAiRB+BIGgirSGBaQEA ISoiJNB2BzA8IDwd
oSBwACAjEGtlmHk9IiEwAxBkRiSh9ElkKkB2B0AKUCuCIVgGcAEAAZBza3Mi L2A+KT8gVx0AA6Bp
yCBkbx+ibGkrUCDy1yVKLtAT4HYdEG4vAA7A7wWQH0ABoCSwLgqiCoQyL9Uy cS0zwk8FEGcLgAdA
wwXQB5BzYWdlM8MypC5GA2EfYCE5LQEAdi1pHyFuYweQQAWQL1BwnRQQLgWw HvAnwWJlE+BMbGYg
EDjgSm8T4G7jIDAEIFV0ejQwMqQGYAsCMB9gTSfBNy8wOQYvAdA7MCAxNjox cwFAMrNUbzYPN5o6
FXVMYmoFkB9RUmUfYFvtNi1dI8Yl8XAXwTKkCuO1CoBILtBECJAhsSwyqv8c 8gCQHXIUQCeFAiAj
Ah1DfwQgKpBEQRggQUBD8QWweXguIEYFsUWxHbhB5XPOaAhgK9Ag8XZvL3Ef 4vcdPQWxHTwuOeAl
4CeERqD/HPBGMElAMqQD8CLwSKpEQfxkaRggHfAFsSfDSUBGCPsdJSDgYiMQ Q/ZGYEHlHTTvH9Mi
pCPHMqpCB5AFQBggumcLEXNC5Tk2MqpDJZH5L1BhdSaAQoQgUBPQCIGEYjoy pD4gSSclIfdGgB7S
UQF1TGEhOVDyQSR/HwADoDelI8YmgCEwKCF0/icEIDEABUA3sB1QWjMnUT9I UAfgUQEu80agV/Yx
KX8f0hggXJElSiLARmEHMSDud19iLsEFoHAgwiOeAHD3IOAh8yaAcFxBH+Af glyk/zRAKnAe4SdS
WwExRySEAHDueWEjMdVYUDJfMFlQHtL3UIdhNEWSYjRRCIEEIAIQ7yvQEoED 8B/gIEtxBCAFoF8C
MAtxHtIxOAQgKyBQd/0vMmJp4QXAHVAT0CPAC2B7ADAFsG1cFGEhLrIOwXK/ IqEf1y7QIDAg0WMS
cjdA/x+hJoAfsQWgJjELcR+TIzD/A6BcwiCwYyEfsGriJjAAcB0nsmoKwF6I dC5ESVOAQ0xBSU1F
Ulfn/lVE8DSxIPFOICMwUBJc0PtfYQPxZSaAH+ILgG3iHWD/J7JrBSDUZAMH gTTSH3IdoP9k0SSw
NPBwRGsBILABAAIw/wcxJoBjEh+CAjAJ8AEAd8E/RPJtEh/iWVI5AVIDZGTn GCAEEAngKHNfMDRg
B4D/cEEG4DDRYxJ34wQgYSAvAP8wsziQLqEgZSMyIxBWwB/g3WDBemHiLwBO QWVk0C+B/V5xSTjg
R6IKwDDiH8R9p/9OQQUgCJACMCaAhXZfYlBR/1zBIKQiVGagThGAASFxeTP/ JoCJwViwbOAfQESj
SmEq4O9Y039DeoljES9G0gJAbWH/B4ACMGQzitId8CMBHaFkEL9pYFARTBJJ QXNDg4FjN2D/BTBc
oi9BAaADEB+wfmSJg/8mIHryIzBZUVAziYIqcHCg/yNxbyAAgCFwAkBQJGQD igD/JZFGoQhwX1IE
YBggeHSQJvcu8AeRXMJ3CsCUMSKBI8L/KvF8BSYyUdKUNAQQRKOMRf942SaA MQAFwJdjH7GQpJFP
5YmhZQtgeXOFJzCzhIX/YfJ6ilsBmBAFsGOhXRFMYf9rA29FFBB94ZjknkGZ kyVStzS0TBIAcGse
EjHVX6Wv/6a/p4oypDYtJXMe0i9QIaA3qJ89XzKzaAJAN+A6L2ovNuEuN6kv JYIDgS+bqnJ40i82
LTKvCn2x0AAeADUQAQAAAD4AAAA8MDI4QUU4QTdDMDRFRTE0ODg5QkU5OUU1 NDUwQkUzMkQwMzZF
QkFCQ0BrbmRtZXgwMS5iYXJjby5jb20+AAAAHgA5EAEAAAD8AAAAPGg3bzMx cSQ0YjgkMUBidWls
ZC5lY2xpcHNlLm9yZz48aDdva2puJGE3MiQxQGJ1aWxkLmVjbGlwc2Uub3Jn Pgk8aDdvdjlsJHBj
MyQxQGJ1aWxkLmVjbGlwc2Uub3JnPjxoN3FtZnAkOGM1JDFAYnVpbGQuZWNs aXBzZS5vcmc+CTxo
N3FxNTYkb3VnJDFAYnVpbGQuZWNsaXBzZS5vcmc+PG1haWxtYW4uMC4xMjUy MzI1MjQzLjE4OTg0
LmJ1Y2ttaW5zdGVyLWRldkBlY2xpcHNlLm9yZz4gPGg4MzQ5diRuNjYkMUBi dWlsZC5lY2xpcHNl
Lm9yZz4AHgBHEAEAAAAPAAAAbWVzc2FnZS9yZmM4MjIAAAsA8hABAAAAHwDz EAEAAABWAAAAUgBF
ACUAMwBBACAAWwBiAHUAYwBrAG0AaQBuAHMAdABlAHIALQBkAGUAdgBdACAA cAByAG8AZAB1AGMA
dAAgAGUAeABwAG8AcgB0AC4ARQBNAEwAAAAAAAsA9hAAAAAAQAAHMD2yNAPP L8oBQAAIMP22z7fP
L8oBAwDeP69vAAADAPE/CQQAAB4A+D8BAAAAEQAAAENhaWxsaWF1LCBEaWV0 ZXIAAAAAAgH5PwEA
AABEAAAAAAAAANynQMjAQhAatLkIACsv4YIBAAAAAAAAAC9PPUJBUkNPL09V PUFHMDAxL0NOPVJF
Q0lQSUVOVFMvQ049RElFQwAeAPo/AQAAABUAAABTeXN0ZW0gQWRtaW5pc3Ry YXRvcgAAAAACAfs/
AQAAAB4AAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAALgAAAAMA/T/k BAAAAwAZQAAAAAAD
ABpAAAAAAAMAHUAAAAAAAwAeQAAAAAAeADBAAQAAAAUAAABESUVDAAAAAB4A MUABAAAABQAAAERJ
RUMAAAAAHgAyQAEAAAAkAAAAYnVja21pbnN0ZXItZGV2LWJvdW5jZXNAZWNs aXBzZS5vcmcAHgAz
QAEAAAAPAAAAbWFpbEBqdXR6aWcuZGUAAB4AOEABAAAABQAAAERJRUMAAAAA HgA5QAEAAAACAAAA
LgAAAAMAdkD/////CwApAAAAAAALACMAAAAAAAMABhB+a1N5AwAHEPAGAAAD ABAQAAAAAAMAERAA
AAAAHgAIEAEAAABlAAAAVEhFQ1JFQVRFUFJPRFVDVFlPVVJFVEFMS0lOR0FC T1VUOklTSVRUSEVP
TkVTUEVDSUZJRURJTkJVQ0tNSU5TVEVSQ1NQRVhUSEFUQUNUVUFMTFlDQUxM U1RIRVBST0RVQ1RB
TgAAAAACAX8AAQAAAD4AAAA8MDI4QUU4QTdDMDRFRTE0ODg5QkU5OUU1NDUw QkUzMkQwMzZFQkFC
Q0BrbmRtZXgwMS5iYXJjby5jb20+AAAAYQA=

------_=_NextPart_001_01CA2FCF.B7CAF243--
Re: [buckminster-dev] product export [message #484471 is a reply to message #484470] Mon, 07 September 2009 15:29 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
It's the one specified in the cspecx. It requires though that your
version of buckminster includes the p2 director application (should be
the case with the latest updates AFAIK).


Best regards,
Johannes

Cailliau, Dieter schrieb:
> The create.product you're talking about: is it the one specified in buckminster.cspex that actually calls the product.ant file (from the mailapp example), or is it some action that is specified "inside buckminster" (via <property key="buildFileId" value="buckminster.pdetasks"/>)? When i do it like in the mailapp i have no executable.
>
>
>
>
> -----Original Message-----
> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
> Sent: Mon 7/09/2009 16:10
> To: buckminster-dev@eclipse.org
> Subject: Re: [buckminster-dev] product export
>
> Hi Dieter,
>
> The site.p2 action only creates a p2 repository. For a product you
> should invoke the create.product or create.product.zip action. Those
> will invoke the p2 director on the repository created by site.p2 to
> create the actual product.
>
> Best regards,
> Johannes
>
> Cailliau, Dieter schrieb:
>> I'm trying to use buckminster to export an eclipse product, but it's not clear to me how to do it.
>> 1) there's the mailapp tutorial where i copied the product.ant and cspex, put this is not giving me an executable file anywhere.
>> 2) using site.p2 there is a binaries folder with zips containing executables + swt lib for each platform, but when i extract the one i need and run it, it complains it can not find its companion jar.
>>
>>
>> DISCLAIMER:
>> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
>
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
Re: [buckminster-dev] product export [message #484485 is a reply to message #484471] Mon, 07 September 2009 17:14 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
One reason for the executable not to show up is that the platform is incorrectly specified. Ideally, the build should be
performed in two steps:

1. Build the site.p2 with target.ws, target.os, and target.arch all set to '*'. This will ensure that the repository
contains launchers and other platform specific code for all platforms.

2. Run the create.product with target.ws, target.os, and target.arch explicitly set to reflect the platform for which
you want to create the executable. Using '*' in this step will not work. No executable will be present in the result.

HTH,
Thomas Hallgren


On 09/07/2009 05:29 PM, Johannes Utzig wrote:
> It's the one specified in the cspecx. It requires though that your
> version of buckminster includes the p2 director application (should be
> the case with the latest updates AFAIK).
>
>
> Best regards,
> Johannes
>
> Cailliau, Dieter schrieb:
>> The create.product you're talking about: is it the one specified in
>> buckminster.cspex that actually calls the product.ant file (from the
>> mailapp example), or is it some action that is specified "inside
>> buckminster" (via <property key="buildFileId"
>> value="buckminster.pdetasks"/>)? When i do it like in the mailapp i
>> have no executable.
>>
>>
>>
>>
>> -----Original Message-----
>> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
>> Sent: Mon 7/09/2009 16:10
>> To: buckminster-dev@eclipse.org
>> Subject: Re: [buckminster-dev] product export
>>
>> Hi Dieter,
>>
>> The site.p2 action only creates a p2 repository. For a product you
>> should invoke the create.product or create.product.zip action. Those
>> will invoke the p2 director on the repository created by site.p2 to
>> create the actual product.
>>
>> Best regards,
>> Johannes
>>
>> Cailliau, Dieter schrieb:
>>> I'm trying to use buckminster to export an eclipse product, but it's
>>> not clear to me how to do it. 1) there's the mailapp tutorial where i
>>> copied the product.ant and cspex, put this is not giving me an
>>> executable file anywhere.
>>> 2) using site.p2 there is a binaries folder with zips containing
>>> executables + swt lib for each platform, but when i extract the one i
>>> need and run it, it complains it can not find its companion jar.
>>>
>>> DISCLAIMER:
>>> Unless indicated otherwise, the information contained in this message
>>> is privileged and confidential, and is intended only for the use of
>>> the addressee(s) named above and others who have been specifically
>>> authorized to receive it. If you are not the intended recipient, you
>>> are hereby notified that any dissemination, distribution or copying
>>> of this message and/or attachments is strictly prohibited. The
>>> company accepts no liability for any damage caused by any virus
>>> transmitted by this email. Furthermore, the company does not warrant
>>> a proper and complete transmission of this information, nor does it
>>> accept liability for any delays. If you have received this message in
>>> error, please contact the sender and delete the message. Thank you.
>> _______________________________________________
>> buckminster-dev mailing list
>> buckminster-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>
>>
>>
>>
>> DISCLAIMER:
>> Unless indicated otherwise, the information contained in this message
>> is privileged and confidential, and is intended only for the use of
>> the addressee(s) named above and others who have been specifically
>> authorized to receive it. If you are not the intended recipient, you
>> are hereby notified that any dissemination, distribution or copying of
>> this message and/or attachments is strictly prohibited. The company
>> accepts no liability for any damage caused by any virus transmitted by
>> this email. Furthermore, the company does not warrant a proper and
>> complete transmission of this information, nor does it accept
>> liability for any delays. If you have received this message in error,
>> please contact the sender and delete the message. Thank you.
RE: [buckminster-dev] product export solved [message #484487 is a reply to message #484471] Mon, 07 September 2009 17:37 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dieter.cailliau.barco.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA2FE1.D8F8374C
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have an executable now, i think what fixed it, is specifying these for =
my platform (instead of "*")

target.os=3Dlinux
target.ws=3Dgtk
target.arch=3Dx86

Next i got this when starting the exported product:

java.lang.IllegalStateException: Unable to acquire application service. =
Ensure that the org.eclipse.core.runtime bundle is resolved and started =
(see config.ini).

The solution was to add this in my product file (i did not have this =
because i'm migrating from eclipse 3.2)

<configurations>
<plugin id=3D"org.eclipse.equinox.app" autoStart=3D"true" =
startLevel=3D"4" />
</configurations>


-----Original Message-----
From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
Sent: Mon 7/09/2009 17:29
To: buckminster-dev@eclipse.org
Subject: Re: [buckminster-dev] product export
=20
It's the one specified in the cspecx. It requires though that your=20
version of buckminster includes the p2 director application (should be=20
the case with the latest updates AFAIK).


Best regards,
Johannes

Cailliau, Dieter schrieb:
> The create.product you're talking about: is it the one specified in =
buckminster.cspex that actually calls the product.ant file (from the =
mailapp example), or is it some action that is specified "inside =
buckminster" (via <property key=3D"buildFileId" =
value=3D"buckminster.pdetasks"/>)? When i do it like in the mailapp i =
have no executable.
>=20
>=20
>=20
>=20
> -----Original Message-----
> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
> Sent: Mon 7/09/2009 16:10
> To: buckminster-dev@eclipse.org
> Subject: Re: [buckminster-dev] product export
> =20
> Hi Dieter,
>=20
> The site.p2 action only creates a p2 repository. For a product you=20
> should invoke the create.product or create.product.zip action. Those=20
> will invoke the p2 director on the repository created by site.p2 to=20
> create the actual product.
>=20
> Best regards,
> Johannes
>=20
> Cailliau, Dieter schrieb:
>> I'm trying to use buckminster to export an eclipse product, but it's =
not clear to me how to do it.=20
>> 1) there's the mailapp tutorial where i copied the product.ant and =
cspex, put this is not giving me an executable file anywhere.
>> 2) using site.p2 there is a binaries folder with zips containing =
executables + swt lib for each platform, but when i extract the one i =
need and run it, it complains it can not find its companion jar.=20
>>
>>
>> DISCLAIMER:
>> Unless indicated otherwise, the information contained in this message =
is privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>=20
>=20
>=20
>=20
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message =
is privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.
_______________________________________________
buckminster-dev mailing list
buckminster-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/buckminster-dev




DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

------_=_NextPart_001_01CA2FE1.D8F8374C
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IhMRAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEALAAAAFJFOiBb YnVja21pbnN0ZXIt
ZGV2XSBwcm9kdWN0IGV4cG9ydCBzb2x2ZWQATBABBYADAA4AAADZBwkABwAT ACUAEgABADsBASCA
AwAOAAAA2QcJAAcAEwAlABIAAQA7AQEJgAEAIQAAADAxMTJDM0U1MUEwOENC NDg4ODRGRkM0ODNC
MEMwOUJGADcHAQOQBgAwEQAAOQAAAAMAJgAAAAAAAwA2AAAAAABAADkATDf4 2OEvygEeAD0AAQAA
AAUAAABSRTogAAAAAAIBRwABAAAAMgAAAGM9QkU7YT1SVFQ7cD1CQVJDTzts PUtORE1FWDAxLTA5
MDkwNzE3MzcxOFotNzQ4MDYAAAAeAEkAAQAAACUAAABSZTogW2J1Y2ttaW5z dGVyLWRldl0gcHJv
ZHVjdCBleHBvcnQAAAAAQABOAABPo/vPL8oBHgBaAAEAAAAkAAAAYnVja21p bnN0ZXItZGV2LWJv
dW5jZXNAZWNsaXBzZS5vcmcAAgFbAAEAAABlAAAAAAAAAIErH6S+oxAZnW4A 3QEPVAIAAAAAYnVj
a21pbnN0ZXItZGV2LWJvdW5jZXNAZWNsaXBzZS5vcmcAU01UUABidWNrbWlu c3Rlci1kZXYtYm91
bmNlc0BlY2xpcHNlLm9yZwAAAAACAVwAAQAAACkAAABTTVRQOkJVQ0tNSU5T VEVSLURFVi1CT1VO
Q0VTQEVDTElQU0UuT1JHAAAAAB4AXQABAAAADwAAAEpvaGFubmVzIFV0emln AAACAV4AAQAAADsA
AAAAAAAAgSsfpL6jEBmdbgDdAQ9UAgAAAABKb2hhbm5lcyBVdHppZwBTTVRQ AG1haWxAanV0emln
LmRlAAACAV8AAQAAABQAAABTTVRQOk1BSUxASlVUWklHLkRFAB4AZgABAAAA BQAAAFNNVFAAAAAA
HgBnAAEAAAAkAAAAYnVja21pbnN0ZXItZGV2LWJvdW5jZXNAZWNsaXBzZS5v cmcAHgBoAAEAAAAF
AAAAU01UUAAAAAAeAGkAAQAAAA8AAABtYWlsQGp1dHppZy5kZQAAHgBwAAEA AAAoAAAAW2J1Y2tt
aW5zdGVyLWRldl0gcHJvZHVjdCBleHBvcnQgc29sdmVkAAIBcQABAAAAGwAA AAHKL9AbKAmD+34X
SEj7t8Pg037Ukl0AAkuf2gAeAHQAAQAAABwAAABidWNrbWluc3Rlci1kZXZA ZWNsaXBzZS5vcmcA
HgAaDAEAAAARAAAAQ2FpbGxpYXUsIERpZXRlcgAAAAAeAB0OAQAAACgAAABb YnVja21pbnN0ZXIt
ZGV2XSBwcm9kdWN0IGV4cG9ydCBzb2x2ZWQAAgEJEAEAAADWCAAA0ggAAAgT AABMWkZ17lGsEwMA
CgByY3BnMTI14jIDQ3RleAVBAQMB9/8KgAKkA+QHEwKAD/MAUARWPwhVB7IR JQ5RAwECAGNo4QrA
c2V0MgYABsMRJfYzBEYTtzASLBEzCO8J97Y7GB8OMDURIgxgYwBQMwsJAWQz NhZQC6YgSeIgE+B2
ZSADkQ7ABZAKdQGRbB1Abm93LCAgaSB0aAuAayCmdxPgBUBmaR2gZB6AZnQe cQQgc3AFkAaQeX0L
gGceoQeQHUACEAXAbRx5IAtRADAFsG0gKBULgHMOsGEfoG9mIPAiKiIpCqIK hAqAAZAEcmcUIC5v
cz1sKQuAdXgjq3ckgGd0DmsjqwrAE9A9eDg2zyNKB8AO0R6QZ28FQB6x3wQg HxAJ8CAgJAF0IKUd
gVZwF8EfkXADYGQa0HTKOiNKah0gYS4LYCCwqC5JbB4QZwdAUwGQoQ6wRXhj ZQUwaQIgkDogVW4d
83RvHVCwY3F1aRggHVBwC1BfDeAfMC3hICAEkHYN4GX4LiBFAIAIcC6BHyIq Eq8FsCygBZAkoHAU
EC4FoZkwcHJ1AjAHcSBiMsDuZB4RIAEYIHMG8B0wH6DvAHAfoCmDH5EoFBAd QAWgjm4fYCygC4Bp
KS4jSp5UKiEz8R3QL9J3YQQg/S6iZB+gKOMLgCFzKvQfUeMeESJAIGRpH6Ae QAVASx0TKONiBZBh
dSERaeonIiBtNbByL7EgsQNSQx2AMfQgMy4yIzsgnT5wPDV0CHAvs3M+Phcz PnILUHVnOME6MD0i
bTGqZS7xHkB4JuAvYCK7HVAd0G8tMQAgQQB0MrCmZUKQKYNMZR0wbEEAyjRC kC8/mDwvPr8jaPUj
RC1Hkk8FEEChB0AF0LkHkHNhJDBHkyNERgNhMy4QMzBjazwAImJyLTkBAHYt BuAywC2gc0C/MeYx
oSLAA6A7QBPgbCLgSSLRSm8T4G5uB5FVfHR6NbAjRAZgAjAuEE3BL+E3LzA5 LwHQTwBAIDE3OjI5
NpVvx0nfS2pN5XViagWQTnHUUmUuEFtJ/V05FypU4z4VI0RJdCc34TFyTVDf ICUIkB+hA6AqEmMg
MkJAPxzgBUAYIC7zVlIIYGdo/TEEeQhhVbUdMBQAL9Ii0bdJ+TixMfB1AQBW VHAUQH86IBggKzAF
sS9aNSBZUWz/H6A7QFW1V8M30B1AA/AesI8qAyHBB5AFQHVwZGCyYRDARkFJ SzYcI0RCz2DSGCAt
AAsgcywjRE0GXSNKQwtwLNAHMHUecERXCJBb4gTwaAiBYitVPt4gNvIFACKQ DrAuOSZaAfYnMOIH
QGsgogGgCGBOcb84kjFFVs5J+TJQIDF4MQTpANB0dQdAbCGQL6As0P9clSr0 JuACMDmVPKMqEgDA
JwMQL1EdgWFtC1BlKf8ecAWxajQz8DMBbVEv0jET+yAHV1IiIlE6MDMSShdC kPooMEBhQFEDYCBA
ACAhkDhrZXlBADMwAxBkRvk5sUlkQpAsQApBdjJsCEdhIBQgN9BrcyJEsCn4 PyBXKUI6AS6wamEk
oP92AFeGcDYekB0THkAdiTYl/2eAfJ99rUefSK1ngEmfSq8/S79Mz03VZ4BO T09SNjr+MQFAZzZQ
T1FfhcNSn1Ov91S+Z4B+B0gekGY0Y+V9+P828x/AaDEUQHI1AiBtsmfzfwQg dUBc8RggKnCQQQWw
ef0wgEZdgjkXWgF+B16FC4B8dm96IVfDZ/wFsWfsLv9NsHCQcjQwgDbwJHBf BmeA/wPwLNCVGlz6
cnMdQJJYZ9X/XtEhkJBGLqFnJmfkKgNtVP9ud32eYy9nYmRcffhln2at/WeA STvRQ2AglC6wO4Jb
av8uoSpUHVM9BSrlHnAzMChh/1YyOmIx8CKQp5MzAVlQB+DPLqF5ozCApUcx KSDSGCD/VkVwNm1w
XXEHMSkiLyEekH0FoHBXUm5ONGJsox5wcP+poTh0qgRAoDBAILFyAh17+zmj AHB5rpOf1meAPZCm
oe8gop0XrqSR4mJ/oQiBBCD/AhBewBKBYBOX4QQgNXEBkK814SCxHZgEICsg IHd54v5iITMikBPQ
IaepdCkzHpD/DsE8MDlxapYekE1QNDUysf8ftKpBA3ALU2pDL6ADoDpi/x9g NHEfwLhicOAAcC/S
LCAPbICr98GupEBJU0NM8WGwTUVSpTguMLmxOKK/OiAvoR+RKLCs0QPxZR5w /yoSC4Ah8i+0uIVX
ZiABB4H/SKIf8irgskEs4TQ1NXMBAP8y0QdAHnA0YjiTDrAzUMVS/5FCIUIq EjuCItGeszhAM9H/
NTE1IKygLkAHgDRBBuAdM//FZSkSLrAdEztAKVJXBG3i7yGQQrFZUAUQeq9S LrBdQe5lskAzgavR
SSLgk/IKwP8eIjFEy0ddQQUgCJACMB5w/9MWrNKc4TphVzRtBLQQOhH/zaGB 0S+zHnDXYUNgumA3
ZL+WwnWQIJPM48gpNGEvXYL/AkC64QeAAjCxo9hyKzBtsf8q4R7AtuAqoZiC NVLA0tEh/mMtoqoC
efEBoAMQH8DMBP/XI3DQyJI7Y5zD1yIwQDKw/zfhPDAAgDwAAkCctCjj16D/ o8GS8QhwrMIEYBgg
xhTdxu95oAeROmI3wHLh0W0xKtL/daHJpXDinoLh1AQQWvU4df/Glx5wHkAF wOUDamHeRN7v49dB
REBheXPSxx0T0iX/OFXIVx1x5bAFsLERqnEhEf+4g7zFFBDLgeaE6+HnM3AC v4AEmIIAcB7wWgGf
11/zb//0f/VKZyaBnXAjIKIkoCJwN/ZfiO+Fd2gCQDIgOi9uL4JRMdcxoS9w MgOBL/v4UsZyL4Gd
fZ//X2dEwz//xF/Fb8Z/x4/In8mvyr/Lz//M383vzv/QD9Ef0i/TP9RP/9Vf 1m/Xf9iP2Z/ar9u/
3M//3d/qv9//4Q/iH+Mv5D/lT//mX+dv6H/pj+qf66/sv+3P/+7f7+/w//IP X1H1TzJP9Y//X2D2
3/fv+R9RjvtP/F/9bwv+eTxKfT1wAAAeADUQAQAAAD4AAAA8MDI4QUU4QTdD MDRFRTE0ODg5QkU5
OUU1NDUwQkUzMkQwMzZFQkFCREBrbmRtZXgwMS5iYXJjby5jb20+AAAAHgA5 EAEAAABWAQAAPGg3
bzMxcSQ0YjgkMUBidWlsZC5lY2xpcHNlLm9yZz48aDdva2puJGE3MiQxQGJ1 aWxkLmVjbGlwc2Uu
b3JnPgk8aDdvdjlsJHBjMyQxQGJ1aWxkLmVjbGlwc2Uub3JnPjxoN3FtZnAk OGM1JDFAYnVpbGQu
ZWNsaXBzZS5vcmc+CTxoN3FxNTYkb3VnJDFAYnVpbGQuZWNsaXBzZS5vcmc+ PG1haWxtYW4uMC4x
MjUyMzI1MjQzLjE4OTg0LmJ1Y2ttaW5zdGVyLWRldkBlY2xpcHNlLm9yZz4J PGg4MzQ5diRuNjYk
MUBidWlsZC5lY2xpcHNlLm9yZz4gPG1haWxtYW4uMS4xMjUyMzM3MjU1LjE4 OTg0LmJ1Y2ttaW5z
dGVyLWRldkBlY2xpcHNlLm9yZz4gPGg4Mzh0NCRvOW8kMUBidWlsZC5lY2xp cHNlLm9yZz4AAAAe
AEcQAQAAAA8AAABtZXNzYWdlL3JmYzgyMgAACwDyEAEAAAAfAPMQAQAAAGQA AABSAEUAJQAzAEEA
IABbAGIAdQBjAGsAbQBpAG4AcwB0AGUAcgAtAGQAZQB2AF0AIABwAHIAbwBk AHUAYwB0ACAAZQB4
AHAAbwByAHQAIABzAG8AbAB2AGUAZAAuAEUATQBMAAAACwD2EAAAAABAAAcw 8YWlSdkvygFAAAgw
Bvz82OEvygEDAN4/r28AAAMA8T8JBAAAHgD4PwEAAAARAAAAQ2FpbGxpYXUs IERpZXRlcgAAAAAC
Afk/AQAAAEQAAAAAAAAA3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAAL089QkFS Q08vT1U9QUcwMDEv
Q049UkVDSVBJRU5UUy9DTj1ESUVDAB4A+j8BAAAAFQAAAFN5c3RlbSBBZG1p bmlzdHJhdG9yAAAA
AAIB+z8BAAAAHgAAAAAAAADcp0DIwEIQGrS5CAArL+GCAQAAAAAAAAAuAAAA AwD9P+QEAAADABlA
AAAAAAMAGkAAAAAAAwAdQAAAAAADAB5AAAAAAB4AMEABAAAABQAAAERJRUMA AAAAHgAxQAEAAAAF
AAAARElFQwAAAAAeADJAAQAAACQAAABidWNrbWluc3Rlci1kZXYtYm91bmNl c0BlY2xpcHNlLm9y
ZwAeADNAAQAAAA8AAABtYWlsQGp1dHppZy5kZQAAHgA4QAEAAAAFAAAARElF QwAAAAAeADlAAQAA
AAIAAAAuAAAAAwB2QP////8LACkAAAAAAAsAIwAAAAAAAwAGEB25e2sDAAcQ JQ0AAAMAEBAAAAAA
AwAREAAAAAAeAAgQAQAAAGUAAABJSEFWRUFORVhFQ1VUQUJMRU5PVyxJVEhJ TktXSEFURklYRURJ
VCxJU1NQRUNJRllJTkdUSEVTRUZPUk1ZUExBVEZPUk0oSU5TVEVBRE9GIioi KVRBUkdFVE9TPUxJ
TlVYVEFSAAAAAAIBfwABAAAAPgAAADwwMjhBRThBN0MwNEVFMTQ4ODlCRTk5 RTU0NTBCRTMyRDAz
NkVCQUJEQGtuZG1leDAxLmJhcmNvLmNvbT4AAAB9cg==

------_=_NextPart_001_01CA2FE1.D8F8374C--
Re: [buckminster-dev] product export solved [message #484493 is a reply to message #484487] Mon, 07 September 2009 18:18 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
Hmm, that one should have been fixed already. What version of Buckminster are you using (the PDE support in particular)?

Regards,
Thomas Hallgren

On 09/07/2009 07:37 PM, Cailliau, Dieter wrote:
> I have an executable now, i think what fixed it, is specifying these for my platform (instead of "*")
>
> target.os=linux
> target.ws=gtk
> target.arch=x86
>
> Next i got this when starting the exported product:
>
> java.lang.IllegalStateException: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini).
>
> The solution was to add this in my product file (i did not have this because i'm migrating from eclipse 3.2)
>
> <configurations>
> <plugin id="org.eclipse.equinox.app" autoStart="true" startLevel="4" />
> </configurations>
>
>
> -----Original Message-----
> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
> Sent: Mon 7/09/2009 17:29
> To: buckminster-dev@eclipse.org
> Subject: Re: [buckminster-dev] product export
>
> It's the one specified in the cspecx. It requires though that your
> version of buckminster includes the p2 director application (should be
> the case with the latest updates AFAIK).
>
>
> Best regards,
> Johannes
>
> Cailliau, Dieter schrieb:
>> The create.product you're talking about: is it the one specified in buckminster.cspex that actually calls the product.ant file (from the mailapp example), or is it some action that is specified "inside buckminster" (via<property key="buildFileId" value="buckminster.pdetasks"/>)? When i do it like in the mailapp i have no executable.
>>
>>
>>
>>
>> -----Original Message-----
>> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
>> Sent: Mon 7/09/2009 16:10
>> To: buckminster-dev@eclipse.org
>> Subject: Re: [buckminster-dev] product export
>>
>> Hi Dieter,
>>
>> The site.p2 action only creates a p2 repository. For a product you
>> should invoke the create.product or create.product.zip action. Those
>> will invoke the p2 director on the repository created by site.p2 to
>> create the actual product.
>>
>> Best regards,
>> Johannes
>>
>> Cailliau, Dieter schrieb:
>>> I'm trying to use buckminster to export an eclipse product, but it's not clear to me how to do it.
>>> 1) there's the mailapp tutorial where i copied the product.ant and cspex, put this is not giving me an executable file anywhere.
>>> 2) using site.p2 there is a binaries folder with zips containing executables + swt lib for each platform, but when i extract the one i need and run it, it complains it can not find its companion jar.
>>>
>>>
>>> DISCLAIMER:
>>> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
>> _______________________________________________
>> buckminster-dev mailing list
>> buckminster-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>
>>
>>
>>
>> DISCLAIMER:
>> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
>
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.
RE: [buckminster-dev] product export solved [message #484556 is a reply to message #484493] Tue, 08 September 2009 08:24 Go to previous messageGo to next message
Eclipse UserFriend
Originally posted by: dieter.cailliau.barco.com

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA305E.5B87E54B
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Thomas: I set up my headless about 6 weeks ago using these archives:

-rw-r--r-- 1 dcaillia staff 4.4M 2009-07-27 15:55 =
director_1.0.0.r10307.zip
-rw-r--r-- 1 dcaillia staff 29M 2009-07-27 15:58 =
org.eclipse.buckminster.site.eclipse.headless_1.1.350.r10476 .zip
-rw-r--r-- 1 dcaillia staff 7.2M 2009-07-28 12:33 =
org.eclipse.buckminster.site.external_1.1.0.r10477.zip
-rw-r--r-- 1 dcaillia staff 574K 2009-07-28 14:56 =
site_1.0.0.200906052157-1--311_17163268.zip

These are the eclipse.buckminster plugin versions in my headless =
buckminster

drwxr-xr-x 5 swbuildbot fuse 4.0K 2009-07-27 19:04 =
org.eclipse.buckminster.ant_1.1.350.r10356
-rw-r--r-- 1 swbuildbot fuse 47K 2009-07-27 19:02 =
org.eclipse.buckminster.cmdline_1.0.350.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 1.0M 2009-07-27 19:04 =
org.eclipse.buckminster.core_1.1.350.r10476.jar
-rw-r--r-- 1 swbuildbot fuse 44K 2009-07-27 19:04 =
org.eclipse.buckminster.download_1.1.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 14K 2009-07-27 19:04 =
org.eclipse.buckminster.executor_1.0.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 18K 2009-07-27 19:04 =
org.eclipse.buckminster.fetcher_1.0.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 29K 2009-07-27 19:04 =
org.eclipse.buckminster.generic_1.0.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 16K 2009-07-27 19:02 =
org.eclipse.buckminster.installer_1.0.350.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 30K 2009-07-27 19:04 =
org.eclipse.buckminster.jarprocessor_1.0.0.r10362.jar
drwxr-xr-x 4 swbuildbot fuse 4.0K 2009-07-27 19:04 =
org.eclipse.buckminster.jdt_1.0.0.r10473
-rw-r--r-- 1 swbuildbot fuse 4.5K 2009-07-28 14:58 =
org.eclipse.buckminster.junit_0.7.0.200906052157.jar
-rw-r--r-- 1 swbuildbot fuse 36K 2009-07-27 19:04 =
org.eclipse.buckminster.opml_1.0.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 29K 2009-07-27 19:04 =
org.eclipse.buckminster.osgi.filter_1.0.0.r10450.jar
drwxr-xr-x 4 swbuildbot fuse 4.0K 2009-07-27 19:04 =
org.eclipse.buckminster.pde_1.1.350.r10455
-rw-r--r-- 1 swbuildbot fuse 35K 2009-07-27 19:02 =
org.eclipse.buckminster.runtime_1.1.0.r10447.jar
-rw-r--r-- 1 swbuildbot fuse 26K 2009-07-27 19:04 =
org.eclipse.buckminster.sax_1.0.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 34K 2009-07-28 12:37 =
org.eclipse.buckminster.subversion_1.0.0.r10356.jar
-rw-r--r-- 1 swbuildbot fuse 21K 2009-07-28 12:37 =
org.eclipse.buckminster.subversive_1.0.0.r10356.jar



-----Original Message-----
From: buckminster-dev-bounces@eclipse.org on behalf of Thomas Hallgren
Sent: Mon 7/09/2009 20:18
To: buckminster-dev@eclipse.org
Subject: Re: [buckminster-dev] product export solved
=20
Hmm, that one should have been fixed already. What version of =
Buckminster are you using (the PDE support in particular)?

Regards,
Thomas Hallgren

On 09/07/2009 07:37 PM, Cailliau, Dieter wrote:
> I have an executable now, i think what fixed it, is specifying these =
for my platform (instead of "*")
>
> target.os=3Dlinux
> target.ws=3Dgtk
> target.arch=3Dx86
>
> Next i got this when starting the exported product:
>
> java.lang.IllegalStateException: Unable to acquire application =
service. Ensure that the org.eclipse.core.runtime bundle is resolved and =
started (see config.ini).
>
> The solution was to add this in my product file (i did not have this =
because i'm migrating from eclipse 3.2)
>
> <configurations>
> <plugin id=3D"org.eclipse.equinox.app" autoStart=3D"true" =
startLevel=3D"4" />
> </configurations>
>
>
> -----Original Message-----
> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
> Sent: Mon 7/09/2009 17:29
> To: buckminster-dev@eclipse.org
> Subject: Re: [buckminster-dev] product export
>
> It's the one specified in the cspecx. It requires though that your
> version of buckminster includes the p2 director application (should be
> the case with the latest updates AFAIK).
>
>
> Best regards,
> Johannes
>
> Cailliau, Dieter schrieb:
>> The create.product you're talking about: is it the one specified in =
buckminster.cspex that actually calls the product.ant file (from the =
mailapp example), or is it some action that is specified "inside =
buckminster" (via<property key=3D"buildFileId" =
value=3D"buckminster.pdetasks"/>)? When i do it like in the mailapp i =
have no executable.
>>
>>
>>
>>
>> -----Original Message-----
>> From: buckminster-dev-bounces@eclipse.org on behalf of Johannes Utzig
>> Sent: Mon 7/09/2009 16:10
>> To: buckminster-dev@eclipse.org
>> Subject: Re: [buckminster-dev] product export
>>
>> Hi Dieter,
>>
>> The site.p2 action only creates a p2 repository. For a product you
>> should invoke the create.product or create.product.zip action. Those
>> will invoke the p2 director on the repository created by site.p2 to
>> create the actual product.
>>
>> Best regards,
>> Johannes
>>
>> Cailliau, Dieter schrieb:
>>> I'm trying to use buckminster to export an eclipse product, but it's =
not clear to me how to do it.
>>> 1) there's the mailapp tutorial where i copied the product.ant and =
cspex, put this is not giving me an executable file anywhere.
>>> 2) using site.p2 there is a binaries folder with zips containing =
executables + swt lib for each platform, but when i extract the one i =
need and run it, it complains it can not find its companion jar.
>>>
>>>
>>> DISCLAIMER:
>>> Unless indicated otherwise, the information contained in this =
message is privileged and confidential, and is intended only for the use =
of the addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.
>> _______________________________________________
>> buckminster-dev mailing list
>> buckminster-dev@eclipse.org
>> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>>
>>
>>
>>
>> DISCLAIMER:
>> Unless indicated otherwise, the information contained in this message =
is privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.
> _______________________________________________
> buckminster-dev mailing list
> buckminster-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/buckminster-dev
>
>
>
>
> DISCLAIMER:
> Unless indicated otherwise, the information contained in this message =
is privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

_______________________________________________
buckminster-dev mailing list
buckminster-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/buckminster-dev




DISCLAIMER:
Unless indicated otherwise, the information contained in this message is =
privileged and confidential, and is intended only for the use of the =
addressee(s) named above and others who have been specifically =
authorized to receive it. If you are not the intended recipient, you are =
hereby notified that any dissemination, distribution or copying of this =
message and/or attachments is strictly prohibited. The company accepts =
no liability for any damage caused by any virus transmitted by this =
email. Furthermore, the company does not warrant a proper and complete =
transmission of this information, nor does it accept liability for any =
delays. If you have received this message in error, please contact the =
sender and delete the message. Thank you.

------_=_NextPart_001_01CA305E.5B87E54B
Content-Type: application/ms-tnef;
name="winmail.dat"
Content-Transfer-Encoding: base64

eJ8+IiQIAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcA GAAAAElQTS5NaWNy
b3NvZnQgTWFpbC5Ob3RlADEIAQ2ABAACAAAAAgACAAEEgAEALAAAAFJFOiBb YnVja21pbnN0ZXIt
ZGV2XSBwcm9kdWN0IGV4cG9ydCBzb2x2ZWQATBABBYADAA4AAADZBwkACAAK ABgAKAACAD0BASCA
AwAOAAAA2QcJAAgACgAcACMAAgA8AQEJgAEAIQAAAEI1RTkxN0FEMjZGOUIz NDQ5N0MyNUVGOTRE
MDZDRTgyAFQHAQOQBgBcFQAAOQAAAAMAJgAAAAAAAwA2AAAAAABAADkA56mR z10wygEeAD0AAQAA
AAUAAABSRTogAAAAAAIBRwABAAAAMgAAAGM9QkU7YT1SVFQ7cD1CQVJDTzts PUtORE1FWDAxLTA5
MDkwODA4MjgzNVotNzU5NzYAAAAeAEkAAQAAACwAAABSZTogW2J1Y2ttaW5z dGVyLWRldl0gcHJv
ZHVjdCBleHBvcnQgc29sdmVkAEAATgAA8NGM5y/KAR4AWgABAAAAJAAAAGJ1 Y2ttaW5zdGVyLWRl
di1ib3VuY2VzQGVjbGlwc2Uub3JnAAIBWwABAAAAZQAAAAAAAACBKx+kvqMQ GZ1uAN0BD1QCAAAA
AGJ1Y2ttaW5zdGVyLWRldi1ib3VuY2VzQGVjbGlwc2Uub3JnAFNNVFAAYnVj a21pbnN0ZXItZGV2
LWJvdW5jZXNAZWNsaXBzZS5vcmcAAAAAAgFcAAEAAAApAAAAU01UUDpCVUNL TUlOU1RFUi1ERVYt
Qk9VTkNFU0BFQ0xJUFNFLk9SRwAAAAAeAF0AAQAAABAAAABUaG9tYXMgSGFs bGdyZW4AAgFeAAEA
AAA8AAAAAAAAAIErH6S+oxAZnW4A3QEPVAIAAAAAVGhvbWFzIEhhbGxncmVu AFNNVFAAdGhvbWFz
QHRhZGEuc2UAAgFfAAEAAAAUAAAAU01UUDpUSE9NQVNAVEFEQS5TRQAeAGYA AQAAAAUAAABTTVRQ
AAAAAB4AZwABAAAAJAAAAGJ1Y2ttaW5zdGVyLWRldi1ib3VuY2VzQGVjbGlw c2Uub3JnAB4AaAAB
AAAABQAAAFNNVFAAAAAAHgBpAAEAAAAPAAAAdGhvbWFzQHRhZGEuc2UAAB4A cAABAAAAKAAAAFti
dWNrbWluc3Rlci1kZXZdIHByb2R1Y3QgZXhwb3J0IHNvbHZlZAACAXEAAQAA ABsAAAAByi/n1UZ8
9/VOb/lIgbBLQxwPtwUaAB1+krEAHgB0AAEAAAAcAAAAYnVja21pbnN0ZXIt ZGV2QGVjbGlwc2Uu
b3JnAB4AGgwBAAAAEQAAAENhaWxsaWF1LCBEaWV0ZXIAAAAAHgAdDgEAAAAo AAAAW2J1Y2ttaW5z
dGVyLWRldl0gcHJvZHVjdCBleHBvcnQgc29sdmVkAAIBCRABAAAAqAwAAKQM AADTIgAATFpGdfqS
ZPEDAAoAcmNwZzEyNeIyA0N0ZXgFQQEDAff/CoACpAPkBxMCgA/zAFAEVj8I VQeyESUOUQMBAgBj
aOEKwHNldDIGAAbDESX2MwRGE7cwEiwRMwjvCfe2OxgfDjA1ESIMYGMAUDML CQFkMzYWUAumIFSC
aANxczogSSAUEQAgdXAgbXkgaPBlYWRsB5AEIAGgCGBRBUA2IHcJ4GseoWeG bx3AAJBuZyB0HjBL
FBAesHIT0Gl2B5A6RwqiCoQKgC1ydyHwLUEiIiAxIGRjC3BsHmwHMB2AAZAB ICA0Lgg0TSAB0DA5
LTCQNy0yNyKQNToaYCUisGkYIGN0BbBfMYQuMCWxcjEwMyRQvC56BSAhnyKv I/A5I+9kOCAFsGcu
BZAjEHDJFBAuYhrQa20LgCNQ/QSQLgCQDrAqVx42JZEloMQzNSXjNDc2Jm8n fzsjciZQMij5KgAO
IDoz/jMqHyssDtAEkQdALPMtZYcmXy7vI2M1NzRLMIu+NCTQHyAroiWVJAIw HDAXDkAksCRgMTWw
MzExASWQNzE2MzI2OL80yCE0HPAgZCCAIEEgMe/TEoELUHVnC4AgIPAUAH5p AiAEID5RHgoyaSE6
ZP01cHg1oEGiKLAk8APgMmDtAxBkBuAFQGYf4CCAI7DmMDdZJJE5Oi2gMZ8r Ju0AcHQs+i1ANjUP
NgFCXj0joDdDjxRARL8rNWNtzx5gC4A4tEa4LmoKwEdf/0hvIIAloSj8RG9L uwWwOLJ/LStN707/
SUU3SlE/Mj1k+G93bhewHlAz+E2vVU//SQg4IFcfWC8rFw7ABZAe8O8le1r/ XA9dGDhdz17fKxf+
ZhQgE9AEkGD/Yg9jH0lxbyjQZH9ljysXZwnwBnFj72efaK9pv11yNmsfSt8r F/8rMgdAHnAlhE0/
b39wjyYwr3G/bC8rF3XxcANgYx6B+SV7NjJ16EF6eaBCX0Nv+3mPeppkRlIl xS2wFTB2P7t3TyOh
NTdfKg96uHUDAP9GUCXANLA5HHXvhA94BnGv44CPKwhvcG0z4m5vik/vi19q /41/jopzPkBnEAMQ
/ythgmktUXzvff9/D5OPlJ/+cAEALPsaYJCPkZ94QoWa63JvMj1yiGB0B3Ez +S2wP5BPnn+SZox/
mt8rCWF4/49/pE+lX3hCN00xUSSQp+/5KzZ1Yj6FqZ+qr6u/kqL+Ma0fri+v PyDwsG8hOiE7/bnC
TwUQPkEHQAXQHoEfoHZlucMhNEYDYR1QMmktqQEAdi0e0W57oUC1Vqe1EbUA A6BiZRPgbCOQ5m8j
kBz0IEh0oQnBC5AvIUMGYAIwHVBNvmE3L20kIC8kAiPxOmRQO5Vvb7wPvZrA Ja/QaiVBHVBSamUd
UFu8LV0+AANgZPca0AVADsBwF8EdgAbwIPAPCzEhUgrjCoBIbW0sXSAxYQVA AiAggHMdAHV7mPAe
IGEg8L6BCfCZQGkfYIDKAAdAGCAeUHkuIG5XyTI+hb7yQj1pPFJ5iwhgH9Uo PJJQREUdgH8d0MdT
PlEKsaLwYKALYHIsKT8hOsVQZwsRcyz3O5a/XyF2TwOgwUEkUMFkUyRQtNJQ TckAQyLkde3JAEQI
kD3SdwNgDrAhJX4+HWHKIwORYHQBoB5wILZuWdDJAGkgMQuAax8wn8kyysQr sNiRBCBzcAWQ/QaQ
eSAIAhAFwB4BC1EAMD0FsG3OQCszHlC+8iIq/CIp1pXWlgGQtSAUIJWRUj1M oXV43d133tBnjHRr
3d0goj14OEdF/93HB8AO0diwH7AFQNjRBCD/2TDKkSNRz7EgFMclyvHGtcfW htaWsUB2YS4LYCAQ
zC5JdLHRMGxTAZAOsLxFeHugBTA+wR1QVTPAZ9giJWAesGNxmNA8YWGfzwAj ECLQ6MIdgXJ2DeD5
MkAgRQCACHA8cslBPJLvtRpTMqK2P/FuHmHaEhgg38ek13HKAORDyvEoFBAg gB0FoG6V8LUwC4Bp
KS7f3W078ceSHvDMQnfSMemS/mTKAOOjPxTGtpXxIIDcYP8lAcoA2GAFQMoj 46O+kCLQ+ZliaSfc
QCsgCcDqoSARvwNSPMZ4YDBQ3V75sjzwZHsIcOqjc/k7+dI+FfVQPdoitRpl 6eHYYHhGIM8AviIe
sGCx6CEAIPyQdKLAlmX+IORDTLzwZWz8kOo0/iAv+Twv+h/ditaWf7nPut3W 8LvPvN+9777ySppv
E+BuTMAeoFV0NNDfxFXW8MCPwZE6cDoo0PGXf8KPw58KQ8Tfxe/G+N1tSfx0 J/MB7GLJgtpj1dDZ
wfu+cDySY9pS/dASse6x6ePzEvIe4GdoyRTNsUCl1vBvzAk9WvxAtWB1G8AS 9HD/oSAlFuo78BDJ
xPZg3dcUcvvSMCCAd9ngFjIggNvhIQALHwDO8GQdciBBRkHsSUvxDtaWQh2S v/DROm/W8Akm3W3V
L3NnUAPwZfZi1obx9GPLQSvBxrbNsfYnPGIz0GvawtgQByAKsf/zsuw1E25L u9pRQgDJI+nA/HR1
dKE/UDZANnAZRcbE/0Yi9LX3wzyS0iBc0OpBxyHkYW3b0GUpyQDbcSeUf3vQ 7fEqscxCySPaJxPy
Il8ysfVQ7gK19/4gKOswYR/78NZA2mDPsD9Qa2V5y/yQmMNG9NFJZP4g5zAd /BBlM4Kb69gAc2tz
/iIAQNAwy6HKkfUh6aAnwf8jIDNQFCYtltiwyiPYYNep//EW3cY6XyR3A58E rgWfBq9fB78IzwnY
Cm8LdDbB4DD/JHgMrw2/QzQPHxAvET872P5I2LDVxCDmO9jyE9ngJZG/GbAv lQrwKxIlU/ZAYRmS
37/wx1BN8eVAy4FGGjLGp8/NsSR3ybX8QHZvN3EUY/clXNtxJUwuCdAt8C+U 63D/0fFdYCR3HNAj
EFLKGaov0//KUFAIJTUbgTMwTfZgwCR3/yVE5MMqtCvXTK8gLySzIX3/O9gi 7yP+1vH28f7w2rTp
oP9xQhga6ZHHNdeC+CXGtckA/xgQz0ES0vWCtWDLUGWD7fE9FfB36YI2812H 1vAxKf/a8r/wEuUt
lirQWcEykD0w7+PxzYHYsO1QcBPyK67vUvsqA8kAcGeR85Rn9Dzw6zDf2tEv Yteb9MPXgHlsg2nZ
3/iwzeVax2yUT5JiPQEkIf/2QNtgmPDWAhziVZH2QPBh39gA8NHa0de49kAr sqE3Mv5i21PLUCQA
28dnZOPz2LD/4wH3UMcBJ/bYsAlw7yWiwf/Z1Ggx0hDb0a9RfJPXgfWC/zDQ 72HZ4HZiLkDXgMxC
sUEHadh/n9bwRElTQ0zxHnBNRVJjGekgd7Hzwv/1QOqRyvGZIGrBHNCzgMkC /zeC3BLqpHaFFAba
IaMQPXP/2hLGsHAx59HvJfBjGSDtwf9BoMkA71Lzs1ww7kCDgk7y/9ti5NKz cr8BXGPzYO7B8CH/
8BBqkD0QoxDLAbMg11ODlf/j0umgyigwhStCMzD+QRXw3TzQem1C6aAZ8WW3 AWmi/xUQzJDNss1y
9YKEZImVGfH/+EDV0O3AyQCRRmrCWpH1gf8T1CpkcgD1MYvRr0Hqo8kA/5WR /vB4YPKEVHIy4Nqz
ixPrhlnvUS9Q0nTYACQAoxD/7cBvk5aixwArEcax2OB04N/lYVYy8EJ+0o9R Y+iSZ/L/N0HYELLw
2eCKNJVTLjCGwv/2g1pzlVLrMKLA8wF6oNyA//cgmYBaZOOjldBhoVCh68D9 arJt7WGERJv2NvAJ
gfWC/fLgcqABKpHGojLxh9UuQv9cMqAEPXDMRfOVhMfJANhgf81QozMnwZx0 nR+Vcf/QYfx5c5D3
yiOQVfN1hofXkf+j4FDQbwFoYbOBdoN6xbOA/4mxpLSqEaVjLWI9ZFYy14Dn 2RDNsV2HIF+xr7K/
s4r/JHc/DS2D2sJh0P9QtJ9Gb41HeWiZgO0QOi8vP8Gb7MfskS8tktIgbi+2 ov2Eoi8/DTrvvc8k
lYFfgn//g4+En4Wvhr+Hz4jfie+K//+MD40fji+PP5BPkV+Sb5N//5SPlZ+W r5e/mM+Z35rvm///
nQ+eH58voD+hT6Jfo2+kf/+lj6afp6+ov6nPqt+r76z//64Prx+wL/sks4/w /7PP+0L/tS+2P/NP
uG/7Ubm/us+73/+86vtfAtq/z8Dvwf/DD8Qf/8Uvxj/HT8hfyW/Kf8uPzJ// za/Ov8/P0N/R79L/
1A/VH//WL9c/2E/ZX9pv50/cj92f/96v37/gz+Hf4u/j/+UP5h//5y/oP+lP 6l/rb+x/7Y/un//9
Qf0U8d8u//If/VDzb/R/f/Wv9r733/jv+f+86S06fQE6IB4ANRABAAAAPgAA ADwwMjhBRThBN0Mw
NEVFMTQ4ODlCRTk5RTU0NTBCRTMyRDAzNkVCQUJGQGtuZG1leDAxLmJhcmNv LmNvbT4AAAAeADkQ
AQAAALABAAA8aDdvMzFxJDRiOCQxQGJ1aWxkLmVjbGlwc2Uub3JnPjxoN29r am4kYTcyJDFAYnVp
bGQuZWNsaXBzZS5vcmc+CTxoN292OWwkcGMzJDFAYnVpbGQuZWNsaXBzZS5v cmc+PGg3cW1mcCQ4
YzUkMUBidWlsZC5lY2xpcHNlLm9yZz4JPGg3cXE1NiRvdWckMUBidWlsZC5l Y2xpcHNlLm9yZz48
bWFpbG1hbi4wLjEyNTIzMjUyNDMuMTg5ODQuYnVja21pbnN0ZXItZGV2QGVj bGlwc2Uub3JnPgk8
aDgzNDl2JG42NiQxQGJ1aWxkLmVjbGlwc2Uub3JnPgk8bWFpbG1hbi4xLjEy NTIzMzcyNTUuMTg5
ODQuYnVja21pbnN0ZXItZGV2QGVjbGlwc2Uub3JnPgk8aDgzOHQ0JG85byQx QGJ1aWxkLmVjbGlw
c2Uub3JnPiA8bWFpbG1hbi4yLjEyNTIzNDUwNTYuMTg5ODQuYnVja21pbnN0 ZXItZGV2QGVjbGlw
c2Uub3JnPiA8aDgzaXAxJGo5MSQxQGJ1aWxkLmVjbGlwc2Uub3JnPgAeAEcQ AQAAAA8AAABtZXNz
YWdlL3JmYzgyMgAACwDyEAEAAAAfAPMQAQAAAGQAAABSAEUAJQAzAEEAIABb AGIAdQBjAGsAbQBp
AG4AcwB0AGUAcgAtAGQAZQB2AF0AIABwAHIAbwBkAHUAYwB0ACAAZQB4AHAA bwByAHQAIABzAG8A
bAB2AGUAZAAuAEUATQBMAAAACwD2EAAAAABAAAcw0IKKz10wygFAAAgwBaqM W14wygEDAN4/r28A
AAMA8T8JBAAAHgD4PwEAAAARAAAAQ2FpbGxpYXUsIERpZXRlcgAAAAACAfk/ AQAAAEQAAAAAAAAA
3KdAyMBCEBq0uQgAKy/hggEAAAAAAAAAL089QkFSQ08vT1U9QUcwMDEvQ049 UkVDSVBJRU5UUy9D
Tj1ESUVDAB4A+j8BAAAAFQAAAFN5c3RlbSBBZG1pbmlzdHJhdG9yAAAAAAIB +z8BAAAAHgAAAAAA
AADcp0DIwEIQGrS5CAArL+GCAQAAAAAAAAAuAAAAAwD9P+QEAAADABlAAAAA AAMAGkAAAAAAAwAd
QAAAAAADAB5AAAAAAB4AMEABAAAABQAAAERJRUMAAAAAHgAxQAEAAAAFAAAA RElFQwAAAAAeADJA
AQAAACQAAABidWNrbWluc3Rlci1kZXYtYm91bmNlc0BlY2xpcHNlLm9yZwAe ADNAAQAAAA8AAAB0
aG9tYXNAdGFkYS5zZQAAHgA4QAEAAAAFAAAARElFQwAAAAAeADlAAQAAAAIA AAAuAAAAAwB2QP//
//8LACkAAAAAAAsAIwAAAAAAAwAGENamWOsDAAcQ+RgAAAMAEBAAAAAAAwAR EAAAAAAeAAgQAQAA
AGUAAABUSE9NQVM6SVNFVFVQTVlIRUFETEVTU0FCT1VUNldFRUtTQUdPVVNJ TkdUSEVTRUFSQ0hJ
VkVTOi1SVy1SLS1SLS0xRENBSUxMSUFTVEFGRjQ0TTIwMDktMDctMjcxNTo1 NURJAAAAAAIBfwAB
AAAAPgAAADwwMjhBRThBN0MwNEVFMTQ4ODlCRTk5RTU0NTBCRTMyRDAzNkVC QUJGQGtuZG1leDAx
LmJhcmNvLmNvbT4AAABdDQ==

------_=_NextPart_001_01CA305E.5B87E54B--
Re: Headless (JUnit) launching [message #489023 is a reply to message #484106] Thu, 01 October 2009 09:19 Go to previous messageGo to next message
Carsten Reckord is currently offline Carsten ReckordFriend
Messages: 139
Registered: July 2009
Senior Member
Hi Achim,

On 04.09.2009 12:28, Achim Demelt wrote:
> Thanks for that. There are some parts that I consider including in the final
> version. For IP reasons, I must ask you to attach the same patch to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=243293. Sorry for that, I
> should have though of that before. But if I'm going to check in code based
> on your suggestions, I have to make sure that you submitted that code via
> Bugzilla.

Sorry, I was wound up in other stuff lately and only now saw your reply. I just submitted it to the bugzilla. If you need anything more, I
promise I'll come back here more often now ;)

> I played around a bit with multi-platform launch configs. On my machine,
> this works without any problems. Opening the launch config and running it
> does not change the plug-in configuration.
>
> Which version of Eclipse are you using?

I'm not sure anymore what exactly the cause of our problems was, but somehow, version numbers got dropped (or added?) from the configuration
and subtle version conflicts between the platforms led to problems. With better synchronized eclipse versions on the platforms we have it
running fine now.


Regards,
Carsten
Re: Headless (JUnit) launching [message #489645 is a reply to message #483832] Mon, 05 October 2009 13:19 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Hi,

I would really like to try the new junit testing and coverage support
for my hudson jobs. I searched around for a while, but I could not find
any binaries for download. Are binaries available yet? If not, is
somewhere a brief description on how to create a headless buckminster
with junit support from source?

Thanks in advance,
Johannes
Re: Headless (JUnit) launching [message #489659 is a reply to message #489645] Mon, 05 October 2009 13:46 Go to previous messageGo to next message
Thomas Hallgren is currently offline Thomas HallgrenFriend
Messages: 3232
Registered: July 2009
Senior Member
Hi Johannes,
I belive everything is included in our Helios M2 release. You'll find all the latest stuff at these sites:

http://download.eclipse.org/tools/buckminster/updates-3.6
http://download.eclipse.org/tools/buckminster/headless-3.6

You need a platform that is 3.6M2 or newer to run from an IDE.

Regards,
Thomas Hallgren



On 10/05/2009 03:19 PM, Johannes Utzig wrote:
> Hi,
>
> I would really like to try the new junit testing and coverage support
> for my hudson jobs. I searched around for a while, but I could not find
> any binaries for download. Are binaries available yet? If not, is
> somewhere a brief description on how to create a headless buckminster
> with junit support from source?
>
> Thanks in advance,
> Johannes
Re: Headless (JUnit) launching [message #489670 is a reply to message #489659] Mon, 05 October 2009 14:13 Go to previous messageGo to next message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Thomas Hallgren schrieb:
> Hi Johannes,
> I belive everything is included in our Helios M2 release. You'll find
> all the latest stuff at these sites:
>
> http://download.eclipse.org/tools/buckminster/updates-3.6
> http://download.eclipse.org/tools/buckminster/headless-3.6
>
> You need a platform that is 3.6M2 or newer to run from an IDE.
>
> Regards,
> Thomas Hallgren
>
>
>
> On 10/05/2009 03:19 PM, Johannes Utzig wrote:
>> Hi,
>>
>> I would really like to try the new junit testing and coverage support
>> for my hudson jobs. I searched around for a while, but I could not find
>> any binaries for download. Are binaries available yet? If not, is
>> somewhere a brief description on how to create a headless buckminster
>> with junit support from source?
>>
>> Thanks in advance,
>> Johannes
>

Hi Thomas,

thank you for your reply. I actually tried those URLs before but it gave
me a 404. Works in the update manager though, so that was my own fault...
I tried this the same way I usually install a headless buckminster 3.5:
../director/director -r
http://download.eclipse.org/tools/buckminster/headless-3.6 -d $BUCKY_DIR
-p Buckminster -i org.eclipse.buckminster.cmdline.product

However, that gives me:
Installing org.eclipse.buckminster.cmdline.product 1.1.350.r10655.
An error occurred while collecting items to be installed
session context was:(profile=Buckminster, phase=, operand=, action=).
No repository found containing:
osgi.bundle,org.eclipse.core.contenttype,3.4.100.v20090831
No repository found containing:
osgi.bundle,org.eclipse.core.net,1.2.100.I20090714-0800
No repository found containing:
osgi.bundle,org.eclipse.core.runtime,3.5.100.v20090911
No repository found containing:
osgi.bundle,org.eclipse.equinox.common,3.5.100.v20090817
No repository found containing:
osgi.bundle,org.eclipse.equinox.frameworkadmin,1.0.200.v2009 0831
No repository found containing:
osgi.bundle,org.eclipse.equinox.frameworkadmin.equinox,1.0.2 00.v20090911-1356
No repository found containing:
osgi.bundle,org.eclipse.equinox.launcher,1.0.300.v20090911
No repository found containing:
osgi.bundle,org.eclipse.equinox.launcher.gtk.linux.x86,1.0.3 00.v20090908
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.artifact.repository,1.0.1 00.v20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.console,1.0.100.v20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.core,1.1.0.v20090911-1356
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.director,1.0.100.v2009083 1
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.director.app,1.0.100.v200 90911-1356
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.engine,1.1.0.v20090911-13 56
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.exemplarysetup,1.0.100.v2 0090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.garbagecollector,1.0.100. v20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.jarprocessor,1.0.100.v200 90520-1905
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.metadata,1.0.100.v2009083 1
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.metadata.repository,1.0.1 00.v20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.publisher,1.1.0.v20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.repository,1.0.0.v2009091 1-1800
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.touchpoint.eclipse,1.0.20 0.v20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.p2.touchpoint.natives,1.0.20 0.v20090911-1356
No repository found containing:
osgi.bundle,org.eclipse.equinox.preferences,3.2.300.v2009052 0-1800
No repository found containing:
osgi.bundle,org.eclipse.equinox.registry,3.5.0.v20090911
No repository found containing:
osgi.bundle,org.eclipse.equinox.security,1.0.100.v20090520-1 800
No repository found containing:
osgi.bundle,org.eclipse.equinox.simpleconfigurator,1.0.200.v 20090831
No repository found containing:
osgi.bundle,org.eclipse.equinox.simpleconfigurator.manipulat or,1.0.200.v20090911-1356
No repository found containing:
osgi.bundle,org.eclipse.osgi,3.6.0.v20090914
No repository found containing:
osgi.bundle,org.eclipse.osgi.services,3.2.0.v20090520-1800
No repository found containing:
osgi.bundle,org.eclipse.update.configurator,3.3.100.v2009081 3
No repository found containing: osgi.bundle,org.sat4j.core,2.1.1.v20090825
No repository found containing: osgi.bundle,org.sat4j.pb,2.1.1.v20090825

Do I need a newer director application for that? The director
application I use is the one appointed on the download page (a few weeks
old though) http://www.eclipse.org/buckminster/downloads.html

Best regards,
Johannes
Re: Headless (JUnit) launching [message #489685 is a reply to message #489670] Mon, 05 October 2009 14:39 Go to previous message
Johannes Utzig is currently offline Johannes UtzigFriend
Messages: 329
Registered: July 2009
Senior Member
Ok, it was just a problem with the mirrors. -Declipse.p2.mirrors=false
did the trick. Still get some errors while trying to install the
features from the headless site, but that's probably a mirror problem as
well.
Thanks again for your help


Best regards,
Johannes
Previous Topic:[buckminster-dev] Committer vote for Johannes Utzig has concluded successfully
Next Topic:Custom materialization of Maven artifacts
Goto Forum:
  


Current Time: Thu Dec 18 10:38:28 GMT 2014

Powered by FUDForum. Page generated in 0.02827 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software