jakartaee / enterprise-beans Goto Github PK

EJB tests dependant on JAXRPC have been prunned with Jakarta EE 9 CTS.
Source for the tests can be found at https://github.com/eclipse-ee4j/jakartaee-tck/tree/8.0.2/src/com/sun/ts/tests/ejb/ee/webservices/allowedmethodstest

Details of the tests are as follows:
1)testName: wsbmAllowedMethodsTest1
package: com.sun.ts.tests.ejb.ee.webservices.allowedmethodstest.bm
assertion_ids: EJB:SPEC:121; EJB:SPEC:121.1; EJB:SPEC:121.2;EJB:SPEC:121.3; EJB:SPEC:121.4; EJB:SPEC:121.5; EJB:SPEC:121.6;EJB:SPEC:121.7; EJB:SPEC:121.10; EJB:SPEC:121.11; EJB:SPEC:121.12;EJB:SPEC:121.13; EJB:SPEC:121.14;EJB:SPEC:121.15; EJB:SPEC:121.16;EJB:JAVADOC:172; EJB:SPEC:10; EJB:SPEC:7; EJB:SPEC:67

2)testName: wsbmAllowedMethodsTest2
package: com.sun.ts.tests.ejb.ee.webservices.allowedmethodstest.bm
assertion_ids: EJB:SPEC:121.2; EJB:SPEC:823

3)testName: wscmAllowedMethodsTest1
package: com.sun.ts.tests.ejb.ee.webservices.allowedmethodstest.cm
assertion_ids: EJB:SPEC:120; EJB:SPEC:120.1; EJB:SPEC:120.2;EJB:SPEC:120.3; EJB:SPEC:120.4; EJB:SPEC:120.5; EJB:SPEC:120.6;EJB:SPEC:120.7; EJB:SPEC:120.10; EJB:SPEC:120.11; EJB:SPEC:120.12;EJB:SPEC:120.13; EJB:SPEC:120.14; EJB:SPEC:120.15; EJB:SPEC:67;EJB:JAVADOC:172

This is a place holder issue for Pull request from javaee/javax.ejb#6

• [api] Merge 4.0.0-RC1 branch in master
• [api] Add an empty relativePath to parent to resolve ee4j-parent from repository instead of parent directory
• [api] Legal documents in release jar are incorrect
  The CDDL license.txt is included in META-INF. This is pulled from org.glassfish:legal:1.1 by maven-remote-resources-plugin. This needs to be removed.
  The legal.doc.source property is pointing to current directory, this should be changed to parent directory. The License.md and Notice.md reside in the parent directory.
• [api] Remove the maven-release-plugin, maven-gpg-plugin and nexus-staging-maven-plugin as they are already configured in the parent
• [api] Upgrade java compiler source and target version from 1.6 to 1.8
• [api] Unable to build with JDK11 - Fix javadoc issues and configure maven-javadoc-plugin with source as 1.8
• [api] Prepare for 4.0.0-RC2
• [spec] asciidoc-to-html does not stamp project version, date and status in HTML output.
• [spec] Remove the maven-release-plugin as it is unused.

EJB provides a subsection for scheduler and timers.

To create a timer you can inject a TimerService like

@Inject
TimerService timerService;

The TimerService provides methods to create single-action timer amonst other ways either by TimerService#createTimer(Date, Serializable) or TimerService#createSingleActionTimer(Date, TimerConfig but none where you can with a java.time parameter like LocalDateTime.

Currently, it is required to convert LocalDateTime or other members of java.time to Date by using converters like

public Date convertToDateViaSqlTimestamp(LocalDateTime dateToConvert) {
    return java.sql.Timestamp.valueOf(dateToConvert);
}

or through java.time.Instant

Date convertToDateViaInstant(LocalDateTime dateToConvert) {
    return java.util.Date
      .from(dateToConvert.atZone(ZoneId.systemDefault())
      .toInstant());
}

It was telegraphed that the alignment from JakartaEE/JavaEE to Java 8+ was an important step and adding support for java.time is part of this.

I suggest adding methods

public Timer createSingleActionTimer(LocalDateTime, TimerConfig timerConfig) throws IllegalArgumentException, IllegalStateException, EJBException

and sibling methods to add java.time support to ejb timers.

After reviewing the jenkins log files and the infra release job, I have come to the conclusion that all pom.xml should point to SNAPSHOT in the master branch to perform a successful release.

To fix this issue:

• Revert ea0a7bd
• Remove the following lines in the Jenkins job configuration under the build->execute shell => Line 15

sed -i s/4.0.0-RC1/4.0.0-SNAPSHOT/g pom.xml api/pom.xml spec/pom.xml
sed -i s,https://oss.sonatype.org/,https://jakarta.oss.sonatype.org/, pom.xml api/pom.xml spec/pom.xml

