August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26299) [Red Hat Central] Update to latest Sonarlint 3.6

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26299?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26299: ------------------------------- Fix Version/s: 4.9.0.AM2 > [Red Hat Central] Update to latest Sonarlint 3.6 > ------------------------------------------------ > > Key: JBIDE-26299 > URL: https://issues.jboss.org/browse/JBIDE-26299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > Pull 3.6.0 from https://eclipse-uc.sonarlint.org/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26300) [Red Hat Central] Update to latest Tern 1.x

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-26300: ---------------------------------- Summary: [Red Hat Central] Update to latest Tern 1.x Key: JBIDE-26300 URL: https://issues.jboss.org/browse/JBIDE-26300 Project: Tools (JBoss Tools) Issue Type: Bug Components: central-update Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 4.9.0.AM2 Pull 3.6.0 from https://eclipse-uc.sonarlint.org/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26180: ------------------------------------ {code} [WARNING] Found 11 duplicate jbosstools plugins: [WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_21.0.0.v20170206-1425.jar [WARNING] [1] jbosstools-multiple.target.repo/plugins/com.google.guava_15.0.0.v201403281430.jar [WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.7.0.v201011041433.jar [WARNING] [2] jbosstools-multiple.target.repo/plugins/org.apache.batik.css_1.10.0.v20180703-1553.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.7.0.v201011041433.jar [WARNING] [3] jbosstools-multiple.target.repo/plugins/org.apache.batik.util_1.10.0.v20180703-1553.jar [WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.2.0.v20180409-1502.jar [WARNING] [4] jbosstools-multiple.target.repo/plugins/org.apache.commons.logging_1.1.1.v201101211721.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_7.1.0.v20180122-2126.jar [WARNING] [5] jbosstools-multiple.target.repo/plugins/org.apache.lucene.analyzers-common_6.1.0.v20161115-1612.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_6.1.0.v20170814-1820.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_3.5.0.v20120725-1805.jar [WARNING] [6] jbosstools-multiple.target.repo/plugins/org.apache.lucene.core_7.1.0.v20171214-1510.jar [WARNING] [7] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_2.2.100.v20180626-0953.jar [WARNING] [7] jbosstools-multiple.target.repo/plugins/org.eclipse.jdt.annotation_1.1.300.v20180612-0641.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.1.1.v20180414-0329.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_6.2.0.v20180723-2102.jar [WARNING] [8] jbosstools-multiple.target.repo/plugins/org.objectweb.asm_5.0.1.v201404251740.jar [WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.2.0.v20180723-2102.jar [WARNING] [9] jbosstools-multiple.target.repo/plugins/org.objectweb.asm.tree_6.1.1.v20180414-0329.jar [WARNING] [10] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.2.v20121108-1250.jar [WARNING] [10] jbosstools-multiple.target.repo/plugins/org.slf4j.api_1.7.10.v20170428-1633.jar [WARNING] [11] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.1.v200903091627.jar [WARNING] [11] jbosstools-multiple.target.repo/plugins/org.w3c.dom.smil_1.0.0.v200806040011.jar {code} > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4723) Eclipse marketplace is missing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4723?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4723: ----------------------------- Fix Version/s: 12.9.0.GA (was: 12.0.0.GA) > Eclipse marketplace is missing > ------------------------------ > > Key: JBDS-4723 > URL: https://issues.jboss.org/browse/JBDS-4723 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, updatesite, upstream > Reporter: Anton Hughes > Assignee: Nick Boldt > Fix For: 12.9.0.GA > > > In Jboss Version: 12.0.0.GA there is no eclipse marketplace . > Im not sure if this is intentional or not. > But Im sure a lot of users, like myself, find this a bit annoying. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26180: ------------------------------------ New TP: https://github.com/jbosstools/jbosstools-target-platforms/pull/294 Building: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Results will be: http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.9... > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22138 at 8/10/18 10:53 AM: -------------------------------------------------------------------- [~rob.stryker] [~jeffmaury] I Finally found a fix in (upstream) *org.eclipse.jst.j2ee*: {code:title=org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory} protected void cleanAllDelegates() { Iterator<FlatComponentDeployable> i = moduleDelegates.values().iterator(); while(i.hasNext()) { i.next().clearCache(); } + clearModuleCache(); modulesChanged(); } + @Override + public void clearModuleCache() { + clearCache(null); + } {code} ps. notice the oddness in terms of API: {code}protected void clearCache(IProject project){code} has a parameter *IProject* but it's not being used in neither super class. I now need to build a usecase that shows the bug and then file a bugzilla. was (Author: adietish): [~rob.stryker] [~jeffmaury] I Finally found a fix in (upstream) *org.eclipse.jst.j2ee*: {code:title=org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory} protected void cleanAllDelegates() { Iterator<FlatComponentDeployable> i = moduleDelegates.values().iterator(); while(i.hasNext()) { i.next().clearCache(); } + clearModuleCache(); modulesChanged(); } + @Override + public void clearModuleCache() { + clearCache(null); + } {code} I now need to build a usecase that shows the bug and then file a bugzilla. > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.0.AM2 > > Attachments: image-2018-06-22-19-02-57-247.png > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22138: ------------------------------------------ [~rob.stryker] [~jeffmaury] I Finally found a fix in (upstream) *org.eclipse.jst.j2ee*: {code:title=org.eclipse.jst.j2ee.internal.deployables.J2EEDeployableFactory} protected void cleanAllDelegates() { Iterator<FlatComponentDeployable> i = moduleDelegates.values().iterator(); while(i.hasNext()) { i.next().clearCache(); } + clearModuleCache(); modulesChanged(); } + @Override + public void clearModuleCache() { + clearCache(null); + } {code} I now need to build a usecase that shows the bug and then file a bugzilla. > Server adapter: doesn't respect openshift maven profile > ------------------------------------------------------- > > Key: JBIDE-22138 > URL: https://issues.jboss.org/browse/JBIDE-22138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477 > Openshift plugin 3.1.0.Final-v20160401-2357-B263 > Reporter: Rafael Benevides > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.9.0.AM2 > > Attachments: image-2018-06-22-19-02-57-247.png > > > This is a follow up on JBIDE-22128. > The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes > steps: > # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.) > # EXEC: import the app into your Eclipse workspace > # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift" > # EXEC: create a server adapter and start it > # ASSERT: adapter starts syncing, verify what war is used > Result: > The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-657) Remove older bundle versions in Orbit when newer ones exist

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-657?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg commented on ERT-657: ------------------------------------- Note : a few bundles existed outside of orbit-recipes, in the old (CVS) generated repository, so they'll have to be removed manually. > Remove older bundle versions in Orbit when newer ones exist > ----------------------------------------------------------- > > Key: ERT-657 > URL: https://issues.jboss.org/browse/ERT-657 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > In Orbit, we should push to remove older bundle versions where a newer one can be used. Things like ICU4J, and the Apache Felix stack should be fine, but by declaring our intent to remove others we can also encourage people to migrate for 2018-12 (deadlines for 2018-09 M3 are fast approaching and removals into RC1 shouldn't happen). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-657) Remove older bundle versions in Orbit when newer ones exist

