Re: Using buildnumber-maven-plugin together with jetty plugin
t;>> 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 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 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
>>>>>>>> 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
>>>>>>>> wrote:
>>>>>>>> >>>
>>>>>>>> >>> Hi,
>>>>>>>> >>>
>>>>>>>> >>> I've just setup config with buildnumber-maven-plugin using
>>>>>>>> >>>
>>>>>>>> >>>
>>>>>>>> >> ${project.artifactId}-${project.version}-r$
>>>>>>>> >> {buildNumber}
>>>>>>>> >>>
>>>>>>>> >>> 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: users-unsubscr...@maven.apache.org
>>>>>>>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>> >>>
>>>>>>>> >>>
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> -
>>>>>>>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>>>>>> >> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>> >>
>>>>>>>> >>
>>>>>>>> >
>>>>>>>> >
>>>>>>>> >
>>>>>>>> > --
>>>>>>>> > 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: users-unsubscr...@maven.apache.org
>>>>>>>> > For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>> >
>>>>>>>>
>>>>>>>> -
>>>>>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> 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: users-unsubscr...@maven.apache.org
>>>>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> -
>>>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> 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: users-unsubscr...@maven.apache.org
>>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>
>>>>>>
>>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2644569.html
>>>> Sent from the maven users mailing list archive at Nabble.com.
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>>
>>
>
> --
> View this message in context:
> http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2722049.html
> Sent from the maven users mailing list archive at Nabble.com.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
>>>
>>>>>> -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 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 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
>>>>>>> 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
>>>>>>> wrote:
>>>>>>> >>>
>>>>>>> >>> Hi,
>>>>>>> >>>
>>>>>>> >>> I've just setup config with buildnumber-maven-plugin using
>>>>>>> >>>
>>>>>>> >>>
>>>>>>> >> ${project.artifactId}-${project.version}-r$
>>>>>>> >> {buildNumber}
>>>>>>> >>>
>>>>>>> >>> 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: users-unsubscr...@maven.apache.org
>>>>>>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>> >>>
>>>>>>> >>>
>>>>>>> >>
>>>>>>> >>
>>>>>>> -
>>>>>>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>>>>> >> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>> >>
>>>>>>> >>
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > --
>>>>>>> > 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: users-unsubscr...@maven.apache.org
>>>>>>> > For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>> >
>>>>>>>
>>>>>>> -
>>>>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> 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: users-unsubscr...@maven.apache.org
>>>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> -
>>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> 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: users-unsubscr...@maven.apache.org
>>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>>
>>>>>
>>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>>>
>>> --
>>> View this message in context:
>>> http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2644569.html
>>> Sent from the maven users mailing list archive at Nabble.com.
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>
>
--
View this message in context:
http://n2.nabble.com/Using-buildnumber-maven-plugin-together-with-jetty-plugin-tp2609616p2722049.html
Sent from the maven users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
e >>>>> >>>>> create >>>>> >>>>> >>>>> >>>>> >>>>> false >>>>> false >>>>> >>>>> >>>>> >>>>> org.mortbay.jetty >>>>> maven-jetty-plugin >>>>> 6.1.16 >>>>> >>>>> >>>>> validate >>>>> >>>>> run-exploded >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 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 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 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, 20
Re: Using buildnumber-maven-plugin together with jetty plugin
false >>>>> >>>>> >>>>> >>>>> org.mortbay.jetty >>>>> maven-jetty-plugin >>>>> 6.1.16 >>>>> >>>>> >>>>> validate >>>>> >>>>> run-exploded >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 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 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 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 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 >>>>> &g
Re: Using buildnumber-maven-plugin together with jetty 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 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 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 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 wrote:
>>>> >>>
>>>> >>> Hi,
>>>> >>>
>>>> >>> I've just setup config with buildnumber-maven-plugin using
>>>> >>>
>>>> >>>
>>>> >> ${project.artifactId}-${project.version}-r$
>>>> >> {buildNumber}
>>>> >>>
>>>> >>> as name for my artifacts.
>>>> >>>
>>>> >>> But now when I try to run 'mvn jetty:run-exploded', I get a
>>>> >>> message from
>>>> >> Jetty stating it c
Re: Using buildnumber-maven-plugin together with jetty plugin
s 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 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 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 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 wrote:
>>>> >>>
>>>> >>> Hi,
>>>> >>>
>>>> >>> I've just setup config with buildnumber-maven-plugin using
>>>> >>>
>>>> >>>
>>>> >> ${project.artifactId}-${project.version}-r$
>>>> >> {buildNumber}
>>>> >>>
>>>> >>> 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:
>>>> >>
>&g
Re: Using buildnumber-maven-plugin together with jetty plugin
gt;> 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 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 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 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 wrote:
>>>> >>>
>>>> >>> Hi,
>>>> >>>
>>>> >>> I've just setup config with buildnumber-maven-plugin using
>>>> >>>
>>>> >>>
>>>> >> ${project.artifactId}-${project.version}-r$
>>>> >> {buildNumber}
>>>> >>>
>>>> >>> 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: users-unsubscr...@maven.apache.org
>>>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>>>> >>>
>>>> >>>
>>>> >>
>>>> >> -
>>>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>> >> For additional commands, e-mail: users-h...@maven.apache.org
>>>> >>
>>>> >>
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > 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: users-unsubscr...@maven.apache.org
>>>> > For additional commands, e-mail: users-h...@maven.apache.org
>>>> >
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> 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: users-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>
>>>>
>>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>
>> --
>> 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: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
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 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 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 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 wrote:
>>> >>>
>>> >>> Hi,
>>> >>>
>>> >>> I've just setup config with buildnumber-maven-plugin using
>>> >>>
>>> >>>
>>> >> ${project.artifactId}-${project.version}-r$
>>> >> {buildNumber}
>>> >>>
>>> >>> 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: users-unsubscr...@maven.apache.org
>>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>>> >>>
>>> >>>
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> >> For additional commands, e-mail: users-h...@maven.apache.org
>>> >>
>>> >>
>>> >
>>> >
>>> >
>>> > --
>>> > 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: users-unsubscr...@maven.apache.org
>>> > For additional commands, e-mail: users-h...@maven.apache.org
>>> >
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>>
>>>
>>> --
>>> 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: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
>
>
> --
> 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: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
alidate 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 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 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 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 wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I've just setup config with buildnumber-maven-plugin using
>> >>>
>> >>>
>> >> ${project.artifactId}-${project.version}-r$
>> >> {buildNumber}
>> >>>
>> >>> 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: users-unsubscr...@maven.apache.org
>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>> >>>
>> >>>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > 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: users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: users-h...@maven.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>
>> --
>> 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: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
Thanks for the info Stephen. I didn't expected a new release of SVN so soon!
SVNKIT's probably gonna solve the problem.
Changing the SVN CLI's not gonna help anyway, and as far as I'm concerned no
Macport available for 1.6 yet! I'll be watching that.
cheers
2009/4/13 nodje
>
> I'm not sure of what you mean exactly Stephen.
> This is how I interpreted it:
>
>
>build-jetty
>
>validate
>
>
>org.codehaus.mojo
>buildnumber-maven-plugin
>
>
>validate
>
>create
>
>
>
>
>false
>false
>
>
>
>org.mortbay.jetty
>maven-jetty-plugin
>6.1.16
>
>
>validate
>
>run-exploded
>
>
>
>
>
> 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 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 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 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 wrote:
> >>>
> >>> Hi,
> >>>
> >>> I've just setup config with buildnumber-maven-plugin using
> >>>
> >>>
> >> ${project.ar
Re: Using buildnumber-maven-plugin together with jetty plugin
ously 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 wrote:
>> >>>
>> >>> Hi,
>> >>>
>> >>> I've just setup config with buildnumber-maven-plugin using
>> >>>
>> >>>
>> >> ${project.artifactId}-${project.version}-r$
>> >> {buildNumber}
>> >>>
>> >>> 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: users-unsubscr...@maven.apache.org
>> >>> For additional commands, e-mail: users-h...@maven.apache.org
>> >>>
>> >>>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> >> For additional commands, e-mail: users-h...@maven.apache.org
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > 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: users-unsubscr...@maven.apache.org
>> > For additional commands, e-mail: users-h...@maven.apache.org
>> >
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>>
>>
>> --
>> 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: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
2009/4/13 nodje
>
> I'm not sure of what you mean exactly Stephen.
> This is how I interpreted it:
>
>
>build-jetty
>
>validate
>
>
>org.codehaus.mojo
>buildnumber-maven-plugin
>
>
>validate
>
>create
>
>
>
>
>false
>false
>
>
>
>org.mortbay.jetty
>maven-jetty-plugin
>6.1.16
>
>
>validate
>
>run-exploded
>
>
>
>
>
> 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 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 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 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 wrote:
> >>>
> >>> Hi,
> >>>
> >>> I've just setup config with buildnumber-maven-plugin using
> >>>
> >>>
> >> ${project.artifactId}-${project.version}-r$
> >> {buildNumber}
> >>>
> >>> as name for my artifacts.
> >>>
> >>> But now when I try to run 'mvn jetty:run-exploded', I get a
> >>> message
Re: Using buildnumber-maven-plugin together with jetty plugin
I'm not sure of what you mean exactly Stephen.
This is how I interpreted it:
build-jetty
validate
org.codehaus.mojo
buildnumber-maven-plugin
validate
create
false
false
org.mortbay.jetty
maven-jetty-plugin
6.1.16
validate
run-exploded
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.
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 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 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 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 wrote:
>>>
>>> Hi,
>>>
>>> I've just setup config with buildnumber-maven-plugin using
>>>
>>>
>> ${project.artifactId}-${project.version}-r$
>> {buildNumber}
>>>
>>> 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: users-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>
>>>
>>
>>
Re: Using buildnumber-maven-plugin together with jetty plugin
Or make a batch file magic.bat/magic.sh in your project top directory which calls Maven with the proper parameters... I wouldn't suggest doing this as a regular thing, but its OK for dev purposes. Wayne On Fri, Apr 10, 2009 at 2:11 AM, Stephen Connolly wrote: > 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 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 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 > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
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 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 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 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 wrote:
Hi,
I've just setup config with buildnumber-maven-plugin using
${project.artifactId}-${project.version}-r$
{buildNumber}
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
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 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 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 wrote:
> >
> > Hi,
> >
> > I've just setup config with buildnumber-maven-plugin using
> >
> >
> ${project.artifactId}-${project.version}-r${buildNumber}
> >
> > 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: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
> -----------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
--
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Using buildnumber-maven-plugin together with jetty plugin
On Thu, Apr 9, 2009 at 7:32 AM, Dan Tran 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 wrote:
> >
> > Hi,
> >
> > I've just setup config with buildnumber-maven-plugin using
> >
> >
> ${project.artifactId}-${project.version}-r${buildNumber}
> >
> > 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: users-unsubscr...@maven.apache.org
> > For additional commands, e-mail: users-h...@maven.apache.org
> >
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
Re: Using buildnumber-maven-plugin together with jetty plugin
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?
-D
On Wed, Apr 8, 2009 at 11:40 PM, nodje wrote:
>
> Hi,
>
> I've just setup config with buildnumber-maven-plugin using
>
> ${project.artifactId}-${project.version}-r${buildNumber}
>
> 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: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Using buildnumber-maven-plugin together with jetty plugin
Hi,
I've just setup config with buildnumber-maven-plugin using
${project.artifactId}-${project.version}-r${buildNumber}
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: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
