[JBoss JIRA] (JBTIS-597) Cannot install BPMN2 Modeler - Diagram Editor due to requires 'bundle org.eclipse.emf.validation.ocl 0.0.0' but it could not be found
by Hendy Irawan (JIRA)
[ https://issues.jboss.org/browse/JBTIS-597?page=com.atlassian.jira.plugin.... ]
Hendy Irawan updated JBTIS-597:
-------------------------------
Attachment: keepmy.png
> Cannot install BPMN2 Modeler - Diagram Editor due to requires 'bundle org.eclipse.emf.validation.ocl 0.0.0' but it could not be found
> -------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-597
> URL: https://issues.jboss.org/browse/JBTIS-597
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: BPMN2
> Affects Versions: 4.3.0.Beta1
> Environment: jboss-devstudio-9.1.0.Beta2
> Reporter: Hendy Irawan
> Attachments: keepmy.png
>
>
> {noformat}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: BPMN2 Modeler - Diagram Editor 1.2.3.Final-v20160226-1723-B97 (org.eclipse.bpmn2.modeler.feature.group 1.2.3.Final-v20160226-1723-B97)
> Missing requirement: org.eclipse.bpmn2.modeler.core 1.2.3.Final-v20160226-1723-B97 requires 'bundle org.eclipse.emf.validation.ocl 0.0.0' but it could not be found
> Cannot satisfy dependency:
> From: BPMN2 Modeler - Diagram Editor 1.2.3.Final-v20160226-1723-B97 (org.eclipse.bpmn2.modeler.feature.group 1.2.3.Final-v20160226-1723-B97)
> To: org.eclipse.bpmn2.modeler.core [1.2.3.Final-v20160226-1723-B97]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-597) Cannot install BPMN2 Modeler - Diagram Editor due to requires 'bundle org.eclipse.emf.validation.ocl 0.0.0' but it could not be found
by Hendy Irawan (JIRA)
Hendy Irawan created JBTIS-597:
----------------------------------
Summary: Cannot install BPMN2 Modeler - Diagram Editor due to requires 'bundle org.eclipse.emf.validation.ocl 0.0.0' but it could not be found
Key: JBTIS-597
URL: https://issues.jboss.org/browse/JBTIS-597
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: BPMN2
Affects Versions: 4.3.0.Beta1
Environment: jboss-devstudio-9.1.0.Beta2
Reporter: Hendy Irawan
{noformat}
Cannot complete the install because one or more required items could not be found.
Software being installed: BPMN2 Modeler - Diagram Editor 1.2.3.Final-v20160226-1723-B97 (org.eclipse.bpmn2.modeler.feature.group 1.2.3.Final-v20160226-1723-B97)
Missing requirement: org.eclipse.bpmn2.modeler.core 1.2.3.Final-v20160226-1723-B97 requires 'bundle org.eclipse.emf.validation.ocl 0.0.0' but it could not be found
Cannot satisfy dependency:
From: BPMN2 Modeler - Diagram Editor 1.2.3.Final-v20160226-1723-B97 (org.eclipse.bpmn2.modeler.feature.group 1.2.3.Final-v20160226-1723-B97)
To: org.eclipse.bpmn2.modeler.core [1.2.3.Final-v20160226-1723-B97]
{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21822:
----------------------------------------
Thanks. [~fbricon] Do I interpret last comment correctly that the Eclipse project name doesn't matter for m2e? (I'd like you to answer "right, that's fine" ;) )
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Michal Jurc (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Michal Jurc commented on JBIDE-21822:
-------------------------------------
[~mickael_istria] No errors or warnings even, the root project ({{ejb-remote}}) even runs Maven install successfully without any warnings/errors.
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
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 Thomas Mäder (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Thomas Mäder reassigned JBIDE-21857:
------------------------------------
Assignee: Thomas Mäder (was: Max Rydahl Andersen)
> 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-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21822:
----------------------------------------
[~mjurc] When you import this quick start with the "Import projects from folder", then the projects are built, doesn't red cross/error markers show up on the Maven projects to highlight project/artifactId inconsistency?
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21802) Content assist for image names in "Deploy Docker Image" wizard
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21802?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-21802:
---------------------------------------
[~jcantrill], what I did in JBIDE-21868 is wait for the user to click on the {{Next}} button to fetch the metadata, indeed.
> Content assist for image names in "Deploy Docker Image" wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-21802
> URL: https://issues.jboss.org/browse/JBIDE-21802
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.3.1.CR1
>
>
> The {{Image Name}} field could be enhanced with content assist based on the list of image names+tags retrieved from the selected Docker connection.
> If the user inputs a name that does not match the list, a warning on the page would inform him/her that a remote call to the registry would be performed upon page completion, ie, when clicking on the {{Next}} button.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21822) Remote invocation problem when deploying and running EAP apps from JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21822?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21822:
----------------------------------------
The simplest action would be that the quickstart either specifies the eclipse .project to enforce Eclipse project name in whatever way they are imported, or to have the quickstart use folder name as project name.
For Easymport, that would be possible to add the ability for the "project configurator" to compute and return the desired project name, howeve, the API is in Platform and it's passed API freeze, so it's not something that can be done soon.
> Remote invocation problem when deploying and running EAP apps from JBDS
> -----------------------------------------------------------------------
>
> Key: JBIDE-21822
> URL: https://issues.jboss.org/browse/JBIDE-21822
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, server
> Affects Versions: 4.3.0.Final
> Environment: Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 2015-11-10T17:41:47+01:00)
> Maven home: /opt/apache-maven-3.3.9
> Java version: 1.8.0_74, vendor: Oracle Corporation
> Java home: /usr/java/jdk1.8.0_74/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.3-300.fc23.x86_64+debug", arch: "amd64", family: "unix"
> Fedora 23
> Reporter: Michal Jurc
> Assignee: Rob Stryker
>
> When attempting to follow the steps in ejb-remote quickstart for EAP 6.4.6.GA and 7.0.0.ER6, after deploying the server-side application, the client application has problem with remote invocation of the application deployed:
> {code}
> Exception in thread "main" java.lang.IllegalStateException: EJBCLIENT000025: No EJB receiver available for handling [appName:, moduleName:jboss-ejb-remote-server-side, distinctName:] combination for invocation context org.jboss.ejb.client.EJBClientInvocationContext@731a74c
> at org.jboss.ejb.client.EJBClientContext.requireEJBReceiver(EJBClientContext.java:798)
> at org.jboss.ejb.client.ReceiverInterceptor.handleInvocation(ReceiverInterceptor.java:128)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBClientInvocationContext.sendRequest(EJBClientInvocationContext.java:186)
> at org.jboss.ejb.client.EJBInvocationHandler.sendRequestWithPossibleRetries(EJBInvocationHandler.java:255)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:200)
> at org.jboss.ejb.client.EJBInvocationHandler.doInvoke(EJBInvocationHandler.java:183)
> at org.jboss.ejb.client.EJBInvocationHandler.invoke(EJBInvocationHandler.java:146)
> at com.sun.proxy.$Proxy0.add(Unknown Source)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.invokeStatelessBean(RemoteEJBClient.java:57)
> at org.jboss.as.quickstarts.ejb.remote.client.RemoteEJBClient.main(RemoteEJBClient.java:38)
> {code}
> The same quickstart can be completed when ran from terminal on standalone EAP (EAP not launched and managed by JBDS).
> I was so far unable to reproduce the issue on other machines.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3664?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3664:
-------------------------------------
I was testing vagrant.msi today and when running in quiet mode without UI it ignores target location defined with Public Property INSALLDIR='path/to/dir' and doesn't ask for privilege lifting, but both works for running in Basic or Reduced UI mode.
This means if we use original msi installer we have to run it with UI the same way we do for virtualbox.
> Do we still need/want custom build of vagrant ?
> -----------------------------------------------
>
> Key: JBDS-3664
> URL: https://issues.jboss.org/browse/JBDS-3664
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: installer
> Reporter: Max Rydahl Andersen
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> we seem to install use our custom vagrant build.
> Is that still relevant ?
> With that we need to test much more since our build could be different.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3682:
--------------------------------
Description:
Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
Right way to reference package json would be:
{code}var pjson = require(path.join(__dirname,'../package.json'));{code}
was:
Installer tries to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
Right way to reference package json would be:
{code}var pjson = require(path.join(__dirname,'../package.json'));{code}
> Online installer reports missing package.js file
> ------------------------------------------------
>
> Key: JBDS-3682
> URL: https://issues.jboss.org/browse/JBDS-3682
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
>
> Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
> Right way to reference package json would be:
> {code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years