On 3/11/07, Ted Husted <[EMAIL PROTECTED]> wrote:
> Unfortunately, until we start using Maven to do releases, I don't know what that means. What else would we need to do?
Some variation on "mvn release:prepare" and "mvn release:perform" with -P whatever-profiles-struts2-needs and probably a few more things that won't be discovered until someone tries it. For example, a "dry run" starts off this way: $ mvn release:prepare -DdryRun=true [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Struts 2 [INFO] Struts 2 Core [INFO] Searching repository for plugin with prefix: 'release'. [INFO] ------------------------------------------------------------------------- --- [INFO] Building Struts 2 [INFO] task-segment: [release:prepare] (aggregator-style) [INFO] ------------------------------------------------------------------------- --- [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Executing: svn --non-interactive status [INFO] Working directory: e:\svn\struts\STRUTS_2_0_X [INFO] Checking dependencies and plugins for snapshots ... There are still some remaining snapshot dependencies.: Do you want to resolve them now? (yes/no) no: : So, it will stop the release if it finds any snapshot dependencies. It also checks for local changes and won't proceed if you haven't checked in.
Why can't they all be released together?
They probably can, it's just a matter of someone moving them and making sure the whole thing builds again. My primary goal is "no snapshot dependencies" in released poms. (The struts-master pom doesn't "belong" to either Struts 1 or Struts 2. Eliminating it would mean duplicating the mailing lists, list of committers, etc., in each of the parent poms, but that's also doable.) -- Wendy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
