Home » Archived » Buckminster » Trigger Eclipse Compiler Log generation in Headless Build
 Trigger Eclipse Compiler Log generation in Headless Build [message #1068095] |
Fri, 12 July 2013 03:01  |
Eclipse User |
|
|
|
Hi all,
we're running a reliable (thanks  ) headless build for our plug-ins with Buckminster.
Our ANT-based build is triggered by the build subsystem of Rational Team Concert. We're able to publish several build artifacts in the RTC repository. For example the Junit test logs (launched via Buckminster) are pushed to the repository. This way we can see which tests fail, how long they take, etc. in the RTC Build UI.
There's also a possibility to publish the ECJ log to RTC and view the results like the Junit logs.
Unfortunately we couldn't find a way to generate the ECJ log via the Buckminster compile. AFAIK, the compile log can only be generated if the ECJ BatchCompiler is used.
This should be the case with the ANT-based Headless PDE Build, but not with Buckminster.
Is that correct, or are there some "hidden switches" to enable log generation, for example by setting a property in the 'build.properties'-file of each plug-in?
Thanks in advance,
Jochen
[Updated on: Fri, 12 July 2013 05:35] by Moderator |
|
|
| Re: Trigger Eclipse Compiler Log generation in Headless Build [message #1068109 is a reply to message #1068095] |
Fri, 12 July 2013 04:27  |
| Eclipse User |
|
|
|
On 2013-07-12 09:01, Jochen Schmich wrote:
> Hi all,
>
> we're running a reliable (thanks :) ) headless build for our plug-ins with Buckminster.
>
> Our ANT-based build is triggered by the build subsystem of Rational Team Concert. We're able to publish several build
> artifacts in the RTC repository. For example the Junit test logs (launched via Buckminster) are pushed to the
> repository. This way we can see which tests fail, how long they take, etc. in the RTC Build UI.
>
> There's also a possibility to publish the ECJ log to RTC and view the results like the Junit logs.
>
> Unfortunately we couldn't find a way to generate the ECJ log via the Buckminster compile. AFAIK, the compile log can
> only be generated if the ECJ BatchCompiler is used.
> This should be the case with the ANT-based Headless PDE Build, but not with Buckminster.
>
> Is that correct, or are there some "hidden switches" to enable log generation, for example by setting a property in the
> 'build.properties'-file of each plug-in?
>
Last time I looked, the ANT-based Headless PDE build is not a PDE build at all but rather an external build that mimics
parts of the PDE build. It does not not run the builders configured in your .project file. That means that you get no
errors or warnings from the PDE ManifestBuilder and SchemaBuilder.
Buckminster is all about building headlessly exactly like you would build in the IDE and produce the same set of errors
and warnnings from all configured builders.
That said, you can probably generate the ant-script using PDE, save it, and then run it from Buckminster with an ant
action if that is what you want.
Regards,
Thomas Hallgren
|
|
| |
| Re: Trigger Eclipse Compiler Log generation in Headless Build [message #1103672 is a reply to message #1068095] |
Sat, 07 September 2013 00:58 |
| Eclipse User |
|
|
|
Am 12.07.2013 09:01, schrieb Jochen Schmich:
> Hi all,
>
> we're running a reliable (thanks :) ) headless build for our plug-ins with Buckminster.
>
> Our ANT-based build is triggered by the build subsystem of Rational Team Concert. We're able to publish several build
> artifacts in the RTC repository. For example the Junit test logs (launched via Buckminster) are pushed to the
> repository. This way we can see which tests fail, how long they take, etc. in the RTC Build UI.
>
> There's also a possibility to publish the ECJ log to RTC and view the results like the Junit logs.
>
> Unfortunately we couldn't find a way to generate the ECJ log via the Buckminster compile. AFAIK, the compile log can
> only be generated if the ECJ BatchCompiler is used.
> This should be the case with the ANT-based Headless PDE Build, but not with Buckminster.
>
> Is that correct, or are there some "hidden switches" to enable log generation, for example by setting a property in
> the 'build.properties'-file of each plug-in?
I've absolutely no clue what you all mean by this ECJ, RTC, etc. stuff. But if you're asking for a way to export the
markers found during the Build command to a separate log file you may be interested in
https://bugs.eclipse.org/bugs/show_bug.cgi?id=416771 ;-)
Cheers
/Eike
----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper
|
|
|
Goto Forum:
Current Time: Fri Mar 14 10:27:42 EDT 2025
Powered by FUDForum. Page generated in 0.02465 seconds |
Home