You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@tapestry.apache.org by John <jo...@quivinco.com> on 2013/04/09 11:28:34 UTC

SymbolConstants.APPLICATION_VERSION = maven build version

Is there a neat way for SymbolConstants.APPLICATION_VERSION to match the maven build version?

John

Re: SymbolConstants.APPLICATION_VERSION = maven build version

Posted by John <jo...@quivinco.com>.

I'd like to put a property in the manifest, but not sure how that works during development using the maven jetty plugin.

John
  ----- Original Message ----- 
  From: Dmitry Gusev 
  To: Tapestry users 
  Sent: Tuesday, April 09, 2013 10:29 AM
  Subject: Re: SymbolConstants.APPLICATION_VERSION = maven build version

  I can suggest storing build number to a file during build process and read
  the file in contributeApplicationDefaults.

  On Tue, Apr 9, 2013 at 1:28 PM, John <jo...@quivinco.com> wrote:

  > Is there a neat way for SymbolConstants.APPLICATION_VERSION to match the
  > maven build version?
  >
  > John

  -- 
  Dmitry Gusev

  AnjLab Team
  http://anjlab.com

Re: SymbolConstants.APPLICATION_VERSION = maven build version

Posted by Ivan Khalopik <ik...@gmail.com>.

If you have web application you can use context param to specify
application version:

    <context-param>
        <param-name>tapestry.application-version</param-name>
        <param-value>${project.version}</param-value>
    </context-param>

Then you just need to enable filtering for web.xml in maven-war-plugin,
e.g.:

    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-war-plugin</artifactId>
        <configuration>
            <webXml>src/main/config/web.xml</webXml>

<filteringDeploymentDescriptors>true</filteringDeploymentDescriptors>
        </configuration>
    </plugin>




On Tue, Apr 9, 2013 at 1:11 PM, John <jo...@quivinco.com> wrote:

> found this in the archives!
>
>
> http://mail-archives.apache.org/mod_mbox/tapestry-users/201109.mbox/%3CCACd-vsPwU9sNhgmf9xx7N5Xe8fEQxYVoZOaYAynaVfF-_xvGsQ@mail.gmail.com%3E
>   ----- Original Message -----
>   From: Dmitry Gusev
>   To: Tapestry users
>   Sent: Tuesday, April 09, 2013 10:29 AM
>   Subject: Re: SymbolConstants.APPLICATION_VERSION = maven build version
>
>
>   I can suggest storing build number to a file during build process and
> read
>   the file in contributeApplicationDefaults.
>
>   On Tue, Apr 9, 2013 at 1:28 PM, John <jo...@quivinco.com> wrote:
>
>   > Is there a neat way for SymbolConstants.APPLICATION_VERSION to match
> the
>   > maven build version?
>   >
>   > John
>
>
>
>
>   --
>   Dmitry Gusev
>
>   AnjLab Team
>   http://anjlab.com
>



-- 
BR
Ivan

Re: SymbolConstants.APPLICATION_VERSION = maven build version

Posted by John <jo...@quivinco.com>.

found this in the archives!

http://mail-archives.apache.org/mod_mbox/tapestry-users/201109.mbox/%3CCACd-vsPwU9sNhgmf9xx7N5Xe8fEQxYVoZOaYAynaVfF-_xvGsQ@mail.gmail.com%3E
  ----- Original Message ----- 
  From: Dmitry Gusev 
  To: Tapestry users 
  Sent: Tuesday, April 09, 2013 10:29 AM
  Subject: Re: SymbolConstants.APPLICATION_VERSION = maven build version


  I can suggest storing build number to a file during build process and read
  the file in contributeApplicationDefaults.

  On Tue, Apr 9, 2013 at 1:28 PM, John <jo...@quivinco.com> wrote:

  > Is there a neat way for SymbolConstants.APPLICATION_VERSION to match the
  > maven build version?
  >
  > John




  -- 
  Dmitry Gusev

  AnjLab Team
  http://anjlab.com

Re: SymbolConstants.APPLICATION_VERSION = maven build version

Posted by Dmitry Gusev <dm...@gmail.com>.

I can suggest storing build number to a file during build process and read
the file in contributeApplicationDefaults.

On Tue, Apr 9, 2013 at 1:28 PM, John <jo...@quivinco.com> wrote:

> Is there a neat way for SymbolConstants.APPLICATION_VERSION to match the
> maven build version?
>
> John

-- 
Dmitry Gusev

AnjLab Team
http://anjlab.com