Building with Java 11

classic Classic list List threaded Threaded
54 messages Options
123
Reply | Threaded
Open this post in threaded view
|

Building with Java 11

jgallimore
Its very much a work in progress, but I have been trying to get our build
to run on Java 11, with the full set of tests. I'm doing this in a branch
which I have been keeping up to date with master as best as I can.

My code is here: https://github.com/apache/tomee/pull/293, and broadly
speaking, adds these modules:

      <dependency>
        <groupId>javax.xml.bind</groupId>
        <artifactId>jaxb-api</artifactId>
        <version>2.3.0</version>
      </dependency>
      <dependency>
        <groupId>org.glassfish.jaxb</groupId>
        <artifactId>jaxb-runtime</artifactId>
        <version>2.4.0-b180830.0438</version>
      </dependency>
      <dependency>
        <groupId>com.sun.xml.ws</groupId>
        <artifactId>jaxws-rt</artifactId>
        <version>2.3.1</version>
        <type>pom</type>
      </dependency>
      <dependency>
        <groupId>com.sun.xml.ws</groupId>
        <artifactId>rt</artifactId>
        <version>2.3.1</version>
      </dependency>
      <dependency>
        <groupId>javax.activation</groupId>
        <artifactId>javax.activation-api</artifactId>
        <version>1.2.0</version>
      </dependency>
      <dependency>
        <groupId>com.sun.activation</groupId>
        <artifactId>javax.activation</artifactId>
        <version>1.2.0</version>
      </dependency>
      <dependency>
        <groupId>org.jacorb</groupId>
        <artifactId>jacorb</artifactId>
        <version>3.9</version>
      </dependency>
      <dependency>
        <groupId>org.jboss.spec.javax.rmi</groupId>
        <artifactId>jboss-rmi-api_1.0_spec</artifactId>
        <version>1.0.6.Final</version>
      </dependency>

There are some regressions to look at, and there are some errors in the
output that need looking at, but one milestone I have reached is getting
almost all the arquillian tests (only 1 failure) in the build to pass.
Here's my current failures:
https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4

In terms of the build artifacts, the additional libraries included are:

FastInfoSet-1.2.15
gmbal-api-only-3,1,0-b001
ha-api-3.1.9
istack-commons-runtime-3.0.7
jacorb-3.9
jacorb-omgapi-3.9
javax.activation-1.2.0
javax.activation-api-1.2.0
javax.annotation-api-1.3.2
javax.jws-api-1.1
javax.xml.soap-api-1.4.0
jaxb-runtime-2.4.0-b180830.0438
jaxws-api
jboss-rmi-api_1.0_spec
management-api-3.0.0-b012
mimepull-1.9.10
policy-2.7.5
rt-2.3.1
saaj-impl-1.5.0
stax-ex-1.8
stax2-api-4.1 (as opposed to 3.1.4)
streambuffer-1.5.6
txw2-2.4.0-b180830.0438
woodstox-core-5.1.0 (as opposed to 5.0.3)
xmlschema-core-2.2.4 (as opposed to 2.2.3)

These are obviously being pulled in as transitive dependencies of
dependencies I mention above, and I'm sure some of them can be removed, but
I'll need to work through them to figure out what.

If folks would like to collaborate on this here, it would be most welcome.

Thanks

Jon
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

Daniel Cunha-2
Hi Jon,

fantastic! I'll take a look on it.

Nice work!

Em ter, 8 de jan de 2019 às 13:26, Jonathan Gallimore <
[hidden email]> escreveu:

> Its very much a work in progress, but I have been trying to get our build
> to run on Java 11, with the full set of tests. I'm doing this in a branch
> which I have been keeping up to date with master as best as I can.
>
> My code is here: https://github.com/apache/tomee/pull/293, and broadly
> speaking, adds these modules:
>
>       <dependency>
>         <groupId>javax.xml.bind</groupId>
>         <artifactId>jaxb-api</artifactId>
>         <version>2.3.0</version>
>       </dependency>
>       <dependency>
>         <groupId>org.glassfish.jaxb</groupId>
>         <artifactId>jaxb-runtime</artifactId>
>         <version>2.4.0-b180830.0438</version>
>       </dependency>
>       <dependency>
>         <groupId>com.sun.xml.ws</groupId>
>         <artifactId>jaxws-rt</artifactId>
>         <version>2.3.1</version>
>         <type>pom</type>
>       </dependency>
>       <dependency>
>         <groupId>com.sun.xml.ws</groupId>
>         <artifactId>rt</artifactId>
>         <version>2.3.1</version>
>       </dependency>
>       <dependency>
>         <groupId>javax.activation</groupId>
>         <artifactId>javax.activation-api</artifactId>
>         <version>1.2.0</version>
>       </dependency>
>       <dependency>
>         <groupId>com.sun.activation</groupId>
>         <artifactId>javax.activation</artifactId>
>         <version>1.2.0</version>
>       </dependency>
>       <dependency>
>         <groupId>org.jacorb</groupId>
>         <artifactId>jacorb</artifactId>
>         <version>3.9</version>
>       </dependency>
>       <dependency>
>         <groupId>org.jboss.spec.javax.rmi</groupId>
>         <artifactId>jboss-rmi-api_1.0_spec</artifactId>
>         <version>1.0.6.Final</version>
>       </dependency>
>
> There are some regressions to look at, and there are some errors in the
> output that need looking at, but one milestone I have reached is getting
> almost all the arquillian tests (only 1 failure) in the build to pass.
> Here's my current failures:
> https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4
>
> In terms of the build artifacts, the additional libraries included are:
>
> FastInfoSet-1.2.15
> gmbal-api-only-3,1,0-b001
> ha-api-3.1.9
> istack-commons-runtime-3.0.7
> jacorb-3.9
> jacorb-omgapi-3.9
> javax.activation-1.2.0
> javax.activation-api-1.2.0
> javax.annotation-api-1.3.2
> javax.jws-api-1.1
> javax.xml.soap-api-1.4.0
> jaxb-runtime-2.4.0-b180830.0438
> jaxws-api
> jboss-rmi-api_1.0_spec
> management-api-3.0.0-b012
> mimepull-1.9.10
> policy-2.7.5
> rt-2.3.1
> saaj-impl-1.5.0
> stax-ex-1.8
> stax2-api-4.1 (as opposed to 3.1.4)
> streambuffer-1.5.6
> txw2-2.4.0-b180830.0438
> woodstox-core-5.1.0 (as opposed to 5.0.3)
> xmlschema-core-2.2.4 (as opposed to 2.2.3)
>
> These are obviously being pulled in as transitive dependencies of
> dependencies I mention above, and I'm sure some of them can be removed, but
> I'll need to work through them to figure out what.
>
> If folks would like to collaborate on this here, it would be most welcome.
>
> Thanks
>
> Jon
>


--
Daniel "soro" Cunha
https://twitter.com/dvlc_
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

Jean-Louis MONTEIRO
Great job Jon.
I did some tests so, so we should be able to get something green hopefully
soon
--
Jean-Louis Monteiro
http://twitter.com/jlouismonteiro
http://www.tomitribe.com


On Wed, Jan 9, 2019 at 1:17 PM Daniel Cunha <[hidden email]> wrote:

> Hi Jon,
>
> fantastic! I'll take a look on it.
>
> Nice work!
>
> Em ter, 8 de jan de 2019 às 13:26, Jonathan Gallimore <
> [hidden email]> escreveu:
>
> > Its very much a work in progress, but I have been trying to get our build
> > to run on Java 11, with the full set of tests. I'm doing this in a branch
> > which I have been keeping up to date with master as best as I can.
> >
> > My code is here: https://github.com/apache/tomee/pull/293, and broadly
> > speaking, adds these modules:
> >
> >       <dependency>
> >         <groupId>javax.xml.bind</groupId>
> >         <artifactId>jaxb-api</artifactId>
> >         <version>2.3.0</version>
> >       </dependency>
> >       <dependency>
> >         <groupId>org.glassfish.jaxb</groupId>
> >         <artifactId>jaxb-runtime</artifactId>
> >         <version>2.4.0-b180830.0438</version>
> >       </dependency>
> >       <dependency>
> >         <groupId>com.sun.xml.ws</groupId>
> >         <artifactId>jaxws-rt</artifactId>
> >         <version>2.3.1</version>
> >         <type>pom</type>
> >       </dependency>
> >       <dependency>
> >         <groupId>com.sun.xml.ws</groupId>
> >         <artifactId>rt</artifactId>
> >         <version>2.3.1</version>
> >       </dependency>
> >       <dependency>
> >         <groupId>javax.activation</groupId>
> >         <artifactId>javax.activation-api</artifactId>
> >         <version>1.2.0</version>
> >       </dependency>
> >       <dependency>
> >         <groupId>com.sun.activation</groupId>
> >         <artifactId>javax.activation</artifactId>
> >         <version>1.2.0</version>
> >       </dependency>
> >       <dependency>
> >         <groupId>org.jacorb</groupId>
> >         <artifactId>jacorb</artifactId>
> >         <version>3.9</version>
> >       </dependency>
> >       <dependency>
> >         <groupId>org.jboss.spec.javax.rmi</groupId>
> >         <artifactId>jboss-rmi-api_1.0_spec</artifactId>
> >         <version>1.0.6.Final</version>
> >       </dependency>
> >
> > There are some regressions to look at, and there are some errors in the
> > output that need looking at, but one milestone I have reached is getting
> > almost all the arquillian tests (only 1 failure) in the build to pass.
> > Here's my current failures:
> > https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4
> >
> > In terms of the build artifacts, the additional libraries included are:
> >
> > FastInfoSet-1.2.15
> > gmbal-api-only-3,1,0-b001
> > ha-api-3.1.9
> > istack-commons-runtime-3.0.7
> > jacorb-3.9
> > jacorb-omgapi-3.9
> > javax.activation-1.2.0
> > javax.activation-api-1.2.0
> > javax.annotation-api-1.3.2
> > javax.jws-api-1.1
> > javax.xml.soap-api-1.4.0
> > jaxb-runtime-2.4.0-b180830.0438
> > jaxws-api
> > jboss-rmi-api_1.0_spec
> > management-api-3.0.0-b012
> > mimepull-1.9.10
> > policy-2.7.5
> > rt-2.3.1
> > saaj-impl-1.5.0
> > stax-ex-1.8
> > stax2-api-4.1 (as opposed to 3.1.4)
> > streambuffer-1.5.6
> > txw2-2.4.0-b180830.0438
> > woodstox-core-5.1.0 (as opposed to 5.0.3)
> > xmlschema-core-2.2.4 (as opposed to 2.2.3)
> >
> > These are obviously being pulled in as transitive dependencies of
> > dependencies I mention above, and I'm sure some of them can be removed,
> but
> > I'll need to work through them to figure out what.
> >
> > If folks would like to collaborate on this here, it would be most
> welcome.
> >
> > Thanks
> >
> > Jon
> >
>
>
> --
> Daniel "soro" Cunha
> https://twitter.com/dvlc_
>
   --
    Jean-Louis Monteiro
    http://twitter.com/jlouismonteiro
    http://www.tomitribe.com
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

Otávio Gonçalves de Santana
Hey JonG,
What do you think if you move this branch to the TomEE project?

On Wed, Jan 9, 2019 at 10:40 AM Jean-Louis Monteiro <
[hidden email]> wrote:

> Great job Jon.
> I did some tests so, so we should be able to get something green hopefully
> soon
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Jan 9, 2019 at 1:17 PM Daniel Cunha <[hidden email]> wrote:
>
> > Hi Jon,
> >
> > fantastic! I'll take a look on it.
> >
> > Nice work!
> >
> > Em ter, 8 de jan de 2019 às 13:26, Jonathan Gallimore <
> > [hidden email]> escreveu:
> >
> > > Its very much a work in progress, but I have been trying to get our
> build
> > > to run on Java 11, with the full set of tests. I'm doing this in a
> branch
> > > which I have been keeping up to date with master as best as I can.
> > >
> > > My code is here: https://github.com/apache/tomee/pull/293, and broadly
> > > speaking, adds these modules:
> > >
> > >       <dependency>
> > >         <groupId>javax.xml.bind</groupId>
> > >         <artifactId>jaxb-api</artifactId>
> > >         <version>2.3.0</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>org.glassfish.jaxb</groupId>
> > >         <artifactId>jaxb-runtime</artifactId>
> > >         <version>2.4.0-b180830.0438</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>com.sun.xml.ws</groupId>
> > >         <artifactId>jaxws-rt</artifactId>
> > >         <version>2.3.1</version>
> > >         <type>pom</type>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>com.sun.xml.ws</groupId>
> > >         <artifactId>rt</artifactId>
> > >         <version>2.3.1</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>javax.activation</groupId>
> > >         <artifactId>javax.activation-api</artifactId>
> > >         <version>1.2.0</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>com.sun.activation</groupId>
> > >         <artifactId>javax.activation</artifactId>
> > >         <version>1.2.0</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>org.jacorb</groupId>
> > >         <artifactId>jacorb</artifactId>
> > >         <version>3.9</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>org.jboss.spec.javax.rmi</groupId>
> > >         <artifactId>jboss-rmi-api_1.0_spec</artifactId>
> > >         <version>1.0.6.Final</version>
> > >       </dependency>
> > >
> > > There are some regressions to look at, and there are some errors in the
> > > output that need looking at, but one milestone I have reached is
> getting
> > > almost all the arquillian tests (only 1 failure) in the build to pass.
> > > Here's my current failures:
> > > https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4
> > >
> > > In terms of the build artifacts, the additional libraries included are:
> > >
> > > FastInfoSet-1.2.15
> > > gmbal-api-only-3,1,0-b001
> > > ha-api-3.1.9
> > > istack-commons-runtime-3.0.7
> > > jacorb-3.9
> > > jacorb-omgapi-3.9
> > > javax.activation-1.2.0
> > > javax.activation-api-1.2.0
> > > javax.annotation-api-1.3.2
> > > javax.jws-api-1.1
> > > javax.xml.soap-api-1.4.0
> > > jaxb-runtime-2.4.0-b180830.0438
> > > jaxws-api
> > > jboss-rmi-api_1.0_spec
> > > management-api-3.0.0-b012
> > > mimepull-1.9.10
> > > policy-2.7.5
> > > rt-2.3.1
> > > saaj-impl-1.5.0
> > > stax-ex-1.8
> > > stax2-api-4.1 (as opposed to 3.1.4)
> > > streambuffer-1.5.6
> > > txw2-2.4.0-b180830.0438
> > > woodstox-core-5.1.0 (as opposed to 5.0.3)
> > > xmlschema-core-2.2.4 (as opposed to 2.2.3)
> > >
> > > These are obviously being pulled in as transitive dependencies of
> > > dependencies I mention above, and I'm sure some of them can be removed,
> > but
> > > I'll need to work through them to figure out what.
> > >
> > > If folks would like to collaborate on this here, it would be most
> > welcome.
> > >
> > > Thanks
> > >
> > > Jon
> > >
> >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

Daniel Cunha-2
In reply to this post by Jean-Louis MONTEIRO
Hi Jon,

could not we move your branch to apache/tomee repository?
What you guys think about it?

Em qua, 9 de jan de 2019 às 09:40, Jean-Louis Monteiro <
[hidden email]> escreveu:

> Great job Jon.
> I did some tests so, so we should be able to get something green hopefully
> soon
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
>
> On Wed, Jan 9, 2019 at 1:17 PM Daniel Cunha <[hidden email]> wrote:
>
> > Hi Jon,
> >
> > fantastic! I'll take a look on it.
> >
> > Nice work!
> >
> > Em ter, 8 de jan de 2019 às 13:26, Jonathan Gallimore <
> > [hidden email]> escreveu:
> >
> > > Its very much a work in progress, but I have been trying to get our
> build
> > > to run on Java 11, with the full set of tests. I'm doing this in a
> branch
> > > which I have been keeping up to date with master as best as I can.
> > >
> > > My code is here: https://github.com/apache/tomee/pull/293, and broadly
> > > speaking, adds these modules:
> > >
> > >       <dependency>
> > >         <groupId>javax.xml.bind</groupId>
> > >         <artifactId>jaxb-api</artifactId>
> > >         <version>2.3.0</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>org.glassfish.jaxb</groupId>
> > >         <artifactId>jaxb-runtime</artifactId>
> > >         <version>2.4.0-b180830.0438</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>com.sun.xml.ws</groupId>
> > >         <artifactId>jaxws-rt</artifactId>
> > >         <version>2.3.1</version>
> > >         <type>pom</type>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>com.sun.xml.ws</groupId>
> > >         <artifactId>rt</artifactId>
> > >         <version>2.3.1</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>javax.activation</groupId>
> > >         <artifactId>javax.activation-api</artifactId>
> > >         <version>1.2.0</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>com.sun.activation</groupId>
> > >         <artifactId>javax.activation</artifactId>
> > >         <version>1.2.0</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>org.jacorb</groupId>
> > >         <artifactId>jacorb</artifactId>
> > >         <version>3.9</version>
> > >       </dependency>
> > >       <dependency>
> > >         <groupId>org.jboss.spec.javax.rmi</groupId>
> > >         <artifactId>jboss-rmi-api_1.0_spec</artifactId>
> > >         <version>1.0.6.Final</version>
> > >       </dependency>
> > >
> > > There are some regressions to look at, and there are some errors in the
> > > output that need looking at, but one milestone I have reached is
> getting
> > > almost all the arquillian tests (only 1 failure) in the build to pass.
> > > Here's my current failures:
> > > https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4
> > >
> > > In terms of the build artifacts, the additional libraries included are:
> > >
> > > FastInfoSet-1.2.15
> > > gmbal-api-only-3,1,0-b001
> > > ha-api-3.1.9
> > > istack-commons-runtime-3.0.7
> > > jacorb-3.9
> > > jacorb-omgapi-3.9
> > > javax.activation-1.2.0
> > > javax.activation-api-1.2.0
> > > javax.annotation-api-1.3.2
> > > javax.jws-api-1.1
> > > javax.xml.soap-api-1.4.0
> > > jaxb-runtime-2.4.0-b180830.0438
> > > jaxws-api
> > > jboss-rmi-api_1.0_spec
> > > management-api-3.0.0-b012
> > > mimepull-1.9.10
> > > policy-2.7.5
> > > rt-2.3.1
> > > saaj-impl-1.5.0
> > > stax-ex-1.8
> > > stax2-api-4.1 (as opposed to 3.1.4)
> > > streambuffer-1.5.6
> > > txw2-2.4.0-b180830.0438
> > > woodstox-core-5.1.0 (as opposed to 5.0.3)
> > > xmlschema-core-2.2.4 (as opposed to 2.2.3)
> > >
> > > These are obviously being pulled in as transitive dependencies of
> > > dependencies I mention above, and I'm sure some of them can be removed,
> > but
> > > I'll need to work through them to figure out what.
> > >
> > > If folks would like to collaborate on this here, it would be most
> > welcome.
> > >
> > > Thanks
> > >
> > > Jon
> > >
> >
> >
> > --
> > Daniel "soro" Cunha
> > https://twitter.com/dvlc_
> >
>


--
Daniel "soro" Cunha
https://twitter.com/dvlc_
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

j4fm
I already updated all the JAXB related artifacts to 2.3.1 which comes with
CXF 3.3.0 too.  I already added all the transitive dependency exclusions.
Your extra ones could just be added on top of that.