The first line replaces the RELEASE_VERSION with SNAPSHOT_VERSION in all pom files. This is unnecessary if all poms are already pointing to SNAPSHOT.

The second line is not required since this configuration is part of parent pom and this was removed as part of commit 7151df1#diff-8658bb96fff6ac848cd28d3242fce067L375

Create/Update CONTRIBUTING files

Per input from the Eclipse EMO, each Specification Project needs to ensure that a CONTRIBUTING.md or CONTRIBUTING.adoc file exists in each specification-related repository maintained by Specification Projects.
In addition, the CONTRIBUTING.md or CONTRIBUTING.adoc file needs to include the following text:

## Eclipse Development Process

This Eclipse Foundation open project is governed by the Eclipse Foundation
Development Process and operates under the terms of the Eclipse IP Policy.

The Jakarta EE Specification Committee has adopted the Jakarta EE Specification
Process (JESP) in accordance with the Eclipse Foundation Specification Process
v1.2 (EFSP) to ensure that the specification process is complied with by all
Jakarta EE specification projects.

* https://eclipse.org/projects/dev_process
* https://www.eclipse.org/org/documents/Eclipse_IP_Policy.pdf
* https://jakarta.ee/about/jesp/
* https://www.eclipse.org/legal/efsp_non_assert.php

Please do this at your earliest convenience.
Thank you!

-- EE4J PMC ([email protected])

Passing Release Review is a required step before making a first public release. Deadline for passing the review is Nov 30th, 2018. Release review takes some time to complete, so it makes sense initiating it as soon as possible.

• Start Release Review
• Update Release Review Tracker

Additional information:

• How to submit a release review
• Eclipse Handbook

EJB permission check before call. It is used when the client would like to determine, it has access or not. Example.: a webpage has some input fields and the developer would like to disable the fields that is not allowed.

We need to create a release CI/CD pipeline for this project.

Use these documents as a reference:

• How to release the first Eclipse version of projects
• JSONP release job
• Release job on the new cloud infra

Hi,

I was working on Apache TomEE TCK and investigating a failure.
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/ejb30/lite/naming/context/Client.java#L127

It calls this
https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/ejb30/lite/naming/context/Test.java#L277

In essence, it was failing on TomEE because close was not allowed like bind for instance (close considered as changing the naming context)

The specification says
https://jakarta.ee/specifications/enterprise-beans/4.0/jakarta-enterprise-beans-spec-core-4.0.html#container-provider-responsibility

I checked Tomcat
https://github.com/apache/tomcat/blob/master/java/org/apache/naming/NamingContext.java#L758

It seems to also not allow close.

TCK seems to be considering close() as a read-only operation.
The specification does not seem to make any difference for close().

The container must ensure that the enterprise bean instances have only read access to their environment variables. The container must throw the javax.naming.OperationNotSupportedException from all the methods of the javax.naming.Context interface that modify the environment naming context and its subcontexts.

Does this require an additional not in the spec to clarify what the TCK is actually testing?
Or is the TCK behaviour questionable?

Interop tests have been pruned in Jakarta EE 9 CTS.
Source for the tests can be found at https://github.com/eclipse-ee4j/jakartaee-tck/tree/8.0.2/src/com/sun/ts/tests/interop
The interoperability test directories are:
o rmiiiop
o ejb
o security
o integration
o tx
o csiv2
o saaj

Hi community,

I'm working on the TCK for Apache TomEE and got an interesting failure I'd like to discuss here.

To run them, use the following command

./runtests --web tomee-plume com.sun.ts.tests.ejb32.lite.timer.schedule.expire.Client

This is the part failing

https://github.com/eclipse-ee4j/jakartaee-tck/blob/master/src/com/sun/ts/tests/ejb32/lite/timer/schedule/expire/Client.java#L231

java.lang.IllegalArgumentException: End time cannot be before start time
at org.apache.openejb.quartz.impl.triggers.CronTriggerImpl.setEndTime(CronTriggerImpl.java:417)
at org.apache.openejb.core.timer.EJBCronTrigger.(EJBCronTrigger.java:121)
at org.apache.openejb.core.timer.CalendarTimerData.initializeTrigger(CalendarTimerData.java:61)
at org.apache.openejb.core.timer.TimerData.newTimer(TimerData.java:222)
at org.apache.openejb.core.timer.EjbTimerServiceImpl.initializeNewTimer(EjbTimerServiceImpl.java:738)
at org.apache.openejb.core.timer.EjbTimerServiceImpl.createTimer(EjbTimerServiceImpl.java:715)
at org.apache.openejb.core.timer.TimerServiceImpl.createCalendarTimer(TimerServiceImpl.java:83)
at org.apache.openejb.core.timer.TimerServiceWrapper.createCalendarTimer(TimerServiceWrapper.java:79)
at com.sun.ts.tests.ejb30.timer.common.TimerBeanBaseWithoutTimeOutMethod.createTimer(TimerBeanBaseWithoutTimeOutMethod.java:140)
 
