Re: Current state on 2.0.0-M1

2018-03-06 Thread Andi Huber
Thx Dan. I think, I can live with that no problem. However, M1 has grown structural rather far apart from the 'stable' branch, so any changes made on the 'stable' branch need to be merged into 'M1' not the other way around. Also the idea of rebasing M1 on 'stable' is no longer applicable. (At

Current state on 2.0.0-M1

2018-03-06 Thread Andi Huber
The 'master' branch intended for version (2.0.0-M1) is progressing: We've broken apart our core modules such that its now in the responsibility of developers to pick from the new core-plugins, what they want to include with their domain-code and web-app deployment. Meaning for migration,

Re: Current state on 2.0.0-M1

2018-03-06 Thread Andi Huber
Thanks Jeroen! I can confirm that. Build fails due to missing dependencies. I'll try to fix this as fast as possible. At least this standard build you referenced [1] should work. Other than that, I've everything checked out in my IDE, where everything compiles and every JUnit Test passes. So the

[jira] [Updated] (ISIS-1635) Upgrade dependency to resteasy

2018-03-06 Thread Dan Haywood (JIRA)
[ https://issues.apache.org/jira/browse/ISIS-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Haywood updated ISIS-1635: -- Fix Version/s: 2.0.0-M1 > Upgrade dependency to resteasy > -- > >