The work is in PR 419 which was already reviewed and approved.  It would be
great to have that merged and save other people overlapping some of the same
work.  (Along with #409 for CXF 3.3.0 itself)

Do you see any issues with merging those?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

j4fm
For PR 419 and 409 all the full tests pass too.



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
In reply to this post by Otávio Gonçalves de Santana
I've merged those 2 PRs in. Let's see what the actual diff is for my branch
now.

Jon

On Fri, Mar 1, 2019 at 1:28 PM Otávio Gonçalves de Santana <
[hidden email]> wrote:

> Hey JonG,
> What do you think if you move this branch to the TomEE project?
>
> On Wed, Jan 9, 2019 at 10:40 AM Jean-Louis Monteiro <
> [hidden email]> wrote:
>
> > Great job Jon.
> > I did some tests so, so we should be able to get something green
> hopefully
> > soon
> > --
> > Jean-Louis Monteiro
> > http://twitter.com/jlouismonteiro
> > http://www.tomitribe.com
> >
> >
> > On Wed, Jan 9, 2019 at 1:17 PM Daniel Cunha <[hidden email]>
> wrote:
> >
> > > Hi Jon,
> > >
> > > fantastic! I'll take a look on it.
> > >
> > > Nice work!
> > >
> > > Em ter, 8 de jan de 2019 às 13:26, Jonathan Gallimore <
> > > [hidden email]> escreveu:
> > >
> > > > Its very much a work in progress, but I have been trying to get our
> > build
> > > > to run on Java 11, with the full set of tests. I'm doing this in a
> > branch
> > > > which I have been keeping up to date with master as best as I can.
> > > >
> > > > My code is here: https://github.com/apache/tomee/pull/293, and
> broadly
> > > > speaking, adds these modules:
> > > >
> > > >       <dependency>
> > > >         <groupId>javax.xml.bind</groupId>
> > > >         <artifactId>jaxb-api</artifactId>
> > > >         <version>2.3.0</version>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>org.glassfish.jaxb</groupId>
> > > >         <artifactId>jaxb-runtime</artifactId>
> > > >         <version>2.4.0-b180830.0438</version>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>com.sun.xml.ws</groupId>
> > > >         <artifactId>jaxws-rt</artifactId>
> > > >         <version>2.3.1</version>
> > > >         <type>pom</type>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>com.sun.xml.ws</groupId>
> > > >         <artifactId>rt</artifactId>
> > > >         <version>2.3.1</version>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>javax.activation</groupId>
> > > >         <artifactId>javax.activation-api</artifactId>
> > > >         <version>1.2.0</version>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>com.sun.activation</groupId>
> > > >         <artifactId>javax.activation</artifactId>
> > > >         <version>1.2.0</version>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>org.jacorb</groupId>
> > > >         <artifactId>jacorb</artifactId>
> > > >         <version>3.9</version>
> > > >       </dependency>
> > > >       <dependency>
> > > >         <groupId>org.jboss.spec.javax.rmi</groupId>
> > > >         <artifactId>jboss-rmi-api_1.0_spec</artifactId>
> > > >         <version>1.0.6.Final</version>
> > > >       </dependency>
> > > >
> > > > There are some regressions to look at, and there are some errors in
> the
> > > > output that need looking at, but one milestone I have reached is
> > getting
> > > > almost all the arquillian tests (only 1 failure) in the build to
> pass.
> > > > Here's my current failures:
> > > > https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4
> > > >
> > > > In terms of the build artifacts, the additional libraries included
> are:
> > > >
> > > > FastInfoSet-1.2.15
> > > > gmbal-api-only-3,1,0-b001
> > > > ha-api-3.1.9
> > > > istack-commons-runtime-3.0.7
> > > > jacorb-3.9
> > > > jacorb-omgapi-3.9
> > > > javax.activation-1.2.0
> > > > javax.activation-api-1.2.0
> > > > javax.annotation-api-1.3.2
> > > > javax.jws-api-1.1
> > > > javax.xml.soap-api-1.4.0
> > > > jaxb-runtime-2.4.0-b180830.0438
> > > > jaxws-api
> > > > jboss-rmi-api_1.0_spec
> > > > management-api-3.0.0-b012
> > > > mimepull-1.9.10
> > > > policy-2.7.5
> > > > rt-2.3.1
> > > > saaj-impl-1.5.0
> > > > stax-ex-1.8
> > > > stax2-api-4.1 (as opposed to 3.1.4)
> > > > streambuffer-1.5.6
> > > > txw2-2.4.0-b180830.0438
> > > > woodstox-core-5.1.0 (as opposed to 5.0.3)
> > > > xmlschema-core-2.2.4 (as opposed to 2.2.3)
> > > >
> > > > These are obviously being pulled in as transitive dependencies of
> > > > dependencies I mention above, and I'm sure some of them can be
> removed,
> > > but
> > > > I'll need to work through them to figure out what.
> > > >
> > > > If folks would like to collaborate on this here, it would be most
> > > welcome.
> > > >
> > > > Thanks
> > > >
> > > > Jon
> > > >
> > >
> > >
> > > --
> > > Daniel "soro" Cunha
> > > https://twitter.com/dvlc_
> > >
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

j4fm
Thanks for the merges, hopefully will save time.  Could I make a shameless
request for 418 too?  (and 424 if poss) :D

I'm going to keep a close eye on buildbot too, just in case.

James



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
418 is merged... looking at 424 now.

Jon

On Fri, Mar 1, 2019 at 1:53 PM j4fm <[hidden email]> wrote:

> Thanks for the merges, hopefully will save time.  Could I make a shameless
> request for 418 too?  (and 424 if poss) :D
>
> I'm going to keep a close eye on buildbot too, just in case.
>
> James
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

j4fm
Thanks Jon.  I'm keeping an eye on each run on buildbot.  Maybe I should go
out for a while ;)



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
Yeah... it'll take a few hours for those to run through. Thanks for the PRs
and for keeping an eye out on the build, its much appreciated.

