Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-tck-dev] Jakarta Deployment + jakartaee-tck/issues/211
I just noticed some more tests that also depended on (removed) Jakarta Deployment, the list is mentioned in https://github.com/eclipse-ee4j/jakartaee-tck/pull/292#discussion_r432590225 and contained in the jakartaee/src/main/jbake/content/commonappdeploy.adoc, src/com/sun/ts/lib/harness/commonarchives.properties.

Also, with Jakarta Deployment removed, we no longer will need com.sun.ts.lib.harness.
CommonAppVerifier.

Since Jakarta Deployment was optional for Jakarta EE 8, these tests must also have been optional as well or the Jakarta Deployment wasn't really used, one or the other I think.

Scott

On Mon, May 18, 2020 at 1:35 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:

On Fri, May 15, 2020 at 4:08 PM Scott Marlow <smarlow@xxxxxxxxxx> wrote:
Hi,

I started some work on removing Jakarta Deployment as mentioned on issue#211 [1].  One question that I raised is whether GlassFish 6.0 can depend on com.sun.ts.lib.implementation.sun.javaee.glassfish.AutoDeployment for test deployment [2]?

The above AutoDeployment class will copy deployment archives into the GlassFish 6.0 deployment folder which should work.  

In theory, we could start to think about using Arquillian as well (for TCK deployment handling) but I think that should be discussed separately from removing Jakarta Deployment.
 

Back to the top