[JBoss JIRA] (JBDS-2672) Change 64-bit Warning on Early Access
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2672?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji edited comment on JBDS-2672 at 6/28/13 5:06 AM:
---------------------------------------------------------------
Thanks Nick for CCing us on this. I don't mind the wording but a table would be good to just be very clear on this.
Visual Page Editor supported configurations:
{noformat}
64bit OS X | 64bit Windows
64bit JBDS + 64bit JDK X | X
32bit JBDS + 32bit JDK ✓ | ✓
{noformat}
was (Author: mmusaji):
Thanks Nick for CCing us on this. I don't mind the wording but a table would be good to just be very clear on this.
Visual Page Editor supported configurations:
64bit OS X | 64bit Windows
64bit JBDS + 64bit JDK X | X
32bit JBDS + 32bit JDK ✓ | ✓
> Change 64-bit Warning on Early Access
> -------------------------------------
>
> Key: JBDS-2672
> URL: https://issues.jboss.org/browse/JBDS-2672
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Current description on https://devstudio.jboss.com/earlyaccess/7.0.0.Beta1.html says:
> {quote}
> The Visual Page Editor does not run on 64-bit Windows or Mac. While the source editor does work, visual editing & preview do not. If you require this, run the installer with a 32-bit JDK.
> {quote}
> Making readers believe that we do not run on 64-bit OS. The real issue is 64-bit JVMs. A 32-bit JVM on a 64-bit OS is great.
> So, a rewording attempt:
> {quote}
> The Visual Page Editor does not provide visual editing nor preview when run on a 64-bit JVM. However, it does provide visual editing when used on a 32-bit JVM even on a 64-bit Windows or Mac OS X.
> {quote}
--
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, 9 months
[JBoss JIRA] (JBDS-2672) Change 64-bit Warning on Early Access
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2672?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji edited comment on JBDS-2672 at 6/28/13 5:06 AM:
---------------------------------------------------------------
Thanks Nick for CCing us on this. I don't mind the wording but a table would be good to just be very clear on this.
{noformat}
Visual Page Editor supported configurations:
64bit OS X | 64bit Windows
64bit JBDS + 64bit JDK X | X
32bit JBDS + 32bit JDK ✓ | ✓
{noformat}
was (Author: mmusaji):
Thanks Nick for CCing us on this. I don't mind the wording but a table would be good to just be very clear on this.
Visual Page Editor supported configurations:
{noformat}
64bit OS X | 64bit Windows
64bit JBDS + 64bit JDK X | X
32bit JBDS + 32bit JDK ✓ | ✓
{noformat}
> Change 64-bit Warning on Early Access
> -------------------------------------
>
> Key: JBDS-2672
> URL: https://issues.jboss.org/browse/JBDS-2672
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Current description on https://devstudio.jboss.com/earlyaccess/7.0.0.Beta1.html says:
> {quote}
> The Visual Page Editor does not run on 64-bit Windows or Mac. While the source editor does work, visual editing & preview do not. If you require this, run the installer with a 32-bit JDK.
> {quote}
> Making readers believe that we do not run on 64-bit OS. The real issue is 64-bit JVMs. A 32-bit JVM on a 64-bit OS is great.
> So, a rewording attempt:
> {quote}
> The Visual Page Editor does not provide visual editing nor preview when run on a 64-bit JVM. However, it does provide visual editing when used on a 32-bit JVM even on a 64-bit Windows or Mac OS X.
> {quote}
--
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, 9 months
[JBoss JIRA] (JBDS-2672) Change 64-bit Warning on Early Access
by Mustafa Musaji (JIRA)
[ https://issues.jboss.org/browse/JBDS-2672?page=com.atlassian.jira.plugin.... ]
Mustafa Musaji commented on JBDS-2672:
--------------------------------------
Thanks Nick for CCing us on this. I don't mind the wording but a table would be good to just be very clear on this.
Visual Page Editor supported configurations:
64bit OS X | 64bit Windows
64bit JBDS + 64bit JDK X | X
32bit JBDS + 32bit JDK ✓ | ✓
> Change 64-bit Warning on Early Access
> -------------------------------------
>
> Key: JBDS-2672
> URL: https://issues.jboss.org/browse/JBDS-2672
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Burr Sutter
> Assignee: Nick Boldt
> Fix For: 7.0.0.Beta2
>
>
> Current description on https://devstudio.jboss.com/earlyaccess/7.0.0.Beta1.html says:
> {quote}
> The Visual Page Editor does not run on 64-bit Windows or Mac. While the source editor does work, visual editing & preview do not. If you require this, run the installer with a 32-bit JDK.
> {quote}
> Making readers believe that we do not run on 64-bit OS. The real issue is 64-bit JVMs. A 32-bit JVM on a 64-bit OS is great.
> So, a rewording attempt:
> {quote}
> The Visual Page Editor does not provide visual editing nor preview when run on a 64-bit JVM. However, it does provide visual editing when used on a 32-bit JVM even on a 64-bit Windows or Mac OS X.
> {quote}
--
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, 9 months
[JBoss JIRA] (JBIDE-10695) Cartridges: provide some doc/context for users to know what they do
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10695:
-------------------------------------
Summary: Cartridges: provide some doc/context for users to know what they do (was: for all or at least key cartridges include some doc/context for users to know what they do)
> Cartridges: provide some doc/context for users to know what they do
> -------------------------------------------------------------------
>
> Key: JBIDE-10695
> URL: https://issues.jboss.org/browse/JBIDE-10695
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> currently "embeddable catridges" just list all the base names for the cartridges and users gets no info on what they do.
> i.e. postgresql-8.4 and mysql-5.1 could list something like:
> "Enables mysql database for your OpenShift application.
> The connection details are available as environment variables ($OPENSHIFT_DB_PASSWORD, ...) and for
> JBoss AS application it is enabled via datasource named: MysqlDS."
> (the values above is just from my memory - need to check the full names/values)
> Would also be good if there was a stable url to get to docs for these since they do require a "masters desgree in openshift" to fully understand.
--
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, 9 months
[JBoss JIRA] (JBIDE-10695) Cartridges: provide some doc/context for users to know what they do
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10695:
-------------------------------------
Issue Type: Enhancement (was: Bug)
> Cartridges: provide some doc/context for users to know what they do
> -------------------------------------------------------------------
>
> Key: JBIDE-10695
> URL: https://issues.jboss.org/browse/JBIDE-10695
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
>
> currently "embeddable catridges" just list all the base names for the cartridges and users gets no info on what they do.
> i.e. postgresql-8.4 and mysql-5.1 could list something like:
> "Enables mysql database for your OpenShift application.
> The connection details are available as environment variables ($OPENSHIFT_DB_PASSWORD, ...) and for
> JBoss AS application it is enabled via datasource named: MysqlDS."
> (the values above is just from my memory - need to check the full names/values)
> Would also be good if there was a stable url to get to docs for these since they do require a "masters desgree in openshift" to fully understand.
--
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, 9 months
[JBoss JIRA] (JBIDE-10695) Cartridges: provide some doc/context for users to know what they do
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10695:
-------------------------------------
Priority: Major (was: Minor)
> Cartridges: provide some doc/context for users to know what they do
> -------------------------------------------------------------------
>
> Key: JBIDE-10695
> URL: https://issues.jboss.org/browse/JBIDE-10695
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.1.x
>
>
> currently "embeddable catridges" just list all the base names for the cartridges and users gets no info on what they do.
> i.e. postgresql-8.4 and mysql-5.1 could list something like:
> "Enables mysql database for your OpenShift application.
> The connection details are available as environment variables ($OPENSHIFT_DB_PASSWORD, ...) and for
> JBoss AS application it is enabled via datasource named: MysqlDS."
> (the values above is just from my memory - need to check the full names/values)
> Would also be good if there was a stable url to get to docs for these since they do require a "masters desgree in openshift" to fully understand.
--
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, 9 months
[JBoss JIRA] (JBIDE-10695) Cartridges: provide some doc/context for users to know what they do
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10695?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10695:
-------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Cartridges: provide some doc/context for users to know what they do
> -------------------------------------------------------------------
>
> Key: JBIDE-10695
> URL: https://issues.jboss.org/browse/JBIDE-10695
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
>
> currently "embeddable catridges" just list all the base names for the cartridges and users gets no info on what they do.
> i.e. postgresql-8.4 and mysql-5.1 could list something like:
> "Enables mysql database for your OpenShift application.
> The connection details are available as environment variables ($OPENSHIFT_DB_PASSWORD, ...) and for
> JBoss AS application it is enabled via datasource named: MysqlDS."
> (the values above is just from my memory - need to check the full names/values)
> Would also be good if there was a stable url to get to docs for these since they do require a "masters desgree in openshift" to fully understand.
--
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, 9 months
[JBoss JIRA] (JBIDE-10541) If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-10541:
-------------------------------------
Steps to Reproduce:
# EXEC: launch OpenShift Application wizard
# EXEC: provide valid credentials
# EXEC: create a new application and have it imported to your workspace
# EXEC: when the import process tells you that there are local commits to be pushed, tell it *Yes*
# EXEC: add a new file to your OpenShift enabled project
# EXEC: tell the OpenShift server adapter to publish
Result:
The adapter tells you that you dont have any changes to push
Expected:
The adapter should notice the new file, that was not added to the git index yet, and add & commit before publishing
was:
# EXEC: launch OpenShift Application wizard
# EXEC: provide valid credentials
# EXEC: select/create application
# EXEC: create new project/use existing project
# EXEC: add a new file to your OpenShift enabled project
# EXEC: tell the OpenShift server adapter to publish
Result:
The adapter tells you that you dont have any changes to push
Expected:
The adapter should notice the new file, that was not added to the git index yet, and add & commit before publishing
> If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-10541
> URL: https://issues.jboss.org/browse/JBIDE-10541
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.0.M5
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Fix For: 4.1.x
>
>
> Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo.
> Should make a check against the fetched upstream and see what has changed since that is a fast local operation.
--
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, 9 months