Re: Maven archtype project creation Webobjects 5.3.3 + Wonder support

From: Lachlan Deck (lachlan.dec..mail.com)
Date: Tue Feb 10 2009 - 22:26:48 EST

  • Next message: David Holt: "EntityModeler Backing Map error"

    On 11/02/2009, at 1:42 PM, Mr. G Brown wrote:

    > On Feb 10, 2009, at 3:04 AM, Lachlan Deck wrote:
    >
    >> Hi Greg,
    >>
    >> the problem with your pom is twofold[*]:
    >> a) wonder.common specified as the groupId for ERExtensions rather
    >> than wonder.core. As mentioned, this is a problem with the template
    >> - you just need to fix it after you've created the project.
    >>
    >> b) you'll need to use a dependencyManagement section to ensure the
    >> woversion you want etc is always used during dependencies lookup
    >> (i.e., stuff you depend on also depends on WO)
    >
    > Some things are working now, somethings are broken.
    >
    > The wo archetype project generator takes parameters but doesn't do
    > much with them. I build wonder with a profile wo53, and then a new
    > maven /wolips project
    > WebObjectsVersion - value 5.3.3 is used, there is a woversion
    > property in the pom.
    > wonderversion - 5.0.0-snapshot This isn't in the wiki (me fix after
    > this discussion clears) It doesn't show up in the pom (at least for
    > 5.3.3) and is not used. Shouldn't it set the wonderversion property
    > into the pom?

    As I mentioned the default template for the project is pretty bare-
    bones. I'll submit a patch to Henrique sometime soon and / or we'll
    come up with something better than what's there currently.

    The pom I attached is a suggested better place to start as the result
    of creating a new project - 'cause it works:-) and is closer to what
    you should be doing anyway :-)

    I'm planning on (but lots of things are going on atm) updating the
    wiki, chatting with Henrique etc soon.

    > WonderSupport - This seems to 1.) add a a
    > wonder.common:erextensions.jar dependancy but it should add a
    > <dependency>
    > <groupId>wonder.core</groupId>
    > <artifactId>ERExtensions</artifactId>
    > <version>${wonderversion}</version>
    > <classifier>wo53</classifier>
    > </dependency>
    > 2.) it also adds a import er.extensions.ERXApplication; // << wrong
    > as there is no ERXApplication there! it moved!

    Sure. Another problem with the template. This just needs a check in
    the template for whether or not we're >= 5.0 for Wonder.

    > public class Application extends ERXApplication { // there is a
    > er.extensions.appserver.ERXApplication, is that the correct one?

    Yep.

    > TrueWarSupport - not even looking at that yet.

    No worries. Only needed if you're planning on deploying to servlet
    containers.

    > DependencyManagement : I just have one pom now, that is for child
    > poms, correct? Should the archetype project generator do something
    > with that?

    http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html

    This section should, I think, get created with the pom. It'll ensure
    that the versions specified in that section are what versions are used
    throughout (including for dependencies of dependencies...)

    > It looks like Wonder has been re-arranged, and the eclipse tool set
    > create projects that refer to the old wonder arrangements.

    This is nothing do to with Eclipse. This is the woproject-maven plugin
    for maven which produces the project. The only thing that you need to
    do is right click on src/main/java and choose Source > Organize Imports.

    > Now I get:
    > No ERX_MARKER field in NSMutableArray found.
    > This means your class path is incorrect. Adjust it so that
    > ERExtensions come before JavaFoundation

    Adjust dependency management so that ERExtensions is first.

    > No matter how I arrange the libraries, I get the above message.
    > However, from the terminal [INFO] BUILD SUCCESSFUL.
    >
    > I think I need newer software.

    I'm using Eclipse 3.4.1, WOLips nightlies, m2eclipse. Maven 2.0.9
    should be minimum.

    with regards,

    --
    

    Lachlan Deck



    This archive was generated by hypermail 2.0.0 : Tue Feb 10 2009 - 22:27:36 EST