[JBoss JIRA] (JBIDE-25926) Create readme.md for this project
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-25926:
-----------------------------------
Summary: Create readme.md for this project
Key: JBIDE-25926
URL: https://issues.jboss.org/browse/JBIDE-25926
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: stack-server-protocol
Affects Versions: 4.6.0.AM1
Reporter: Rob Stryker
A readme should be made immediately to inform interested parties how to use this or run the proof-of-concept.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25925) Copy eclipse classes for IVMRunner and implementations
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25925?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-25925:
--------------------------------
Fix Version/s: 4.6.0.AM1
> Copy eclipse classes for IVMRunner and implementations
> ------------------------------------------------------
>
> Key: JBIDE-25925
> URL: https://issues.jboss.org/browse/JBIDE-25925
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: stack-server-protocol
> Reporter: Rob Stryker
> Fix For: 4.6.0.AM1
>
>
> A key part of all java-based launch configurations is IVMRunner. This class and its implementations ensure that launching an arbitrary java file can be done on all platforms. Other necessary classes will be things like wrapping the process in a RuntimeProcess object, listening for termination events, etc.
> This requires significant code from org.eclipse.core.runtime, org.eclipse.debug.core, and org.eclipse.jdt.launching.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25925) Copy eclipse classes for IVMRunner and implementations
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-25925:
-----------------------------------
Summary: Copy eclipse classes for IVMRunner and implementations
Key: JBIDE-25925
URL: https://issues.jboss.org/browse/JBIDE-25925
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: stack-server-protocol
Reporter: Rob Stryker
A key part of all java-based launch configurations is IVMRunner. This class and its implementations ensure that launching an arbitrary java file can be done on all platforms. Other necessary classes will be things like wrapping the process in a RuntimeProcess object, listening for termination events, etc.
This requires significant code from org.eclipse.core.runtime, org.eclipse.debug.core, and org.eclipse.jdt.launching.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25289) Standalone CDK configuration jenkins job (to be used in other jobs)
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25289?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25289:
----------------------------------
Fix Version/s: LATER
(was: 4.5.x)
> Standalone CDK configuration jenkins job (to be used in other jobs)
> -------------------------------------------------------------------
>
> Key: JBIDE-25289
> URL: https://issues.jboss.org/browse/JBIDE-25289
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: jenkins
> Fix For: LATER
>
>
> Every job that uses CDK needs to utilize some steps using execute shell build steps that sets up CDK and prepare it to be used by integration tests (OS or CDK itests).
> Much easier would be to have one job, that would take care of all necessary steps required to clean up/ download/ set up and/or run CDK.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-25923:
-------------------------------
Sprint: devex #148 April 2018
> Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25923
> URL: https://issues.jboss.org/browse/JBIDE-25923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Attachments: ServerAdapterEAP.gif, ServerAdapterEAPRepaired.gif
>
>
> When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log:
> {code}
> 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
> 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months