When we want to set the endTime to Quartz, we get the exception above which does not sound stupid.

The test says

   * @testName: endNeverExpires
   * 
   * @test_Strategy: create a timer with year="currentYear - currentYear+1", and
   * end="currentYear-1". The end value is prior to the year values, and this
   * timer will never expire. Creating this timer will succeed, but any timer
   * method access in a subsequent business method will result in
   * NoSuchObjectLocalException.

To me it appears to be a misuse of the endDate.
Did I miss something?

This is a place holder issue for Pull request from javaee/javax.ejb#1

In order to prepare this project to engage in specification work, we need to convert it into a specification project as defined by the Eclipse Foundation Specification Process (EFSP). As part of this work, we will change the project name and the scope.

We'll use this issue to capture the work that needs to be done as part of this effort.

• Resolve #38
• Resolve #37
• Successful complete a restructuring review
• Designate the project as a specification project of the Jakarta EE Working Group
• Change project name
• Change project scope

This assumes that the project team chooses to use a single repository for both the specification document and the existing API. Webmaster can create a separate spec repository if the project team prefers that.

Update the scope statement for the project: https://projects.eclipse.org/projects/ee4j.jakartaee-platform/governance

See https://docs.google.com/spreadsheets/d/1FPLjo_DJDOQngVtdrYgaDk98d9NBG-0ODgdmOG3LOsI/edit?usp=sharing for examples.

Now that the specification committee ballot has concluded, the following steps need to be completed by the spec team:

• promotes api staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
• go through the merged jakarta.ee specification website page to verify all the links are valid.
• approve the compatibility request.
• merge any final release branch as appropriate for the branch management for the project.
  N/A

Per the discussions on the Spec Committee and Platform Dev mailing lists, it's been discovered that many of the Javadoc and Spec references to the EFSL need updating. Please reference the following required updates and keep them in mind as your Spec Project is updating the files for Jakarta EE 9.

Note: Some Spec Projects have already started or even completed these updates. If so, just kindly return/close this Issue. Thanks!

Required EFSL updates for Javadoc

For javadoc, the EFSL.html located in src/main/javadoc/doc-files should be modified as follows:

• the <<url to this license>> needs to be replaced with efsl.php link[1]
• the [title and URI of the Eclipse Foundation specification document] needs to be replaced with the Specification Name and URL (Reference [2] for an example.)
• The javadoc footer copyright year needs to be updated to 2018, 2020 as defined in the pom.xml

Required EFSL updates for Specifications

For specification, the license-efsl.adoc located in src/main/asciidoc should be modified as follows:

• Update copyright year to 2018, 2020 from 2019. Add link to EFSL.
• the <<url to this license>> needs to be replaced with efsl.php link[1]
• the [title and URI of the Eclipse Foundation specification document] needs to be replaced with the Specification Name and URL (Reference [2] for an example.)

[1] https://www.eclipse.org/legal/efsl.php
[2] https://jakarta.ee/specifications/enterprise-beans/4.0/

Core Specification:
Chapter 6. Persistence - 5 Links
Section 9.2.1. Application Exceptions - 2 Links
Section 11.2.5. Programmatic Access to Caller’s Security Context - 2 links
Section 11.6.5. Security Methods in jakarta.ejb.EJBContext - 2 links
12.2.5.3. Timeout Callback Method Requirements - 2 links

Optional Specification:
Section 13.3. Public Draft - 3 links
Section 13.5. Final Release Candidate - 1 link

see jakartaee/specifications#318

Jakarta release of this API has wrong value of OSGi Bundle-SymbolicName in MANIFEST.MF.
Current value is javax.ejb-api but expected value could be jakarta.ejb-api .

@hussainnm can you please specify which exact changes are still open for the core specification document? I will then process these.

This should apply for all files mentioned in: https://github.com/eclipse-ee4j/ejb-api/blob/master/spec/src/main/asciidoc/enterprise-beans-spec-core.adoc

I can of course go through the complete set of instructions as described in https://github.com/jakartaee/specification-committee/blob/master/steps_javaee_to_jakartaee.adoc, if thats the right place to start

The "jakarta.ejb-api-4.0.0-RC1.jar" API jar contains classes from the "jakarta.transaction" package.   They also show up in the javadoc jar as well.

https://jakarta.oss.sonatype.org/content/repositories/releases/jakarta/ejb/jakarta.ejb-api/4.0.0-RC1/

The "jakarta.transaction" package should just be a dependency, not an include.

Server to server (different vm and host) connection
Server to client (java se api)(different vm and host)

Easy way via jax-rs: create/generate rest service to EJB remote if annotated: @Remote(jaxRsPath="/example") (if empty that is not allowed) or @Remote(jaxRsConfigClass=Example.class)

Security: basic authentication and client cert authentication is already defined.

Client easy way: use MicroProfile Rest Client or own api to provide lower layer to access EJB Remote at Java SE.

To test Jakarta EE 8 compatibility we need to create a Jenkins job on project's Cloud Jenkins instance formally testing the API against the relevant TCK and as needed, relevant CTS subset tests.

For projects that do not already have automated testing, there is provided parameterized Jenkins job that can be invoked to perform these tests. User provides a link to an Eclipse GlassFish test build and sets the test sub-set parameters:

• For CTS -- https://ci.eclipse.org/jakartaee-tck/job/jakartaeetck-certification/
• For Stand-alone TCKs -- https://ci.eclipse.org/jakartaee-tck/job/standalonetck-certification/

Additional instructions and guidance for using and directly running TCKs is available on this wiki. Also in the jakartaee-tck project repository.

Is your feature request related to a problem? Please describe.
Jakarta EE 9 is the next major release, with the main focus of moving from the javax namespace to the jakarta namespace.

Describe the solution you'd like
This issue will be used to track the progress of this work effort via the Jakarta EE 9 Project board.

Additional context
Jakarta EE Specification Process
Eclipse Project Handbook
Eclipse Release Record for Jakarta EE 9

ToDo

• Create Eclipse Release Record in your respective Jakarta Specification Project.
  Most Component Release Records will just reference the Jakarta EE 9 Platform Release Plan. But, if your Component deviates at all from the Platform Release Plan, then a description of the changes will be required in the Release Record.
  Skeletal EJB 4.0 Release Record was created, but more detailed information is required before we can initiate a ballot...
• Initiate a ballot for your Jakarta Release Record/Plan.
  Again, if your component is only doing the required minimum as defined by the Jakarta EE 9 Platform Release Plan, then no separate ballot is required. You are already approved. But, if your component deviates from the Platform Release Plan, then you will need to initiate your own ballot as defined by the Jakarta EE Specification Process.
• Jakarta-ize your Specification document (if applicable)
  Many of the Jakarta EE components now have the source for their Specification documents. It is strongly recommended that these Specification documents are properly updated to represent Jakarta EE instead of Java EE. Some helpful instructions are documented here.
• javax -> jakarta Spec updates
  If your component has Specification source, then all javax package references need to be updated to use jakarta package references.
• javax -> jakarta API updates
  Your component APIs need to move from using the javax namespace to using the jakarta namespace.
• Release Candidate (RC) of Jakarta API in Maven Central
  A Release Candidate of your component API should be pushed to Maven Central as soon as humanly possible. This will allow other dependent components to utilize your APIs as they are updating their APIs. Multiple revisions of these Release Candidate APIs are allowed (and probably expected) during the development cycle.
• javax -> jakarta TCK updates
  Your component TCK needs to be updated to use the jakarta namespace.
• javax -> jakarta Compatible Implementation updates
  Your compatible implementation that will be used to demonstrate completeness of the Specification needs to be updated to use the jakarta namespace.
• Final Jakarta API available in Staging Repo
  When ready, your final version of the API needs to be staged to get ready for the PR review and approvals.
• Draft Specification and Apidoc PRs ready for review
  Like we did for Jakarta EE 8, draft PRs need to be created and reviewed in preparation for the final ballots.
• Release Review Ballot started
  Each Jakarta EE component will need to initiate a separate Release Review ballot after proper reviewing has completed. To be clear, there will not be a blanket Release Review for all of Jakarta EE 9 like we did for the Plan Review. Each component needs a separate Release Review.

• Organization Name ("Organization") and, if applicable, URL:
  
  Eclipse Foundation
• Product Name, Version and download URL (if applicable):
  
  Eclipse GlassFish 5.1
• Specification Name, Version and download URL:
  
  Jakarta EE Platform, 8
• TCK Version, digital SHA-256 fingerprint and download URL:
  
  Jakarta EE Platform TCK 8.0, SHA-256: 847c80c9c80bea4682006f186292b68acdd0ce9b239d998856c3a379c3a7be50
• Public URL of TCK Results Summary:
  
  TCK results summary
• Any Additional Specification Certification Requirements:
  
  Jakarta Injection Specification
  jakarta.inject-tck-1.0-bin.zip,
  b679bac9b1057df894753892a880ba6ade530607dd811157106ed767aa26481f
  
  Jakarta Contexts and Dependency Injection
  cdi-tck-2.0.6-dist.zip,
  75e969a7a3b3c77332154a2008309aad821a923d8684139242048a7640762808
  
  Jakarta Bean Validation
  beanvalidation-tck-dist-2.0.5.zip,
  4b10c1e850c871c0e47fd3c80177a81d855612085d4d2036aef4ea82b8db63d3
• Java runtime used to run the implementation:
  
  Oracle JDK 1.8.0_191
• Summary of the information for the certification environment, operating system, cloud, ...:
  
  Linux Centos 7, Apache Derby
