-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Prepare for the 4.1.0.RC1 release (#562)
* Drop the unused eclipse ide sections in doc * add logging to weld embedded profile of tck runner * Fix the wildfly updater pom * Towards RC1, updated dist build docs and cleaned up the TCK reference guide * Rename the Configuration CdiLiteMode to CoreMode Fixes #561 * Allow the distribution license to be specified via license.file property * Remove unused lib dir * Update to cdi.api.version 4.1.0.RC1 --------- Signed-off-by: Scott M Stark <[email protected]>
- Loading branch information
Showing
30 changed files
with
172 additions
and
429 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,21 @@ | ||
= Jakarta CDI TCK dist-build | ||
This document describes how the dist-build functions to produce the CDI TCK distribution zip bundle. | ||
This document describes how the dist-build functions to produce the CDI TCK distribution zip bundle. In the description below, CDI_TCK_DIST refers to the root directory of the CDI TCK distribution zip after being unpacked. For example, for the 4.1.0 release it would be cdi-tck-4.1.0. | ||
|
||
== Files in dist-build | ||
- The src/main/assembly/assembly.xml defines how the distribution zip is put together from contents in the CDI TCK repo, and the Weld artifacts | ||
- The src/test/* tree is copied to the CDI_TCK_DIST/weld/jboss-tck-runner/src/test and is related to running the TCK against Weld and WildFly/Weld. | ||
- artifact-install.pom is installed as CDI_TCK_DIST/artifacts/pom.xml along with the TCK artifacts and its dependencies to allow one to install the TCK into a local maven repository. | ||
- jboss-as-updater.pom is bundled as CDI_TCK_DIST/weld/jboss-as/pom.xml and can be used to update a bare WildFly installation with the Weld version and Jakarta API artifacts that correspond to the versions used by the TCK. | ||
- jboss-runner.pom is bundled as CDI_TCK_DIST/weld/jboss-tck-runner/pom.xml and contains the profiles used to run the TCK against, Weld in embedded and se modes as well as inside of the WildFly container. | ||
- pom.xml - defines the distribution dependencies and the maven-assembly-plugin configuration | ||
- README.adoc is the CDI_TCK_DIST top level readme file that describes the distribution contents | ||
|
||
== Running the build | ||
To create the distribution, run the following from the project root: | ||
|
||
[source, console] | ||
---- | ||
mvn -Drelease install | ||
---- | ||
|
||
The distribution zip file will be found in the dist-build/target directory. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,36 @@ | ||
# Additional loggers to configure (the root logger is always configured) | ||
loggers=org.jboss.weld,org.jboss.weld.Bootstrap | ||
|
||
logger.level=INFO | ||
logger.handlers=FILE,CONSOLE | ||
|
||
logger.org.jboss.weld.level=INFO | ||
logger.org.jboss.weld.useParentHandlers=true | ||
|
||
logger.org.jboss.weld.Bootstrap.level=INFO | ||
logger.org.jboss.weld.Bootstrap.useParentHandlers=true | ||
|
||
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler | ||
handler.CONSOLE.level=INFO | ||
handler.CONSOLE.formatter=COLOR-PATTERN | ||
handler.CONSOLE.properties=autoFlush,target | ||
handler.CONSOLE.autoFlush=true | ||
handler.CONSOLE.target=SYSTEM_OUT | ||
|
||
handler.FILE=org.jboss.logmanager.handlers.PeriodicRotatingFileHandler | ||
handler.FILE.level=ALL | ||
handler.FILE.formatter=PATTERN | ||
handler.FILE.properties=autoFlush,append,fileName,suffix | ||
handler.FILE.constructorProperties=fileName,append | ||
handler.FILE.autoFlush=true | ||
handler.FILE.append=true | ||
handler.FILE.fileName=tck.log | ||
handler.FILE.suffix=.yyyy-MM-dd | ||
|
||
formatter.PATTERN=org.jboss.logmanager.formatters.PatternFormatter | ||
formatter.PATTERN.properties=pattern | ||
formatter.PATTERN.pattern=%d{yyyy-MM-dd HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%e%n | ||
|
||
formatter.COLOR-PATTERN=org.jboss.logmanager.formatters.PatternFormatter | ||
formatter.COLOR-PATTERN.properties=pattern | ||
formatter.COLOR-PATTERN.pattern=%K{level}%d{HH\:mm\:ss,SSS} %-5p [%c] (%t) %s%e%n |
Oops, something went wrong.