You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user of devon4j, I want to upgrade my project to the latest version of devon4j to get security-fixes and new features, but I do not want to be forced to migrate to JUnit5 so that I do not have to waste lots of effort and money without adding real value for a "legacy project".
The automigration in devonfw-ide is not working properly so manual migration to JUnit5 is required. It absolutely makes sense to start greenfield projects with JUnit5 but projects that started with JUnit4 and have tons of tests already should not be forced to upgrade.
Of course this can be fiddled manually with exclusions and added dependencies. However, it would be much better to add a devon4j-test-junit4 module that cleanly provides this support and change the migration in devonfw-ide to instead replace devon4j-test with devon4j-test-junit4 for projects prior to devon4j 3.2.0.
The text was updated successfully, but these errors were encountered:
As a user of devon4j, I want to upgrade my project to the latest version of devon4j to get security-fixes and new features, but I do not want to be forced to migrate to JUnit5 so that I do not have to waste lots of effort and money without adding real value for a "legacy project".
The automigration in devonfw-ide is not working properly so manual migration to JUnit5 is required. It absolutely makes sense to start greenfield projects with JUnit5 but projects that started with JUnit4 and have tons of tests already should not be forced to upgrade.
Of course this can be fiddled manually with exclusions and added dependencies. However, it would be much better to add a
devon4j-test-junit4module that cleanly provides this support and change the migration indevonfw-ideto instead replacedevon4j-testwithdevon4j-test-junit4for projects prior to devon4j3.2.0.The text was updated successfully, but these errors were encountered: