[JBoss JIRA] (JBTIS-550) Update to latest Mars Graphiti 0.13
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-550?page=com.atlassian.jira.plugin.... ]
Paul Leacu edited comment on JBTIS-550 at 2/4/16 2:05 PM:
----------------------------------------------------------
Issue is a CRC error in graphiti - new graphiti due out Friday - Feb 5
https://issues.jboss.org/browse/JBDS-3586?focusedCommentId=13157181&page=...
*Reason:* Update graphiti capture to avoid crc issue
*Project page/sources:*
*Version:* S-0.13.0M5-201602031129
*License and owner:* EPL
*Original p2 repo:* http://download.eclipse.org/graphiti/updates/milestones/S-0.13.0M5-201602...
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/graphiti/S-0.13...
*Include Sources:* Yes
*Affected JBoss Tools components:* JBDSIS
*Include in JBDS:* Yes (JBDSIS)
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
=== Summary ===
[pleacu@pleacu-2-laptop x86_64]$ more ~/temp/diff-tpea
< org.eclipse.graphiti.feature.feature.group [0.13.0.v20150818-1354]
< org.eclipse.graphiti.mm [0.13.0.v20150818-1354]
< org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20150818-1354]
< org.eclipse.graphiti.ui [0.13.0.v20150818-1354]
< org.eclipse.graphiti.ui.capabilities [0.13.0.v20150818-1354]
< org.eclipse.graphiti [0.13.0.v20150818-1354]
< org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20150818-1354]
< org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20150818-1354]
< org.eclipse.graphiti.doc [0.13.0.v20150818-1354]
< org.eclipse.graphiti.pattern [0.13.0.v20150818-1354]
< org.eclipse.graphiti.feature.feature.jar [0.13.0.v20150818-1354]
< org.eclipse.graphiti.export.batik [0.13.0.v20150818-1354]
> org.eclipse.graphiti.export.feature.feature.jar [0.13.0.v20160203-1129]
> org.eclipse.graphiti.feature.feature.group [0.13.0.v20160203-1129]
> org.eclipse.graphiti.mm [0.13.0.v20160203-1129]
> org.eclipse.graphiti.feature.feature.jar [0.13.0.v20160203-1129]
> org.eclipse.graphiti.tools.newprojectwizard [0.13.0.v20160203-1129]
> org.eclipse.graphiti.pattern [0.13.0.v20160203-1129]
> org.eclipse.graphiti.doc [0.13.0.v20160203-1129]
> org.eclipse.graphiti.ui.capabilities [0.13.0.v20160203-1129]
> org.eclipse.graphiti.export.batik [0.13.0.v20160203-1129]
> org.eclipse.graphiti.ui [0.13.0.v20160203-1129]
> org.eclipse.graphiti.export.feature.feature.group [0.13.0.v20160203-1129]
> org.eclipse.graphiti [0.13.0.v20160203-1129]
=== Summary ===
file:///home/pleacu/git-clone/jbosstools-integration-stack.orig/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs
file:///home/pleacu/git-clone/jbosstools-integration-stack/target-platform/target/target-platform-ea.target.repo contains 12 unique IUs
{code}
was (Author: pleacu):
Issue is a CRC error in graphiti - new graphiti due out Friday - Feb 5
https://issues.jboss.org/browse/JBDS-3586?focusedCommentId=13157181&page=...
> Update to latest Mars Graphiti 0.13
> -----------------------------------
>
> Key: JBTIS-550
> URL: https://issues.jboss.org/browse/JBTIS-550
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Mirror latest Graphiti to JBT.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21652) We should make OS 3 application status more visible for users
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-21652:
--------------------------------------
Summary: We should make OS 3 application status more visible for users
Key: JBIDE-21652
URL: https://issues.jboss.org/browse/JBIDE-21652
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Alexey Kazakov
Fix For: 4.3.1.CR1, 4.4.0.Alpha1
Currently it can be confusing for users when an application is not available because it's building.
We should think about our options, how we could improve visibility of the application status in both OS Explorer and Servers view (for OS server adapters).
For example we could add a status line for an "application" node (or even for a project?) and show "Building..." or something if any of its services is building. We also could use a red font for such statuses. An gif icon would be ideal but I'm not sure it's technically possible.
OS Server adapter is a separate story but we need to add status for it too. Maybe it's worth a separate issue.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21651) Create and use Mars.2 RC4 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21651?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21651:
-------------------------------
Description:
Prepare new 4.52.x TPs to use Mars.2 bits.
https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
First RC4 bits should be available the week of 2/12 - 2/19, with 4.3.1.CR1 TP freeze day on Mar 1.
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
was:
Prepare new 4.52.x TPs to use Mars.2 bits.
https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day).
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
> Create and use Mars.2 RC4 target platform
> -----------------------------------------
>
> Key: JBIDE-21651
> URL: https://issues.jboss.org/browse/JBIDE-21651
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.3.1.Beta2
>
>
> Prepare new 4.52.x TPs to use Mars.2 bits.
> https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
> First RC4 bits should be available the week of 2/12 - 2/19, with 4.3.1.CR1 TP freeze day on Mar 1.
> 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)
10 years, 2 months
[JBoss JIRA] (JBIDE-21650) Make Import OS3 Application more context-oriented
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21650?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21650:
-----------------------------------------------
[~mlabuda], is not fixing JBIDE-21617 addressed that problem? Could you please verify that what [~fbricon] did (copied from his comment):
1. Only display BuildConfig selection when necessary.
2. Only display relevant BuildConfigs when selecting a project
works, and if there are use cases not covered by that fix, please describe them in this issue.
> Make Import OS3 Application more context-oriented
> -------------------------------------------------
>
> Key: JBIDE-21650
> URL: https://issues.jboss.org/browse/JBIDE-21650
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: import_wizard, openshift_v3
>
> Currently we don't make difference from where Import Application... context menu item in OpenShift Explorer view is invoked. If a connection contains 2 and more projects, and at least 2 of those projects contains a build config, there are always listed all projects with build configs in Import OpenShift Application wizard no matter what. Even if I have selected a specific service or project, invoked Import Application wizard lists all projects and build configs. It would be nice to have it more context oriented - when select Import Application... context menu item on a specific service, build config related to this service should be preselected in wizard (maybe only project where the service is located should be listed and its build configs with selected the selected one). If opened via context menu of a project, project should be preselected (maybe only project with its build config could be visible).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21205) Modify runtime detection to ensure a detector is only asked to initialize runtime definitions it created
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21205?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-21205:
-------------------------------------
The patches seem to work for me, but after fixing some NPE's, still seem to fail for Lars. Unfortunately, Lars will need to debug it because I'm having some problems setting up the environment for fuse.
> Modify runtime detection to ensure a detector is only asked to initialize runtime definitions it created
> --------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21205
> URL: https://issues.jboss.org/browse/JBIDE-21205
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha1
>
>
> See https://issues.jboss.org/browse/JBIDE-21193 for some background.
> A runtime detector is asked to initialize all RuntimeDefinition objects, not just ones it created. While this "works" if you expect a detector to know all type-strings that it creates RuntimeDefinition objects using, it is still less than optimal and the workflow is a bit counter-intuitive.
> Suggestion is to add a new constructor to RuntimeDefinition and add abstract method for creating those definitions to AbstractRuntimeDetectorDelegate to instantiate these definitions.
> Care should be taken since this is all public API and used in Fuse, cdk, servertools, and other locations. It may not be possible to compel consumers to use the new API at all, and so the benefit may be zero.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 2 months
[JBoss JIRA] (JBIDE-21651) Create and use Mars.2 RC4 target platform
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21651:
----------------------------------
Summary: Create and use Mars.2 RC4 target platform
Key: JBIDE-21651
URL: https://issues.jboss.org/browse/JBIDE-21651
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, target-platform
Affects Versions: 4.3.1.Beta1
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.3.1.Beta2
Prepare new 4.52.x TPs to use Mars.2 bits.
https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day).
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)
10 years, 2 months