@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: https://github.com/gitgb/splitpom.git 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! From the auto generated generic pom.xml: <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> <!-- 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> <url>http://wiki.objectstyle.org/confluence/display/WONDER/Home</url> <properties> <skip.apple.frameworks xmlns:p="http://maven.apache.org/POM/4.0.0";>false</skip.apple.frameworks> <!--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? G Brown [email protected] On Sep 13, 2015, at 7:26 PM, Henrique Prange <[email protected]> wrote: > Ramsey, > > The last change to WebObjects Maven plugins were back in 2010. Lots of things > changed since then in Maven tooling world. I took the time during the weekend > to make the Maven plugin and the Maven archetypes compatible with the current > features. I still have to make a release and update the docs. In the > meantime, could you try the new archetypes and the new version of the > maven-wolifecycle-plugin? > > You can add a Remote Catalog using the URL below (Eclipse -> Preferences -> > Maven -> Archetypes) to get the new archetypes: > > http://maven.wocommunity.org/service/local/repositories/snapshots/content/archetype-catalog.xml > > After that, you can create a new Maven Project using the Eclipse wizard. > Select the WOCommunity catalog and include snapshot archetypes. Follow the > wizard steps and the new project should be created with no errors. The new > archetypes will configure the maven-wolifecycle-plugin version to > 2.3-SNAPSHOT. > > Let me know if you have any problems. > > Cheers, > > Henrique > >> On 11/09/2015, at 18:19, Ramsey Gurley <[email protected]> wrote: >> >> So I really desperately want to migrate my projects to Maven. I tried back >> in May when I had a chance, and failed. I’m trying again now. I can’t get a >> hello world to compile. I’m starting here >> >> https://wiki.wocommunity.org/display/WOL/Quick+Start >> >> But from step 5 on, nothing works. I installed the m2e plugin on mars, >> imported my hello world, and I get >> >> Plugin execution not covered by lifecycle configuration: >> org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:woapplication >> (execution: default-woapplication, phase: generate-test-resources) >> pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem >> >> and >> >> Plugin execution not covered by lifecycle configuration: >> org.objectstyle.woproject.maven2:maven-wolifecycle-plugin:2.0.17:define-woapplication-resources >> (execution: default-define-woapplication-resources, phase: validate) >> pom.xml /testing line 26 Maven Project Build Lifecycle Mapping Problem >> >> If I simply try to mvn clean package in the project directory, I get >> >> [ERROR] Failed to execute goal on project testing: Could not resolve >> dependencies for project test:testing:woapplication:1.0-SNAPSHOT: The >> following artifacts could not be resolved: >> wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT, >> wonder.core:WOOgnl:jar:wo54:6.1.3-SNAPSHOT, >> wonder.core:ERPrototypes:jar:6.1.3-SNAPSHOT: Failure to find >> wonder.core:ERExtensions:jar:wo54:6.1.3-SNAPSHOT in >> http://maven.wocommunity.org/content/groups/public-snapshots was cached in >> the local repository, resolution will not be reattempted until the update >> interval of wocommunity.snapshots has elapsed or updates are forced -> [Help >> 1] >> >> Can anyone explain why this isn’t working? >> >> Thanks, >> >> Ramsey >> _______________________________________________ >> Do not post admin requests to the list. They will be ignored. >> Webobjects-dev mailing list ([email protected]) >> Help/Unsubscribe/Update your Subscription: >> https://lists.apple.com/mailman/options/webobjects-dev/hprange%40gmail.com >> >> This email sent to [email protected] > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Webobjects-dev mailing list ([email protected]) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/webobjects-dev/gsbrown%40umich.edu > > This email sent to [email protected]
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
