Bug 900856 (JBPAPP6-1587)

Link: Added: This issue is related to AS7-582

Attaching includes - new, original, and resulting merge.

Attachment: Added: IncludesNew.txt
Attachment: Added: IncludesOrig.txt
Attachment: Added: Includes.txt

Attaching packages, for comparison.

Attachment: Added: packagesOrig.txt
Attachment: Added: packages-new.txt

Filled http://bugzilla.slf4j.org/show_bug.cgi?id=270 to fix
{quote}
unmappable character for encoding UTF-8
[ERROR] // J�rn Huxhorn: ...
{quote}

Link: Added: This issue depends JBPAPP-9210

{code}
~/work/AS7/ozizka-git/build$ mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding='JBoss Enterprise Application Platform 6.0.1.GA'  -Dmaven.repo.local=../local-repo-eap -s ../tools/maven/conf/settings.xml
{code}

when building the javadoc from EAP, using  ER1 tag, and a command 

       AS7/ozizka-git/build$ mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding='JBoss Enterprise Application Platform 6.0.1.GA'  -Dmaven.repo.local=../local-repo-eap -s ../tools/maven/conf/settings.xml

, I get the following error:

      [ERROR] Unable to get dependency information for junit:junit:jar:4.10-redhat-1: Failed to process POM for junit:junit:jar:4.10-redhat-1: Non-resolvable parent POM for org.jboss:jboss-parent:8-redhat-1: Could not find artifact
      org.jboss.component.management:jboss-component-version-master:pom:6.0.0-redhat-1 in eap6-mirror-setting (http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-6-rhel-6-build/latest/maven/)

I assume 6.0.1-redhat-1 should be used, right?
   http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-6-rhel-6-build/latest/maven/org/jboss/component/management/jboss-component-version-master/

So it should use parent 9-redhat-1:
   http://download.lab.bos.redhat.com/brewroot/repos/jb-eap-6-rhel-6-build/latest/maven/org/jboss/jboss-parent/9-redhat-1/

Link: Added: This issue depends JBPAPP-9865

Link: Added: This issue depends JBPAPP-9877

Apart from reclassification, we also agreed to wait for some fixes in deps' poms - see dependency jiras.
I will resume with ER2.

Should I treat the "unsupported" flag the same as "private", i.e. not include it and it's deps in the Javadoc?

Link: Added: This issue depends JBPAPP-9944

For JavaDoc, unsupported should be treated same as private.

7.1.3.CR1 doesn't contain module com.googlecode.jtype, EAP ER2 does

I'm attaching unsupported[A|B].txt for anyone who wants to compare:
A has unsupported included,
B has them not included.

Attachment: Added: unsupportedA.txt
Attachment: Added: unsupportedB.txt

TODO: Put to readme and push:
{code}
git reset extractPublicApiArtifactsList.sh upstream/master
git reset extractPackageGroupsByModules.sh upstream/master
{code}

http://www.qa.jboss.com/~ozizka/AS7/javadoc/javadoc-EAP-6.0.1.ER2.zip
http://www.qa.jboss.com/~ozizka/AS7/javadoc/6.0.1-ER2/

7. Number of not valid POM's and metadata files
19 of 913
https://hudson.qa.jboss.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-valid-POM-and-Metadata-files

14. Number of BOMs with failures when receiving dependency tree on test pom file with dependency on BOM from repository
6 of 13 (with MEAD and central repo enabled)
8 of 13 (just with MEAD repo)
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-boms-for-dependency-tree

15. Number of BOMs with failures when receiving effective pom on test pom file with dependency on BOM from repository
2 of 13 (with MEAD and central repo enabled)
2 of 13 (just with MEAD repo)
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EAP6/view/EAP6-Repository/job/eap-60-repository-maven-check-boms-for-effective-pom

Link: Added: This issue is related to AS7-583

Closing this issue as it makred as resolved.

It is not meant for verification (task)

Reopening as per JBPAPP-10099

Notes for myself

{code}
cp -r ../ozizka-git3/build/src/main/resources/modules/ build/src/main/resources/modules/
./build/javadoc/extractPublicApiArtifactsList.sh
# Copy <includes>, check changes and exclude errorneous .jar's
./build/javadoc/extractPackageGroupsByModules.sh  > grp.txt
# Copy & check the <groups>
cd build
export JAVA_HOME=/usr/lib/jvm/jdk1.7.0_04/
mvn javadoc:aggregate -PjavadocDist -Djavadoc.branding='JBoss Enterprise Application Platform 6.0.1.GA';
{code}

Uploaded fixed (see JBPAPP-10099) Javadoc: 
http://www.qa.jboss.com/~ozizka/AS7/javadoc/javadoc-EAP-6.0.1.ER3-master.jar
http://www.qa.jboss.com/~ozizka/AS7/javadoc/6.0.1-ER3-master/

This time, I've had problems with Netty. The group was changed from org.jboss.netty to io.netty, but still some parts have Netty in guts:
https://github.com/jbossas/jboss-as/pull/3187#issuecomment-9465445

Generated from current AS/master, using eap/master's module.xml's.

Link: Added: This issue relates to JBPAPP-10222

Regenerated, this time using eap/eap6 module.xml's.
(Master is just a copy of upstream/master.)

http://www.qa.jboss.com/~ozizka/AS7/javadoc/6.0.1.ER3-eap6.jar
http://www.qa.jboss.com/~ozizka/AS7/javadoc/6.0.1.ER3-eap6

Yea, sorry for that - there are other jiras for the same issue with javadoc, so it is a little confusing.

As I commented on [JBPAPP-10099|https://issues.jboss.org/browse/JBPAPP-10099]

---------------------------
http://pastebin.test.redhat.com/112541

There may be some  confusion about org.apache.cxf.* as api is public and implementation isn't. However I've made some quick tweaks of control script so it now shouldn't list package as leaked if it is also part of some public module

No problem. I use Jira extensively, also to track my tasks... so I may have jiras which seem to be duplicate. You can tell such apart by Reporter == Assignee == Ondrej Zizka :)
Usually, people verify and then reopen/close jiras of which they are Reporters.

Need to update upstream...

This issue is not a blocker nor a critical for EAP 6.0.1. Thus it is moved to TBD EAP 6 to be triaged for the next EAP 6.x release.

Ok. Actually, I believe the EAP part is done, just waiting for QA to confirm.

Link: Added: This issue is a dependency of JBPAPP-10099

Docs QE Status: Removed: NEW 

Link: Added: This issue relates to JBPAPP6-1327

EAP part is certainly not done. There are no leaked private packages in the doc anymore, but some public packages are still missing (because they are blacklisted) - see JBPAPP6-1327. If there is a reason why those packages are missing then it should be mentioned in Module Classification document on docspace. Then it will be considered correct and we can close this issue. 

After the update of Classification document the only issue left is com.googlecode.jtype but Ondra should be discussing this with productization - let me know about the decision. 

Asked Brian and Jimmy Wilson to confirm that it's a public API.

Brian confirmed com.googlecode.jtype  is not supposed to be public. See JBPAPP6-1673.

Link: Added: This issue depends JBPAPP6-1673

JavaDoc for EAP 6.0.1.GA was provided with the release: http://download.devel.redhat.com/released/JBEAP-6/6.0.1/zip/

Considering this Done.