Thanks Dan.
The -Dskip.nightly allowed me to progress further, and the web links are
repaired.
However there is still a sea of maven errors. I think Slack may be a
better forum for resolving the maven stacktrace tsunami. Please send an
ASF slack invite to this email address.
I use cygwin on Windows 10. I checked an i am using amazon correto
11.0.17 and maven 3.8.6
Most recent maven terminal condition log statement:
[ERROR] Failed to execute goal
org.springframework.boot:spring-boot-maven-plugin:2.7.4:run
(default-cli) on project simpleapp-jpa-webapp: An exception occurred
while running. null: InvocationTargetException: Unable to start web
server; nested exception is
org.springframework.boot.web.server.WebServerException: Unable to start
embedded Tomcat: Error creating bean with name
'org.apache.isis.viewer.restfulobjects.viewer.webmodule.IsisRestfulObjectsInteractionFilter':
Unsatisfied dependency expressed through field 'interactionService';
Cheers,
Terry.
On 11/12/2022 18:47, Dan Haywood wrote:
Hi Terry,
thanks for your interest, and thanks for flagging the issues you've
encountered.
To take #3 first, I've fixed the link on the home page. There are actually
two versions of the demo, one for JPA and a JDO. Admittedly the deploy is
a bit flaky and that's something I've been meaning to fix - they get
redeployed each night and it's a bit glitchy. You should (at least today)
find that the JPA version of the demo is available ...
https://demo-wicket.jpa.isis.incode.work/ Or, if you want to see
something simpler, then the simpleapp (JDO) is up,
https://simpleapp.jdo.isis.incode.work/.
Re: #2, thanks for the suggestions on documentation improvements. I guess
we haven't documented anything because we haven't hit an issue, though I
agree that the prereqs are not obvious. So I've updated the quick start
section on the home page to also list them, basically JDK 11 and Maven 3.6+.
Re: #1, unfortunately I can't reproduce your problem ... on a brand new
Ubuntu VM, with just the prereqs installed, I was able to pull everything
down and run the simpleapp.
What I have done on the home page is changed the "mvn clean install"
command a little, to deactivate a couple of profiles which also pull from
the ASF staging and our own nightly repo ... so that should reduce the
noise and help track the issue. Try running with the -X flag also, ie "mvn
clean install -Dskip.staging -Dskip.nightly -X"
The other thing you can do is just to clone the github repo (
https://github.com/apache/isis-app-simpleapp) and check out the "jpa"
branch, which should correspond to M9.
Let us know how you get on. You might also want to join the ASF slack, we
can send an invite to you to our channel if you wish.
Cheers
Dan
On Sun, 11 Dec 2022 at 14:50, Terry Lurie <tezza...@yahoo.co.uk.invalid>
wrote:
Hi Team,
I am evaluating Isis / Causeway in December 2022. There are some Quick
Start problems stopping me evaluating it further.
Your project seems really exciting so although there were major issues I
wanted to let you know portions are currently broken.
I'm an experienced java developer.
*1/3) Quick Start Broken**
*
Your Quickstart ->
> APP=isis-app-simpleapp > BRANCH=jpa > curl
https://codeload.github.com/apache/$APP/zip/$BRANCH | jar xv > cd
$APP-$BRANCH > > mvn clean install > mvn -pl webapp spring-boot:run
is currently broken.
Looking at the maven output, it appears the version 2.0.0-M9
dependencies are not published properly.
Maven error:
[ERROR] Failed to execute goal on project simpleapp-jpa-webapp: Could
not resolve dependencies for project
org.apache.isis.starters:simpleapp-jpa-webapp:jar:2.0.0-M9: Could not
find artifact
org.apache.isis.starters:simpleapp-jpa-module-simple:jar:2.0.0-M9 in
nightly-builds (https://raw.githubusercontent.com/apache-isis-commit
ters/isis-nightly/master/mvn-snapshots
<https://raw.githubusercontent.com/apache-isis-committers/isis-nightly/master/mvn-snapshots>
)
*2/3) Documentation assumes Quickstart succeeds*
If the Quickstart breaks, the documentation has few workarounds. Perhaps
consider have the publishing of all the prerequisites automated somehow.
And possibly a scheduled pipeline check that the Quickstart process
actually succeeds.
Or a break-glass section in the documentation for the learners like me
who stumble on the project at the time the Quickstart is broken.
*3/3) https://demo-wicket.isis.incode.work/ is 404*
Where your front page Quickstart section says:
"You can also explore the Apache Isis programming model through the demo
app, running here <https://demo-wicket.isis.incode.work/>."
The here link returns a 404 ( https://demo-wicket.isis.incode.work/ )
What advice do you have for me to continue deeper evaluation until the
Quick Start process is fixed up ?
Terry.
