Custom plugin to expose parameter exposed during build? Possible?

Hi Brian

Build numbers can be reported from build scripts by service messages.
Do you really need a plugin?

Michael

Wow, great feature I had no knowledge of, thanks.  Will this work within the Maven Runner though?

yes, this is universal approach to interact with externals tools.

Thanks Michael that was exactly what I needed.  I added the following to my Maven pom.xml and it works for continuous and release builds:

  <build>
  ...
    <plugins>
    ...
      <plugin>
        <artifactId>maven-antrun-plugin</artifactId>
        <version>1.6</version>
        <executions>
          <execution>
            <id>echo-buildnumber</id>
            <goals>
              <goal>run</goal>
            </goals>
            <phase>validate</phase>
            <configuration>
              <target>
                <!-- The main purpose here is to override what TeamCity thinks is the build 
                     number during a release. It will be run twice, but the second (and final) 
                     time should be during the release build and the version will be the version 
                     of the released artifact.
                     NOTE: This also has the effect of overriding the build pattern of the 
                     TeamCity build configuration, whether it is set to %mave.project.version% 
                     or not.
                -->
                <echo message="##teamcity[buildNumber '${project.version}']"/>
              </target>
            </configuration>
          </execution>
        </executions>
      </plugin>
    </plugins>
  </build>