[
https://issues.apache.org/jira/browse/ISIS-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388013#comment-16388013
]
Dan Haywood commented on ISIS-1897:
---
At a quick glance, looks good. This info needs to g
[
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
> --
>
>
Maven Build of 'master' source should work now!
In case anybody is interested, I post a little script here [2], that
builds from most recent sources using branch 'master' at github.
Cheers Andi!
[2]
#!/bin/bash
rm -r ~/.m2/repository/org/apache/isis
rm master.zip
rm -r isis-master
wget https://
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
Great stuff Andy!
To maintain visibility to the community and keep the barrier for
collaboration low I would prefer that you keep working in master. But a
good feedback loop is important (I learned that from Dan) so we will
allocate some time to have a publicly available CI and Docker images of th
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 lea
Hi Andi,
Thanks for this, and the update.
To expand on your status update, right now we have two main branches of
development:
- the "maint-1.16.2" branch ... this is where I cut the 1.16.2 release from
- the "master" branch, which holds the stuff intended for the 2.0.0-M1.
Since "master" is cur
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, domain-c
