cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <>
Subject Re: M3 - will try to do it now
Date Tue, 13 Sep 2011 06:08:59 GMT
Yes, the docbook is a special case - it is not yet ready for inclusion, so it is not linked
to the main build. The bigger problem is all other modules that are conditionally added via
profiles e.g. when building on a certain platform. E.g.:



On Sep 13, 2011, at 1:02 AM, Richard Frovarp wrote:

> On 09/12/2011 03:26 PM, Andrus Adamchik wrote:
>> On Sep 12, 2011, at 10:42 PM, Andrus Adamchik wrote:
>>> I am going to document these steps on the site once we finish the release end
to end.
>> Ok, there's always a catch... after mvn release:whatever, we have a bunch of POMs
still not updated (excluded from the default release profile) :
>> $ find . -name pom.xml |xargs grep SNAPSHOT
>> ./assembly/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./docs/docbook/cayenne-guide/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./docs/docbook/main/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./docs/docbook/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-generic/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-generic-ext/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-mac/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-mac-ext/pom.xml:		<version>3.1-SNAPSHOT</version>
>> ./modeler/cayenne-modeler-win/pom.xml:		<version>3.1-SNAPSHOT</version>
>> So will still have to change those with Perl until we figure out a better way. Will
continue on this hopefully tomorrow.
>> Andrus
> They're being excluded because they don't have a chain from ./pom.xml to them. For instance,
docs/pom.xml just references /docs/doc and not docs/docbook under the module declaration.
> I don't know if adding them to the module declarations has a side effect you don't want
or not.

View raw message