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
{{ message }}
This repository has been archived by the owner on Dec 15, 2018. It is now read-only.
It would be great to have am integration testsuite that runs locally, so that we can make sure we don't break anything. Currently the tests are more examples than tests as building, deploying and testing them is quiet difficult.
One thing I would like to mention. As you may know we are currently in the process of migrating Ozark to the Eclipse Foundation (see the Eclipse Krazo proposal). As part of this migration, we have to check the licenses of our dependencies to make sure that all the license are allowed (see #179). It MAY be possible, that we need to drop some extensions because they have dependencies with disallowed license. But that's not official yet. But I guess if we start to migrate the examples to the new test suite module, we should prefer to migrate example apps which test core features and example apps which test ASL2-licensed extensions first. Just to make sure we don't spend too much time on migrating apps which we have to remove as part of the migration anyway.
It would be great to have am integration testsuite that runs locally, so that we can make sure we don't break anything. Currently the tests are more examples than tests as building, deploying and testing them is quiet difficult.
See here for the discussion on the mailing list: https://groups.google.com/d/msg/jsr371-users/NZXgRX9610E/jb1l706fCQAJ
The text was updated successfully, but these errors were encountered: