first of all, I'm somewhat of a beginner when it comes to Buckminster or
the intrinsic details of PDE Build - so please apologize if some of my
questions/conclusions will seem rather stupid or just plan wrong in the
eyes of the more experienced user.

I've recently run into a problem with my (Buckminster-driven) build that
seems to have arisen at the time that I installed the standard
Checkstyle Eclipse plug-in and enabled its use for all my OSGI/Eclipse
RCP projects.

Since then, its seems that any Buckminster build triggered from directly
within the Eclipse IDE ("Buckminster > Run Action...") will fail if at
least one of my plug-ins still has a error-level Checkstyle validation
marker:

When this happens, Buckminster seems to display the supposed "error
message" (coming from Checkstyle) within both the standard console as
well as within a dedicated message box and simply abort the build.

While this may be just the desired behavior for errors occurring within
some of the more "critical" builders of one's own project (e.g. the
Scala builder for Scala-based projects), it's certainly sub-optimal for
builders that play only a "supporting" role within the overall process
(e.g. collect some metrics).

So I wonder: Is there a standard way to make Buckminster/PDE Build
either skip the builder in question or to ignore any "errors" that may
arise from its execution?

Deactivating Checkstyle, uninstalling the plug-in (and thus builder) or
invoking Buckminster from outside the IDE (where the builder is also not
available) makes the problem go away. Still, I'd be surprised if there
was no better solution available that I (with my limited Buckminster/PDE
Build knowledge) currently can't think of.

Anyway, thanks in advance for your help and kind assistance.

Chris

PS: The version of Buckminster/Eclipse used is that which was released
as part of the Helios release train only recently. No further tampering
has been done :-).

There is currently no way to selectively disregard certain kinds of errors. It sounds like a good enhancement so I
suggest you add a bugzilla for it.

Another enhancement request to consider could be to ask that the checkstyle builder could consider violations warnings
rather then errors.

I'm curious, why isn't the Checkstyle builder available outside of the IDE?

Regards,
Thomas Hallgren

