Hi Olivier,
it does actually help! It works in IDEA now.
But if it can filter the ${timestamp}, it doesn't work anymore for
${buildNumber}:
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:00:16
Thats' weird. And same behavior from the CLI (fortunately, consistent):
[INFO] [buildnumber:create {execution: default}]
[INFO] Change the default 'svn' provider implementation to 'javasvn'.
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Storing buildNumber: null at timestamp: 2009-04-14 14:03:31
It works from the CLI with the regular providerImplemtation (unspecified as it
was before) but still the latest version of the plugin:
[INFO] [buildnumber:create {execution: default}]
[INFO] Checking for local modifications: skipped.
[INFO] Updating project files from SCM: skipped.
[INFO] Executing: /bin/sh -c cd /Users/nodje/Documents/project/company/project
&& svn --non-interactive info
[INFO] Working directory: /Users/nodje/Documents/project/allence/alpha2
[INFO] Storing buildNumber: 3077 at timestamp: 2009-04-14 14:05:13
>From the trace differences, it looks like the javasvn providerImplementation
>doesn't actually call the svn info to get the revision number.
Seems to be a problem on the buildnumber-maven-plugin side. Are you also
working on it by the way?
Because the [2] link didn't exist yesterday !? :)
cheers
-nodje
You can try the current trunk of the buildnumber plugin which support
using svnjava [1].
How to use it it's documented here [2]
HTH,
--
Olivier
[1] http://code.google.com/p/maven-scm-provider-svnjava/
[2] http://mojo.codehaus.org/buildnumber-maven-plugin/using-svnjava.html
2009/4/13 Stephen Connolly <[email protected]>:
> 2009/4/13 nodje <[email protected]>
>
>>
>> I'm not sure of what you mean exactly Stephen.
>> This is how I interpreted it:
>>
>> <profile>
>> <id>build-jetty</id>
>> <build>
>> <defaultGoal>validate</defaultGoal>
>> <plugins>
>> <plugin>
>> <groupId>org.codehaus.mojo</groupId>
>> <artifactId>buildnumber-maven-plugin</artifactId>
>> <executions>
>> <execution>
>> <phase>validate</phase>
>> <goals>
>> <goal>create</goal>
>> </goals>
>> </execution>
>> </executions>
>> <configuration>
>> <doCheck>false</doCheck>
>> <doUpdate>false</doUpdate>
>> </configuration>
>> </plugin>
>> <plugin>
>> <groupId>org.mortbay.jetty</groupId>
>> <artifactId>maven-jetty-plugin</artifactId>
>> <version>6.1.16</version>
>> <executions>
>> <execution>
>> <phase>validate</phase>
>> <goals>
>> <goal>run-exploded</goal>
>> </goals>
>> </execution>
>> </executions>
>> </plugin>
>>
>> And it works pretty fine, even though the builnumber:create goal get
>> executed 4 times in the process.
>> This is definitely an option even though it's not very straightforward.
>>
>> Can someone confirm this is the only solution today, since, as I
>> understand, it's not currently possible to make plugin goals depend on each
>> others. Is that right?
>>
>> The major problem for integration in our process now is that Intellij IDEA
>> doesn't seem to support the plugin. It would say "your SVN client is too
>> old". It's probably the IDEA SVN client implementation that returns a
>> "fancy" 'svn info' response.
>
>
> That's because IntelliJ uses SVNKIT and not the SVN CLI.
>
> have you updated your SVN CLI to 1.6??? (or TortoiseSVN)
>
> Seemingly once SVNKIT 1.3 is released, providing they have not changed the
> API of SVNKIT you could just replace the SVNKIT jar in intellij with the 1.3
> version and you'd be fine.
>
> -Stephen
>
>
>>
>> I keep the plugin for our PROD and TEST profiles that are used only for
>> creating WAR to deploy, and that's perfect here. People should be able to
>> learn to do that outside of IDEA.
>>
>> thanks
>> -nodje
>>
>>
>> because executing mojos directly never invokes the lifecycle.
>>
>> you could have a profile with a default goal of validate and with the
>> plugins you want bound to the validate phase of the lifecycle
>>
>> then
>>
>> mvn -Pmagic
>>
>> would do it for you (if your profile id is magic)
>>
>> Sent from my [rhymes with myPod] ;-)
>>
>> On 10 Apr 2009, at 10:01, nodje <[email protected]> wrote:
>>
>> >
>> > thanks.
>> > It works when you chain the goals manually:
>> >
>> > mvn buildnumber:create jetty:run-exploded does work.
>> >
>> > Now, I can already hear the developers complaining.
>> > Is there a way to tell jetty plugin to execute buildnumber:create?
>> >
>> > I could add an <execution> section to link the create goal to any
>> > jetty invocation, but then it would call the builnumber:create
>> > twice, wouldn't it?
>> >
>> > I can't really understand why
>> > mvn buildnumber:create jetty:run-exploded
>> > is different from a regular
>> > mvn jetty:run-exploded
>> > since buildnumber:create is link to the very first lifecycle goal
>> > validate anyway.
>> >
>> > cheers
>> >
>> >
>> > On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran <[email protected]> wrote:
>> >
>> >> I may be wrong, but i think finalName is constructed early in the
>> >> cycle and therefor buildNumber var is not propagate properly, does
>> >> maven 2.1.0 help?
>> >
>> >
>> > No, the problem is that since Nodje is executing jetty plugin directly
>> > rather than a lifecycle phase, the buildNumber obviously doesn't get
>> > evaluated. Would it work if you execute both of them explicitly,
>> > i.e. mvn
>> > buildnumber:create jetty:run-exploded?
>> >
>> > Kalle
>> >
>> >
>> >>
>> >> On Wed, Apr 8, 2009 at 11:40 PM, nodje <[email protected]> wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I've just setup config with buildnumber-maven-plugin using
>> >>>
>> >>>
>> >> <finalName>${project.artifactId}-${project.version}-r$
>> >> {buildNumber}</finalName>
>> >>>
>> >>> as name for my artifacts.
>> >>>
>> >>> But now when I try to run 'mvn jetty:run-exploded', I get a
>> >>> message from
>> >> Jetty stating it can't find
>> >>> appname-1.1-rnull.
>> >>>
>> >>> So it seems Jetty isn't aware of the ${buildNumber} variable when it
>> >> check the name of the war it has to deploy.
>> >>>
>> >>> Did anyone successfully use both plugin together?
>> >>>
>> >>> cheers
>> >>> -nodje
>> >>> --
>> >>> View this message in context:
>> >>
>> http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2609616.html
>> >>> Sent from the maven users mailing list archive at Nabble.com.
>> >>>
>> >>>
>> >>> ---
>> >>> ------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: [email protected]
>> >>> For additional commands, e-mail: [email protected]
>> >>>
>> >>>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: [email protected]
>> >> For additional commands, e-mail: [email protected]
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2615332.html
>> > Sent from the maven users mailing list archive at Nabble.com.
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [email protected]
>> > For additional commands, e-mail: [email protected]
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2626800.html
>> Sent from the maven users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2631273.html
Sent from the maven users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
