Repository: juddi Updated Branches: refs/heads/master 9c86cd3db -> 39f48ebcd
JUDDI-962 adding hooks to copy the asciidoc/docbook generated stuff into the correct relevative paths during site generation Project: http://git-wip-us.apache.org/repos/asf/juddi/repo Commit: http://git-wip-us.apache.org/repos/asf/juddi/commit/39f48ebc Tree: http://git-wip-us.apache.org/repos/asf/juddi/tree/39f48ebc Diff: http://git-wip-us.apache.org/repos/asf/juddi/diff/39f48ebc Branch: refs/heads/master Commit: 39f48ebcd78587a2faa1b519f67fe4e8eef1fcfc Parents: 9c86cd3 Author: Alex O'Ree <[email protected]> Authored: Mon Sep 25 07:23:54 2017 -0400 Committer: Alex O'Ree <[email protected]> Committed: Mon Sep 25 07:23:54 2017 -0400 ---------------------------------------------------------------------- pom.xml | 49 ++++++++++++++++++++++++++++++ src/site/markdown/committers.md | 2 ++ src/site/markdown/issue-tracking.html | 15 --------- src/site/markdown/source.md | 21 ++++++++++++- 4 files changed, 71 insertions(+), 16 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/juddi/blob/39f48ebc/pom.xml ---------------------------------------------------------------------- diff --git a/pom.xml b/pom.xml index 49c297c..6f9f54e 100644 --- a/pom.xml +++ b/pom.xml @@ -808,6 +808,54 @@ under the License. <profiles> + <profile> + <id>prepare-site</id> + <activation> + <file> + <exists>src/site/site.xml</exists> + </file> + </activation> + <build> + <plugins> + <plugin> + <groupId>org.apache.maven.plugins</groupId> + <artifactId>maven-antrun-plugin</artifactId> + <dependencies> + <!-- force the juddi docs module to build --> + <dependency> + <groupId>org.apache.juddi.juddi-docs</groupId> + <artifactId>juddi-docs</artifactId> + <version>${project.version}</version> + <type>pom</type> + </dependency> + + </dependencies> + <executions> + <execution> + <phase>site</phase> + <configuration> + <target> + + + <copy todir="target/site/docs/3.3/juddi-client-guide/"> + <fileset dir="docs/asciidoc/ClientGuide/target/docbook/publish/en-US"/> + </copy> + + <copy todir="target/site/docs/3.3/juddi-guide/"> + <fileset dir="docs/asciidoc/Guide/target/docbook/publish/en-US"/> + </copy> + + </target> + </configuration> + <goals> + <goal>run</goal> + </goals> + </execution> + </executions> + </plugin> + </plugins> + </build> + </profile> <profile> <id>doclint-java8-disable</id> <activation> @@ -965,6 +1013,7 @@ under the License. <exclude>**/*.sh</exclude> <exclude>**/*.bat</exclude> <exclude>**/*.policy</exclude> + <exclude>**/*.md</exclude> <exclude>**/*.form</exclude> <exclude>**/jboss-deployment-structure.xml</exclude> <exclude>**/MANIFEST.MF</exclude> http://git-wip-us.apache.org/repos/asf/juddi/blob/39f48ebc/src/site/markdown/committers.md ---------------------------------------------------------------------- diff --git a/src/site/markdown/committers.md b/src/site/markdown/committers.md index b96a603..e8b8b26 100644 --- a/src/site/markdown/committers.md +++ b/src/site/markdown/committers.md @@ -51,6 +51,8 @@ All jUDDI committers are encouraged to create public/ private key pairs and plac ### Release Procedure +**TIP:** produce the release artifacts with JRE/JDK7 + 1. Ensure the build works (mvn clean install -Pdist) 2. Grab the current version's release notes using JIRA. Goto JIRA, Versions, pick the version, then Release notes. Replace the release notes html file within the source with the contents from JIRA. 3. mvn release:prepare -Papache-release http://git-wip-us.apache.org/repos/asf/juddi/blob/39f48ebc/src/site/markdown/issue-tracking.html ---------------------------------------------------------------------- diff --git a/src/site/markdown/issue-tracking.html b/src/site/markdown/issue-tracking.html deleted file mode 100644 index 926ffeb..0000000 --- a/src/site/markdown/issue-tracking.html +++ /dev/null @@ -1,15 +0,0 @@ -<html> -<head -<meta http-equiv="refresh" content="1; url=http://issues.apache.org/jira/browse/JUDDI"; /> -<script type="text/javascript"> - window.location.href="http://issues.apache.org/jira/browse/JUDDI";; -</script> -</head> -<body> -Redirecting... -<br><br> -Click this link if this takes too long... -<a href="http://issues.apache.org/jira/browse/JUDDI";> -http://issues.apache.org/jira/browse/JUDDI -</a>. -</html> http://git-wip-us.apache.org/repos/asf/juddi/blob/39f48ebc/src/site/markdown/source.md ---------------------------------------------------------------------- diff --git a/src/site/markdown/source.md b/src/site/markdown/source.md index cdb9b30..7bd9bb2 100644 --- a/src/site/markdown/source.md +++ b/src/site/markdown/source.md @@ -36,4 +36,23 @@ The Git client can go through a HTTP proxy, if you configure it to do so. $ git config --global http.proxy (server) -See the [http://git-scm.com/docs](Manual) for more information. \ No newline at end of file +See the [http://git-scm.com/docs](Manual) for more information. + + +### Approximate build times + +Often (well, not really that often) we get asked about how long it takes to build jUDDI. Here you go. + +Numbers below are on Windows 10, SSD, AMD 8 core CPU and with linear surefire execution. + +| Configuration | Build time (hh:mm:ss) | Description | +| ------------------------------------ | ---------------------- | --------------------------------------------- | +| mvn clean install -DskipTests=true | 00:01:16 | skipping the tests +| mvn clean install | 00:27:25 | the normal build with tests +| nvn clean install -T 1C | 00:15:33 | the normal build with one thread per CPU core +| mvn clean install -Pdist | 00:41:02 | just like the release profile but without sigatures, includes integration tests +| mvn clean install -Pdist -T 1C | 00:40:30 | just like the release profile but without sigatures, includes integration tests +| mvn release:prepare -Papache-release | | this happens when we cut a release (the whole 9 yards), includes integration tests +| mvn site | 00:16:37 | generate the website +| mvn site:stage | 00:00:28 | prepare the site for upload + --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
