[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ]
Paul Leacu updated JBTIS-1015:
------------------------------
Attachment: a5.png
a4.png
a3.png
a2.png
a1.png
> Latest JBDSIS Target Platform cannot be used locally
> ----------------------------------------------------
>
> Key: JBTIS-1015
> URL: https://issues.jboss.org/browse/JBTIS-1015
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: a1.png, a2.png, a3.png, a4.png, a5.png
>
>
> Current state of understanding:
> There are 2 different bugs:
> * when using local "Directory": the jars which should be exploded in folder stay in jars
> ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself?
> ** the implication is that we can't start a CDK server with such a TP
> * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance)
> ** looks like a p2 bugs
> ** the implication is that the TP doesn't resolve at all
> If one of these two bugs can be fixed, we will have a way to consume a local Target Platform.
> see [JBTIS-1008] for original discussions
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-23678:
-------------------------------
Description:
Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
Install manifest contains:
* org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
* 1.6.201 (2 versions), and
* 2.0.200 (1 version) - *total 7 references*!
Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
was:
Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515.
Install manifest contains:
* org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
* 1.6.201 (2 versions), and
* 2.0.200 (1 version) - *total 7 references*!
Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have newer versions of JSON/JSDT plugins in our target platform than are in Neon.2.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23515) Create and use Neon.2 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23515?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23515:
------------------------------------
Note: current 4.62.0.AM1-SNAPSHOT target platform includes Neon.2 bits and also the latest WTP M3.8.2 bits, which were NOT released to Neon.2 (but which contain fixes for these features:
{code}
org.eclipse.wst.json_core.feature.feature.group 1.0.2.v201610212029
org.eclipse.wst.json_ui.feature.feature.group 1.0.2.v201610212029
org.eclipse.wst.jsdt.feature.feature.group 2.0.200.v201610280128
org.eclipse.wst.xml_ui.feature.feature.group 3.8.2.v201610032207
{code}
We're also including m2e 1.7.1, which is newer than Neon.2's 1.7.0 version. 1.7.1 should be included in Neon.3, eventually.
{code}
org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805
{code}
> Create and use Neon.2 target platform
> -------------------------------------
>
> Key: JBIDE-23515
> URL: https://issues.jboss.org/browse/JBIDE-23515
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: target-platform
> Affects Versions: 4.4.1.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.4.3.Final
>
>
> Once available in December, we should move up to Neon.2
> 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
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23711) "Edit default route" on Build config does nothing
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-23711:
----------------------------------
Summary: "Edit default route" on Build config does nothing
Key: JBIDE-23711
URL: https://issues.jboss.org/browse/JBIDE-23711
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.3.AM1
Reporter: Radim Hopp
Context menu of build configs in properties view has entry "Edit default route..." which does nothing. Is it even supposed to be there?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23710) Disable scaling on completed deployments
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-23710:
----------------------------------
Summary: Disable scaling on completed deployments
Key: JBIDE-23710
URL: https://issues.jboss.org/browse/JBIDE-23710
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.4.3.AM1
Reporter: Radim Hopp
In web console, scaling completed deployments is disabled.
In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift.
Sometimes I also got this exception (but not allways):
{noformat}
!ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562
!MESSAGE Unable to scale wildfly-1
!STACK 0
com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
at okhttp3.RealCall.execute(RealCall.java:57)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{noformat}
I think we should do the same as web console -> disable scaling options on completed deployments.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-23678 at 1/10/17 10:56 AM:
--------------------------------------------------------------
Smoke test shows the problem w/ ide-config.properties was a red herring (but I'm glad I fixed it!)
Real issue is that EPP packages for Java and JavaEE contain different (older) versions of features than we have in our 4.62.x target platforms, because I pulled a maintenance build of WTP 3.8.2 which I assumed would be released to Neon.2... but was not.
{code}
JavaEE Neon.2 bundle:
./features/org.eclipse.wst.json_core.feature_1.0.0.v201609072018 (installed)
./features/org.eclipse.wst.json_ui.feature_1.0.0.v201609072018 (installed)
./features/org.eclipse.wst.jsdt.feature_2.0.0.v201608301904 (installed)
Neon.2 TP site, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
org.eclipse.wst.json_core.feature.feature.group 1.0.2.v201610212029 (from WTP M3.8.2 site)
org.eclipse.wst.json_ui.feature.feature.group 1.0.2.v201610212029 (from WTP M3.8.2 site)
org.eclipse.wst.jsdt.feature.feature.group 2.0.200.v201610280128 (from WTP M3.8.2 site)
Neon.x release site as of Jan 10:
org.eclipse.wst.json_core.feature.feature.group 1.0.0.v201609072018 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.wst.json_ui.feature.feature.group 1.0.0.v201609072018 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
{code}
{code}
Java Neon.2 bundle:
./features/org.eclipse.wst.xml_ui.feature_3.8.0.v201608061842 (installed)
./features/org.eclipse.m2e.feature_1.7.0.20160603-1933 (installed)
Neon.2 TP site
org.eclipse.wst.xml_ui.feature.feature.group 3.8.2.v201610032207 (from WTP M3.8.2 site)
org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 (not in Neon.2 - released by Fred separately but not included in Neon.2)
Neon.x release site as of Jan 10:
org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201608061842 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933 (version from Neon.0, Neon.1 and Neon.2)
{code}
was (Author: nickboldt):
Smoke test shows the problem w/ ide-config.properties was a red herring (but I'm glad I fixed it!)
Real issue is that EPP packages for Java and JavaEE contain different (older) versions of features than we have in our 4.62.x target platforms, because I pulled a maintenance build of WTP 3.8.2 which I assumed would be released to Neon.2... but was not.
{code}
JavaEE Neon.2 bundle:
./features/org.eclipse.wst.json_core.feature_1.0.0.v201609072018
./features/org.eclipse.wst.json_ui.feature_1.0.0.v201609072018
./features/org.eclipse.wst.jsdt.feature_2.0.0.v201608301904
Neon.2 TP site, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
org.eclipse.wst.json_core.feature.feature.group 1.0.2.v201610212029 (from WTP M3.8.2 site)
org.eclipse.wst.json_ui.feature.feature.group 1.0.2.v201610212029 (from WTP M3.8.2 site)
org.eclipse.wst.jsdt.feature.feature.group 2.0.200.v201610280128 (from WTP M3.8.2 site)
Neon.x release site as of Jan 10:
org.eclipse.wst.json_core.feature.feature.group 1.0.0.v201609072018 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.wst.json_ui.feature.feature.group 1.0.0.v201609072018 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
{code}
{code}
Java Neon.2 bundle:
./features/org.eclipse.wst.xml_ui.feature_3.8.0.v201608061842 (installed)
./features/org.eclipse.m2e.feature_1.7.0.20160603-1933 (installed)
Neon.2 TP site
org.eclipse.wst.xml_ui.feature.feature.group 3.8.2.v201610032207 (from WTP M3.8.2 site)
org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 (not in Neon.2 - released by Fred separately but not included in Neon.2)
Neon.x release site as of Jan 10:
org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201608061842 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933 (version from Neon.0, Neon.1 and Neon.2)
{code}
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23678) remediation required installing jbosstools 4.4.3.AM1 on Neon.2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23678?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-23678:
------------------------------------
Smoke test shows the problem w/ ide-config.properties was a red herring (but I'm glad I fixed it!)
Real issue is that EPP packages for Java and JavaEE contain different (older) versions of features than we have in our 4.62.x target platforms, because I pulled a maintenance build of WTP 3.8.2 which I assumed would be released to Neon.2... but was not.
{code}
JavaEE Neon.2 bundle:
./features/org.eclipse.wst.json_core.feature_1.0.0.v201609072018
./features/org.eclipse.wst.json_ui.feature_1.0.0.v201609072018
./features/org.eclipse.wst.jsdt.feature_2.0.0.v201608301904
Neon.2 TP site, http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
org.eclipse.wst.json_core.feature.feature.group 1.0.2.v201610212029 (from WTP M3.8.2 site)
org.eclipse.wst.json_ui.feature.feature.group 1.0.2.v201610212029 (from WTP M3.8.2 site)
org.eclipse.wst.jsdt.feature.feature.group 2.0.200.v201610280128 (from WTP M3.8.2 site)
Neon.x release site as of Jan 10:
org.eclipse.wst.json_core.feature.feature.group 1.0.0.v201609072018 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.wst.json_ui.feature.feature.group 1.0.0.v201609072018 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
{code}
{code}
Java Neon.2 bundle:
./features/org.eclipse.wst.xml_ui.feature_3.8.0.v201608061842 (installed)
./features/org.eclipse.m2e.feature_1.7.0.20160603-1933 (installed)
Neon.2 TP site
org.eclipse.wst.xml_ui.feature.feature.group 3.8.2.v201610032207 (from WTP M3.8.2 site)
org.eclipse.m2e.feature.feature.group 1.7.1.20161104-1805 (not in Neon.2 - released by Fred separately but not included in Neon.2)
Neon.x release site as of Jan 10:
org.eclipse.wst.xml_ui.feature.feature.group 3.8.0.v201608061842 (from WTP R3.8.1 site - same bits from Neon.1 and Neon.2)
org.eclipse.m2e.feature.feature.group 1.7.0.20160603-1933 (version from Neon.0, Neon.1 and Neon.2)
{code}
> remediation required installing jbosstools 4.4.3.AM1 on Neon.2
> --------------------------------------------------------------
>
> Key: JBIDE-23678
> URL: https://issues.jboss.org/browse/JBIDE-23678
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.3.AM2
>
> Attachments: remediation-required-jbt443am1.png, remediation-required-jbt443am1_skip_items.png, remediation-required-jbt443am1_upgrades.png
>
>
> Remediation required for installing jbosstools 4.4.3.AM1 -- seems we have older versions of JSON/JSDT plugins than are in Neon.2. Need to update our TP - JBIDE-23515.
> Install manifest contains:
> * org.eclipse.wst.jsdt.feature 2.0.0 (4 versions),
> * 1.6.201 (2 versions), and
> * 2.0.200 (1 version) - *total 7 references*!
> Also, org.eclipse.wst.web_ui.feature.feature.group depends on org.eclipse.wst.jsdt.feature.feature.group, which pulls in another ref/requirement.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-23642) [baseline compare check] plugins in jbosstools-server need to be upversioned so they're greater than versions in last stable jbosstools site
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23642?page=com.atlassian.jira.plugi... ]
Jan Richter closed JBIDE-23642.
-------------------------------
Closing, since build is blue now.
> [baseline compare check] plugins in jbosstools-server need to be upversioned so they're greater than versions in last stable jbosstools site
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23642
> URL: https://issues.jboss.org/browse/JBIDE-23642
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.3.AM1
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.3.AM1
>
>
> Building jbosstools-server from master branch, after releasing JBoss Tools 4.4.2.Final to the stable site [1] on Dec 8 last week:
> {code}
> mvn clean install -DskipTests -DskipBaselineComparison=false{code}
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.archives.ui: Duplicate version but different content found for (org.jboss.ide.eclipse.archives.ui/3.6.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.archives.scanner.feature: Duplicate version but different content found for (org.jboss.tools.archives.scanner.feature.feature.jar/3.6.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.classpath.core: Duplicate version but different content found for (org.jboss.ide.eclipse.as.classpath.core/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.doc.user: Duplicate version but different content found for (org.jboss.ide.eclipse.as.doc.user/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.ui.mbeans: Duplicate version but different content found for (org.jboss.ide.eclipse.as.ui.mbeans/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.rse.core: Duplicate version but different content found for (org.jboss.ide.eclipse.as.rse.core/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.management.as7: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.as7/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.management.eap61plus: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.eap61plus/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.ide.eclipse.as.management.wildfly9: Duplicate version but different content found for (org.jboss.ide.eclipse.as.management.wildfly9/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.as.catalog: Duplicate version but different content found for (org.jboss.tools.as.catalog/3.2.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.jmx.local: Duplicate version but different content found for (org.jboss.tools.jmx.local/1.8.2.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.wtp.runtimes.tomcat: Duplicate version but different content found for (org.jboss.tools.wtp.runtimes.tomcat/1.3.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:0.26.0:compare-version-with-baselines (default) on project org.jboss.tools.wtp.server.launchbar.feature: Duplicate version but different content found for (org.jboss.tools.wtp.server.launchbar.feature.source.feature.jar/1.3.102.v20161121-2100). Also exists in baseline, but its content is different. -> [Help 1]
> {code}
> [1] <lastStableRepository>http://download.jboss.org/jbosstools/neon/stable/updates/</lastStableRepository> - https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22816) Create application from image (or builder) may lead to update being detected
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22816?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22816:
-------------------------------
Story Points: 0 (was: 8)
> Create application from image (or builder) may lead to update being detected
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22816
> URL: https://issues.jboss.org/browse/JBIDE-22816
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.AM2
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.3.AM2
>
>
> When creating a new application from image or builder, an update may be detected and no resources being created. The pb is that the model is set to the Openshift project and asynchronously updated the get the list of projects that will set the Openshift project to the first thus misleading the rest of the processing
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBIDE-22805) Add Scale... menus on Pod resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22805?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22805:
------------------------------------------
[~jrichter1] thx for spotting this missing piece. I filed it to JBIDE-23709. Closing this as verified.
> Add Scale... menus on Pod resources
> -----------------------------------
>
> Key: JBIDE-22805
> URL: https://issues.jboss.org/browse/JBIDE-22805
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.4.1.AM1
> Reporter: Fred Bricon
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.4.3.AM2
>
>
> I'm regularly confused/frustrated to not find the Scale... menus on the running pods. Each time I need to slap myself in the face to remind me I need to go to the Service level.
> I think it'd be more intuitive if the scale menus were present on the running pods (not on the build ones).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months