[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Carsten Pfeiffer (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Carsten Pfeiffer commented on JBIDE-2720:
-----------------------------------------
[~yradtsevich] We actually had a similar problem unrelated to the 64 Bit build. I.e. we had this problem also with the 32 Bit xulrunner build from JBoss. You appear to have multiple versions of the MSVCRT library and one of them is slightly incompatible. Use Process Explorer to find which one is being used: use the View > Lower Pane View > DLLs to switch to the correct view. Select the DLL and use the "Properties" context menu entry to show the full path.
A workaround is to change the PATH so that that dll cannot be found.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.0.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for windows 64 bit.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13248) openshift-java-client: provide nice names, versions and descriptions for cartridges
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13248?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-13248 at 5/6/13 3:44 AM:
------------------------------------------------------------------
in protocol 1.2 we already have support for nice cartridge names etc.:
{code:title=curl -H "Accept: application/xml; version=1.2" --user adietish@redhat.com:XXXXX https://openshift.redhat.com/broker/rest/cartridges}
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>mongodb-2.2</name>
<version>2.2</version>
<display-name>MongoDB NoSQL Database 2.2</display-name>
<description>MongoDB is a scalable, high-performance, open source NoSQL database.</description>
<license>ASL 2.0</license>
<license-url>http://www.apache.org/licenses/LICENSE-2.0.txt</license-url>
<tags>
<tag>service</tag>
<tag>database</tag>
<tag>nosql</tag>
<tag>embedded</tag>
</tags>
<website>http://www.10gen.com</website>
<type>embedded</type>
<supported-scales-from>1</supported-scales-from>
<scales-from>1</scales-from>
<supported-scales-to>1</supported-scales-to>
<scales-to>1</scales-to>
<current-scale>0</current-scale>
<scales-with>haproxy-1.4</scales-with>
<help-topics>
<help-topic>
<Building-with-MongoDB>https://openshift.redhat.com/community/developers/mongodb</Building-with-MongoDB>
</help-topic>
</help-topics>
<usage-rates/>
</cartridge>
{code}
was (Author: adietish):
in protocol 1.2 we already have support for nice cartridge names:
{code:title=curl -H "Accept: application/xml; version=1.2" --user adietish@redhat.com:XXXXX https://openshift.redhat.com/broker/rest/cartridges}
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>mongodb-2.2</name>
<version>2.2</version>
<display-name>MongoDB NoSQL Database 2.2</display-name>
<description>MongoDB is a scalable, high-performance, open source NoSQL database.</description>
<license>ASL 2.0</license>
<license-url>http://www.apache.org/licenses/LICENSE-2.0.txt</license-url>
<tags>
<tag>service</tag>
<tag>database</tag>
<tag>nosql</tag>
<tag>embedded</tag>
</tags>
<website>http://www.10gen.com</website>
<type>embedded</type>
<supported-scales-from>1</supported-scales-from>
<scales-from>1</scales-from>
<supported-scales-to>1</supported-scales-to>
<scales-to>1</scales-to>
<current-scale>0</current-scale>
<scales-with>haproxy-1.4</scales-with>
<help-topics>
<help-topic>
<Building-with-MongoDB>https://openshift.redhat.com/community/developers/mongodb</Building-with-MongoDB>
</help-topic>
</help-topics>
<usage-rates/>
</cartridge>
{code}
> openshift-java-client: provide nice names, versions and descriptions for cartridges
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13248
> URL: https://issues.jboss.org/browse/JBIDE-13248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> The response (protocol v1.3) when querying the OpenShift REST service for cartridges (standalone and embeddable ones) was enhanced lately. It now offers
> * <display-name />
> * <version />
> * <description />
> eventually
> * <website />
> * <help-topics />
> We should add at least these 3 in the ICartridge.
> There are also further interesting informations:
> * <tag />
> * <scales-from /> & <scales-to />
> * <scales-with />
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13248) openshift-java-client: provide nice names, versions and descriptions for cartridges
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13248?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-13248 at 5/6/13 3:46 AM:
------------------------------------------------------------------
in protocol 1.2 we already have support for nice cartridge names etc.:
{code:xml|title=curl -H "Accept: application/xml; version=1.2" --user adietish@redhat.com:XXXXX https://openshift.redhat.com/broker/rest/cartridges}
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>mongodb-2.2</name>
<version>2.2</version>
<display-name>MongoDB NoSQL Database 2.2</display-name>
<description>MongoDB is a scalable, high-performance, open source NoSQL database.</description>
<license>ASL 2.0</license>
<license-url>http://www.apache.org/licenses/LICENSE-2.0.txt</license-url>
<tags>
<tag>service</tag>
<tag>database</tag>
<tag>nosql</tag>
<tag>embedded</tag>
</tags>
<website>http://www.10gen.com</website>
<type>embedded</type>
<supported-scales-from>1</supported-scales-from>
<scales-from>1</scales-from>
<supported-scales-to>1</supported-scales-to>
<scales-to>1</scales-to>
<current-scale>0</current-scale>
<scales-with>haproxy-1.4</scales-with>
<help-topics>
<help-topic>
<Building-with-MongoDB>https://openshift.redhat.com/community/developers/mongodb</Building-with-MongoDB>
</help-topic>
</help-topics>
<usage-rates/>
</cartridge>
{code}
was (Author: adietish):
in protocol 1.2 we already have support for nice cartridge names etc.:
{code:title=curl -H "Accept: application/xml; version=1.2" --user adietish@redhat.com:XXXXX https://openshift.redhat.com/broker/rest/cartridges}
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>mongodb-2.2</name>
<version>2.2</version>
<display-name>MongoDB NoSQL Database 2.2</display-name>
<description>MongoDB is a scalable, high-performance, open source NoSQL database.</description>
<license>ASL 2.0</license>
<license-url>http://www.apache.org/licenses/LICENSE-2.0.txt</license-url>
<tags>
<tag>service</tag>
<tag>database</tag>
<tag>nosql</tag>
<tag>embedded</tag>
</tags>
<website>http://www.10gen.com</website>
<type>embedded</type>
<supported-scales-from>1</supported-scales-from>
<scales-from>1</scales-from>
<supported-scales-to>1</supported-scales-to>
<scales-to>1</scales-to>
<current-scale>0</current-scale>
<scales-with>haproxy-1.4</scales-with>
<help-topics>
<help-topic>
<Building-with-MongoDB>https://openshift.redhat.com/community/developers/mongodb</Building-with-MongoDB>
</help-topic>
</help-topics>
<usage-rates/>
</cartridge>
{code}
> openshift-java-client: provide nice names, versions and descriptions for cartridges
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13248
> URL: https://issues.jboss.org/browse/JBIDE-13248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> The response (protocol v1.3) when querying the OpenShift REST service for cartridges (standalone and embeddable ones) was enhanced lately. It now offers
> * <display-name />
> * <version />
> * <description />
> eventually
> * <website />
> * <help-topics />
> We should add at least these 3 in the ICartridge.
> There are also further interesting informations:
> * <tag />
> * <scales-from /> & <scales-to />
> * <scales-with />
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13248) openshift-java-client: provide nice names, versions and descriptions for cartridges
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13248?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13248:
------------------------------------------
in protocol 1.2 we already have support for nice cartridge names:
{code:title=curl -H "Accept: application/xml; version=1.2" --user adietish@redhat.com:XXXXX https://openshift.redhat.com/broker/rest/cartridges}
<response>
<status>ok</status>
<type>cartridges</type>
<data>
<cartridge>
<name>mongodb-2.2</name>
<version>2.2</version>
<display-name>MongoDB NoSQL Database 2.2</display-name>
<description>MongoDB is a scalable, high-performance, open source NoSQL database.</description>
<license>ASL 2.0</license>
<license-url>http://www.apache.org/licenses/LICENSE-2.0.txt</license-url>
<tags>
<tag>service</tag>
<tag>database</tag>
<tag>nosql</tag>
<tag>embedded</tag>
</tags>
<website>http://www.10gen.com</website>
<type>embedded</type>
<supported-scales-from>1</supported-scales-from>
<scales-from>1</scales-from>
<supported-scales-to>1</supported-scales-to>
<scales-to>1</scales-to>
<current-scale>0</current-scale>
<scales-with>haproxy-1.4</scales-with>
<help-topics>
<help-topic>
<Building-with-MongoDB>https://openshift.redhat.com/community/developers/mongodb</Building-with-MongoDB>
</help-topic>
</help-topics>
<usage-rates/>
</cartridge>
{code}
> openshift-java-client: provide nice names, versions and descriptions for cartridges
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-13248
> URL: https://issues.jboss.org/browse/JBIDE-13248
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> The response (protocol v1.3) when querying the OpenShift REST service for cartridges (standalone and embeddable ones) was enhanced lately. It now offers
> * <display-name />
> * <version />
> * <description />
> eventually
> * <website />
> * <help-topics />
> We should add at least these 3 in the ICartridge.
> There are also further interesting informations:
> * <tag />
> * <scales-from /> & <scales-to />
> * <scales-with />
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2563) JBDS70_1213: [Commit] (?) (P?) Support Hosted OpenShift - Multiple "versions"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2563?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim edited comment on JBDS-2563 at 5/6/13 3:42 AM:
----------------------------------------------------------------
[~maxandersen] Yes, in a first step we decided to support protocol 1.2 which is available in online and enterprise (JBIDE-12320). Protocol 1.2 will allow us to offer many of the new features we currently strive for (JBIDE-13248). We'll drop support for 1.0 and 1.1 as discussed and suggested with the OpenShift team. We'll head for support for multiple protocols later (JBIDE-14386).
was (Author: adietish):
[~maxandersen] Yes, in a first step we decided to support protocol 1.2 which is available in online and enterprise (JBIDE-12320). We'll drop support for 1.0 and 1.1 as discussed and suggested with the OpenShift team. We'll head for support for multiple protocols later.
> JBDS70_1213: [Commit] (?) (P?) Support Hosted OpenShift - Multiple "versions"
> -----------------------------------------------------------------------------
>
> Key: JBDS-2563
> URL: https://issues.jboss.org/browse/JBDS-2563
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Requirements
> Reporter: Jiri Pallich
> Assignee: Andre Dietisheim
> Fix For: 7.0.0.Beta1
>
>
> OpenShift Hosted vs On-Premise
> Maybe related to JBDS61_0530.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14386) openshift-java-client: support multiple protocol version
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-14386:
----------------------------------------
Summary: openshift-java-client: support multiple protocol version
Key: JBIDE-14386
URL: https://issues.jboss.org/browse/JBIDE-14386
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.1.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.x
In JBIDE-12320 we decided to get over to protocol 1.2 as minimum protocol for the client since there are no products that require a lower protocol version. The next step is to have support for multiple protocol versions since online, enterprise, on prmeise etc. may support different protocol versions depending on the installed product version.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Carsten Pfeiffer (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Carsten Pfeiffer commented on JBIDE-2720:
-----------------------------------------
[~yradtsevich] I could make available our binary xulrunner so you can check if this is a build-problem
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.0.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for windows 64 bit.
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2563) JBDS70_1213: [Commit] (?) (P?) Support Hosted OpenShift - Multiple "versions"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2563?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-2563:
----------------------------------------
[~maxandersen] Yes, in a first step we decided to support protocol 1.2 which is available in online and enterprise (JBIDE-12320). We'll drop support for 1.0 and 1.1 as discussed and suggested with the OpenShift team. We'll head for support for multiple protocols later.
> JBDS70_1213: [Commit] (?) (P?) Support Hosted OpenShift - Multiple "versions"
> -----------------------------------------------------------------------------
>
> Key: JBDS-2563
> URL: https://issues.jboss.org/browse/JBDS-2563
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Requirements
> Reporter: Jiri Pallich
> Assignee: Andre Dietisheim
> Fix For: 7.0.0.Beta1
>
>
> OpenShift Hosted vs On-Premise
> Maybe related to JBDS61_0530.
--
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
12 years, 11 months
[JBoss JIRA] (JBDS-2562) JBDS70_1211: [Partial] (?) (P2) Break free from CLI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2562?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-2562:
----------------------------------------
Since the fix version is already set to Beta1 we close this as "Partially Completed", right? We wont carry this on to further versions until all parts are implemented?
> JBDS70_1211: [Partial] (?) (P2) Break free from CLI
> ---------------------------------------------------
>
> Key: JBDS-2562
> URL: https://issues.jboss.org/browse/JBDS-2562
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Requirements
> Reporter: Jiri Pallich
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 7.0.0.Beta1
>
>
> Level 1: "Actions" in OpenShift -> backup start, stop, restart etc.
> Level 2: Run Debug (enable_jpda, enable portforwarding, setup remote debug launch, ...) - optional
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by Carsten Pfeiffer (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
Carsten Pfeiffer commented on JBIDE-2720:
-----------------------------------------
[~dgolovin] I tested this with Windows 7 Ultimate N SP1
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Yahor Radtsevich
> Fix For: 4.0.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64 bit jdk, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for windows 64 bit.
--
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
12 years, 11 months