buildr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rhett Sutphin (JIRA)" <>
Subject [jira] Commented: (BUILDR-463) Setting a system property in the buildfile causes a NoClassDefFoundError
Date Fri, 02 Jul 2010 16:18:49 GMT


Rhett Sutphin commented on BUILDR-463:

Thanks for the fix.  I want to clarify something in your comment:

> First, a workaround: if you do this you will be fine:
> test.enhance do
>  ... some java stuff
> end

I'm actually not setting the system property _for_ the tests -- it's just that setting it
causes (caused) the tests to break.  If the project didn't use JUnit tests, I'm sure the next
thing that needed RJB's classpath to be set would have broken instead.

>From the poking around I did trying to figure out what was causing this error yesterday,
your fix seems reasonable to me.

> Setting a system property in the buildfile causes a NoClassDefFoundError
> ------------------------------------------------------------------------
>                 Key: BUILDR-463
>                 URL:
>             Project: Buildr
>          Issue Type: Bug
>          Components: Core features
>    Affects Versions: 1.4
>         Environment: MRI 1.8.7-p174
> (does not happen on JRuby)
>            Reporter: Rhett Sutphin
>            Assignee: Antoine Toulme
>             Fix For: 1.4.1
> If a buildfile sets a system property like so:
>"foo", "bar")
> a subsequent attempt to run JUnit tests will fail with a NoClassDefFoundError for org/apache/buildr/JavaTestFilter.
 A minimal project which demonstrates this can be found in this gist:
.  Clone it and then run `buildr clean test` to replicate.
> This worked in 1.3.5.  It continues to work in 1.4.0 in JRuby, but not in MRI.
> (Apologies for not catching this in an RC -- most of my prerelease testing was with a
different project that didn't do this.)

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message