[
https://issues.apache.org/jira/browse/BUILDR-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12906535#action_12906535
]
mark petrovic commented on BUILDR-161:
--------------------------------------
I see this repeatedly with no JUnit3 tests in my project workspace.
Googling around, I suspect this is not a buildr-specific issue:
http://www.google.com/search?aq=f&sourceid=chrome&ie=UTF-8&q=Trying+to+override+old+definition+of+datatype+junit#hl=en&q=Trying+to+override+old+definition+of+datatype+junit&aq=f&aqi=&aql=&oq=Trying+to+override+old+definition+of+datatype+junit&gs_rfai=&pbx=1&fp=5673716d440c1f33
but instead some sort of Ant classloader issue.
the question is whether it compromises or changes the nature of what buildr
does during the test phase.
> "Trying to override old definition of datatype junit" warning message
> ---------------------------------------------------------------------
>
> Key: BUILDR-161
> URL: https://issues.apache.org/jira/browse/BUILDR-161
> Project: Buildr
> Issue Type: Bug
> Components: Test frameworks
> Affects Versions: 1.3.3
> Environment: Trunk (revision 701212)
> Reporter: lacton
> Priority: Trivial
>
> I see "Trying to override old definition of datatype junit" warning messages
> when running tests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
