Hi,

We did a three days coding marathon to prepare the work on JabRef 3.0.
The goal was to streamline the codebase and make it more accessible to
the outside.

The whole work takes part on the master branch. The version there is
called "2.80" to show that transition to Jabref 3.0 is not yet
complete, but Java 8 support is in and preparation work has been made.

The switch to gradle is now complete. No ant necessary any more amd a
major update of all dependencies.

What is more, we use CircleCI, which makes the binary builds
downloadable after each build. In CircleCI, go to the JabRef project
and choose the artifacts tab. You have to create an account for that.


We found that the plugin system is seldomly used outside. Since our
rework of classes will break existing plugins and we are very open to
pull request, we removed plugin support. All plugin developers should
get in touch with us to discuss the next steps.


The branch dev_2.11 has been created. It is used to prepare the
release of the 2.11 version. We will include important fixes here, but
will focus on getting a first 2.80 version ready. Therefore, we
recommend to include new features in the master branch.


If you have any questions, please get in touch with us.

Cheers,

Oliver

------------------------------------------------------------------------------
_______________________________________________
Jabref-devel mailing list
Jabref-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jabref-devel

Reply via email to