Eclipse Community Forums: Buckminster » Dropping particular SWT into headless Buckminster installation?

Help

Home

Home » Eclipse Projects » Buckminster » Dropping particular SWT into headless Buckminster installation?

Show: Today's Messages :: Show Polls :: Message Navigator

Dropping particular SWT into headless Buckminster installation? [message #742596]

Thu, 20 October 2011 12:29

Volker Stolz
Messages: 61
Registered: July 2009

Member

I've automated builds for our simple Eclipse plugins through a headless Buckminster (3.7) and Hudson for QA purposes, not for building update-sites etc., which works like a charm. Except for the project depending on SWT. Now I've looked at a lot of articles involving SWT, but none of them seem to spell out which bit to get from http://eclipse.org/swt/, or rather http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/index.php#SWT, and where to put it.

I'd be happy to simply make Buckminster do platform-specific builds (Solaris in my case) in a first instance, so I don't mind putting it into Buckminster itself, instead of customizing a platform first---there's no single incantation of './buckminster install' that will do the trick in that case?

-Volker

Report message to a moderator

Re: Dropping particular SWT into headless Buckminster installation? [message #743088 is a reply to message #742596]

Fri, 21 October 2011 01:24

Thomas Hallgren
Messages: 3165
Registered: July 2009

Senior Member

It should be enough to just include the org.eclipse.rcp feature in your target platform in order to get SWT. The rest
should be fully automatic.

- thomas

On 2011-10-20 18:29, Volker Stolz wrote:
> I've automated builds for our simple Eclipse plugins through a headless Buckminster (3.7) and Hudson for QA purposes,
> not for building update-sites etc., which works like a charm. Except for the project depending on SWT. Now I've looked
> at a lot of articles involving SWT, but none of them seem to spell out which bit to get from http://eclipse.org/swt/, or
> rather http://download.eclipse.org/eclipse/downloads/drops/R-3.7.1-201109091335/index.php#SWT, and where to put it.
>
> I'd be happy to simply make Buckminster do platform-specific builds (Solaris in my case) in a first instance, so I don't
> mind putting it into Buckminster itself, instead of customizing a platform first---there's no single incantation of
> './buckminster install' that will do the trick in that case?
>
> -Volker
>

Report message to a moderator

Re: Dropping particular SWT into headless Buckminster installation? [message #743250 is a reply to message #743088]

Fri, 21 October 2011 05:13

Volker Stolz
Messages: 61
Registered: July 2009

Member

Thanks Thomas! Following Ralf Ebert's article did the trick---I hadn't realized that defining a platform is so easy.

Volker

PS: Now I'm struggling with the following for a JUnit Plugin Test:

Waiting for jobs to end
junit '-l' 'eu.hatsproject.absplugin/junit.launch' '-o' 'eu.hatsproject.absplugin/junit.xml' '--maxTimeAwaitJunitReport' '20'
ERROR: Plugin validation errors were detected:
{eu.hatsproject.absplugin_0.0.0.qualifier=[Lorg.eclipse.osgi.service.resolver.ResolverError;@1f28aca, org.eclipse.jdt.core_3.7.1.v_OTDT_r201_201109101025=[Ljava.lang.Object;@760a1d, org.eclipse.equinox.preferences_3.4.1.R37x_v20110725=[Ljava.lang.Object;@1920fcc, org.eclipse.osgi_3.7.1.R37x_v20110808-1106=[Ljava.lang.Object;@4b4d26, org.eclipse.equinox.registry_3.5.101.R37x_v20110810-1611=[Ljava.lang.Object;@1b5ff11, org.eclipse.equinox.security_1.1.0.v20110502=[Ljava.lang.Object;@17ce10d}
WARN:  Process /usr/jdk/instances/jdk1.6.0/bin/java (Oct 21, 2011 5:08:37 PM) terminated with exit status 1.
Doing full workspace refresh
Waiting for jobs to end
java.lang.IllegalArgumentException: Export has failed because no test session is available. (Maybe the argument -maxTimeAwaitJunitReport will help)

Report message to a moderator

Re: Dropping particular SWT into headless Buckminster installation? [message #743365 is a reply to message #743250]

Fri, 21 October 2011 07:46

Volker Stolz
Messages: 61
Registered: July 2009

Member

I've pulled together all the pieces now, and have headless JUnit Plugin tests working---mostly thanks to older postings by Thomas and Ralf's article. Other important insights were:
Configure the JUnit plugin test with features instead of plugins, and eliminate all platform-specific entries from the launch-config, incl. -X VM switches.

Volker

Report message to a moderator

Previous Topic:	Additional p2 utilization actor
Next Topic:	Buckminster article in Dr.Dobb's

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri May 24 12:25:09 EDT 2013