by Roland Grunberg (JIRA)

Roland Grunberg created ERT-657: ----------------------------------- Summary: Remove older bundle versions in Orbit when newer ones exist Key: ERT-657 URL: https://issues.jboss.org/browse/ERT-657 Project: Eclipse Release Train Issue Type: Task Reporter: Roland Grunberg Assignee: Roland Grunberg In Orbit, we should push to remove older bundle versions where a newer one can be used. Things like ICU4J, and the Apache Felix stack should be fine, but by declaring our intent to remove others we can also encourage people to migrate for 2018-12 (deadlines for 2018-09 M3 are fast approaching and removals into RC1 shouldn't happen). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ERT-657) Remove older bundle versions in Orbit when newer ones exist

by Roland Grunberg (JIRA)

[ https://issues.jboss.org/browse/ERT-657?page=com.atlassian.jira.plugin.sy... ] Roland Grunberg updated ERT-657: -------------------------------- Sprint: devex #153 August 2018 > Remove older bundle versions in Orbit when newer ones exist > ----------------------------------------------------------- > > Key: ERT-657 > URL: https://issues.jboss.org/browse/ERT-657 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Roland Grunberg > Assignee: Roland Grunberg > > In Orbit, we should push to remove older bundle versions where a newer one can be used. Things like ICU4J, and the Apache Felix stack should be fine, but by declaring our intent to remove others we can also encourage people to migrate for 2018-12 (deadlines for 2018-09 M3 are fast approaching and removals into RC1 shouldn't happen). -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018