• By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.
• By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

Since Enterprise Beans 4.0 is not going to be backward compatible release because of the package and namespace change. What should be kept in Compatibility and Migration chapter.

The deployment descriptor target namespace is also changed, so statements like below will not hold true:

All Enterprise Beans 4.0 implementations must support Enterprise Beans
3.1, Enterprise Beans 3.0, Enterprise Beans 2.1, Enterprise Beans 2.0, and Enterprise Beans 1.1 as well as Enterprise Beans 3.2
deployment descriptors. The definitions of the Enterprise Beans 3.2, Enterprise Beans 3.1, Enterprise Beans 3.0, Enterprise Beans 2.1,
Enterprise Beans 2.0, and Enterprise Beans 1.1 deployment descriptors can be found in the
Enterprise Beans 3.2<> and earlier specifications.

• Integrate to Eclipse GlassFish
• Pass all CTS/TCK tests

#17 must be finished before starting working on this task.

• Uptake new Eclipse versions of dependencies (if any). Use GlassFish 5.1 Release Tracker wiki to find components versions to use.

• Release to OSSRH staging repository

• Update GlassFish 5.1 Release Tracker with released version number.

As per the release plan, any reference to javax.xml.rpc needs to be removed.

The Support for Jakarta XML Web Service Endpoints chapter in optional document needs to be removed.

In the Runtime Environment chapter, the table Enterprise Beans API Group defines Jakarta XML RPC Web Service Endpoints as optional. This row needs to be removed.

This is a place holder issue for Pull request from javaee/javax.ejb#3

This is a place holder issue for Pull request from javaee/javax.ejb#4

It would be useful if remote interface controlled via JavaScript as well as JSON-B and WebSocket/WebService.

Description: Jakarta EE generate JavaScript file e.g.: /app/jseb/JebName/RemoteInterfaceName
(note: jseb - JakartaScript Enterprise Bean)
what is includable via web browsers.

There is an issue in EJB staging which shall be solved before promoting of EJB API to central. There are 2 instances of final EJB API 4.0.0 in staging:

[INFO]  * Connected to Nexus at https://jakarta.oss.sonatype.org:443/, is version 2.14.19-01 and edition "Professional"
[INFO] Getting list of available staging repositories...
[INFO] 
[INFO] ID                   State    Description                   
[INFO] jakartaejb-1002      CLOSED   jakarta.ejb:jakarta.ejb-api:4.0.0
[INFO] jakartaejb-1003      CLOSED   jakarta.ejb:jakarta.ejb-api:4.0.0
[INFO] ------------------------------------------------------------------------

the content of jakartaejb-1002 is https://jakarta.oss.sonatype.org/content/repositories/jakartaejb-1002/jakarta/ejb/jakarta.ejb-api/4.0.0/ and content of jakartaejb-1003 is https://jakarta.oss.sonatype.org/content/repositories/jakartaejb-1003/jakarta/ejb/jakarta.ejb-api/4.0.0/

due to staging specifics actual visible content at https://jakarta.oss.sonatype.org/content/repositories/staging/jakarta/ejb/jakarta.ejb-api/4.0.0/ refers to jakartaejb-1002
However I presume desired final version of EJB API 4.0.0 is published at jakartaejb-1003.
So, before promoting to central one of stagings shall be removed (presumably jakartaejb-1002)

Please kindly consider solving this before EJB API 4.0.0 is promoted to central.

All current API libraries shipped must be distributed to Maven Central under a sub-package of the jakarta groupId. Before the first release Maven coordinates of this project must be changed as it's described here.

@schedule has been made repeatable and we need to enrich TCK to add new tests for it.

EJBTransactionRolledbackException class description states:

This exception is thrown to a remote client to indicate that the
transaction associated with processing of the request has been
rolled back, or marked to roll back.

But this exception can be thrown to both remote and local client of ejb business methods. So we may need to remove the word "remote", and probably replace it with something like "is thrown to a caller of bean business method to indicate ..."

I would like to assist with the work that needs to be done for Jakarta EE 9:

• javax > jakarta namespace in documentation
• javax > jakarta namespace in Java code
• ...

Last CTS runs indicate no failures in this component. It's time to make a public release. Before the release make sure that Eclipse Release Review is passed and all dependencies have been released.

• Organization Name ("Organization") and, if applicable, URL:
  
  Eclipse Foundation
• Product Name, Version and download URL (if applicable):
  
  Eclipse Glassfish 6.0 RC2
• Specification Name, Version and download URL:
  
  Enterprise Beans 4.0
• TCK Version, digital SHA-256 fingerprint and download URL:
  
  Jakarta EE 9 TCK RC1

SHA-256: 75b2493a117e7f8fe775cc7e2e8a605a203611895091f4bb9aaabed57f813392

• Public URL of TCK Results Summary:
  
  TCK Result Summary
