You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Han Hong Fang (JIRA)" <ji...@apache.org> on 2010/12/01 03:46:11 UTC

[jira] Updated: (GERONIMODEVTOOLS-600) Build script should detect JDK data model(32bit or 64bit) instead of OS architecture

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

Han Hong Fang updated GERONIMODEVTOOLS-600:
-------------------------------------------

    Fix Version/s:     (was: 2.1.6)
                   2.1.7

update Fix Version from 2.1.6 to 2.1.7.

> Build script should detect JDK data model(32bit or 64bit) instead of OS architecture
> ------------------------------------------------------------------------------------
>
>                 Key: GERONIMODEVTOOLS-600
>                 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-600
>             Project: Geronimo-Devtools
>          Issue Type: Improvement
>          Components: eclipse-plugin
>    Affects Versions: 2.1.6, 2.2.1, 3.0
>            Reporter: Delos Dai
>            Assignee: Delos Dai
>             Fix For: 2.2.1, 2.1.7, 3.0
>
>
> In current eclipse/pom.xml, maven activation will detect OS architecture to decide which version of eclipse to be downloaded. It often fails on 64-bit system because of two reasons,because a 64-bit system may either use a 32-bit JDK or 64-bit JDK. Therefor, we have to detect JDK data model(32bit or 64bit) instead of OS architecture. 
> After my investigation, we can make use of property "sun.arch.data.model" to get the JDK data model. With this property, we can improve the build script to find correct eclipse version based on JDK data model.
>  

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