Re: Announcing the "Incode Platform"

Hi Guys, One item not on your list is to better promote the capabilities of Apache Isis as a framework, not insignificant! Just having the 'Incode Platform' as an entity will assist in that I feel. I have just in the past week started a small experimental project which relates to promoting

Apache Isis source code (master) is now hosted at github

Dear committers (and any one else), just to say that as per INFRA-15082, ASF infra have now moved the Apache Isis git repo, and the master is now hosted at github, ie it is no longer a mirror. If you want to push changes to our repo, you'll therefore need to: a) on your local clone, update the

[jira] [Commented] (ISIS-1712) 1.15.1 release activities

[ https://issues.apache.org/jira/browse/ISIS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176514#comment-16176514 ] ASF subversion and git services commented on ISIS-1712: --- Commit

[jira] [Commented] (ISIS-1712) 1.15.1 release activities

[ https://issues.apache.org/jira/browse/ISIS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176513#comment-16176513 ] ASF subversion and git services commented on ISIS-1712: --- Commit

[jira] [Commented] (ISIS-1712) 1.15.1 release activities

[ https://issues.apache.org/jira/browse/ISIS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176515#comment-16176515 ] ASF subversion and git services commented on ISIS-1712: --- Commit

[jira] [Created] (ISIS-1737) Hiding of elements doesn't work on interfaces

Erik de Hair created ISIS-1737: -- Summary: Hiding of elements doesn't work on interfaces Key: ISIS-1737 URL: https://issues.apache.org/jira/browse/ISIS-1737 Project: Isis Issue Type: Bug

Announcing the "Incode Platform"

Over the last few years we (Dan, Johan and Jeroen) have developed a number of addons and supporting modules, originally at http://www.isisaddons.org and later also at http://catalog.incode.org . Each of these modules had their own repo and example app demonstrating their usage, and each were

Re: Update Isis project documentation

On Fri, 22 Sep 2017 at 12:53 Kevin Meyer wrote: > Hi, > > Am I correct in guessing that Apache CMS is no longer available to edit > the project documentation? > > correct > I assume I would edit the documentation in git at [1]? > > correct > The "Edit inline via PR" has

Update Isis project documentation

Hi, Am I correct in guessing that Apache CMS is no longer available to edit the project documentation? I assume I would edit the documentation in git at [1]? The "Edit inline via PR" has also been removed, right? (I don't see it in Firefox). Cheers, Kevin [1]

Re: [VOTE] Apache Isis Core release 1.15.1 RC1

My +1 Further comments: After a "mvn clean install", run the archetype-generated simpleapp by: $ cd webapp $ mvn jetty:run After a "mvn clean install", run the archetype-generated helloworld by (There is no web-app directory): $ mvn jetty:run Thanks again to Dan for organising this release!

Re: Kotlin archetye (WAS: AW: Complaints against Lombok?)

Hi Jorg, it's certainly possible to mix Kotlin and Java, pretty much seamlessly, even on a file-by-file basis. For anyone not in the know, this is JetBrains language and so it has had deep integration with the IntelliJ IDE from the off. I recommend the Talking Kotlin podcast [1] to learn some

Re: [VOTE] Apache Isis Core release 1.15.1 RC1

I'm in the process of checking this release... For anyone else doing this for the first time: a. The guidelines URL [1] is wrong, it should be [2]. b. The "mvn dependency:go-offline" fails to complete (unable to find schema resources). This can be worked around in the usual way (install using

Kotlin archetye (WAS: AW: Complaints against Lombok?)

Hi, changing (part of) a development environment is always effort. For me switching to IntelliJ already pays off and I'll give Kotlin a try too. I assume mixing languages would be possible as well? Best regards Jörg -Ursprüngliche Nachricht- Von: Dan Haywood

[jira] [Commented] (ISIS-1712) 1.15.1 release activities

[ https://issues.apache.org/jira/browse/ISIS-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176277#comment-16176277 ] ASF subversion and git services commented on ISIS-1712: --- Commit

[jira] [Commented] (ISIS-1277) setAccessible() will be gone with JDK 9

[ https://issues.apache.org/jira/browse/ISIS-1277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176247#comment-16176247 ] Jörg Rade commented on ISIS-1277: - The hibernate ways:

Re: [VOTE] Apache Isis Core release 1.15.1 RC1

+1 > El 22 sept 2017, a las 1:39, Dan Haywood > escribió: > > I've cut a release for Apache Isis Core and the two archetypes: > > * Core 1.15.1 > * HelloWorld Archetype 1.15.1 > * SimpleApp Archetype 1.15.1 > > This is mostly a bugfix release, including

Re: Complaints against Lombok?

Hi Kev, @Dan: Did you consider other helpers? How did you choose Lombok? (Probably like others), we were looking at how to make the Estatio codebase easier to understand/work with, and I remembered seeing some blog posts about it and decided to check it out. Since it integrates nicely with the

Re: Complaints against Lombok?

Hi all, from my point of view, choosing Lombok is not bad idea. It reduces a lot of code that developers do not want to write. yes, a specific Lombok version will only work with few JDKs. But it doesn't matter because we do not change our JDK every day. Every time when JDK upgrade, we have to

Re: Complaints against Lombok?

Hi all, I started to love @Getter and @Setter for more thant 1 year ago, and really happy with that ;) Clearer code, with less boilerplate, and more readable Domain Entities. Basically it’s the same C# people is enjoying. Properties have become a first-class citizen on most Java classes.

AW: Complaints against Lombok?

Hi, from the user (developer) perspective I love Lombok's @Getter @Setter for making source much more compact and saving me brain dead key presses. Thereby increasing readability and maintainability of code. AFAIK Lombok intercepts somewhere before compile time and IntelliJ even offers menu

Re: Complaints against Lombok?

Hi Dan, I acknowledge that tech is probably not the biggest take-up challenge we face. However I'd prefer an argument like "we don't use Lombok in Isis sources, only examples, so any other boiler-plate-removal-choice is entirely under use-control" :) As I understand it, it's precisely because

[jira] [Commented] (ISIS-1645) Integrate Kyro as an alternative technology for view models

[ https://issues.apache.org/jira/browse/ISIS-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16176050#comment-16176050 ] Jörg Rade commented on ISIS-1645: - Project name was changed from Kyro to Kryo ... > Integrate Kyro as an

Re: Complaints against Lombok?

Hi Kevin, I'd be surprised if Lombok really counts against us ... in terms of technology choices more likely is our use of JDO (I've just started on the DN 5.1 upgrade, so plan to support JPA by Xmas, at latest). Remember also that Lombok is just a compile-time thing. I see from [4] that the

Complaints against Lombok?

Hi, We use and encourage the use of Lombok[1][2]. However, inspired by a conversation I had with one of our architects the other day, I did a little research and found that people complain that Lombok is hacky and fragile (uses private Java API) [3]. Is any of this really an issue? Are any of

[jira] [Created] (ISIS-1736) ConfigurationServiceDefault has issue

Steve Cameron created ISIS-1736: --- Summary: ConfigurationServiceDefault has issue Key: ISIS-1736 URL: https://issues.apache.org/jira/browse/ISIS-1736 Project: Isis Issue Type: Bug