search

johvargas / sfdc-wsc

Automatically exported from code.google.com/p/sfdc-wsc
0 stars 0 forks source link

Enhancement Request: New Option for Code Generation ("-Dseparate.source.from.comiled"?) #53

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
There are really two parts to this request that boil down to one need: the need 
to be able to deploy JAR files that contain only classes, no source code.

The standard sfdc-wsc library JAR file, and the generated JAR file created by 
running com.sforce.ws.tools.wsdlc, contain both the .class files and the .java 
files. This makes them substantially bigger than they otherwise would, and also 
presents a challenge to developers who don't want source code deployed with 
their application.

Thankfully, I was able to write a little ant script that easily enough stripped 
the .java files from the JAR files, but it seems to me that it would make sense 
for you to be able to download a binaries sfdc-wsc JAR file, a sources sfdc-wsc 
JAR file and (optionally) a JAR file that contains both if needed.

Also, you could add a simple command-line argument to com.sforce.ws.tools.wsdlc 
(perhaps "-Dseparate.source.from.comiled"?) that instructs it to either leave 
the .java files out of the generated JAR file, or create two JAR files, one 
with binaries and one with sources.

Thoughts?

Original issue reported on code.google.com by nicholas...@puresafety.com on 6 Mar 2012 at 10:02

GoogleCodeExporter commented 8 years ago 
Can I get some feedback on this? When is the next anticipated release for 
sfdc-wsc? Any idea how easy/difficult it would be to get this in the next 
release?

Original comment by nicholas...@puresafety.com on 3 Jul 2012 at 9:59

GoogleCodeExporter commented 8 years ago 
Any chance on getting this one implemented? Seems much easier than the other 
suggestion I made, #52. :-)

Original comment by nicholas...@puresafety.com on 31 Jan 2013 at 9:03

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
For those interested I've made a Maven fork using git-svn (thus still in sync 
with this Subversion repository) and I've merged the changes introduced by 23.

The idea beside being able to use Maven is also to separate the part that is 
used by the tool to generate the classes and the part that is intended to be 
deployed on production and of course avoiding the Java sources being packed 
with the classes.
More details here: http://code.google.com/p/sfdc-wsc-maven

Beside that I've also created a JAX-WS implementation:
http://github.com/vitkin/sfdc-jaxws

Original comment by victor.i...@gmail.com on 4 Feb 2013 at 2:42