Create a release module for the tck distribution #1531
Conversation
Fixes #1523 Signed-off-by: Scott M Stark <[email protected]>
…nguage-tck version change Signed-off-by: Scott M Stark <[email protected]>
| </goals> | ||
| <configuration> | ||
| <groupId>jakarta.tck</groupId> | ||
| <artifactId>el-tck</artifactId> |
There was a problem hiding this comment.
Should this be changed to "el-platform-tck" or rename el module artifact id to "el-tck"
There was a problem hiding this comment.
I think it would be better to have a common naming convention for all modules in platform TCK. Maybe better to keep "el-tck" and rename the artifact id in module el. I named it "el-platform-tck" to distinguish with the standalone el-tck/ folder.
There was a problem hiding this comment.
@alwin-joseph - Please note rename of EL standalone TCK, should not duplicate balloted EL standalone TCK artifact.That will impact future service releases of EL standalone TCK.
There was a problem hiding this comment.
For standalone el-tck/ module, we have below :
<artifactId>jakarta-expression-language-tck</artifactId>
<name>el-tck</name>
For platform el/ module
<artifactId>el-platform-tck</artifactId>
<name>el</name>
Maybe we can continue to use el-platform-tck as artifact name for platform(so as to not confuse with el-tck module name of the standalone) and correct the same here in line 128, for now.
Fixes Issue
Fixes #1523
CC @alwin-joseph @anajosep @arjantijms @cesarhernandezgt @dblevins @m0mus @edbratt @gurunrao @jansupol @jgallimore @kazumura @kwsutter @LanceAndersen @bhatpmk @RohitKumarJain @shighbar @gthoman @brideck @OndroMih @dmatej
@starksm64 @scottmarlow