- Build from the code
- Install the archetype in your repository
mvn clean install - Create a project using blazeds-spring archetype from the local archetype repository
mvn archetype:generate -DartifactId=<your artifactId> -DarchetypeCatalog=local
- OR Create a project from the remote repository
mvn archetype:generate -DartifactId=<your artifactId> -DarchetypeCatalog=http://maven-blazeds-spring-archetype.googlecode.com/svn/maven2/ - Initial setup
mvn clean install-DtemplateURI=folder:html-template The reason we must have -DtemplateURI when doing mvn install at master-pom level is the default templateURI is folder:../html-template which is relative to the app-flex folder, while at master-pom level, the default value is no longer valid
- Import project into Eclipse
- Your Eclipse must have m2eclipse plugin and WTP
- Using File->Import->Existing project into workspace
- After importing, some of the errors may occur:
- JRE version. Please change it accordingly in project properties
- m2eclipse is not updating the dependencies, right click on the project, and choose Maven2->Update Dependencies
- Create Tomcat container to host the application
- You must have Apache Tomcat installed in your local machine
- Create a new server and add your web project to tomcat. So in Server View, it would be similar to this
- If successful, you must see the whole web application folder in the Apache Tomcat deployment folder (red rectangle), relative to your workspace folder
- Debug application
- You can debug Java code by running tomcat under Debug mode
- Or you can debug Flex Application by running Flex Application in Debug mode
|
Good job, But the archetype needs more work. For starters I could get it working only when version is set to "1.0" and the artifactID is set to "app". Any other values for these 2 fields results in a non working application, which I suspect is due to hard-coding "1.0" and "app" in certain places.