@Ramsey,
I don't want to shock you but the documentation is out of date!
At one time one could create maven projects using eclipse, but that stopped working. The way I now initialize a maven project is using the command line. That always seems to work. Perhaps I can go over the documentation but it will be in 4 to 6 weeks.
@Henrique,
While you are in there working on the archetypes, I do have a suggestion.
If you look at the pom.xml for wonder it contains all kinds of good reusable information. It has the plug-ins, versions, etc. all needed to create the wonder project. But this same information is also needed to create any wonder/WebObjects project. So we see there is a highly reusable part mixed in with a very specific part in the wonder pom.xml. So why not split the pom.xml into a reusable generic WO parent pom.xml and the specific parts to build the wonder project?
I have been doing this and it seems to work well. I use a utility which is described here:
The downside is that the newly created/initialized project needs to have its pom.xml edited as outlined in the github project above. That utility can create the generic reusable parent pom.xml for I think any version of wonder. If the maven archetypes created the initial pom.xml that would work with this or a generic parent pom.xml then people would be using the correct version of plug-ins that would match the same version of plug-ins as used to create wonder.
I think it would be a good move to someday soon re-factor the wonder pom.xml into a highly reusable parent pom.xml and a more specific part to build wonder. This would mean maven users would get all your work on updating the generic parent pom.xml for free! Think of your wonderful karma!
<?xml version="1.0" encoding="UTF-8"?>
<!--
This parent pom was auto generated by splitting the main pom into parent/child poms.
-->
<modelVersion>4.0.0</modelVersion>
<groupId>wonder</groupId>
<artifactId>generic-woparent</artifactId>
<version>5.8.2</version>
<packaging>pom</packaging>
<name>Wonder generic woparent</name>
<description>
Includes the generic woparent pom for all Wonder/WebObjects projects. Has repositories needed, dependency
management, etc. Override in your project's pom when necessary items like distributionManagement.
Sections from the wonder master pom are passed through to create the parent pom. Also, a
wonder.version parameter is created, its value based off the wonder master pom.
</description>
<properties>
<!--make property skip.apple.frameworks false to include apple jars-->
<wonder.version>5.8.2</wonder.version>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
<project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
<webobjects.version>5.4.3</webobjects.version>
</properties>
<build>
…..
These auto generated generic-woparent poms could be inserted into the
maven.wocommunity.com repository for all past versions of wonder, which would make past wonder versions work with a new pom generated by a new maven wonder archetype. But who would use an old version of wonder?