You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Peter Donald (JIRA)" <ji...@apache.org> on 2011/06/22 12:11:06 UTC
[jira] [Closed] (BUILDR-463) Setting a system property in the
buildfile causes a NoClassDefFoundError
[ https://issues.apache.org/jira/browse/BUILDR-463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Donald closed BUILDR-463.
-------------------------------
> Setting a system property in the buildfile causes a NoClassDefFoundError
> ------------------------------------------------------------------------
>
> Key: BUILDR-463
> URL: https://issues.apache.org/jira/browse/BUILDR-463
> 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:
> Java.java.lang.System.setProperty("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: http://gist.github.com/460611 . 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira