The idea is to just type "mvn clean install" from the root. I'll update staged version to get rid of that 3.0.1-SNAPSHOT. The scripts use mvn to update the versions to the release, but they always miss something.
I
see the old-tck is not integrated with the main
pom as a module to be executed from
authentication-tck-3.0.1/tck. Is this expected?
Should we be running the old tck tests separately
from authentication-tck-3.0.1/tck/old-tck.
That's strange, they should run by default via the
profile:
I
was trying to run the old tck tests from
authentication-tck-3.0.1/tck/old-tck, using “mvn
clean install
-Pstaging,glassfish-ci-managed,platform
-Dglassfish.version=7.0.0-M6”. I get pom.xml not
found, possibly due to version mismatch between
3.0.1-SNAPSHOT and 3.0.1.
Does that also happen with the staged version, or only
when running from a checkout of the repository?
The
major thing fixed in the service release is
merging the two bundles from the 3.0.0 release
into one. A smaller fix is printing the result
summary directly in the log of a maven build.
Previously the result summary was dependent on
parsing the junit xml based file.
If
the TCK bundle is found to be correct, we can
initiate its promotion.
I
just tested it on GlassFish 7.0 M6, where it
passes.