Hi @trajano This is really old and I suspect no longer valid repo. I've since moved completely to jakarta ee4j version which is working well on all jdks. Anyways, figured I would send what I had from the past as it does not harm. I'm not sure if the actual jira you originally raised was ever fixed. The ticket is still open but as you are likely aware, oracle is no longer maintaining the old location. It doesn't appear as-is that all ported over to ee4j at least on that reference ticket. The plugin itself is. It might make sense to determine if the issue is still present and get a new ticket open. It also might make sense to lock down this repo past this point as usefulness is likely no longer here. At any rate, just cleaning up left over items I had that do successfully build with no downside I can see. Thanks.
Hi @trajano This is really old and I suspect no longer valid repo. I've since moved completely to jakarta ee4j version which is working well on all jdks. Anyways, figured I would send what I had from the past as it does not harm. I'm not sure if the actual jira you originally raised was ever fixed. The ticket is still open but as you are likely aware, oracle is no longer maintaining the old location. It doesn't appear as-is that all ported over to ee4j at least on that reference ticket. The plugin itself is. It might make sense to determine if the issue is still present and get a new ticket open. It also might make sense to lock down this repo past this point as usefulness is likely no longer here. At any rate, just cleaning up left over items I had that do successfully build with no downside I can see. Thanks.