Re: Maven?

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Mon Aug 21 2006 - 11:41:23 EDT

  • Next message: Mike Schrag: "Re: WWDC 2006"

    Yes, you have to install maven and invoke the install goal in the
    directory of a given directory. That will produce a jar that could be
    downloaded and installed from within maven.

    I'll could provide more details if you're willed to build and host
    the plugins.
    Uli
    Am 21.08.2006 um 12:54 schrieb Mike Schrag:

    > So these build independently of the main wolips build?
    >
    > ms
    >
    > On Aug 19, 2006, at 12:51 PM, Ulrich Köster wrote:
    >
    >> Mike, could we set up a build server/repository for the maven
    >> plugins?
    >>
    >> Uli
    >> Am 19.08.2006 um 18:40 schrieb Ulrich Köster:
    >>
    >>> http://www.objectstyle.org/confluence/display/WOL/Maven+Plugins
    >>>
    >>> Am 19.08.2006 um 08:03 schrieb Ulrich Köster:
    >>>
    >>>> Yes, the wiki part is missing. We're using it for quite a while
    >>>> now. Anyway it's 1.0.2 only.
    >>>>
    >>>> Uli
    >>>> Am 19.08.2006 um 02:18 schrieb Mike Schrag:
    >>>>
    >>>>> This is all Ulrich's work. Here's an email he sent to me when
    >>>>> I asked him some info about it (Assuming he's OK with me
    >>>>> forwarding this):
    >>>>>
    >>>>> "Instead of wrting a build.xml you have to define some
    >>>>> properties. Building, deploying and tagging is the same for a
    >>>>> woa and a whatever project.
    >>>>>
    >>>>> From a project.xml:
    >>>>> <build>
    >>>>>
    >>>>> <sourceDirectory>${basedir}/src/java</sourceDirectory>
    >>>>>
    >>>>> <resources>
    >>>>>
    >>>>> <resource>
    >>>>>
    >>>>> <directory>${basedir}/src/java</directory>
    >>>>>
    >>>>> <includes>
    >>>>>
    >>>>> <include>**/*.properties</include>
    >>>>>
    >>>>> <include>**/*.wo/**</include>
    >>>>>
    >>>>> <include>**/*.api</include>
    >>>>>
    >>>>> </includes>
    >>>>>
    >>>>> <excludes>
    >>>>>
    >>>>> <exclude>**/build*.properties</exclude>
    >>>>>
    >>>>> <exclude>project.properties</exclude>
    >>>>>
    >>>>> <exclude>target/**</exclude>
    >>>>>
    >>>>> </excludes>
    >>>>>
    >>>>> <filtering>false</filtering>
    >>>>>
    >>>>> </resource>
    >>>>>
    >>>>> <resource>
    >>>>>
    >>>>> <directory>${basedir}/Resources</directory>
    >>>>>
    >>>>> <targetPath>Resources</targetPath>
    >>>>>
    >>>>> </resource>
    >>>>>
    >>>>> </resources>
    >>>>>
    >>>>> </build>
    >>>>>
    >>>>> All you have to call is 'maven jar' and you'll get a framework
    >>>>> as jar. No difference between building a 'standard' jar and a
    >>>>> 'wo' jar. Maven manages all dependecies. The woa includes all
    >>>>> dependencies. Just build it, scp it to server, unpack it and
    >>>>> you're a ready. I'll add some docs to the wiki when I find
    >>>>> the time. "
    >>>>>
    >>>>> ms
    >>>>>
    >>>>> On Aug 18, 2006, at 7:02 PM, RedBugz Software wrote:
    >>>>>
    >>>>>> I just noticed that the latest WOLips builds make mention of
    >>>>>> Maven. I can't find anything on the wiki about it. Any
    >>>>>> interesting things happening to allow building WO apps in
    >>>>>> Maven, or just borrowing some Maven code? I'd like to know more.
    >>>>>>
    >>>>>> thanks,
    >>>>>> Logan
    >>>>>
    >>>>
    >>>
    >>
    >



    This archive was generated by hypermail 2.0.0 : Mon Aug 21 2006 - 11:41:26 EDT