They are binary identical as it is checked by the TCK. The reason we have our own AFAIR is that - when we work on a preview of the spec, we need to write our own anyways as the Oracle teams don't necessarily have the same timeframe - there is some license subtleties involved and we prefer to write our own from a clean room. - some APIs have actual code - and thus bugs - and we want to be able to fix them - and have. Emmanuel On Wed 2014-05-21 3:03, hanasaki(a)gmail.com wrote:

Looks that report is counting internal impl classes and all maven deps, so its not very accurate. It’s a good idea though. On May 21, 2014, at 8:18 AM, Andrey Ponomarenko <aponomarenko(a)rosalab.ru&gt; wrote: -- Jason T. Greene WildFly Lead / JBoss EAP Platform Architect JBoss, a division of Red Hat

Question is what is proper or reference, for our Jars we are sure they pass Java EE6/7 TCK signature tests (which tests mostly what you are comparing) question is from where id javaee.jar you are using come frome, and does it also pass TCK signature tests. On Wed, May 21, 2014 at 4:17 PM, Andrey Ponomarenko <aponomarenko(a)rosalab.ru > I've corrected the report: > > http://upstream-tracker.org/downloads/compat_reports/javaee/6.0_to_jboss-... > > Added --skip-internal="\A(java_cup|org)" cmd option in order to check > javax package only. > > Jason Greene wrote: > > Looks that report is counting internal impl classes and all maven deps, > so its not very accurate. It’s a good idea though. > > > > On May 21, 2014, at 8:18 AM, Andrey Ponomarenko <aponomarenko(a)rosalab.ru&gt; > > > >> API changes report: > >> > http://upstream-tracker.org/downloads/compat_reports/javaee/6.0_to_jboss-... > >> > >> It's generated by https://github.com/lvc/japi-compliance-checker > >> > >> $> japi-compliance-checker -l javaee javaee-api-6.0.jar > >> jboss-javaee-all-6.0-3.0.2.Final.jar > >> > >> hanasaki(a)gmail.com wrote: > >>> What are the differences between the JBoss EE6 API and the Oracle EE6 > >>> API as specified by the below maven dependencies? What issues, if any, > >>> are there in using the oracle javax api spec? Since the spec is final, > >>> wouldn't there be no differences to expect? > >>> > >>> Thank you. > >>> > >>> reference info below: > >>> > >>> <dependency> > >>> <groupId>javax</groupId> > >>> <artifactId>javaee-api</artifactId> > >>> <version>6.0</version> > >>> <scope>compile</scope> > >>> </dependency> > >>> > >>> <groupId>org.jboss.spec</groupId> > >>> <artifactId>jboss-javaee-6.0</artifactId> > >>> <artifactId>jboss-javaee-all-6.0</artifactId> > >>> <version>3.0.2.Final</version> > >>> </dependency> > > -- > Andrey Ponomarenko, NTC IT ROSA. > http://www.rosalab.com/ > > _______________________________________________ > wildfly-dev mailing list > wildfly-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/wildfly-dev >

On Wed, May 21, 2014 at 4:27 PM, Andrey Ponomarenko <aponomarenko(a)rosalab.ru I know where it is from, but question is, is it official javaee artifact?, AFAIK only with JEE7 did this became mandatory as part of JSR for example just compare http://repo1.maven.org/maven2/javax/javaee-api/7.0/javaee-api-7.0.pom vs http://repo1.maven.org/maven2/javax/javaee-api/6.0/javaee-api-6.0.pom to see what I mean, tomaz

Agreed, that is why I am saying that javaee6 jar is not really representative, what was done with javaee7 one is completely different story. On Wed, May 21, 2014 at 5:16 PM, Shelly McGowan <smcgowan(a)redhat.com&gt; wrote: