After an upgrade to 3.0.1 (well first to 3.0 then 3.0.1) all our maven release goals fail, however deploys are fine. Here is the log report:
: Building xrite-commons
: task-segment: (aggregator-style)
: Verifying that there are no local modifications...
: Executing: svn --non-interactive status
: Working directory: c:\BuildAgent\work\23044d751bcc9843
: Checking dependencies and plugins for snapshots ...
: Transforming 'xrite-commons'...
: Not generating release POMs
: Executing goals 'clean verify'...
: Executing: mvn clean verify --no-plugin-updates --batch-mode -P default,default
: 'mvn' is not recognized as an internal or external command,
: operable program or batch file.
: BUILD ERROR
: Maven execution failed, exit code: '1'
: For more information, run Maven with the -e switch
: Total time: 2 minutes 18 seconds
: Finished at: Fri Jan 11 16:50:01 EST 2008
: Final Memory: 11M/26M
: Process exit code: 1
: Number of processed tests: 792
: Publishing artifacts (<1s)
: Will process paths:
: Publishing artifacts 'teamcity-info.xml' to root artifacts directory
: Artifacts path teamcity-info.xml not found
: Build finished
This doesn't make any sense to me, why would mvn not be found? I see this upgrade pushed out maven 2.0.8. And it finds maven just fine for deploys, etc. ???