• Any Additional Specification Certification Requirements:
  
  None
• Java runtime used to run the implementation:
  
  Oracle JDK 1.8.0_191
• Summary of the information for the certification environment, operating system, cloud, ...:
  
  None
• By checking this box I acknowledge that the Organization I represent accepts the terms of the EFTL.
• By checking this box I attest that all TCK requirements have been met, including any compatibility rules.

I ran the dash-licenses tool to check if any CQs needs to be created for this release

api

java -jar .\org.eclipse.dash.licenses-0.0.1-SNAPSHOT.jar -summary DEPENDENCIES .\maven.sorted
Sep 28, 2020 7:08:01 PM org.eclipse.dash.licenses.foundation.EclipseFoundationSupport queryLicenseData
INFO: Querying Eclipse Foundation for license data for 521 items.
Sep 28, 2020 7:08:06 PM org.eclipse.dash.licenses.foundation.EclipseFoundationSupport queryLicenseData
INFO: Found 186 items.
Sep 28, 2020 7:08:06 PM org.eclipse.dash.licenses.clearlydefined.ClearlyDefinedSupport queryLicenseData
INFO: Querying ClearlyDefined for license data for 335 items.
Sep 28, 2020 7:08:16 PM org.eclipse.dash.licenses.clearlydefined.ClearlyDefinedSupport queryLicenseData
INFO: Found 290 items.
License information could not be automatically verified for the following content:

https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15058
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5252
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5149
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-i18n/1.0-beta-10
https://clearlydefined.io/definitions/maven/mavencentral/dom4j/dom4j/1.1
https://clearlydefined.io/definitions/maven/mavencentral/org.slf4j/slf4j-jdk14/1.5.6
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.scm/maven-scm-providers-standard/1.9.4
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.plugins/maven-resources-plugin/2.6
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.plugins/maven-site-plugin/3.9.0
https://clearlydefined.io/definitions/maven/mavencentral/org.jsoup/jsoup/1.10.2
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.groovy/groovy/3.0.4
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-i18n/1.0-beta-7
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.nexus/nexus-client-core/2.14.3-02
https://clearlydefined.io/definitions/maven/mavencentral/jtidy/jtidy/4aug2000r7-dev
https://clearlydefined.io/definitions/maven/mavencentral/sslext/sslext/1.2-0
https://clearlydefined.io/definitions/maven/mavencentral/com.github.spotbugs/spotbugs-annotations/4.0.4
https://clearlydefined.io/definitions/maven/mavencentral/commons-chain/commons-chain/1.1
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.sisu/sisu-guice/3.2.3
https://clearlydefined.io/definitions/maven/mavencentral/antlr/antlr/2.7.2
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.groovy/groovy-all/1.7.6
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.nexus.plugins/nexus-restlet1x-model/2.14.3-02
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-interactivity-api/1.0-alpha-6
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-interactivity-api/1.0-alpha-4
https://clearlydefined.io/definitions/maven/mavencentral/com.sun.jersey/jersey-core/1.17.1
https://clearlydefined.io/definitions/maven/mavencentral/org.slf4j/jcl-over-slf4j/1.5.6
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.nexus.maven/nexus-common/1.6.8
https://clearlydefined.io/definitions/maven/mavencentral/logkit/logkit/1.0.1
https://clearlydefined.io/definitions/maven/mavencentral/org.beanshell/bsh/2.0b4
https://clearlydefined.io/definitions/maven/mavencentral/com.github.javaparser/javaparser-core/3.15.22
https://clearlydefined.io/definitions/maven/mavencentral/nekohtml/xercesMinimal/1.9.6.2
https://clearlydefined.io/definitions/maven/mavencentral/com.mks.api/mksapi-jar/4.10.9049
https://clearlydefined.io/definitions/maven/mavencentral/classworlds/classworlds/1.1-alpha-2
https://clearlydefined.io/definitions/maven/mavencentral/org.netbeans.lib/cvsclient/20060125
https://clearlydefined.io/definitions/maven/mavencentral/net.sf.saxon/Saxon-HE/9.9.1-2
https://clearlydefined.io/definitions/maven/mavencentral/org.osgi/org.osgi.compendium/4.2.0
https://clearlydefined.io/definitions/maven/mavencentral/com.sun.jersey.contribs/jersey-apache-client4/1.17.1
https://clearlydefined.io/definitions/maven/mavencentral/com.github.spotbugs/spotbugs/4.0.4
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.shared/maven-dependency-tree/2.1
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.enforcer/enforcer-api/3.0.0-M3
https://clearlydefined.io/definitions/maven/mavencentral/org.glassfish.build/spec-version-maven-plugin/2.1
https://clearlydefined.io/definitions/maven/mavencentral/classworlds/classworlds/1.1
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-container-default/1.0-alpha-9
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-container-default/1.0-alpha-8
https://clearlydefined.io/definitions/maven/mavencentral/org.slf4j/slf4j-nop/1.5.3
https://clearlydefined.io/definitions/maven/mavencentral/com.sun.jersey/jersey-client/1.17.1
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-digest/1.0
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.doxia/doxia-sink-api/1.0-alpha-7
https://clearlydefined.io/definitions/maven/mavencentral/avalon-framework/avalon-framework/4.1.3

