[jira] [Commented] (ISIS-569) Fix JMock to support JDK7 (JavassistImposteriser)
[ https://issues.apache.org/jira/browse/ISIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142408#comment-15142408 ] Jörg Rade commented on ISIS-569: 1.11.1 still seems to refer to jmock > Fix JMock to support JDK7 (JavassistImposteriser) > - > > Key: ISIS-569 > URL: https://issues.apache.org/jira/browse/ISIS-569 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: core-1.2.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: core-1.5.0 > > > Isis standardized on using JMock a while back, however as a library it > doesn't seem to be keeping up. > Specifically, its mocking of classes depends on cglib 2.x (and therefore asm > 3.x), which conflicts with cglib 3/ asm 4.x (required for JDK 7). > Candidates to replace it are mockito and jmockit. Personally I don't much > like mockito; jmockit comes out well in this comparison: > https://blog.42.nl/articles/mockito-powermock-vs-jmockit/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1306) Enable graph visualisation in Wicket Viewer
Vladimir Nisevic created ISIS-1306: -- Summary: Enable graph visualisation in Wicket Viewer Key: ISIS-1306 URL: https://issues.apache.org/jira/browse/ISIS-1306 Project: Isis Issue Type: New Feature Components: Core: Viewer: Wicket Reporter: Vladimir Nisevic Assignee: Dan Haywood Would be nice to have possibility to visualize graphs with. e.g http://graphviz.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-569) Fix JMock to support JDK7 (JavassistImposteriser)
[ https://issues.apache.org/jira/browse/ISIS-569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142432#comment-15142432 ] Jörg Rade commented on ISIS-569: [INFO] [INFO] Building Isis Unit Test Support 1.12.0-SNAPSHOT [INFO] [INFO] [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ isis-core-unittestsupport --- [INFO] org.apache.isis.core:isis-core-unittestsupport:jar:1.12.0-SNAPSHOT [INFO] +- org.ops4j.pax.tipi:org.ops4j.pax.tipi.junit:jar:4.12.0.1:compile [INFO] | \- org.ops4j.pax.tipi:org.ops4j.pax.tipi.hamcrest.core:jar:1.3.0.1:compile [INFO] +- org.picocontainer:picocontainer:jar:2.15:compile [INFO] +- org.jmock:jmock:jar:2.6.0:compile [INFO] | +- org.hamcrest:hamcrest-core:jar:1.1:compile [INFO] | \- org.hamcrest:hamcrest-library:jar:1.1:compile [INFO] +- org.jmock:jmock-junit4:jar:2.6.0:compile > Fix JMock to support JDK7 (JavassistImposteriser) > - > > Key: ISIS-569 > URL: https://issues.apache.org/jira/browse/ISIS-569 > Project: Isis > Issue Type: Improvement > Components: Core >Affects Versions: core-1.2.0 >Reporter: Dan Haywood >Assignee: Dan Haywood > Fix For: core-1.5.0 > > > Isis standardized on using JMock a while back, however as a library it > doesn't seem to be keeping up. > Specifically, its mocking of classes depends on cglib 2.x (and therefore asm > 3.x), which conflicts with cglib 3/ asm 4.x (required for JDK 7). > Candidates to replace it are mockito and jmockit. Personally I don't much > like mockito; jmockit comes out well in this comparison: > https://blog.42.nl/articles/mockito-powermock-vs-jmockit/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1306) Enable graph visualisation in Wicket Viewer
[ https://issues.apache.org/jira/browse/ISIS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen van der Wal updated ISIS-1306: - Priority: Minor (was: Major) > Enable graph visualisation in Wicket Viewer > --- > > Key: ISIS-1306 > URL: https://issues.apache.org/jira/browse/ISIS-1306 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: Wicket >Reporter: Vladimir Nisevic >Assignee: Dan Haywood >Priority: Minor > > Would be nice to have possibility to visualize graphs with. e.g > http://graphviz.org/ or maybe with http://visjs.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1306) Enable graph visualisation in Wicket Viewer
[ https://issues.apache.org/jira/browse/ISIS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen van der Wal updated ISIS-1306: - Issue Type: Wish (was: Brainstorming) > Enable graph visualisation in Wicket Viewer > --- > > Key: ISIS-1306 > URL: https://issues.apache.org/jira/browse/ISIS-1306 > Project: Isis > Issue Type: Wish > Components: Core: Viewer: Wicket >Reporter: Vladimir Nisevic >Assignee: Dan Haywood >Priority: Minor > > Would be nice to have possibility to visualize graphs with. e.g > http://graphviz.org/ or maybe with http://visjs.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (ISIS-1306) Enable graph visualisation in Wicket Viewer
[ https://issues.apache.org/jira/browse/ISIS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15142849#comment-15142849 ] Jeroen van der Wal commented on ISIS-1306: -- This a rather vague requirement. Could you elaborate more? Perhaps spike a sample app? > Enable graph visualisation in Wicket Viewer > --- > > Key: ISIS-1306 > URL: https://issues.apache.org/jira/browse/ISIS-1306 > Project: Isis > Issue Type: Wish > Components: Core: Viewer: Wicket >Reporter: Vladimir Nisevic >Assignee: Dan Haywood >Priority: Minor > > Would be nice to have possibility to visualize graphs with. e.g > http://graphviz.org/ or maybe with http://visjs.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1306) Enable graph visualisation in Wicket Viewer
[ https://issues.apache.org/jira/browse/ISIS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeroen van der Wal updated ISIS-1306: - Issue Type: Brainstorming (was: New Feature) > Enable graph visualisation in Wicket Viewer > --- > > Key: ISIS-1306 > URL: https://issues.apache.org/jira/browse/ISIS-1306 > Project: Isis > Issue Type: Brainstorming > Components: Core: Viewer: Wicket >Reporter: Vladimir Nisevic >Assignee: Dan Haywood >Priority: Minor > > Would be nice to have possibility to visualize graphs with. e.g > http://graphviz.org/ or maybe with http://visjs.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ISIS-1306) Enable graph visualisation in Wicket Viewer
[ https://issues.apache.org/jira/browse/ISIS-1306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vladimir Nisevic updated ISIS-1306: --- Description: Would be nice to have possibility to visualize graphs with. e.g http://graphviz.org/ or maybe with http://visjs.org/ was: Would be nice to have possibility to visualize graphs with. e.g http://graphviz.org/ > Enable graph visualisation in Wicket Viewer > --- > > Key: ISIS-1306 > URL: https://issues.apache.org/jira/browse/ISIS-1306 > Project: Isis > Issue Type: New Feature > Components: Core: Viewer: Wicket >Reporter: Vladimir Nisevic >Assignee: Dan Haywood > > Would be nice to have possibility to visualize graphs with. e.g > http://graphviz.org/ or maybe with http://visjs.org/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (ISIS-1307) Integrating User Help Documentation
Steve Cameron created ISIS-1307: --- Summary: Integrating User Help Documentation Key: ISIS-1307 URL: https://issues.apache.org/jira/browse/ISIS-1307 Project: Isis Issue Type: Improvement Components: Core Reporter: Steve Cameron Assignee: Dan Haywood Priority: Minor At the moment there is the @PropertyLayout#describedAs() attribute for providing help 'hints' to users. I am wondering if there could be added a more detailed help information being provide to a user pressing F1 key? More specifically to design a mechanism for help documentation to be navigated to (into) from the Isis Wicket viewer interface in a context sensitive way. Broadening this further still, maybe there is a good way to keep user documentation embedded within the Java domain object class files and to generate formatted user help documents in a similar way that Javadoc is generated? I've done a little research on this approach but cannot find an example of where this has been done, but to my mind it seems natural as a Naked Objects way to do it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
