Hi Martin, Thanks for reporting this. Actually, there is a ticket for this, ISIS-1748 [1], and which details a work-around.
I hadn't realized that the issue was that the config was missing from the "standard" maven mixin, though... that's useful. On your side note: if you don't want to use the maven mixin, you can of course refactor the pom. Running mvn help:effective-pom is one way to materialize the mixin. Thx Dan [1] https://issues.apache.org/jira/browse/ISIS-1748 On Wed, 6 Dec 2017 at 06:40 Martin Hesse <[email protected]> wrote: > Hi, > > I recently tried to bootstrap a new project using the 1.15.1 simple > archetype. After importing the project into eclipse I found that the > compiler settings (source/target level) in the parent project are not > detected by the compiler plugin in the child projects, even though they do > appear in the respective "effective POM" views. In the library dependencies > of the child projects in eclipse I see the code level set to 1.5, which of > course can't work. > > Then I tried to locate the definition of the compiler plugin and it seems > to come with one of the maven mixins (standard?). > > Currently it seems I can't get the project to run as I used to back when > relying on archetype versions that didn't use the mixins. > > Anyone experienced this before or knows a solution for this? > > On a side note: I would rather continue using eclipse and consider > materializing the mixins directly into the POM, or in other words replace > the mixin dependency with the mixin contents (if that makes sense?). > > Thanks and regards > Martin >
