[jbosstools-issues] [JBoss JIRA] (JBDS-2546) About Dialog - What version of Eclipse am I running?

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBDS-2546?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12784415#comment-12784415 ] 

Nick Boldt edited comment on JBDS-2546 at 6/25/13 1:06 PM:
-----------------------------------------------------------

Initial investigation suggests I can pull the build ID (starts with "I", located in o.e.platform plugin's about.mappings file) and the org.eclipse.platform plugin or org.eclipse.platform.feature feature version from the artifacts being pushed into the installer. 

But there's no Kepler version in there since we don't build on top of a EPP package. And even if we did, there's no obvious mapping between Kepler version and the EPP plugin version. For example, org.eclipse.epp.package.jee_2.0.0.20130521-1725 == Kepler RC3.

Further investigation suggests that there are multiple versions of an eclipse platform. I think the simplest would be to track just the platform feature.

{code}
o.e.platform Plugin:

Eclipse-SourceReferences: scm:git:git://git.eclipse.org/gitroot/platfo
 rm/eclipse.platform.git;path="platform/org.eclipse.platform";tag="I20
 130514-2000";commitId=132e377fd86df9bb834a781e9da8202fe9563762

Bundle-Version: 4.3.0.v20130526-2000

0=I20130526-2000

o.e.platform Feature:

      version="4.3.0.v20130526-2122"

   <plugin
         id="org.eclipse.platform"
         download-size="391"
         install-size="621"
         version="4.3.0.v20130526-2000"/>
{code}

*HOWEVER* this information needs to be pulled into the About dialog *every time Eclipse or JBDS is installed/updated*, which means writing new information to plugins/com.jboss.jbds.product_*.jar!/about.mappings or storing this information elsewhere.

So, while it would be reasonably simple to set the version of Eclipse contained in a given JBDS install *at build time*, that doesn't guarantee that it would be the same exact version should a user update JBDS to a newer Eclipse w/o also updating JBDS at the same time.
                
      was (Author: nickboldt):
    Initial investigation suggests I can pull the build ID (starts with "I", located in o.e.platform plugin's about.mappings file) and the org.eclipse.platform plugin or org.eclipse.platform.feature feature version from the artifacts being pushed into the installer. 

But there's no Kepler version in there since we don't build on top of a EPP package. And even if we did, there's no obvious mapping between Kepler version and the EPP plugin version. For example, org.eclipse.epp.package.jee_2.0.0.20130521-1725 == Kepler RC3.
                  
> About Dialog - What version of Eclipse am I running?
> ----------------------------------------------------
>
>                 Key: JBDS-2546
>                 URL: https://issues.jboss.org/browse/JBDS-2546
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: ui/branding
>            Reporter: Burr Sutter
>            Assignee: Nick Boldt
>            Priority: Minor
>             Fix For: 7.0.x
>
>         Attachments: 2013-03-12_1930.png, 2013-03-12_1931.png, 2013-03-12_19312.png, 2546-feature-list.png, 2546-nested-feature-list.png
>
>
> How does someone answer the following question:
> What version of Eclipse is "inside" JBoss Developer Studio?
> Ideally, the string of "Eclipse Juno 4.2.1" and its build-id would be listed underneath the JBDS version, build id and build date.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira