Bug 1008554
Summary: | Missing javadoc for org.jboss.xts | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jakub Cechacek <jcechace> |
Component: | Other | Assignee: | Yong Yang <yyang> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Jakub Cechacek <jcechace> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.2.0 | CC: | dosoudil, jkudrnac |
Target Milestone: | CR1 | ||
Target Release: | EAP 6.2.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-12-15 16:23:02 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1026701 | ||
Bug Blocks: |
Description
Jakub Cechacek
2013-09-16 15:09:52 UTC
I'm not sure what the right component is for Javadoc bugs, but Documentation should be used for formal documentation maintained by Content Services. Javadoc does not fall under this category. Maybe we need a new component for it? This artifact was excluded from javadoc generation before 6.2.0 due to some error. Now it has been fixed in Jenkins, https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/EAP6-javadoc/75/, and will be included in next ER. FYI: $ cat build/javadoc/artifactsBlacklist.txt org.jboss.as:jboss-as-controller-client org.jboss:jboss-dmr org.jboss.jbossts:jbossxts org.jboss.jbossts:jbossxts-api org.jboss.weld:weld-core org.picketbox:picketbox-commons xalan:serializer org.apache.ws.security:wss4j These javadocs are generated in EAP6.2.0 ER6. The following package still remains missing in docs for 6.2.0.ER6 /home/jcechace/tools/eap/eap6/620/er6/jboss-eap-6.2/modules/system/layers/base/org/jboss/xts/main/jbossxts-4.17.12.Final-redhat-1.jar 1 missing: org.jboss.jbossts.xts.bridge.at No org/jboss/jbossts/xts/bridge/ in jbossxts sources jar, need to rebuild org.jboss.jbossts-narayana-all to solve this issue. [yyang@dhcp-17-104 javadoc-er6]$ jar tf localRepo/org/jboss/jbossts/xts/jbossxts/4.17.12.Final-redhat-1/jbossxts-4.17.12.Final-redhat-1.jar | grep bridge org/jboss/jbossts/xts/bridge/ org/jboss/jbossts/xts/bridge/at/ org/jboss/jbossts/xts/bridge/at/BridgeWrapper.class META-INF/maven/org.jboss.jbossts.xts/bridge/ META-INF/maven/org.jboss.jbossts.xts/bridge/pom.xml META-INF/maven/org.jboss.jbossts.xts/bridge/pom.properties [yyang@dhcp-17-104 javadoc-er6]$ jar tf localRepo/org/jboss/jbossts/xts/jbossxts/4.17.12.Final-redhat-1/jbossxts-4.17.12.Final-redhat-1-sources.jar | grep bridge [yyang@dhcp-17-104 javadoc-er6]$ The source for BridgeWrapper is located in corresponding maven (sub-)module (../bridge/). Including BridgeWrapper.class in jbossxts artifact is configured by using maven-shade-plugin. Hi Vladimir, to keep the sources jar and binary jar consistent, is it possible to remove BridgeWrapper.class from binary jar or add BridgeWrapper.java to sources jar? Optional parameter createSourcesJar has been added into configuration of maven-shade-plugin for jbossxts. Fixed jbossxts source jar will be available in the next builds of jbossts/narayana i.e. newer than 4.17.15.Final-redhat-1. jbossxts sources jar fixed in https://brewweb.devel.redhat.com/buildinfo?buildID=306066 Verified 6.2.0.CR1 |