-------------------------------------------------------
About the fork
The original repo is achieved, and tests can't run without upgrade dependencies.
This fork is intended to release a standby tool of jar (yes there are other forks released jar package).
- Add Eclipse project settings
- Upgrade API level to jdk1.8 (new features like lambda are ignored. See test/resources/api8/StaticLambda.cs.txt)
- Upgrade org.eclipse.jdt.core to 3.25.0 (to fix internal error)
- Fix "-cp" option problem - it's actually java's option. But used as sharpen command line arguments (see doc for usage, source folder name: src) This fork use -clsp=.../* for multiple jars.
- Add maven project support - resolve the dependencies with maven
- Add examples (TODO)
- Add doc (TODO)
A discussion about future
Probably the early AST structure before JDK 1.5 is close with c#. But it should getting harder and harder to keep both ASTs mapped while both language keep extending. E.g., any thoughts about mapping JDK 1.8 stream to C#?
Please let me know if you have any advice.
Test the Fork
This fork added some test case that's not easy to be handled. As it's only for a temporary solution for Anclient.cs, it's just ignored some error. To test, use
mvn test -Die=true
-------------------------------------------------------
Sharpen - Automated Java->C# coversion
Sharpen is a library and command-line tool for automating Java to C# code conversion. You can provide configuration classes to control a wide range of class and functionality mapping.
Sharpen doesn’t provide a compatibility runtime (i.e, an implementation of all java functionality on top of .NET), but it does provide some utility classes to meet the most common needs.
It’s likely that you will need to create a configuration class to customize and perfect your conversion, and you may need to apply patches to the result as well.
Sharpen was originally created by db40 svn source here in the format of an Eclipse plugin, but it has since been refactored to work from the command line and on build servers.
Building and testing sharpen itself
- Clone this repository
- Install Java 7 and maven. Java 6 and 8 and later aren’t supported.
- Run ‘mvn clean test’ to test
- Run ‘mvn install ’ to generate .jar files in /sharpen.core/target
Running sharpen
mvn install
should have created a file namedsharpencore-0.0.1-SNAPSHOT-jar-with-dependencies.jar
. This is a self-contained copy of sharpen that can be run anywhere.- Run
java -jar sharpencore-0.0.1-SNAPSHOT-jar-with-dependencies.jar SOURCEPATH -cp JAR_DEPENDENCY_A JAR_DEPENDENCY_B
Each dependecy needed by the java source should be specified as a full path to the jar file. SOURCEPATH should also be a full path. - Run -help for syntax
Sharpen allows for configuration through code
Sharpen’s command-line options don’t let you fully override all conversion options and behaviour. For example if you need to change mapping of primitive types or allow/deny mapping between iterators and enumerators, ...
Creating external config class
Your external configuration class must:
- inherit Configuration class;
- must be publicly visible;
- must have a public constructor;
An example configuration project can be found here https://github.com/ydanila/sharpen_imazen_config.
Using your custom config class
Name your jar file <configuration class name>
.sharpenconfig.jar in the sharpen directory. Then specify the full configuration name via the command line parameter -configurationClass
(or via the options file).
For example, for the XMP core port with this prebuilt Sharpen configuration could be used as follows.
java -jar sharpen-jar-with-dependencies.jar C:/java_src/ -configurationClass sharpen.config.MEConfiguration @sharpen-all-options-without-configuration
Configuration also could be specified in an options file. In this case, for the XMP core port with this prebuilt Sharpen configuration it could be used like this:
java -jar sharpen-jar-with-dependencies.jar C:/java_src/ @sharpen-all-options