Re: Assemblies progress [was: (CAY-719) Finalize Maven assembly scripts for the upcoming 3.0 milestone releases]

From: Andrus Adamchik (andru..bjectstyle.org)
Date: Mon Dec 25 2006 - 07:16:19 EST

  • Next message: Andrus Adamchik (JIRA): "[JIRA] Created: (CAY-726) SQLTemplate parsing bug when macros appear at the end of line"

    In between the holiday parties I checked in some code to build user-
    friendly aggregated artifacts [1] using a custom aggregator plugin
    [2]. After running "mvn install" from the root of the source tree,
    the following new artifacts will be installed:

    org.apache.cayenne:cayenne-agent:3.0-SNAPSHOT
    org.apache.cayenne:cayenne-server:3.0-SNAPSHOT
    org.apache.cayenne:cayenne-client:3.0-SNAPSHOT

    Andrus

    [1] http://svn.apache.org/repos/asf/incubator/cayenne/main/trunk/
    framework/
    [2] http://svn.apache.org/repos/asf/incubator/cayenne/main/trunk/
    other/maven-cayenne-build-plugin/

    On Dec 18, 2006, at 1:56 PM, Andrus Adamchik wrote:

    > Just checked in assembly code that exports Wiki docs using
    > Confluence Maven plugin developed by Bill and Cris:
    >
    > http://cwiki.apache.org/CAY/building-cayenne.html
    >
    >
    > One important issue still remains unresolved - how to build
    > "aggregated" jar artifacts. Originally I thought those should be a
    > part of the release assembly. But to keep Cayenne friendly to the
    > Maven users, ideally we should make aggregated artifacts available
    > via Maven as well. So here is the new artifacts that I have in mind:
    >
    > 1. cayenne-server.jar: aggregation of cayenne-jdk1.4, cayenne-
    > jdk1.5 and cayenne-jpa
    > 2. cayenne-client.jar: filtered aggregation of cayenne-jdk1.4 and
    > cayenne-jdk1.5
    >
    > [As an aide note, I am envisioning "cayenne-server-deps.jar".
    > Mapping to jars from the previous release would look like this (a)
    > cayenne.jar becomes cayenne-server-deps.jar; (b) cayenne-nodeps.jar
    > becomes cayenne-server.jar. In other words "nodeps" will be
    > implied, while "deps" will be explicit. Anyways "*-deps.jar"
    > doesn't have to be a maven artifact, just a part of the assembly,
    > so we won't discuss it here.]
    >
    > Back to 1. and 2. As it often happens with Maven, after spending
    > lots of time on it, I realized that current Maven facilities
    > (namely dependency and assembly plugins) are completely inadequate
    > for building aggregated artifacts. Looks like we need to write a
    > specialized plugin. I'll keep working on that...
    >
    > Did I mention before what I think of Maven as a productivity
    > tool ? :-)
    >
    > Andrus
    >
    >
    >
    >
    > On Dec 11, 2006, at 5:11 PM, Andrus Adamchik (JIRA) wrote:
    >> Finalize Maven assembly scripts for the upcoming 3.0 milestone
    >> releases
    >> ---------------------------------------------------------------------
    >> --
    >>
    >> Key: CAY-719
    >> URL: http://issues.apache.org/cayenne/browse/CAY-719
    >> Project: Cayenne
    >> Type: Task
    >>
    >> Components: Cayenne Core Library
    >> Versions: 3.0
    >> Reporter: Andrus Adamchik
    >> Assigned to: Andrus Adamchik
    >> Fix For: 3.0
    >>
    >>
    >> We need maven to be able to produce Cayenne distro similar to what
    >> 2.0 ant script does. This way we'll be able to make releases once
    >> Cayenne ASF status is resolved. And of course it should make more
    >> usable nightly builds.
    >>
    >>
    >>
    >> --
    >> This message is automatically generated by JIRA.
    >> -
    >> If you think it was sent incorrectly contact one of the
    >> administrators:
    >> http://issues.apache.org/cayenne/secure/Administrators.jspa
    >> -
    >> For more information on JIRA, see:
    >> http://www.atlassian.com/software/jira
    >>
    >>
    >
    >



    This archive was generated by hypermail 2.0.0 : Mon Dec 25 2006 - 07:16:56 EST