Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Jonathan Gallimore
Everything I've got so far is committed. The build should produce additional artifacts witha jakartaee9 classifier in the tomee/Apache-tomee module. The PR idea sounds interesting. Happy to work on that tomorrow. Jon On Wed, 3 Jun 2020, 18:54 David Blevins, wrote: > Significantly better.

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Jonathan S. Fisher
I'm just curious, could this be done at runtime with a Java Agent? On Wed, Jun 3, 2020 at 12:54 PM David Blevins wrote: > Significantly better. Can you check that in? > > > What I'm imagining to make it easier to digest the breadth of data: > > - run the asmifier on the unmodified zip > -

Re: [RESULT] [VOTE] Release TomEE 8.0.2

2020-06-03 Thread Jenkins, Rodney J (Rod)
I have built the new images. I am testing this as I send this email. There will be a pull request to docker-tomee within the hour. When that is approved, I will updated Dockerhub. Thanks, Rod. On 6/1/20, 8:30 AM, "Jenkins, Rodney J (Rod)" wrote: Nationwide Information Security

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread David Blevins
Significantly better. Can you check that in? What I'm imagining to make it easier to digest the breadth of data: - run the asmifier on the unmodified zip - check every file into *github* - run the asmifier on the modified zip - check that in and create a PR - we can then pick through the

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Jonathan Gallimore
Made some progress by adjusting the rules - here's the latest counts (not including string references): Path javax uses total ./opensaml-xmlsec-api-3.3.1.jar 2 ./opensaml-soap-api-3.3.1.jar 5 ./java-support-7.3.0.jar 12 ./opensaml-saml-impl-3.3.1.jar 7 ./opensaml-core-3.3.1.jar 5

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread David Blevins
> On Jun 3, 2020, at 9:03 AM, Jonathan Gallimore > wrote: > > Just wanted to follow up with some details on how I'm getting the numbers > below. I'm using this tool: https://github.com/tomitribe/jkta So people have a heads-up on that tool, I'm currently working on the Tomitribe side with

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Daniel Dias Dos Santos
very good Jon : ) -- *Daniel Dias dos Santos* Java Developer SouJava & JCP Member GitHub: https://github.com/Daniel-Dos Linkedin: www.linkedin.com/in/danieldiasjava Twitter: http://twitter.com/danieldiasjava Em qua., 3 de jun. de 2020 às 13:05, Jonathan Gallimore < jonathan.gallim...@gmail.com>

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Jonathan Gallimore
I should clarify, the output I pasted is from these commands: java -jar ~/dev/jkta/target/jkta-0.11-SNAPSHOT-shaded.jar usage dir . > jars.tsv java -jar ~/dev/jkta/target/jkta-0.11-SNAPSHOT-shaded.jar usage dir --include-strings=true . > jars.strings.tsv and the first 2 commands provide the data

Re: Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Jonathan Gallimore
Just wanted to follow up with some details on how I'm getting the numbers below. I'm using this tool: https://github.com/tomitribe/jkta Once TomEE is built, I'm extracting the zip, changing to the lib folder, and running the following commands: for f in *.jar; do java -jar

Javax to Jakarta Bytecode transformation progress

2020-06-03 Thread Jonathan Gallimore
HI folks I've been working on doing this translation on the bytecode of the built artifacts. This is done as part of the Maven build, and the "jakartaee9" artifacts are installed as part of the tomee/apache-tomee module. After running a scan of javax references afterwards, we have the following