- it slows my svn updates seriously. My Eclipse is showing the sync with code.google for at least 10 seconds for each update - signavio being JDK6 and we trying to be JDK5 makes it hard to get the build running properly
As I wrote in the latest mail I see 3 options to get around it:
1.) Signavio releases the core components as a jar in some Maven repository 2.) Signavio transforms the core components into a Maven project itself (and release it in some repo) 3.) Create a “proxy” Maven project in Activiti, include the Core Components via svn:externals and build the stuff there
Any thoughts? But currently maybe let's wait what is feasible or fits best for Signavio?
Ah, and a quick addition: Signavio currently tries to get the code base Java 5 compatible (I hope in time for beta2), lets cross fingers and hope, that they will not find any show stopper for that 😉
code freeze is tomorrow. i think we should plan for the fact that they will not be ready unless there is a clear commitment to deliver what we need by friday noon. crossing fingers is going to get our release out in time 🙂