On 07/02/2010 05:59 PM, Christian Kesselheim wrote:
> Hi everybody,
>
> first of all, I'm somewhat of a beginner when it comes to Buckminster or
> the intrinsic details of PDE Build - so please apologize if some of my
> questions/conclusions will seem rather stupid or just plan wrong in the
> eyes of the more experienced user.
>
> I've recently run into a problem with my (Buckminster-driven) build that
> seems to have arisen at the time that I installed the standard
> Checkstyle Eclipse plug-in and enabled its use for all my OSGI/Eclipse
> RCP projects.
>
> Since then, its seems that any Buckminster build triggered from directly
> within the Eclipse IDE ("Buckminster > Run Action...") will fail if at
> least one of my plug-ins still has a error-level Checkstyle validation
> marker:
>
> =================== (Console) ======================
> [start org.apache.oro:osgi.bundle$2.0.8.qualifier#eclipse.build]
> [end org.apache.oro:osgi.bundle$2.0.8.qualifier#eclipse.build]
> [start org.eclipse.riena.client:osgi.bundle$2.1.0.qualifier#eclipse .build]
> [end org.eclipse.riena.client:osgi.bundle$2.1.0.qualifier#eclipse .build]
> [start lu.kreios.mtg.client:osgi.bundle$1.0.0.qualifier#eclipse.bui ld]
> '4' is a magic number. <- Actually a Checkstyle violation message
> ====================================================
>
> ===================== (Log) ========================
> !ENTRY org.eclipse.buckminster.core 4 293 2010-07-02 16:55:22.717
> !MESSAGE '4' is a magic number.
> ====================================================
>
> When this happens, Buckminster seems to display the supposed "error
> message" (coming from Checkstyle) within both the standard console as
> well as within a dedicated message box and simply abort the build.
>
> While this may be just the desired behavior for errors occurring within
> some of the more "critical" builders of one's own project (e.g. the
> Scala builder for Scala-based projects), it's certainly sub-optimal for
> builders that play only a "supporting" role within the overall process
> (e.g. collect some metrics).
>
> So I wonder: Is there a standard way to make Buckminster/PDE Build
> either skip the builder in question or to ignore any "errors" that may
> arise from its execution?
>
> Deactivating Checkstyle, uninstalling the plug-in (and thus builder) or
> invoking Buckminster from outside the IDE (where the builder is also not
> available) makes the problem go away. Still, I'd be surprised if there
> was no better solution available that I (with my limited Buckminster/PDE
> Build knowledge) currently can't think of.
>
> Anyway, thanks in advance for your help and kind assistance.
>
> Chris
>
> PS: The version of Buckminster/Eclipse used is that which was released
> as part of the Helios release train only recently. No further tampering
> has been done :-).

With "outside of the IDE", I meant to refer to stand-alone buckminster
installations - such as the ones you can provision using P2 Director and
the Buckminster headless update site (after all, that's just what e.g.
the Buckminster Hudson plug-in does for you behind the scenes).

Concerning the bug report I should create: What would be the best way to
see this issue addressed in Buckminster? Extend the existing
eclipse.build actor to support an additional property, namely the list
of builder classes whose errors are to be ignored? I image than ignoring
the builder as a whole (i.e. not trigger it as part of the build
process) would be too much to ask for, partly because PDE Build doesn't
provide an equivalent facility/configuration option that Buckminster
could then re-use?

Thanks in advance,

Chris

On 7/2/10 6:20 PM, Thomas Hallgren wrote:
> Hi Christian,
>
> There is currently no way to selectively disregard certain kinds of
> errors. It sounds like a good enhancement so I suggest you add a
> bugzilla for it.
>
> Another enhancement request to consider could be to ask that the
> checkstyle builder could consider violations warnings rather then errors.
>
> I'm curious, why isn't the Checkstyle builder available outside of the IDE?
>
> Regards,
> Thomas Hallgren
>
>
> On 07/02/2010 05:59 PM, Christian Kesselheim wrote:
>> Hi everybody,
>>
>> first of all, I'm somewhat of a beginner when it comes to Buckminster or
>> the intrinsic details of PDE Build - so please apologize if some of my
>> questions/conclusions will seem rather stupid or just plan wrong in the
>> eyes of the more experienced user.
>>
>> I've recently run into a problem with my (Buckminster-driven) build that
>> seems to have arisen at the time that I installed the standard
>> Checkstyle Eclipse plug-in and enabled its use for all my OSGI/Eclipse
>> RCP projects.
>>
>> Since then, its seems that any Buckminster build triggered from directly
>> within the Eclipse IDE ("Buckminster > Run Action...") will fail if at
>> least one of my plug-ins still has a error-level Checkstyle validation
>> marker:
>>
>> =================== (Console) ======================
>> [start org.apache.oro:osgi.bundle$2.0.8.qualifier#eclipse.build]
>> [end org.apache.oro:osgi.bundle$2.0.8.qualifier#eclipse.build]
>> [start
>> org.eclipse.riena.client:osgi.bundle$2.1.0.qualifier#eclipse .build]
>> [end org.eclipse.riena.client:osgi.bundle$2.1.0.qualifier#eclipse .build]
>> [start lu.kreios.mtg.client:osgi.bundle$1.0.0.qualifier#eclipse.bui ld]
>> '4' is a magic number. <- Actually a Checkstyle violation message
>> ====================================================
>>
>> ===================== (Log) ========================
>> !ENTRY org.eclipse.buckminster.core 4 293 2010-07-02 16:55:22.717
>> !MESSAGE '4' is a magic number.
>> ====================================================
>>
>> When this happens, Buckminster seems to display the supposed "error
>> message" (coming from Checkstyle) within both the standard console as
>> well as within a dedicated message box and simply abort the build.
>>
>> While this may be just the desired behavior for errors occurring within
>> some of the more "critical" builders of one's own project (e.g. the
>> Scala builder for Scala-based projects), it's certainly sub-optimal for
>> builders that play only a "supporting" role within the overall process
>> (e.g. collect some metrics).
>>
>> So I wonder: Is there a standard way to make Buckminster/PDE Build
>> either skip the builder in question or to ignore any "errors" that may
>> arise from its execution?
>>
>> Deactivating Checkstyle, uninstalling the plug-in (and thus builder) or
>> invoking Buckminster from outside the IDE (where the builder is also not
>> available) makes the problem go away. Still, I'd be surprised if there
>> was no better solution available that I (with my limited Buckminster/PDE
>> Build knowledge) currently can't think of.
>>
>> Anyway, thanks in advance for your help and kind assistance.
>>
>> Chris
>>
>> PS: The version of Buckminster/Eclipse used is that which was released
>> as part of the Helios release train only recently. No further tampering
>> has been done :-).
>

On 7/2/10 7:07 PM, Christian Kesselheim wrote:
> Hi Thomas,
>
> Thanks for that lighting-fast reply.
>
> With "outside of the IDE", I meant to refer to stand-alone buckminster
> installations - such as the ones you can provision using P2 Director and
> the Buckminster headless update site (after all, that's just what e.g.
> the Buckminster Hudson plug-in does for you behind the scenes).
>
So, CheckStyle is just a bundle like anything else, and should be
possible to install this in headless Buckminster as well (but maybe it
isn't available in headless configuration).