Hi Diego,
OK, so I just tried this out, and you are right that there is a slight
issue trying to compile the code under JDK 1.7, but it's easy enough to
work around.
basically, where you are getting the compile exceptions, change the code to
cast to the raw type, eg:
@Override
public List<Class<?>> getModules() {
return (List)Arrays.asList(
...
);
}
I had to do this for DomainAppAppManifest, DomainAppDomManifest.
Similarly
public List<Class<? extends FixtureScript>> getFixtures() {
return (List)Lists.newArrayList(RecreateSimpleObjects.class);
}
in DomainAppAppManifestWithFixtures
I also had the following changes to pom.xml (you mentioned some of these):
- adjust maven-enforcer-plugin configuration:
<requireJavaVersion>
<version>[1.7.0,)</version>
</requireJavaVersion>
- adjust maven-compiler-plugin configuration:
<configuration>
<source>1.7</source>
<target>1.7</target>
<!--
<compilerArgument>-parameters</compilerArgument>
-->
</configuration>
HTH
Dan
On 27 February 2016 at 15:41, Diego <[email protected]> wrote:
> Hello everyone.
>
> I was trying to get acquainted with Apache Isis (which I find fascinating)
> by means
> of the tutorial pages using the simpleapp archetype.
>
> I'm having multiple issues though:
>
> a) Config issues
>
> b) Source code issues
>
> My setup:
>
> Windows 10, Eclipse Luna, Maven 3.3.9, JDK 1.7.0_79-b15 (64 bit)
>
> About a)
>
> Using Maven from the command line (pasted) :
>
>
> c:\Work2\Testing\myapp3\myapp>c:\Work2\bin\apache-maven-3.3.9-bin\apache-maven-3.3.9\bin\mvn
> archetype:generate -D archetypeGroupId=org.apache.isis.archetype -D
> archetypeArtifactId=simpleapp-archetype -D archetypeVersion=1.11.1 -D
> groupId=com.mycompany -D artifactId=myapp -D version=1.0-SNAPSHOT -B
>
>
> Maven is signalling source and target being 1.8 and also having troubles
> with
>
> this in the POM file
>
> <compilerArgument>-parameters</compilerArgument>
>
> To solve this, I tried Maven v 3.2.1 and v.3.0.5 adjusting to 1.7 and
> commenting out the compiler argument (and modifying requireJavaVersion in
> maven enforcer plugin)
>
> About b)
>
> By tweaking the parameters, somehow I managed to start the compilaton
> process on Maven 3.3.9 (mvn -e -X clean compile ) but I'm getting
> 'incompatible types" compiler errors:
>
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project myapp-dom: Compilation failure
> /C:/Work2/Testing/myapp2/myapp/dom/src/main/java/domainapp/dom/
> DomainAppDomManifest.java:[36,29] incompatible types
> required: java.util.List<java.lang.Class<?>>
> found: java.util.List<java.lang.Class<domainapp.dom.
> DomainAppDomainModule>>
>
> ....
> ....
>
> Caused by: org.apache.maven.plugin.compiler.CompilationFailureException:
> Compilation failure
> /C:/Work2/Testing/myapp2/myapp/dom/src/main/java/domainapp/dom/
> DomainAppDomManifest.java:[36,29] incompatible types
> required: java.util.List<java.lang.Class<?>>
> found: java.util.List<java.lang.Class<domainapp.dom.
> DomainAppDomainModule>>
>
>
> I tried some code tweaking and got further complaints about some method not
> overridden (getModules() by AppManifest abstract class)
>
> I did some research and this MIGHT be related to a JDK bug but..
> basically... I'm lost.
>
> I saw that Apache Isis 1.11 was re-released (1.11.1) to comply with 1.7
> (and still supports 1.7 as a minimum fortunately) so this might be
> related.
>
> Can you help?
>
>
> Cheers,
>
> Diego
>
> P.S. = I also tried using 1.12.0-SNAPSHOT and using Maven from inside
> Eclipse, with the same effect
>
