Please stick to trunk revision 63 until I tell you otherwise.
I am in the process of migrating from Apache Ant to Apache Maven as a build system. I'm also moving from manually-generated project files to automatically generated projects using CMake.
CMake allows me to generate project files for different compilers from the same configuration file (less work to maintain).
Maven will allow us to streamline the build process so one day it will even build Boost for you if you need it.
The currently committed code will build Jace but there isn't yet a way to generate proxies using Maven. I hope to be done by early next week.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I committed a Maven plugin for Jace so you should be able to:
1. Enhance Java peers
2. Generate C++ peers
3. Generate C++ proxies
This hasn't been tested yet but it should work the same as under Ant.
I've also migrated the repository to Mercurial to make it easier to maintain moving forward. You can find a short Mercurial tutorial here: http://hginit.com/
I need to complete the following tasks before releasing Jace 1.2.0:
1. Automate building Boost
2. Update the documentation
3. Update the "cmake" plugin to build under Linux
I could really use your help here to speed things up. Please let me know if you're able to contribute patches for any of the above.
Thank you,
Gili
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've trimmed all Maven-related changes from the repository (revision 64 onward) because they were incomplete and the project wouldn't build. These newer changes (and the fixes for the aforementioned build problems) now show up exclusively on http://code.google.com/p/jace/.
Anyone who wishes to continue using the SourceForge project should now be able to build the project properly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please stick to trunk revision 63 until I tell you otherwise.
I am in the process of migrating from Apache Ant to Apache Maven as a build system. I'm also moving from manually-generated project files to automatically generated projects using CMake.
CMake allows me to generate project files for different compilers from the same configuration file (less work to maintain).
Maven will allow us to streamline the build process so one day it will even build Boost for you if you need it.
The currently committed code will build Jace but there isn't yet a way to generate proxies using Maven. I hope to be done by early next week.
If anyone is willing to try out some bleeding-edge code, take a look at http://code.google.com/p/jace/
I committed a Maven plugin for Jace so you should be able to:
1. Enhance Java peers
2. Generate C++ peers
3. Generate C++ proxies
This hasn't been tested yet but it should work the same as under Ant.
I've also migrated the repository to Mercurial to make it easier to maintain moving forward. You can find a short Mercurial tutorial here: http://hginit.com/
I need to complete the following tasks before releasing Jace 1.2.0:
1. Automate building Boost
2. Update the documentation
3. Update the "cmake" plugin to build under Linux
I could really use your help here to speed things up. Please let me know if you're able to contribute patches for any of the above.
Thank you,
Gili
Boost build system has been committed to http://code.google.com/p/boost-maven-project/
Boy, that was *a lot* more work than expected! Next I will be updating Jace to link to the boost project.
I believe the migration is complete. Please take a look at http://code.google.com/p/jace/ and let me know if you run into any problems.
Thanks,
Gili
I've trimmed all Maven-related changes from the repository (revision 64 onward) because they were incomplete and the project wouldn't build. These newer changes (and the fixes for the aforementioned build problems) now show up exclusively on http://code.google.com/p/jace/.
Anyone who wishes to continue using the SourceForge project should now be able to build the project properly.