Jon

On Fri, Mar 1, 2019 at 3:00 PM j4fm <[hidden email]> wrote:

> Thanks Jon.  I'm keeping an eye on each run on buildbot.  Maybe I should go
> out for a while ;)
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
I've cleaned up this branch so the dependencies should now be correct (and
minimal). I'm currently running a Java 8 full build with tests. Assuming
that works, I'll propose merging this to master and setting up a Java 11
build to run alongside the Java 8. That should enable folks to look at test
issues on master.

I'm hoping CXF and recent microprofile component updates will fix some of
the test issues.

Jon

On Fri, Mar 1, 2019 at 3:05 PM Jonathan Gallimore <
[hidden email]> wrote:

> Yeah... it'll take a few hours for those to run through. Thanks for the
> PRs and for keeping an eye out on the build, its much appreciated.
>
> Jon
>
> On Fri, Mar 1, 2019 at 3:00 PM j4fm <[hidden email]> wrote:
>
>> Thanks Jon.  I'm keeping an eye on each run on buildbot.  Maybe I should
>> go
>> out for a while ;)
>>
>>
>>
>> --
>> Sent from:
>> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>>
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

j4fm
I would be happy to pull your PR and build against JDK 11 before merging.  I
can start that build now.

I see buildbot seems to have frozen.  I think really my PR 419 should run
before the current 409 because the former is mostly prep for the latter.

If you are okay with it, I will click stop (if it lets me) on the current
build and let the two PRs run together?

Thanks



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
On Fri, Mar 1, 2019 at 4:14 PM j4fm <[hidden email]> wrote:

> I would be happy to pull your PR and build against JDK 11 before merging.
> I
> can start that build now.
>

Bigger concern is that builds against Java 8, and is green with Java 8. I
think your recent changes make that more likely to succeed (thanks!). I
know the build without tests works JDK 11, but I imagine we'll have some
test failures on Java 11. Last run, this was the set:
https://gist.github.com/jgallimore/6968379060a4d4b25f2b6c888a49bbb4

I see the goal for merge being a green build against Java 8. Getting this
merged to master enables others to help with test fixing. We have at least
Otavio and Dani looking at that, and I'm sure other will be interested in
helping.


>
> I see buildbot seems to have frozen.  I think really my PR 419 should run
> before the current 409 because the former is mostly prep for the latter.
>
> If you are okay with it, I will click stop (if it lets me) on the current
> build and let the two PRs run together?
>

Go for it. If it doesn't work, let me know and I'll kill stuff off and
force a new build.

Jon


>
> Thanks
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

j4fm
Ah yeah that makes sense.

It won't let me stop the current stuck build.  Would you be able to?

From the logs it looks like it succeeds up until the point it's frozen...
I'm not sure what's up with it.  Have you seen it freeze like this before?
Maybe it's an issue with the CI agent instead?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

César Hernández Mendoza
>
> I'll propose merging this to master and setting up a Java 11
> build to run alongside the Java 8. That should enable folks to look at test
> issues on master.


+1 , I'm also willing to help with test fixes related to Java 11.

El vie., 1 mar. 2019 a las 10:28, j4fm (<[hidden email]>)
escribió:

> Ah yeah that makes sense.
>
> It won't let me stop the current stuck build.  Would you be able to?
>
> From the logs it looks like it succeeds up until the point it's frozen...
> I'm not sure what's up with it.  Have you seen it freeze like this before?
> Maybe it's an issue with the CI agent instead?
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>


--
Atentamente:
César Hernández Mendoza.
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
In reply to this post by j4fm
Killed of the builds and forced a new one.
https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1048

