Hi,
Thanks for the reply.
The whole team is not using SVN to version the code. My case, I'm using git.
So every time I run the install goal that builds the whole project, it fails
since I have an SVN repository in the SCM tag. So, what I want is to run the
build number process manually or at least in another goal rather than
install... the site goal doesn't fit too.
Any ideas?
--
Rui
On Thu, Feb 24, 2011 at 6:21 PM, Baptiste MATHUS <m...@batmat.net> wrote:
> Hi,
> Imo, running this goal from the command line is nonsense. This will create
> a
> property that's designed to be typically used inside other parts of the
> pom.
> What are you trying to do?
>
> BTW, if you run this goal from CLI, why don't you just add the next goal to
> be run on the same command line?
> Le 24 févr. 2011 16:23, "Rui Vilão" <rpvi...@gmail.com> a écrit :
> > Hi,
> >
> > I'm using the buildnumber plugin and I want to execute a given antrun
> goal
> > ONLY when I explicitly call that plugin from the console.
> >
> > So, imagine that I execute mvn buildnumber:create and in the pom I do
> > something like:
> >
> > <plugin>
> > <artifactId>maven-antrun-plugin</artifactId>
> > <executions>
> > <phase>WHAT DO I PUT HERE?!</phase>
> > <execution>
> > <goals>
> > <goal>run</goal>
> > </goals>
> > <configuration>
> > <tasks>
> > <echo message="${version}.${buildNumber}" file="build"
> > append="false"/>
> > </tasks>
> > </configuration>
> > </execution>
> > </executions>
> > </plugin>
> >
> > So I don't want to run this in a common life cycle. Install doesn't work
> for
> > me and the immediately after that one is deploy, that doesn't work
> either.
> >
> > Any thoughts?
> >
> > Thanks in advance,
> >
> > Rui
>
