+1 to using Genesis 2.0 as this lets us use Nexus to deploy artifacts (this was discussed in another thread awhile back.)
-1 to requiring Maven 2.2.1, as Genesis 2.0 only requires 2.0.10 or later - https://svn.apache.org/repos/asf/geronimo/genesis/tags/genesis-2.0/genesis-default-flava/pom.xml - ... <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-enforcer-plugin</artifactId> <executions> <execution> <phase>validate</phase> <goals> <goal>enforce</goal> </goals> <configuration> <rules> <requireMavenVersion> <version>[2.0.10,)</version> </requireMavenVersion> </rules> </configuration> </execution> </executions> </plugin> ... -Donald On 3/11/10 10:42 AM, Forrest Xia wrote: > To use apache-release profile and maven release plugin to do release, I > guess :-) > > Forrest > > On Thu, Mar 11, 2010 at 9:46 PM, Kevan Miller <[email protected] > <mailto:[email protected]>> wrote: > > > On Mar 11, 2010, at 3:54 AM, Rex Wang wrote: > > > Hi Jarek, > > Could you help update the scripts? > > Read more of my mail... ;-) So, I assume *why* is because of the > move to Genesis 2.0. So, brings up a new question... ;-) Why update > G 2.1 to use Genesis 2.0? > > --kevan > >