Jon

On Fri, Mar 1, 2019 at 4:28 PM j4fm <[hidden email]> wrote:

> Ah yeah that makes sense.
>
> It won't let me stop the current stuck build.  Would you be able to?
>
> From the logs it looks like it succeeds up until the point it's frozen...
> I'm not sure what's up with it.  Have you seen it freeze like this before?
> Maybe it's an issue with the CI agent instead?
>
>
>
> --
> Sent from:
> http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

Otávio Gonçalves de Santana
Hey guys

I'm working to make the tests compatible with both Java 8 and Java 11
version.


Right now, I'm at the failover
<https://github.com/apache/tomee/tree/master/itests/failover> project that
has this issue:

java.lang.IllegalAccessException: class
org.apache.openejb.loader.BasicURLClassPath cannot access class
jdk.internal.loader.URLClassPath (in module java.base) because module
java.base does not export jdk.internal.loader to unnamed module
@4c6e276e
    at java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)


There are two ways to solve it;

   - the first one is using the filemodule-info.java
   - Using the add-module argument at maven.


<plugin>
    <artifactId>maven-compiler-plugin</artifactId>
    <configuration>
        <compilerArgs>
            <arg>--add-modules</arg>
            <arg>dk.internal.loader</arg>
        </compilerArgs>
    </configuration></plugin>


However, both make unavailable the situation to run Java 8.

I still working to solve it.

On Fri, Mar 1, 2019 at 2:11 PM Jonathan Gallimore <
[hidden email]> wrote:

> Killed of the builds and forced a new one.
> https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1048
>
> Jon
>
> On Fri, Mar 1, 2019 at 4:28 PM j4fm <[hidden email]> wrote:
>
> > Ah yeah that makes sense.
> >
> > It won't let me stop the current stuck build.  Would you be able to?
> >
> > From the logs it looks like it succeeds up until the point it's frozen...
> > I'm not sure what's up with it.  Have you seen it freeze like this
> before?
> > Maybe it's an issue with the CI agent instead?
> >
> >
> >
> > --
> > Sent from:
> > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> >
>
Reply | Threaded
Open this post in threaded view
|

Re: Building with Java 11

jgallimore
Nice,  thanks for looking at that!

On Fri, 1 Mar 2019, 18:16 Otávio Gonçalves de Santana, <
[hidden email]> wrote:

> Hey guys
>
> I'm working to make the tests compatible with both Java 8 and Java 11
> version.
>
>
> Right now, I'm at the failover
> <https://github.com/apache/tomee/tree/master/itests/failover> project that
> has this issue:
>
> java.lang.IllegalAccessException: class
> org.apache.openejb.loader.BasicURLClassPath cannot access class
> jdk.internal.loader.URLClassPath (in module java.base) because module
> java.base does not export jdk.internal.loader to unnamed module
> @4c6e276e
>     at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
>
>
> There are two ways to solve it;
>
>    - the first one is using the filemodule-info.java
>    - Using the add-module argument at maven.
>
>
> <plugin>
>     <artifactId>maven-compiler-plugin</artifactId>
>     <configuration>
>         <compilerArgs>
>             <arg>--add-modules</arg>
>             <arg>dk.internal.loader</arg>
>         </compilerArgs>
>     </configuration></plugin>
>
>
> However, both make unavailable the situation to run Java 8.
>
> I still working to solve it.
>
> On Fri, Mar 1, 2019 at 2:11 PM Jonathan Gallimore <
> [hidden email]> wrote:
>
> > Killed of the builds and forced a new one.
> > https://ci.apache.org/builders/tomee-trunk-ubuntu-jvm8/builds/1048
> >
> > Jon
> >
> > On Fri, Mar 1, 2019 at 4:28 PM j4fm <[hidden email]> wrote:
> >
> > > Ah yeah that makes sense.
> > >
> > > It won't let me stop the current stuck build.  Would you be able to?
> > >
> > > From the logs it looks like it succeeds up until the point it's
> frozen...
> > > I'm not sure what's up with it.  Have you seen it freeze like this
> > before?
> > > Maybe it's an issue with the CI agent instead?
> > >
> > >
> > >
> > > --
> > > Sent from:
> > > http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html
> > >
> >
>
123