[JBoss JIRA] (JBIDE-21066) update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21066?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21066.
-------------------------------
Verified with 4.4.0.Alpha3 nightly.
> update tm.terminal in JBT/JBDS target platforms (was Extra step in opening terminal in git perspective?)
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21066
> URL: https://issues.jboss.org/browse/JBIDE-21066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.3.0.Final
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
> Attachments: terminal.png, Terminal.webm, tm.term.view.png
>
>
> If a user opens a terminal view from the git perspective - for example, by performing "show in" for a local repo, an empty terminal view is displayed. The user must then click on the terminal icon to actually open the terminal. This seems like an extra step - why wouldn't we open a terminal when we open the terminal view?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22443) Add to TP build a check that produced TP can be installed in target Eclipse version
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22443?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-22443 at 5/31/16 9:27 AM:
----------------------------------------------------------------
[~maxandersen] Right, that would be a good check. I actually run this sometimes locally to verify PRs for TP. Full DevStudio build takes around 15 minutes + download time for new TP bits.
was (Author: dgolovin):
[~maxandersen]Right, that would be a good check. I actually run this sometimes locally to verify PRs for TP. Full DevStudio build takes around 15 minutes + download time for new TP bits.
> Add to TP build a check that produced TP can be installed in target Eclipse version
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-22443
> URL: https://issues.jboss.org/browse/JBIDE-22443
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, target-platform
> Reporter: Mickael Istria
>
> Recently, a change in TP (jetty 9.3.6) was introduced and everything built fine with it; until the very end of the build process: during install-tests.
> This issue would *probably* have occured if trying to install all content of the TP into the target Eclipse IDE (using install-grinder or p2director or whatever installation). So it would be good to have inside the TP build (as a "verify" plugin in pom.xml) something that would try to find whether target Eclipse version and our TP are already compatible.
> Technical notes:
> * Trying to install all IUs from the release train site + our TP seems easier to implement
> * We do not need to actually install the artifacts, just making the p2 request and getting whether the request managed to find a working plan without remediation seems enough.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21439) Add JSON Editor to JBDS/JBT Target Platform
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21439?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-21439.
-------------------------------
Verifying the JSON editor is present in 4.60.0.Alpha1 and Alpha3-SNAPSHOT and it is not installed OOTB.
> Add JSON Editor to JBDS/JBT Target Platform
> -------------------------------------------
>
> Key: JBIDE-21439
> URL: https://issues.jboss.org/browse/JBIDE-21439
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Reporter: Alexey Kazakov
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
>
> Missing description. Need update site from which to fetch IUs, and a list of which IUs to add.
> Also need to know what to do with the JSON editor once it's in the TP... will it be installed OOTB like YAML editor in JBIDE-21377? Or will it be a new Central connector?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22200) Create and use Neon M7 target platform
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-22200.
-------------------------------
Verified with 4.4.0.Alpha3 and devstudio 10.0.0.Alpha3.
> Create and use Neon M7 target platform
> --------------------------------------
>
> Key: JBIDE-22200
> URL: https://issues.jboss.org/browse/JBIDE-22200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
> Attachments: p2diff_jbdevstudio_4.60.0.Alpha1-SNAPSHOT_latest.txt, p2diff_jbdevstudio_4.60.0.Alpha1-SNAPSHOT_summary_latest.txt, p2diff_jbosstools_4.60.0.Alpha1-SNAPSHOT_latest.txt, p2diff_jbosstools_4.60.0.Alpha1-SNAPSHOT_summary_latest.txt
>
>
> Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386.
> https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S...
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build;
> * update install/matrix jobs to use new Eclipse JEE/platform binary;
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months