-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade Ant library JAX-WS from 2.2.6 to 2.3.3 #3607
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a failure from the sigtest:
Class javax.xml.ws.spi.Provider
"E1.2 - API type removed" : field public final static java.lang.String javax.xml.ws.spi.Provider.JAXWSPROVIDER_PROPERTY = "javax.xml.ws.spi.Provider"
given, that this is a compile time constant, this should have been inlined at build time. I would consider living with that fact, rebuild the sigfiles and be done with it.
I ran |
The build scripts of the modules inherit from
So you should be able to run |
Thank you for the guidance @matthiasblaesing, all test are successful now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I have found a type (missing extension) and one question to improve my understanding. Apart from that this looks very good to me. Thank you.
<package>com.sun.tools.ws</package> | ||
<package>com.sun.tools.ws.ant</package> | ||
<package>com.sun.tools.ws.api</package> | ||
<package>com.sun.tools.ws.api.wsdl</package> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are the new exports in this file needed for WSDL generation or what is the motivation? My curiosity was triggered by the com.sun.tools.ws.ant
package.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I removed all the packages and added only the ones that the build process needed until it completed successfully, re gen-sigtests, check-sigtests and re-test everything as per the description. I think this is the correct approach.
-Utilize jakarta libraries instead of javax -Update license type to EDL-1.0 where needed -Remove unneeded dependencies
-Replace old javax dependencies with new ones from Eclipse Jakarta: --jaxws-api > jakarta.xml.ws-api --jsr181-api > jakarta.jws-api --saaj-api > jakarta.xml.soap-api
-Remove entries to ignore-binary-overlaps file
inside <public-packages>, but just the parent packages.
everything is green here too. Would you like to squash some/all of the commits? |
I will, thanks Michael |
-Mavenize jaxws-api external jars -Utilize jakarta libraries instead of javax -Update license type to EDL-1.0 where needed -Remove unneeded dependencies -Fix wrong paths directing to jaxws and jaxb jars -Replace old javax dependencies with new ones from Eclipse Jakarta: --jaxws-api > jakarta.xml.ws-api --jsr181-api > jakarta.jws-api --saaj-api > jakarta.xml.soap-api
Fixes Issue-3622
Library Notes:
jaxws21api
:NetBeans Testing:
j2ee.dd.webservice
,websvc.jaxws21api
,websvc.jaxws21
,tomcat5
,websvc.design
,websvc.jaxwsmodel
,websvc.manager
,java.project.ui
andwedsvc.saas.api
Web Page:
https://projects.eclipse.org/projects/ee4j.jaxws