What I've found works for this is to have a profile named something like
"all-subprojects" that really includes all these non-released subprojects and
then configure the deploy plugin in each of them with <skip>true</skip> so they
don't actually get released. Then you can include the all-subprojects profile
in the release plugin arguments. (If you do this you should be able to do your
${arguments} trick in the openejb top level pom and use the normal apache 10
pom as well)
thanks
david jencks
On Sep 30, 2011, at 12:36 PM, David Blevins wrote:
> Seems we have some oddness in the source.
>
> <openejb.version>4.0.0-beta-1-SNAPSHOT</openejb.version>
> ./examples/mbean-auto-registration/pom.xml
>
> <openejb.version>4.0.0-beta-1-SNAPSHOT</openejb.version>
> ./examples/dynamic-datasource-routing/pom.xml
>
> <openejb.version>4.0.0-beta-1-SNAPSHOT</openejb.version>
> ./examples/bean-validation-design-by-contract/pom.xml
>
> <openejb.version>4.0.0-beta-1-SNAPSHOT</openejb.version>
> ./examples/datasource-ciphered-password/pom.xml
>
> <openejb.version>4.0.0-beta-1-SNAPSHOT</openejb.version>
> ./examples/webapps/resources-declared-in-webapp/pom.xml
>
> <version>1.0-SNAPSHOT</version>
> <version>4.0.0-beta-1-SNAPSHOT</version>
> <version>6.0-2-SNAPSHOT</version>
> ./examples/webapps/applet/pom.xml
>
> <openejb.version>4.0.0-beta-1-SNAPSHOT</openejb.version>
> ./examples/webapps/rest-example/pom.xml
>
>
> Seems these examples don't run with the build so they didn't get updated by
> the maven release plugin.
>
> I'm going to reroll just to be on the safe side.
>
>
> -David
>
