Closed glassfishrobot closed 15 years ago
Reported by jungicz@java.net
jitu@java.net said: wsimport has Xnocompile option. But not for wsgen. Assigning this to Rama
syvalta@java.net said: Additionally, ability to specify target java version would be really useful (for example, -target 1.5 could be passed to javac). People often use newer jdk's and that results in Bad version number exceptions when they try to deploy to java5 based servers. Additionally, this means builds are jdk version dependent.
scm_issue_link@java.net said: Code changed in jax-ws-sources User: ramapulavarthi Path: /jax-ws-sources/jaxws-ri/tools/wscompile/src/com/sun/tools/ws/ant/WsGen2.java (1.3.4.2) /jax-ws-sources/jaxws-ri/tools/wscompile/src/com/sun/tools/ws/wscompile/WsgenTool.java (1.5.4.3) http://fisheye5.cenqua.com/changelog/jax-ws-sources/?cs=jaxws22:ramapulavarthi:20090922021308
Log: JAX-WS-360: Add Xnocompile option for wsgen similar to wsimport.
ramapulavarthi@java.net said: There is already a target option for wsimport to generate as per the target version of the JAX-WS specification. To customize the target option for javac, Users can use -Xnocompile option and then specify different options of javac.
ramapulavarthi@java.net said: Fixed in 2.2.
Was assigned to ramapulavarthi@java.net
This issue was imported from java.net JIRA JAX_WS-360
Marked as fixed on Monday, September 21st 2009, 12:18:46 pm
It would be useful to have a possibility to force wsgen/wsimport to not compile generated classes (such option could be called ie "nocompile" or "Xnocompile") mainly in cases when one needs to compile generated stuff with different JDK (eg. 5) then is used for running wsgen/wsimport (eg. JDK 6) to workaround for example http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6553734
Environment
Operating System: All Platform: All
Affected Versions
[2.1]