Re: Best Practices for Managing the Classpath?

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Fri Nov 03 2006 - 02:44:26 EST

  • Next message: Ulrich Köster: "Re: woproject-maven-plugin Next Steps"

    Moin Chuck,

    on tuesday we deployed our first woapplication build with maven. It's
    a huge improvement for the one who made the release and the one who
    deployed it.

    The woapplication has all dependencies included. No need to touch the
    *Classpath.txt files. Very sweet. I'll add some lines to the wiki.

    uli
    Am 01.11.2006 um 00:32 schrieb Chuck Hill:

    > Hi,
    >
    > I am updating some rather old processes that I have been using with
    > WOLips for a while now. I suspect that some of them were born of
    > bugs long since dead. I am trying to figure out the best way to
    > manage generating the runtime (command line) classpath files. Up
    > to now, I have set up each project to install into /Library/
    > Frameworks when it builds. Other projects include the installed
    > projects via the standard WOFrameworks Library. This works, but as
    > I bundle my frameworks into my applications, I would like to avoid
    > this install step.
    >
    > I tried not installing and adding them to the WOFrameworks Library
    > and instead just referencing them as Required Projects in the Java
    > Build path. This works fine for building and launching. I can see
    > that WOLips has included references to these frameworks:
    >
    > $ cat woproject/ant.frameworks.wo.wolocalroot
    > Library/Frameworks/FrontBasePlugIn.framework
    > Library/Java/Extensions/OpenBaseJDBC.jar
    > Library/Java/Extensions/frontbasejdbc.jar
    > Library/Frameworks/RequiredFramework.framework
    >
    > However, when the project is built, FrontBasePlugIn.framework
    > (installed in /Library/Frameworks) is embedded and added to the
    > classpath but RequiredFramework.framework (which only exists in the
    > workspace) is neither embedded nor added to the classpath.
    >
    > I also tried including the jar for RequiredFramework.framework in
    > the Libraries. Again, WOLips sees this:
    >
    > $ cat woproject/ant.frameworks.wo.wolocalroot
    > Library/Frameworks/FrontBasePlugIn.framework
    > Library/Java/Extensions/OpenBaseJDBC.jar
    > Library/Java/Extensions/frontbasejdbc.jar
    > RequiredFramework/ RequiredFramework.framework
    >
    > but neither embeds it nor adds it to classpath.
    >
    > Is there any way to handle this other than installing the
    > frameworks and referencing the installed versions?
    >
    > Do you consider what happens for Required Projects to be a bug?
    > Should embedding these be handled by WOProject?
    >
    > Some probably related bugs:
    >
    > http://objectstyle.org/jira/browse/WOL-124
    > http://objectstyle.org/jira/browse/WOL-156
    > http://objectstyle.org/jira/browse/WOL-289
    >
    >
    > Thanks for any thoughts on this,
    >
    > Chuck
    >
    > --
    >
    > Practical WebObjects - for developers who want to increase their
    > overall knowledge of WebObjects or who are trying to solve specific
    > problems.
    > http://www.global-village.net/products/practical_webobjects
    >
    >
    >
    >
    >



    This archive was generated by hypermail 2.0.0 : Fri Nov 03 2006 - 02:44:34 EST