Please create contribution questionnaires for this content.

spec

java -jar .\org.eclipse.dash.licenses-0.0.1-SNAPSHOT.jar -summary DEPENDENCIES .\maven.sorted
Sep 28, 2020 7:32:57 PM org.eclipse.dash.licenses.foundation.EclipseFoundationSupport queryLicenseData
INFO: Querying Eclipse Foundation for license data for 237 items.
Sep 28, 2020 7:32:59 PM org.eclipse.dash.licenses.foundation.EclipseFoundationSupport queryLicenseData
INFO: Found 103 items.
Sep 28, 2020 7:32:59 PM org.eclipse.dash.licenses.clearlydefined.ClearlyDefinedSupport queryLicenseData
INFO: Querying ClearlyDefined for license data for 134 items.
Sep 28, 2020 7:33:14 PM org.eclipse.dash.licenses.clearlydefined.ClearlyDefinedSupport queryLicenseData
INFO: Found 110 items.
License information could not be automatically verified for the following content:

https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5252
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5149
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://clearlydefined.io/definitions/maven/mavencentral/org.jruby/dirgra/0.3
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm-util/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.scm/maven-scm-provider-integrity/1.11.2
https://clearlydefined.io/definitions/maven/mavencentral/dom4j/dom4j/1.1
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm-analysis/4.1
https://clearlydefined.io/definitions/maven/mavencentral/com.mks.api/mksapi-jar/4.10.9049
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-i18n/1.0-beta-7
https://clearlydefined.io/definitions/maven/mavencentral/classworlds/classworlds/1.1-alpha-2
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.release/maven-release-api/3.0.0-M1
https://clearlydefined.io/definitions/maven/mavencentral/xmlunit/xmlunit/1.5
https://clearlydefined.io/definitions/maven/mavencentral/org.netbeans.lib/cvsclient/20060125
https://clearlydefined.io/definitions/maven/mavencentral/sslext/sslext/1.2-0
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.scm/maven-scm-providers-standard/1.11.2
https://clearlydefined.io/definitions/maven/mavencentral/commons-chain/commons-chain/1.1
https://clearlydefined.io/definitions/maven/mavencentral/commons-validator/commons-validator/1.3.1
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.enforcer/enforcer-api/3.0.0-M3
https://clearlydefined.io/definitions/maven/mavencentral/antlr/antlr/2.7.2
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.groovy/groovy-all/1.7.6
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-container-default/1.0-alpha-9
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-interactivity-api/1.0-alpha-6
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-digest/1.0
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm-tree/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.beanshell/bsh/2.0b4

Please create contribution questionnaires for this content.

Final list of CQs that need to be created:

