[ 
https://issues.apache.org/activemq/browse/SMX4-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lars Heinemann updated SMX4-24:
-------------------------------

        Summary: welcome screen and info command display wrong version 
information of servicemix  (was: info command displays wrong version 
information of servicemix)
    Description: 
- the problem is that the version displayed is grabbed from servicemix kernel, 
so m1 of smx4 distrib uses kernel 1.0-m2
- same to the welcome screen version information

IRC Snippet:

<lhein> gnodet__: just downloaded the smx4-m1 binary for linux from webpage. 
Now after I started and typed info into console it displays "ServiceMix version 
         1.0-m2" ;) Secret Update Feature?
<gnodet__> sounds weird
<gnodet__> the version is built at runtime so i don't know how it could be wrong
<gnodet__> did you deploy additional stuff ?
<lhein> no, just downloaded and untarred it
<lhein> maybe a const set wrong?
<gnodet__> well, no, it uses maven filtering resources in a property file
<lhein> i am just wondering because webpage says m1, the untarred folder is 
known as apache-servicemix-4.0-m1...so I just didn't expected m2 here ;)
<gnodet> ah, i see now
<gnodet> the problem is that the version displayed is grabbed from servicemix 
kernel, so m1 of smx4 distrib uses kernel 1.0-m2
<gnodet> i guess it should be fixed somehow, please raise a jira ;-)

  was:
the problem is that the version displayed is grabbed from servicemix kernel, so 
m1 of smx4 distrib uses kernel 1.0-m2

IRC Snippet:

<lhein> gnodet__: just downloaded the smx4-m1 binary for linux from webpage. 
Now after I started and typed info into console it displays "ServiceMix version 
         1.0-m2" ;) Secret Update Feature?
<gnodet__> sounds weird
<gnodet__> the version is built at runtime so i don't know how it could be wrong
<gnodet__> did you deploy additional stuff ?
<lhein> no, just downloaded and untarred it
<lhein> maybe a const set wrong?
<gnodet__> well, no, it uses maven filtering resources in a property file
<lhein> i am just wondering because webpage says m1, the untarred folder is 
known as apache-servicemix-4.0-m1...so I just didn't expected m2 here ;)
<gnodet> ah, i see now
<gnodet> the problem is that the version displayed is grabbed from servicemix 
kernel, so m1 of smx4 distrib uses kernel 1.0-m2
<gnodet> i guess it should be fixed somehow, please raise a jira ;-)


> welcome screen and info command display wrong version information of 
> servicemix
> -------------------------------------------------------------------------------
>
>                 Key: SMX4-24
>                 URL: https://issues.apache.org/activemq/browse/SMX4-24
>             Project: ServiceMix 4
>          Issue Type: Bug
>    Affects Versions: 4.0-m1
>         Environment: Linux
>            Reporter: Lars Heinemann
>            Priority: Minor
>
> - the problem is that the version displayed is grabbed from servicemix 
> kernel, so m1 of smx4 distrib uses kernel 1.0-m2
> - same to the welcome screen version information
> IRC Snippet:
> <lhein> gnodet__: just downloaded the smx4-m1 binary for linux from webpage. 
> Now after I started and typed info into console it displays "ServiceMix 
> version          1.0-m2" ;) Secret Update Feature?
> <gnodet__> sounds weird
> <gnodet__> the version is built at runtime so i don't know how it could be 
> wrong
> <gnodet__> did you deploy additional stuff ?
> <lhein> no, just downloaded and untarred it
> <lhein> maybe a const set wrong?
> <gnodet__> well, no, it uses maven filtering resources in a property file
> <lhein> i am just wondering because webpage says m1, the untarred folder is 
> known as apache-servicemix-4.0-m1...so I just didn't expected m2 here ;)
> <gnodet> ah, i see now
> <gnodet> the problem is that the version displayed is grabbed from servicemix 
> kernel, so m1 of smx4 distrib uses kernel 1.0-m2
> <gnodet> i guess it should be fixed somehow, please raise a jira ;-)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to