Test archetypes in Eclipse before release

[timdonovanuk]

This is a feature request to please ensure archetype compatibility with Eclipse + AEM plugin before release. The archetype is supposed to be a springboard for developers (particularly new ones), but it never seems to be a smooth process. Every release seems brings new problems, and requires lots of pom hacking and Googling to ensure an error free project.

As an example, the latest archetype (23):

• hangs windows Eclipse during AEM project creation (probably related to archetype fails to run correctly when -DoptionDispatcherConfig=cloud is used on windows #329)
• requires manually changing filevault-package-maven-plugin to a later version ([21 and above] FileNotFoundException when importing code to eclipse #358)
• has jackrabbit-filter: Node is not contained in any of the filter rules errors
• has Project build error: Unknown packaging: content-packagepom.xml errors

I know end to end testing of everything is not possible, but it would be nice if the default path of Eclipse -> New AEM project always worked without half a dozen errors and warnings.

Thank you!

[timdonovanuk]

And a picture being worth a thousand words, this is what a new developer will see after using the latest archetype in Eclipse to create a fresh project:

[timdonovanuk]

Oh and one other thing...the project should actually build without errors too! If you were unfortunate enough to specify frontendModule=general you'll find your shiney new project doesn't actually mvn clean install:

[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project org.foo:foo:0.0.1-SNAPSHOT (C:\eclipse-workspace-2\foo\pom.xml) has 1 error
[ERROR] Child module C:\eclipse-workspace-2\foo\ui.frontend of C:\eclipse-workspace-2\foo\pom.xml does not exist

and requires commenting out the frontend modules in the root pom.xml.

[timdonovanuk]

And if you tick the publish to server box, you'll get yet another error...

Publishing failed
Failed installing bundle : Manifest does not have a Bundle-SymbolicName
Manifest does not have a Bundle-SymbolicName
Failed publishing path=/conf/foo/settings/wcm/policies/rep:policy, result=JcrResult[ success:false, exception: org.apache.sling.ide.transport.RepositoryException - javax.jcr.nodetype.ConstraintViolationException: {internal}policy is protected.]

[timdonovanuk]

And if you try building from the command line you get....

[INFO] Scanning for projects...
[ERROR] [ERROR] Project 'org.foo:foo.ui.frontend:0.0.1-SNAPSHOT' is duplicated in the reactor @
[ERROR] Project 'org.foo:foo.ui.frontend:0.0.1-SNAPSHOT' is duplicated in the reactor -> [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/DuplicateProjectException

[msagolj]

• verified that the project builds without errors
• verified that the project does not throw anymore filevault-package-maven-plugin warnings
• verified that the generated project can be imported in eclipse (there are still some eclipse specific warnings that require changes in eclipse settings but are unrelated to the archetype project itself )
• Due to the changed groupId the released archetype 24 will not be found/selectable in the eclipse AEM plugin tool. This requires a new release of the AEM plugin tool

[msagolj]

Corresponding issue in developer tools: adobe/aem-eclipse-developer-tools#91

[gabrielwalt]

Closing this issue as it's more of a task that impacts the Eclipse plugin than the Archetype