https://clearlydefined.io/definitions/maven/mavencentral/antlr/antlr/2.7.2
https://clearlydefined.io/definitions/maven/mavencentral/avalon-framework/avalon-framework/4.1.3
https://clearlydefined.io/definitions/maven/mavencentral/classworlds/classworlds/1.1
https://clearlydefined.io/definitions/maven/mavencentral/classworlds/classworlds/1.1-alpha-2
https://clearlydefined.io/definitions/maven/mavencentral/com.github.javaparser/javaparser-core/3.15.22
https://clearlydefined.io/definitions/maven/mavencentral/com.github.spotbugs/spotbugs-annotations/4.0.4
https://clearlydefined.io/definitions/maven/mavencentral/com.github.spotbugs/spotbugs/4.0.4
https://clearlydefined.io/definitions/maven/mavencentral/com.mks.api/mksapi-jar/4.10.9049
https://clearlydefined.io/definitions/maven/mavencentral/com.sun.jersey.contribs/jersey-apache-client4/1.17.1
https://clearlydefined.io/definitions/maven/mavencentral/com.sun.jersey/jersey-client/1.17.1
https://clearlydefined.io/definitions/maven/mavencentral/com.sun.jersey/jersey-core/1.17.1
https://clearlydefined.io/definitions/maven/mavencentral/commons-chain/commons-chain/1.1
https://clearlydefined.io/definitions/maven/mavencentral/commons-validator/commons-validator/1.3.1
https://clearlydefined.io/definitions/maven/mavencentral/dom4j/dom4j/1.1
https://clearlydefined.io/definitions/maven/mavencentral/jtidy/jtidy/4aug2000r7-dev
https://clearlydefined.io/definitions/maven/mavencentral/logkit/logkit/1.0.1
https://clearlydefined.io/definitions/maven/mavencentral/nekohtml/xercesMinimal/1.9.6.2
https://clearlydefined.io/definitions/maven/mavencentral/net.sf.saxon/Saxon-HE/9.9.1-2
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.doxia/doxia-sink-api/1.0-alpha-7
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.enforcer/enforcer-api/3.0.0-M3
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.plugins/maven-resources-plugin/2.6
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.plugins/maven-site-plugin/3.9.0
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.release/maven-release-api/3.0.0-M1
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.scm/maven-scm-provider-integrity/1.11.2
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.scm/maven-scm-providers-standard/1.11.2
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.scm/maven-scm-providers-standard/1.9.4
https://clearlydefined.io/definitions/maven/mavencentral/org.apache.maven.shared/maven-dependency-tree/2.1
https://clearlydefined.io/definitions/maven/mavencentral/org.beanshell/bsh/2.0b4
https://clearlydefined.io/definitions/maven/mavencentral/org.beanshell/bsh/2.0b4
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.groovy/groovy-all/1.7.6
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.groovy/groovy/3.0.4
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-container-default/1.0-alpha-8
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-container-default/1.0-alpha-9
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-digest/1.0
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-i18n/1.0-beta-10
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-i18n/1.0-beta-7
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-interactivity-api/1.0-alpha-4
https://clearlydefined.io/definitions/maven/mavencentral/org.codehaus.plexus/plexus-interactivity-api/1.0-alpha-6
https://clearlydefined.io/definitions/maven/mavencentral/org.glassfish.build/spec-version-maven-plugin/2.1
https://clearlydefined.io/definitions/maven/mavencentral/org.jruby/dirgra/0.3
https://clearlydefined.io/definitions/maven/mavencentral/org.jsoup/jsoup/1.10.2
https://clearlydefined.io/definitions/maven/mavencentral/org.netbeans.lib/cvsclient/20060125
https://clearlydefined.io/definitions/maven/mavencentral/org.osgi/org.osgi.compendium/4.2.0
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm-analysis/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm-tree/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm-util/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.ow2.asm/asm/4.1
https://clearlydefined.io/definitions/maven/mavencentral/org.slf4j/jcl-over-slf4j/1.5.6
https://clearlydefined.io/definitions/maven/mavencentral/org.slf4j/slf4j-jdk14/1.5.6
https://clearlydefined.io/definitions/maven/mavencentral/org.slf4j/slf4j-nop/1.5.3
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.nexus.maven/nexus-common/1.6.8
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.nexus.plugins/nexus-restlet1x-model/2.14.3-02
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.nexus/nexus-client-core/2.14.3-02
https://clearlydefined.io/definitions/maven/mavencentral/org.sonatype.sisu/sisu-guice/3.2.3
https://clearlydefined.io/definitions/maven/mavencentral/sslext/sslext/1.2-0
https://clearlydefined.io/definitions/maven/mavencentral/xmlunit/xmlunit/1.5
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15058
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=18240
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5149
https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5252

Background information:
https://waynebeaton.wordpress.com/2019/04/04/renaming-java-ee-specifications-for-jakarta-ee/

Checklist:

• GitHub
• README file
• CONTRIBUTING file
• Eclipse Project under https://projects.eclipse.org/projects/ee4j

The MANIFEST.MF of jakarta.ejb-api-4.0.0-RC1.jar still has reference to javax.transaction

Import-Package: jakarta.ejb;version="4.0.0",jakarta.ejb.embeddable;ver
 sion="4.0.0",jakarta.ejb.spi;version="4.0.0",jakarta.enterprise.conte
 xt,jakarta.enterprise.util,jakarta.interceptor,jakarta.transaction;ve
 rsion="4.0.0",javax.naming,javax.transaction;version="[1.3,2.0)",java
 x.transaction.xa

This is a place holder issue for Pull request from javaee/javax.ejb#5

A requirement for the EE10 release is for API jars to include a proper module-info.class. Please create a service release to include this.

jakartaee/platform#421

Instructions

• Update text files
• Generate "boilerplate" specification project
• Make a staging release
• Generate Stand-alone TCK test results
• Submit a PR to jakartaee/specifications repository
• Update the Jakarta EE API jar by submitting a PR to the jakartaee-api project

See here for detailed instructions.

This is a place holder issue for Pull request from javaee/javax.ejb#2

Just an FYI... The original (oracle) EJB Enterprise Beans specification source is now available via this CQ: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21461

Please import/modify/merge it when time allows, hopefully in time for Jakarta EE 9. Thanks!

@schedule has been made repeatable so we need to update the signature tests for it

This task is for creating a basic build CI/CD pipeline for this project on Eclipse infrastructure. More information is here: https://ci.eclipse.org/.

Update Eclipse GlassFish to use the new version of your API (and implementation, if applicable) by submitting a PR to GlassFish.

Although a new version of GlassFish will not be released for Jakarta EE 8, we hope to release an update sometime later.