[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3605:
--------------------------------
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3605:
-----------------------------
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3605:
-----------------------------
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3605:
-----------------------------
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3605:
-----------------------------
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 9.1.0.CR1
>
> Attachments: RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3653:
--------------------------------------
[~ldimaggio], [~ppitonak] can QE help [~dgolovin] with testing his proposed solution above (VAGRANT_DOTFILE_PATH=c:\FREDBR~1\.vagrant.d)?
> User's home folder with spaces cannot be used by vagrant during install
> -----------------------------------------------------------------------
>
> Key: JBDS-3653
> URL: https://issues.jboss.org/browse/JBDS-3653
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> Vagrant complains about
> {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem"
> The directory where plugins are installed (the Vagrant home directory)
> has a space in it. On Windows, there is a bug in Ruby when compiling
> plugins into directories with spaces. Please move your Vagrant home
> directory to a path without spaces and try again
> {quote}
> When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance:
> {code}C:\Users\User Name\.vagrant.d{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21857:
-------------------------------------
[~tmader] Where are you looking to discover this low level information in the debugger? Can you think of any workaround? Is this an error in eap/wf keeping the old class around? Or is Eclipse debugger caching it somehow? Is there any api we can use to force the debugger to forget some classes or packages? Thats probably not a safe workaround, though, since the same package could be used in multiple deployments.
Also I know I haven't experienced this before, but then I don't think I tested it super-methodically because it seemed to work. Is it a guarantee the old class's presence prevents any further changes? Or is it kinda based on which class happens to be at the top of the list / set / etc?
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Thomas Mäder
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21857) Hot class reload doesn't work on OpenShift
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Fred Bricon edited comment on JBIDE-21857 at 3/17/16 1:52 PM:
--------------------------------------------------------------
OK so it seems we can reproduce the same behavior locally:
- deploy jboss kitchensink on a local WF or EAP server, in debug mode
- register a new member, to make sure the classes are loaded
- add a new print() { System.err.println("print")} method in MemberRegistration(), called in register(Member member)
- saving the file, a dialog will open telling you code can't be replaced. Select to restart the module
- register a new member, the console will display "print"
- change print() to display "print again"
- saving the file, a dialog will open telling you code can't be replaced <-- this is bad, we expect the debugger to load the non structural change on-the-fly
was (Author: fbricon):
OK so it seems we can reproduce the same behavior locally:
- deploy jboss kitchensink on a local WF or EAP server, in debug mode
- register a new member, to make sure the classes are loaded
- add a new print() { System.err.println("print")} method in MemberRegistration(), called in register(Member member)
- saving the file, a dialog will open telling you code can't be replaced. Select to restart the module
- register a new member, the console will display "print"
- change print() to display "print again"
- saving the file, a dialog will open telling you code can't be replaced <-- this is bad, we expect the debugger to load the non structural change ob the fly
> Hot class reload doesn't work on OpenShift
> ------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Thomas Mäder
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years