[
https://issues.apache.org/jira/browse/BEANUTILS-287?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Henri Yandell closed BEANUTILS-287.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
New "test" target added; ie) I killed the massive duplication as the feature of
being able to run just one test from the Ant script doesn't seem worth the risk
of missing tests. The MemoryTestCase (which fails) is being excluded as with
the project.xml.
I also updated the build.properties.sample to not include collections, and to
by default look in the local .maven repository.
> Missing unit tests using ant and unit test errors using maven
> --------------------------------------------------------------
>
> Key: BEANUTILS-287
> URL: https://issues.apache.org/jira/browse/BEANUTILS-287
> Project: Commons BeanUtils
> Issue Type: Bug
> Affects Versions: 1.7.0
> Reporter: Gail Badner
> Fix For: 1.8.0
>
>
> When running unit tests with ant, 402 tests are executed and all are
> successful.
> The following test cases are are not executed with ant:
> ConstructorUtilsTestCase
> FileConverterTestCase
> URLConverterTestCase
> When running unit tests with maven, 413 tests are executed, but 2 fail:
> BeanificationTestCase.testMemoryTestMethodology
> LocaleBeanificationTestCase.testMemoryTestMethodology
> Both errors are due to java.lang.ClassNotFoundException:
> org.apache.commons.beanutils.BetaBean
> When this is fixed, it would be nice if the junit ant task were used to run
> the tests so that the JUnit report can be generated.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
