[JBoss JIRA] (JBIDE-21607) "Show In -> Browsersim" on EJB module should be disabled
by Martin Malina (JIRA)
Martin Malina created JBIDE-21607:
-------------------------------------
Summary: "Show In -> Browsersim" on EJB module should be disabled
Key: JBIDE-21607
URL: https://issues.jboss.org/browse/JBIDE-21607
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: browsersim
Affects Versions: 4.3.1.Beta2
Reporter: Martin Malina
This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled.
Rob did his part for Show in Server, but he says separate JIRAs are needed in other components.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21608) "Show In -> Web Browser via Live Reload" on EJB module should be disabled
by Martin Malina (JIRA)
Martin Malina created JBIDE-21608:
-------------------------------------
Summary: "Show In -> Web Browser via Live Reload" on EJB module should be disabled
Key: JBIDE-21608
URL: https://issues.jboss.org/browse/JBIDE-21608
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: livereload
Affects Versions: 4.3.1.Beta2
Reporter: Martin Malina
This is a followup of JBIDE-21138 . When you deploy an ejb module, all the items in Server View under Show in are enabled, but they don't do anything. They should be disabled.
Rob did his part for Show in Server, but he says separate JIRAs are needed in other components.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21606) Consider using java 8 for EAP 6.4 by default
by Martin Malina (JIRA)
Martin Malina created JBIDE-21606:
-------------------------------------
Summary: Consider using java 8 for EAP 6.4 by default
Key: JBIDE-21606
URL: https://issues.jboss.org/browse/JBIDE-21606
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.1.Beta2
Reporter: Martin Malina
Here's the problem that I just hit:
I added EAP 6.4 to JBDS 9.1 using runtime detection. Then I created the html5 project from JBoss Central using the EAP 6.4 server as target runtime.
Then on the project, I just Run -> Run on Server.
The server started, but deployment failed on Unsupported version: 51.0
Which is a bit strange, because the server was running with java 6. But anyhow. It seems the quictstart requires java 1.8 now. But default, EAP 6 will be set up to use java 6.
So ideally EAP 6.4 would use java 8 if present. But I know we discussed similar things in the past and there didn't seem to be any way to make something like this happen. But I just wanted to present this use case and perhaps there is some possibility?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21603:
---------------------------------------
Yeah, 10 years ago you were happy if you didn't see the Blue Screen of Death way too often on Windows :) But times have changed, welcome to 2016! :)
> CDK Runtime is useless stub and should be removed
> -------------------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21603:
-------------------------------------
We're all so spoiled now ;) Why, just 10 years ago, developers would simply ignore such things that didn't seem useful, rather than claim confusion! As long as it wasn't blocking the workflow, we'd just click on around it... and then we'd walk uphill in the snow to get to school, with no shoes on, and slaughter our own chickens for dinner! ;)
> CDK Runtime is useless stub and should be removed
> -------------------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21603:
---------------------------------------
OK, if not broken, it's definitely confusing, because the runtime is there, but you cannot create another one or do anything with it. I agree with removing it altogether if it doesn't break anything.
> CDK Runtime is useless stub and should be removed
> -------------------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21603:
--------------------------------
Fix Version/s: 4.3.1.CR1
> CDK Runtime is useless stub and should be removed
> -------------------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21603) Runtime environments and cdk are broken
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21603:
-------------------------------------
We don't store any data in a runtime. We provide no UI for a runtime. What is present is basically a stub runtime with no saved values, which is never used. Removing the runtime entirely could prevent something like publishing to work, so it was left in for now in its stub form. I wouldn't go so far as to say it's 'broken' so much as 'useless' ;)
Since it doesn't look like the CDK server will have publish support, and instead publish support will be implemented by the openshift server, it's probably safe to completely remove the notion of a "runtime" for CDK.
> Runtime environments and cdk are broken
> ---------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21603) CDK Runtime is useless stub and should be removed
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21603?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-21603:
--------------------------------
Summary: CDK Runtime is useless stub and should be removed (was: Runtime environments and cdk are broken)
> CDK Runtime is useless stub and should be removed
> -------------------------------------------------
>
> Key: JBIDE-21603
> URL: https://issues.jboss.org/browse/JBIDE-21603
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> When you open the New Server dialog and want to create a new CDK server while there is already one existing, it will preselect the existing runtime. There is an "Add" button to add a new runtime, but it doesn't work - when you click it, nothing happens.
> 1. Create a cdk server
> 2. Open the new server dialog again
> 3. For server type, select CDK
> 4. The server runtime env field will show the existing runtime. Click Add next to the field to create a new runtime - nothing happens
> At first, I thought it was just this. But now I'm confused what the design really is. At first it seemed you just added the notion of runtimes just like we use them for JBoss AS / WildFly / EAP. Then it seemed you dropped runtimes and just used servers. But now it seems there is still a runtime displayed in the server editor.
> When I first created a cdk server manually (this was cdk beta4), it has its own runtime. Then I used runtime detection to add another cdk server (this was openshift-vagrant git repo), but in server editor, it shows the Beta4 runtime is used and there is no way to change it. Then in preferences -> Server -> Runtime Environments, you can see the one runtime, but you can't edit it. And when you want to add a new one, there is no CDK type in the new runtime dialog.
> So it seems we're somewhere halfway between not using runtimes at all and using them to some degree.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months