[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25597:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.6.0.AM1)
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final, 4.6.x
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25597:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.6.x*
> TP: create target platforms based on Eclipse Photon
> ---------------------------------------------------
>
> Key: JBIDE-25597
> URL: https://issues.jboss.org/browse/JBIDE-25597
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.5.2.Final
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Labels: target-platform
> Fix For: 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final, 4.6.x
>
> Attachments: base.log
>
>
> In order to start Photon based builds, we need a working Photon based target platform
> For sprint 148 / AM1: Photon.0.M6
> For sprint 149 / AM2: Photon.0.M7
> For sprint 150 / AM3: Photon.0.RC3
> For sprint 151 / GA: Photon.0.GA
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25974) CDK 3.4 runtime detection failing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25974?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25974:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.6.x*
> CDK 3.4 runtime detection failing
> ---------------------------------
>
> Key: JBIDE-25974
> URL: https://issues.jboss.org/browse/JBIDE-25974
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.6.x
>
> Attachments: image-2018-05-07-17-59-59-316.png
>
>
> Runtime detection doesn't work for 3.4.0 with the whitelist. A regex would be better
> steps:
> # EXE: Preferences > JBoss Runtime Detection > Download
> # ASSERT: List of available runtimes shows up, containing CDK 3.4.0
> # EXEC: Choose "CDK 3.4.0" & hit "Next"
> # EXEC: next page: provide credentials & hit "Next"
> # EXEC: next page: accept the terms & hit "Next"
> # EXEC: next page: use the suggested defaults, make sure that "Install folder" is a separate folder (ex. freshly created ~/cdk/) & hit "Finish"
> # ASSERT: wait for the download to finish
> Result:
> The download wont detect the new CDK 3.4.0 that you just downloaded
> !image-2018-05-07-17-59-59-316.png!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 10 months
[JBoss JIRA] (JBIDE-25925) Copy eclipse classes for IVMRunner and implementations
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25925?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25925:
-------------------------------
Fix Version/s: 4.6.x
(was: 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.x
>
>
> 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, 10 months
[JBoss JIRA] (JBIDE-25925) Copy eclipse classes for IVMRunner and implementations
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25925?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25925:
------------------------------------
[checkUnresolvedIssues.py] Slip to fixversion = *4.6.x*
> 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.x
>
>
> 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, 10 months