[JBoss JIRA] (JBIDE-20997) Should not be able to create duplicative labels
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20997?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20997:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> Should not be able to create duplicative labels
> -----------------------------------------------
>
> Key: JBIDE-20997
> URL: https://issues.jboss.org/browse/JBIDE-20997
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Final
> Reporter: Marián Labuda
> Fix For: 4.4.0.Alpha1
>
>
> User should not be able to create more labels with same label name. In the table on the New OpenShift Application wizard page with resource labels there can exists more labels with same name and value. It would be nice to have similar validation in Resource Label dialog to inform user about already existing label and do not allow him to create such a label.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20976:
------------------------------------
Re: angular update, see JBIDE-21001 where we discuss the fact that the version used when building jbosstools-jst for 4.3.0.Final is NOT the version that was included in the Early Access site for 4.3.0.Final. That mismatch needs to be corrected.
> Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20976
> URL: https://issues.jboss.org/browse/JBIDE-20976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png
>
>
> Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS.
> Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer).
> Details in these logs:
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> Affected IUs (now sorted alphabetically):
> {code}
> org.eclipse.core.runtime 3.11.1.v20150903-1804
> org.eclipse.egit 4.0.2.201509141540-r
> org.eclipse.egit.core 4.0.2.201509141540-r
> org.eclipse.egit.doc 4.0.2.201509141540-r
> org.eclipse.egit.ui 4.0.2.201509141540-r
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318
> org.eclipse.jdt 3.11.1.v20150904-0015
> org.eclipse.jdt.doc.user 3.11.1.v20150819-1130
> org.eclipse.jetty.webapp 9.2.13.v20150730
> org.eclipse.jetty.xml 9.2.13.v20150730
> org.eclipse.jgit 4.0.2.201509141540-r
> org.eclipse.jgit.archive 4.0.2.201509141540-r
> org.eclipse.jst.common.frameworks 1.1.701.v201509021802
> org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356
> org.eclipse.jst.web_core.feature 3.7.1.v201509021802
> org.eclipse.jst.web_ui.feature 3.7.1.v201509021802
> org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443
> org.eclipse.pde 3.11.1.v20150904-0345
> org.eclipse.pde.doc.user 3.11.1.v20150903-1352
> org.eclipse.platform 4.5.1.v20150904-0015
> org.eclipse.platform.doc.user 4.5.1.v20150819-1130
> org.eclipse.rcp 4.5.1.v20150904-0015
> org.eclipse.sapphire 9.0.1.201509151939
> org.eclipse.sapphire.java 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939
> org.eclipse.sapphire.modeling 9.0.1.201509151939
> org.eclipse.sapphire.modeling.xml 9.0.1.201509151939
> org.eclipse.sapphire.osgi 9.0.1.201509151939
> org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939
> org.eclipse.sapphire.platform 9.0.1.201509151939
> org.eclipse.sapphire.ui 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939
> org.eclipse.sapphire.workspace 9.0.1.201509151939
> org.eclipse.sapphire.workspace.ui 9.0.1.201509151939
> org.eclipse.swt 3.104.1.v20150825-0743
> org.eclipse.wst.common_core.feature 3.7.1.v201508262220
> org.eclipse.wst.common_ui.feature 3.7.1.v201508262220
> org.eclipse.wst.jsdt.feature 1.6.201.v201508262249
> org.eclipse.wst.server.core 1.7.0.v201508271522
> org.eclipse.wst.server.discovery 1.1.0.v201508271522
> org.eclipse.wst.server.ui 1.5.201.v201509022125
> org.eclipse.wst.server_core.feature 3.3.600.v201508271522
> org.eclipse.wst.server_ui.feature 3.3.600.v201509022125
> org.eclipse.wst.validation 1.2.700.v201508251749
> org.eclipse.wst.web_core.feature 3.7.1.v201508271605
> org.eclipse.wst.web_ui.feature 3.7.1.v201509022125
> org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926
> org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-20957:
----------------------------------------
Ah, I forgot that Mickael is on PTO, will do, thank you Nick!
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
> ------------------------------------------------------------
>
> Key: JBIDE-20957
> URL: https://issues.jboss.org/browse/JBIDE-20957
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Playground]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-20957:
----------------------------------
Assignee: Alexey Kazakov (was: Mickael Istria)
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
> ------------------------------------------------------------
>
> Key: JBIDE-20957
> URL: https://issues.jboss.org/browse/JBIDE-20957
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Playground]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20957) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20957?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-20957:
------------------------------------
Since [~mickael_istria] is on PTO, could you review & apply these PRs, [~akazakov] ?
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Playground]
> ------------------------------------------------------------
>
> Key: JBIDE-20957
> URL: https://issues.jboss.org/browse/JBIDE-20957
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: playground
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Playground]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.3.1 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Playground task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-525) Ineligible update sites after installing SAP tooling
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-525:
---------------------------------------
Summary: Ineligible update sites after installing SAP tooling
Key: JBTIS-525
URL: https://issues.jboss.org/browse/JBTIS-525
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 8.0.4.CR2
Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR2
Reporter: Andrej Podhradsky
After installing SAP tooling there are ineligible update sites related to jbosstools, see the attached screenshot.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months