Hi, We are starting to build Jaxx 3.0. This major version will not be necessary compatible with Jaxx 2.x, but some tools will be here to help migrate!. Here is some major changes we'd like to introduce in Jaxx 3.0: o Minimum Jdk 7 requirement o Be able to use jdk 7 grammar in your code (this is yet possible with jaxx 2.24 :)) o Review the modules (one module for one component) o Minimize generated code dependencies (a very thin module jaxx-runtime-api) o Remove the JXLayer dependency (Jdk 7 offers the JLayer API) o Remove the javax.help dependency o Improve the usage of jaxx css files (and be able to rename this extension) o Add a new file type jaxx script o Develop some plugins to help his usage (for IntelliJ I suppose) o Use Eugene to generate the code o Add some extension mecanisms inside Jaxx o ... If you have any idea you'd like to see in version 3.0, you are welcome! tony. -- Tony Chemit -------------------- tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: chemit@codelutin.com twitter: https://twitter.com/tchemit
On Thu, 23 Apr 2015 20:49:13 +0200 Tony Chemit <chemit@codelutin.com> wrote:
Hi,
Just for the record, Jaxx-2.x use now separate git branches : develop-2.x master-2.x develop and master branches are now dedicated to Jaxx 3.0. To produce a release of a Jaxx 2.x, just go to the develop-2.x and do as usual (the pom is well configured for this). To fix a bug or still add a feature in Jaxx 2.x I recommend to use another clone of the jaxx git repository and configure git-flow (AVH of course!) to use the develop-2.x and master-2.x as main branches. It will helps you not to specify each time the develop-2.x as starting point of new features... Voila, :) tony. -- Tony Chemit -------------------- tél: +33 (0) 2 40 50 29 28 http://www.codelutin.com email: chemit@codelutin.com twitter: https://twitter.com/tchemit
participants (1)
-
Tony Chemit