buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dani Perez (JIRA)" <>
Subject [jira] [Updated] (BUILDR-635) JRE container entry to be declared before user sources and dependencies
Date Sat, 28 Apr 2012 21:28:48 GMT


Dani Perez updated BUILDR-635:

    Attachment: 0001-Fixes-BUILDR-635-JRE-container-entry-to-be-declared-.patch

Please, let me know if the patch has not the right format.

I don't know how to write a spec for it, sorry.
> JRE container entry to be declared before user sources and dependencies
> -----------------------------------------------------------------------
>                 Key: BUILDR-635
>                 URL:
>             Project: Buildr
>          Issue Type: Bug
>          Components: IDE
>    Affects Versions: 1.4.7
>         Environment: Linux / 32 bits / Fedora 15
> java version "1.6.0_25"
> Java(TM) SE Runtime Environment (build 1.6.0_25-b06)
> Java HotSpot(TM) Client VM (build 20.0-b11, mixed mode, sharing)
>            Reporter: Dani Perez
>            Priority: Minor
>              Labels: eclipse, ide, ide-plugins
>             Fix For: 1.4.7
>   Original Estimate: 20m
>  Remaining Estimate: 20m
> (I reported this issue in github because I hadn't read Buildr's contribution policy.
> See in order to reproduce the bug. In summary, if you
use Drools, it already ships a JRE container. Since the user's dependencies are written first
to '.classpath' , Drools container will be taken instead of Eclipse's. In my case, it produces
undesired effects like disabling Java Generics because I use the last JDK in Eclipse whereas
Drools doesn't.
> It makes sense to me to have JRE libs before user libs but I ignore if this change might
have side effects. This bug might potentially affect any dependency making use of its own
embedded JRE (i.e.: rather unlikely).

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message