• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO Maven getting started
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO Maven getting started


  • Subject: Re: WO Maven getting started
  • From: G Brown <email@hidden>
  • Date: Wed, 16 Sep 2015 11:41:56 -0400

@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@hidden




On Sep 13, 2015, at 7:26 PM, Henrique Prange <email@hidden> 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
Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >WO Maven getting started (From: Ramsey Gurley <email@hidden>)
 >Re: WO Maven getting started (From: Henrique Prange <email@hidden>)

  • Prev by Date: Joda LocalTime attribute in ERRest
  • Next by Date: Re: WO Maven getting started
  • Previous by thread: Re: WO Maven getting started
  • Next by thread: Re: WO Maven getting started
  • Index(es):
    • Date
    • Thread