Quick start pom.xml for Valkyrie-RCP dependant app

[bravegag]

After some struggle creating a new application on top of Valkyrie-RCP I realize it is quite hairy to setup and have all the configurations/aspectj waivers etc etc aligned with Valkyrie-RCP. The cause of all exceptions and troubles I have had are because the guesswork around setting the new pom.xml . Looking at e.g. sample simple is easy because it inherits all the settings, dependencies and plugins from the parent pom but starting up correctly a new App on top of Valkyrie-RCP is nothing like trivial.

I also tried generating a new project using Valkyrie RCP archetype to copy its pom.xml but it also fails with +/- the same kind of error I get:

Choose a number or apply filter (format: [groupId:]artifactId, case sensitive contains): 263: 116 Choose dk.navicon:valkyrie-rcp-archetype version: 1: 1.1 2: 1.2-SNAPSHOT Choose a number: 2: 2 Define value for property 'groupId': : test Define value for property 'artifactId': : test Define value for property 'version': 1.0-SNAPSHOT: : 1.2-SNAPSHOT Define value for property 'package': test: : Confirm properties configuration: groupId: test artifactId: test version: 1.2-SNAPSHOT package: test Y: :

/Users/bravegag/code/test$ tree . ├── pom.xml ├── src │   └── main │   ├── java │   │   └── test │   │   ├── ApplicationRunner.java │   │   ├── SimpleApplicationConfig.java │   │   └── SimpleCommandConfig.java │   └── resources │   ├── META-INF │   │   └── valkyrie │   │   └── context.xml │   └── logback.xml └── target ├── classes │   ├── META-INF │   │   └── valkyrie │   │   └── context.xml │   ├── builddef.lst │   ├── logback.xml │   └── test │   ├── ApplicationRunner.class │   ├── SimpleApplicationConfig.class │   └── SimpleCommandConfig.class └── generated-sources └── annotations

14 directories, 12 files /Users/bravegag/code/test$ mvn clean install exec:java -Dexec.mainClass="test.test.ApplicationRunner" [INFO] Scanning for projects... [INFO]
[INFO] ------------------------------------------------------------------------ [INFO] Building Valkyrie Project Archetype 1.2-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ test --- [INFO] Deleting /Users/bravegag/code/test/target [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ test --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 2 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ test --- [INFO] Compiling 3 source files to /Users/bravegag/code/test/target/classes [INFO] [INFO] --- aspectj-maven-plugin:1.3.1:compile (default) @ test --- [ERROR] can't determine superclass of missing type org.springframework.transaction.interceptor.TransactionAspectSupport when batch building BuildConfig[null] #Files=3 AopXmls=#0 [Xlint:cantFindType] [ERROR] can't determine superclass of missing type org.springframework.aop.interceptor.AsyncExecutionAspectSupport when batch building BuildConfig[null] #Files=3 AopXmls=#0 [Xlint:cantFindType] [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 3.510s [INFO] Finished at: Fri May 10 17:19:32 CEST 2013 [INFO] Final Memory: 14M/528M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.codehaus.mojo:aspectj-maven-plugin:1.3.1:compile (default) on project test: Compiler errors: [ERROR] error can't determine superclass of missing type org.springframework.transaction.interceptor.TransactionAspectSupport [ERROR] when batch building BuildConfig[null] #Files=3 AopXmls=#0 [ERROR] [Xlint:cantFindType] [ERROR] error can't determine superclass of missing type org.springframework.aop.interceptor.AsyncExecutionAspectSupport [ERROR] when batch building BuildConfig[null] #Files=3 AopXmls=#0 [ERROR] [Xlint:cantFindType] [ERROR] -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[lievendoclo]

Then we should take a look at fixing the archetype.

[bravegag]

Agreed, this would to start by troubleshooting the configuration of the generated code btw I tried generating the project using Valkyrie 1.1 and get the same result.

btw one useful workaround not to get blocked on this is to make my project be a Maven submodule of Valkyrie samples and do the development there. Then it is possible to temporarily circumvent the issues with the standalone application Maven settings and archetype issue.

[lievendoclo]

Is this still an issue or are we going to go for a gradle-based solution?

[cmadsen]

I have not done anything to fix it yet. I'm guessing it is just a matter of correcting/upgrading some of the plugin version numbers.