[jboss-jira] [JBoss JIRA] (AS7-6072) Automate creating EAP 6.x public API Javadoc
Ondrej Zizka (JIRA)
jira-events at lists.jboss.org
Wed Dec 5 06:14:21 EST 2012
[ https://issues.jboss.org/browse/AS7-6072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12739531#comment-12739531 ]
Ondrej Zizka edited comment on AS7-6072 at 12/5/12 6:13 AM:
------------------------------------------------------------
Jenkins script
{code}
mv upstream/build/src/main/resources/modules upstream/build/src/main/resources/modules_
cp -r eap/build/src/main/resources/modules upstream/build/src/main/resources/
cd $WORKSPACE/upstream/build/
mkdir javadoc/target
### Includes and excludes.
javadoc/extractPublicApiArtifactsList.sh --batch > javadoc/target/dependencySourceInclExcl.xml
### Groups.
javadoc/extractPackageGroupsByModules.sh > javadoc/target/groups.xml
### Copy <includes>, exclude errorneous .jar's
#xsltproc --output pom2.xml javadoc/pomSetIncludes.xsl pom.xml
## xsltproc doesn't work well with namespaces. Let's try Xalan.
mkdir -p target
cd target
wget -nc http://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar
wget -nc http://repo1.maven.org/maven2/xalan/serializer/2.7.1/serializer-2.7.1.jar
cd ..
#mvn dependency:get -Dartifact=xalan:xalan:2.7.1 -DxremoteRepositories=central::default::http://repo1.maven.apache.org/maven2 -DrepoUrl=http://repo1.maven.apache.org/maven2 -Dmaven.repo.local=foo
#mvn dependency:copy-dependencies -DincludeGroupIds=xalan -DoutputDirectory=target/jars
#java -cp serializer-2.7.1.jar -jar xalan-2.7.1.jar -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl ## Doesn't work for some reason.
java -cp target/serializer-2.7.1.jar:target/xalan-2.7.1.jar org.apache.xalan.xslt.Process -IN pom.xml -OUT pom2.xml -XSL javadoc/ pomSetIncludesAndGroups.xsl
mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding="$BRANDING";
{code}
was (Author: ozizka):
Jenkins script
{code}
mv upstream/build/src/main/resources/modules upstream/build/src/main/resources/modules_
cp -r eap/build/src/main/resources/modules upstream/build/src/main/resources/
cd $WORKSPACE/upstream/build/
mkdir javadoc/target
### Includes and excludes.
javadoc/extractPublicApiArtifactsList.sh --batch > javadoc/target/dependencySourceInclExcl.xml
### Groups.
javadoc/extractPackageGroupsByModules.sh > javadoc/target/groups.xml
### Copy <includes>, exclude errorneous .jar's
#xsltproc --output pom2.xml javadoc/pomSetIncludes.xsl pom.xml
## xsltproc doesn't work well with namespaces. Let's try Xalan.
mkdir -p target
cd target
wget -nc http://repo1.maven.org/maven2/xalan/xalan/2.7.1/xalan-2.7.1.jar
wget -nc http://repo1.maven.org/maven2/xalan/serializer/2.7.1/serializer-2.7.1.jar
cd ..
#mvn dependency:get -Dartifact=xalan:xalan:2.7.1 -DxremoteRepositories=central::default::http://repo1.maven.apache.org/maven2 -DrepoUrl=http://repo1.maven.apache.org/maven2 -Dmaven.repo.local=foo
#mvn dependency:copy-dependencies -DincludeGroupIds=xalan -DoutputDirectory=target/jars
#java -cp serializer-2.7.1.jar -jar xalan-2.7.1.jar -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl ## Doesn't work for some reason.
java -cp target/serializer-2.7.1.jar:target/xalan-2.7.1.jar org.apache.xalan.xslt.Process -IN pom.xml -OUT pom2.xml -XSL javadoc/pomSetIncludes.xsl
mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding="$BRANDING";
{code}
> Automate creating EAP 6.x public API Javadoc
> --------------------------------------------
>
> Key: AS7-6072
> URL: https://issues.jboss.org/browse/AS7-6072
> Project: Application Server 7
> Issue Type: Enhancement
> Components: Build System, Documentation
> Affects Versions: 7.1.3.Final (EAP)
> Reporter: Ondrej Zizka
> Assignee: Ondrej Zizka
> Fix For: 7.2.0.CR1
>
>
> First attempt: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/EAP6-javadoc/
> What's needed:
> * Blacklist of skipped .jar's (cause exceptions when generating)
> * XSLT to put <include>'s to pom.xml
> * XSLT to put <groups> to pom.xml
> See also https://docspace.corp.redhat.com/docs/DOC-105009 (bottom)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jboss-jira
mailing list