JDK-8074313 : JDK-8022885 broke jaxws build, not replacing @@JAXB_JDK_VERSION@@
  • Type: Bug
  • Component: xml
  • Sub-Component: jaxb
  • Priority: P4
  • Status: Closed
  • Resolution: Won't Fix
  • Submitted: 2015-03-03
  • Updated: 2018-04-11
  • Resolved: 2018-04-11
Related Reports
Relates :  
JDK-8176508 - Update JAX-WS RI integration to latest version
Description
When working with JEP-223 (new version string), I discovered that the jaxws build contains a string "@@JAXB_JDK_VERSION@@" in properties files, where prior to JDK-8022885 a version string was placed.

I assume that upstream changed the hard-coded version string to this tag, and that the upstream build system replaces this string. However, that logic was not ported forward to our build system.

This is the changeset that introduced the problem:
changeset:   396:b99d7e355d4b
parent:      392:6cdc6ed98780
user:        mkos
date:        Fri Aug 23 09:57:21 2013 +0100
description:
8022885: Update JAX-WS RI integration to 2.2.9-b14140
8013016: Rebase 8009009 against the latest jdk8/jaxws
Reviewed-by: alanb, chegar

I'm not sure how to separate what parts of the changeset that is due to JDK-8022885 and what is due to JDK-8013016.
Comments
The Java EE modules have been removed from the JDK
11-04-2018
I reopened issue, change is fixed in standalone and waiting for JDK sync.
20-04-2017
I suppose it's not been synched yet. Is it true, Roman?
20-04-2017
[~rgrigoriadi] What version is this fixed in? I'm still seeing @@JAXB_JDK_VERSION@@ in both jdk9 and jdk10...
20-04-2017
Now properly replaced with current version of JAXB.
18-04-2017
Something wrong in integration scripts?
29-06-2015
I'm putting this on infrastructure/build, but really someone with JAXWS knowledge needs to handle this. Can't figure out what component that should be, though.
03-03-2015