5:28 a.m.
Stefan Bunciak created JBIDE-11850:
--------------------------------------
Summary: OpenShift server: provide warning when changing deploy project
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch
deploy project from JBoss app to for example Ruby and vice versa. Furthermore when tried
to deploy Ruby app instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:13 a.m.
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11850:
---------------------------------------------
it makes perfect sense to be able to switch ;)
The server adapter is no longer tied to specific project type or project instance.
the NPE should not happen though so renaming issue.
OpenShift server: provide warning when changing deploy project
--------------------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:13 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-11850:
----------------------------------------
Summary: error when changing to ruby project and deploying (was: OpenShift server:
provide warning when changing deploy project)
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:28 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Stefan Bunciak commented on JBIDE-11850:
----------------------------------------
@Max:
It makes sense to switch the project, but not the application type on OpenShift.
Application type cannot be changed on OpenShift (confirmed by our OpenShift evangelist).
So publishing/deploying Ruby application on JBoss cannot work, imho.
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:37 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11850:
---------------------------------------------
Stefan - we can't see nor detect what kind of projects will work on the remote server
side.
What would you base it on ? It's just a git repository.
They DIY module on openshift can take everything.
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:06 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Stefan Bunciak commented on JBIDE-11850:
----------------------------------------
@Max:
I've figured out a solution, please comment:
* while creating/importing OpenShift application we do *know* its type, so
* we can save the type as properties to :
** <project>/.settings/org.jboss.tools.openshift.express.ui.prefs (application)
** <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml (server)
* then we can compare their types and decide (but handle the case when there is not such
information)
WDYT of it?
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:08 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Stefan Bunciak edited comment on JBIDE-11850 at 5/22/12 10:08 AM:
------------------------------------------------------------------
@Max:
I've figured out a solution (probably little complicated), please comment:
* while creating/importing OpenShift application we do *know* its type, so
* we can save the type as properties to :
** <project>/.settings/org.jboss.tools.openshift.express.ui.prefs (application)
** <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml (server)
* then we can compare their types and decide (but handle the case when there is not such
information)
WDYT of it?
was (Author: sbunciak):
@Max:
I've figured out a solution, please comment:
* while creating/importing OpenShift application we do *know* its type, so
* we can save the type as properties to :
** <project>/.settings/org.jboss.tools.openshift.express.ui.prefs (application)
** <workspace>/.metadata/.plugins/org.eclipse.wst.server.core/servers.xml (server)
* then we can compare their types and decide (but handle the case when there is not such
information)
WDYT of it?
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:54 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-11850:
---------------------------------------------
and we would do what with it ? just be able to warn the user since in some cases its
perfectly valid.
Again, i'm not seeing why this warning related to the server adapter - the server
adapter is not changing anything remotely, it is just changing the project which will mean
it also starts committing to a different repository.
It is not changing any type or mixing anything unless the user have deployed individual
files to the server that is not from a git repository.
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:48 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Stefan Bunciak commented on JBIDE-11850:
----------------------------------------
Ah, now I see! You are absolutely correct.
{quote}
the server adapter is not changing anything remotely, it is just changing the project
which will mean it also starts committing to a different repository.
{quote}
I thought it will start committing to the original repository (of the old project). Sorry
for making a little confusion.
The result is - just handle the exception.
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:26 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-11850.
---------------------------------
Resolution: Done
Exception is handled during publishStart(), which previously only checked for the
existence of the "magic project". It now also checks for the existence of the
deployment folder as set in the server editor.
If it is null or inaccessible, it will throw a core exception with proper messaging.
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 a.m.
New subject: [JBoss JIRA] (JBIDE-11850) error when changing to ruby project and deploying
[
https://issues.jboss.org/browse/JBIDE-11850?page=com.atlassian.jira.plugi...
]
Stefan Bunciak closed JBIDE-11850.
----------------------------------
Verified in JBoss Developer Studio
Version: 5.0.0.CR1
Build id: v20120605-2229-H183-CR1
Build date: 20120605-2229
error when changing to ruby project and deploying
-------------------------------------------------
Key: JBIDE-11850
URL: https://issues.jboss.org/browse/JBIDE-11850
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers, openshift
Affects Versions: 3.3.0.Beta3
Reporter: Stefan Bunciak
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.CR1
From my point of view does not make sense to allow users to switch deploy project from
JBoss app to for example Ruby and vice versa. Furthermore when tried to deploy Ruby app
instead of JBoss a NPE was thrown:
{code}
java.lang.NullPointerException
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressPublishMethod.publishModule(ExpressPublishMethod.java:122)
at
org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:119)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:27)
at
org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774)
at
org.jboss.tools.openshift.express.internal.core.behaviour.ExpressBehaviour.publish(ExpressBehaviour.java:34)
at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3087)
at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:345)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5070
days inactive
5093
days old
jbosstools-issues@lists.jboss.org
10 comments
3 participants
participants (3)
-
Max Rydahl Andersen (JIRA) -
Rob Stryker (JIRA)
-
Stefan Bunciak (JIRA)