[JBoss JIRA] (JBIDE-21579) Not able to delete service within the latest JBT
by Xia Zhao (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21579?page=com.atlassian.jira.plugi... ]
Xia Zhao updated JBIDE-21579:
-----------------------------
Environment:
OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156
OS: Fedora 17 & MAC OS 10
was:
OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
OS: Fedora 17 & MAC OS 10
> Not able to delete service within the latest JBT
> ------------------------------------------------
>
> Key: JBIDE-21579
> URL: https://issues.jboss.org/browse/JBIDE-21579
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156
> OS: Fedora 17 & MAC OS 10
> Reporter: Xia Zhao
> Labels: openshift_v3
>
> No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21579) Not able to delete service within the latest JBT
by Xia Zhao (JIRA)
Xia Zhao created JBIDE-21579:
--------------------------------
Summary: Not able to delete service within the latest JBT
Key: JBIDE-21579
URL: https://issues.jboss.org/browse/JBIDE-21579
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta2
Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
OS: Fedora 17 & MAC OS 10
Reporter: Xia Zhao
Fix For: 4.3.1.CR1
No error message pop up when attempt to port-forward to a port in use in Jboss Developer Studio. This issue does not repro in Eclipse on Mac OS.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-21441:
-----------------------------------
Description:
*Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport.
That would require to get a recent version of m2e in TP.
*Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import
*Version:* 1.7.0
*License and owner:* EPL, m2e project (Eclipse.org
*Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/
*JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160...
*Include Sources:* No
*Affected JBoss Tools components:* playground, maven
*Include in JBDS:* Yes
*Type of dependency:* distribution
*List of bundles added/removed:*
{code}
+ org.eclipse.m2e.importer
{code}
was:
*Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport.
That would require to get a recent version of m2e in TP.
*Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import
*Version:* ....
*License and owner:* ...
*Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/
*JBoss mirror:* Leave empty
*Include Sources:* Yes|No
*Affected JBoss Tools components:* ... (components that will depend on this change, jbosstools-whatever, discovery/central, JBoss Tools update-site...)
*Include in JBDS:* Yes|No
*Type of dependency:* testing|central-only|distribution
*List of bundles added/removed:*
{code}
suggested diff on the .target files
{code}
If applicable:
*non-p2 repository:* ...
*non-p2 ids:* ...
> Consume m2e Easymport integration from upstream
> -----------------------------------------------
>
> Key: JBIDE-21441
> URL: https://issues.jboss.org/browse/JBIDE-21441
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven, playground, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.x, 4.4.x
>
>
> *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport.
> That would require to get a recent version of m2e in TP.
> *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import
> *Version:* 1.7.0
> *License and owner:* EPL, m2e project (Eclipse.org
> *Original p2 repo:* http://download.eclipse.org/technology/m2e/snapshots/1.7.0/
> *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/m2e/1.7.0.20160...
> *Include Sources:* No
> *Affected JBoss Tools components:* playground, maven
> *Include in JBDS:* Yes
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> + org.eclipse.m2e.importer
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21441) Consume m2e Easymport integration from upstream
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21441?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-21441:
-----------------------------------
Description:
*Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport.
That would require to get a recent version of m2e in TP.
*Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import
*Version:* ....
*License and owner:* ...
*Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/
*JBoss mirror:* Leave empty
*Include Sources:* Yes|No
*Affected JBoss Tools components:* ... (components that will depend on this change, jbosstools-whatever, discovery/central, JBoss Tools update-site...)
*Include in JBDS:* Yes|No
*Type of dependency:* testing|central-only|distribution
*List of bundles added/removed:*
{code}
suggested diff on the .target files
{code}
If applicable:
*non-p2 repository:* ...
*non-p2 ids:* ...
was:
Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport.
That would require to get a recent version of m2e in TP.
> Consume m2e Easymport integration from upstream
> -----------------------------------------------
>
> Key: JBIDE-21441
> URL: https://issues.jboss.org/browse/JBIDE-21441
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven, playground, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.3.x, 4.4.x
>
>
> *Reason:* Now that m2e contains the easymport support ( https://bugs.eclipse.org/bugs/show_bug.cgi?id=464535 ), we should remove our support for m2e in playground and make our JBT Maven feature require Easymport.
> That would require to get a recent version of m2e in TP.
> *Project page/sources:* http://www.eclipse.org/m2e.https://wiki.eclipse.org/E4/UI/Smart_Import
> *Version:* ....
> *License and owner:* ...
> *Original p2 repo:* http://third-party-vendor.com/path/to/updates-site/
> *JBoss mirror:* Leave empty
> *Include Sources:* Yes|No
> *Affected JBoss Tools components:* ... (components that will depend on this change, jbosstools-whatever, discovery/central, JBoss Tools update-site...)
> *Include in JBDS:* Yes|No
> *Type of dependency:* testing|central-only|distribution
> *List of bundles added/removed:*
> {code}
> suggested diff on the .target files
> {code}
> If applicable:
> *non-p2 repository:* ...
> *non-p2 ids:* ...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19768:
-----------------------------------
Fix Version/s: 4.3.1.Beta1
(was: 4.3.1.Beta2)
> Add possibility to select which nested projects to import
> ---------------------------------------------------------
>
> Key: JBIDE-19768
> URL: https://issues.jboss.org/browse/JBIDE-19768
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: noteworthy
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import.
> Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19768:
-----------------------------------
Labels: noteworthy (was: )
> Add possibility to select which nested projects to import
> ---------------------------------------------------------
>
> Key: JBIDE-19768
> URL: https://issues.jboss.org/browse/JBIDE-19768
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Labels: noteworthy
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import.
> Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21558) Warning presented to user kitchensink-angular example - "Angular Eclipse" is not installable in JBoss Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21558?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21558:
---------------------------------------------
JBIDE-20609 does not solve this. One of the reasons JBIDE-20609 is not winning ;)
Fred, any reason why we are checking the plugin id and not the connector id or at least just our angular js plugin instead ?
> Warning presented to user kitchensink-angular example - "Angular Eclipse" is not installable in JBoss Central
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21558
> URL: https://issues.jboss.org/browse/JBIDE-21558
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: project-examples
> Affects Versions: 4.3.1.Beta2
> Environment: Version: 9.1.0.Beta2
> Build id: Beta2-v20160120-1207-B247
> Build date: 20160120-1207
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Attachments: 5.png
>
>
> The sequence of steps is:
> 1) Install JBDS 9.1.0.beta2 (or eclipse + JBossTools 4.3.1.Beta2)
> 2) Install kitchensink-angular sample
> 3) See screenshot - user is prevented with a warning that Eclpse Angular should be installed
> The issue at this point is that Eclipse Angular cannot be installed from JBoss Central - it must be either installed from the Eclipse Marketplace (if the user is running Eclipse + JBossTools) or directly from the plugin download site).
> If we are able to present the user with a warning during the installation process, it would be best if we could also present the user with an install path from JBoss Central.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months