Hi Martin, thx, now I understand it. Dependencies changes are not problematic for us, so I vote: +1.
Am 03.02.2015 um 13:15 schrieb Martin Grigorov <mgrigo...@apache.org>: > Hi ARI, > >> Hi Dan, >> >> I have started to promote isis for an internal sales application, which >> will go productive next week. Our company mainly developing vaadin >> applications, the next steps to push isis further in our company would be >> to developing a vaadin viewer. That why I would vote for not merging Wicket >> into the Core. >> > > Moving Wicket viewer to core means that some Maven groupId and/or > artifactId will change for the users. Nothing more. > For Isis developers this is not an actual change. > For Isis release manager the change will just simplify the process. > > For your Vaadin based application this means that you won't add > wicket-viewer.jar in your dependencies. That's all. > > >> >> Greetings, ARI (H2000) >> >> Am 02.02.2015 um 23:24 schrieb Dan Haywood <d...@haywood-associates.co.uk>: >> >>> Hi folks, >>> >>> Over the last few releases we've been slowly rationalizing the various >>> Maven modules, and for 1.8.0 I'd like to go one further step and merge >> the >>> Wicket viewer into core also. >>> >>> * it's the defacto (human usable) UI for Isis >>> * the use cases that it supports are to a large extent driving the >>> evolution of Isis' metamodel >>> * it simplifies the release process (hopefully will encourage us >> committers >>> to do more frequent releases) >>> >>> From a user (ie programmer) perspective, the impact will be that some of >>> the Maven dependencies will change. We'll update the archetypes though >> to >>> make it easy to see the changes. >>> >>> I'll leave this thread open a few days to allow opinions to be aired; if >> I >>> hear nothing then will assume lazy consensus. >>> >>> Thx >>> Dan >> >>
