Running samples from a binary release in source mode

[sdm]

I tried to run the Kauri samples (from a daily build) in source mode (with the -s option), but this gives errors:
..\..\bin\kauri.bat -s module-source-locations.properties

Running the samples without the -s option works fine.

I attached the errors when running kauri-forms-sample en kauri-representationbuilder-sample, but similar errors occured for some other samples as well.

A list of samples that do work in source mode: kauri-dbresources-sample, kauri-i18n-sample, kauri-security-sample, kauri-template-sample

[sdm]

Error when running kauri-forms-sample in source mode

[sdm]

Error when running kauri-representationbuilder-sample in source mode

[mpo]

First remark to make: these errors occur when using the binary (or daily) build, not when using the svn checkout.

In those binary builds the "Source" of the referenced source modules is just not there.

I suggest we at least document this in the samples-readme and maybe seek into removing these properties files during the distro build. (or generate simplistic ones that do work?)

other ideas?

[mpo]

Sudden idea: we might change the kauri-runtime to be more resilient: Only WARN about sources for modules not being present and falling back to their packaged representations.

[mpo]

Running in non-source mode also is not working as mentioned in the docs

​http://docs.outerthought.org/kauri-docs-current/getting-started/177-kauri.html

I don't think the jars should be included in the package, but they should be easily build from sample-source.

Double-checking testing the samples for final 0.4 needed!

[karel]

Running anything using the kauri.sh script in the distro fails:

kauri.sh passes the distro m2 repo via a system property. The launcher uses the
system property to load the runtime cli jar, but there the system property isn't used (it takes a --maven-repo-path argument, which is never set)

[karel]

Replying to karel:

Running anything using the kauri.sh script in the distro fails:

kauri.sh passes the distro m2 repo via a system property. The launcher uses the
system property to load the runtime cli jar, but there the system property isn't used (it takes a --maven-repo-path argument, which is never set)

Oops, didn't run kauri-deploy-repo. Excuse my noise

[karel]

(In [1739]) Improvements wrt running the samples

Split up source-module-locations properties:

• The default version only lists modules whose sources are included in the pom
• the dev version can list all kauri modules

Replaced 0.4-dev.properties with ${project.version} in dist dependencies

see #274

[karel]

Fixed by [1739]. Still one remark though:

You can never run in source mode when you don't build the modules yourself,
because in source mode, classes will be looked up in target/classes.