August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26256) NPE while closing JBoss Tools HTML Editor editor tab in IDE

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26256?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-26256. --------------------------------- Verified in devstudio-12.9.0.AM2-3149 > NPE while closing JBoss Tools HTML Editor editor tab in IDE > ----------------------------------------------------------- > > Key: JBIDE-26256 > URL: https://issues.jboss.org/browse/JBIDE-26256 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jst > Affects Versions: 4.9.0.AM1 > Reporter: Ondrej Dockal > Assignee: Jeff MAURY > Priority: Critical > Labels: regression > Fix For: 4.9.0.AM2 > > Attachments: html-editor-npe.png > > > I am getting NPE error dialog while closing JBoss Tools HTML Editor with opened xhtml file. Page class is told to be > org.jboss.tools.jst.jsp.jspeditor.HTMLTextEditor. > Error log message: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.ui.workbench". > {code} > Stack trace: > {code} > java.lang.NullPointerException > at org.jboss.tools.jst.web.ui.palette.PaletteAdapter.dispose(PaletteAdapter.java:233) > at org.jboss.tools.common.model.ui.views.palette.PaletteCreator.dispose(PaletteCreator.java:101) > at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.PalettePageImpl.dispose(PalettePageImpl.java:173) > at org.eclipse.gef.ui.views.palette.PaletteView.doDestroyPage(PaletteView.java:118) > at org.eclipse.ui.part.PageBookView.removePage(PageBookView.java:830) > at org.eclipse.ui.part.PageBookView.partClosed(PageBookView.java:762) > at org.eclipse.ui.part.PageBookView$1.partClosed(PageBookView.java:1038) > at org.eclipse.ui.internal.WorkbenchPage$25.run(WorkbenchPage.java:5267) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.WorkbenchPage.firePartClosed(WorkbenchPage.java:5264) > at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.lambda$0(CompatibilityPart.java:106) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40) > at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233) > at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144) > at org.eclipse.swt.widgets.Display.syncExec(Display.java:5830) > at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212) > at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:196) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) > at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) > at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) > at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60) > at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) > at org.eclipse.e4.ui.model.application.ui.impl.UIElementImpl.setWidget(UIElementImpl.java:262) > at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.unbindWidget(SWTPartRenderer.java:147) > at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.disposeWidget(SWTPartRenderer.java:170) > at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.disposeWidget(ContributedPartRenderer.java:270) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeRemoveGui(PartRenderingEngine.java:955) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$1(PartRenderingEngine.java:883) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:878) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.removeGui(PartRenderingEngine.java:862) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.subscribeTopicToBeRendered(PartRenderingEngine.java:183) > at sun.reflect.GeneratedMethodAccessor109.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55) > at org.eclipse.e4.core.di.internal.extensions.EventObjectSupplier$DIEventHandler.handleEvent(EventObjectSupplier.java:88) > at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:196) > at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1) > at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230) > at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148) > at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135) > at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78) > at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39) > at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52) > at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60) > at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374) > at org.eclipse.e4.ui.model.application.ui.impl.UIElementImpl.setToBeRendered(UIElementImpl.java:304) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.hidePart(PartServiceImpl.java:1378) > at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.hidePart(PartServiceImpl.java:1308) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.closePart(StackRenderer.java:1256) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.access$0(StackRenderer.java:1242) > at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer$3.close(StackRenderer.java:1110) > at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1958) > at org.eclipse.swt.custom.CTabFolder.lambda$0(CTabFolder.java:333) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5686) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1370) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4940) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4518) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1170) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1059) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153) > at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:625) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:560) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:152) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:656) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:592) > at org.eclipse.equinox.launcher.Main.run(Main.java:1498) > at org.eclipse.equinox.launcher.Main.main(Main.java:1471) > {code} > Session data: > {code} > eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091 > java.version=1.8.0_172 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26203) Support RHEL 7.5 in Central-CI

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26203?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-26203. --------------------------------- Done. > Support RHEL 7.5 in Central-CI > ------------------------------ > > Key: JBIDE-26203 > URL: https://issues.jboss.org/browse/JBIDE-26203 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.9.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26286) server.it.weekly build errors: baseline and build artifacts have same version but different contents

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26286?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-26286. --------------------------------- Closing, sorry for the dupe. > server.it.weekly build errors: baseline and build artifacts have same version but different contents > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-26286 > URL: https://issues.jboss.org/browse/JBIDE-26286 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, server > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > [~nickboldt], I need your help. I noticed that all of this job is red: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > For example see here: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/server.i... > {code} > 09:39:58 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.archives.scanner.feature: baseline and build artifacts have same version but different contents > 09:39:58 [ERROR] no-classifier: different > 09:39:58 [ERROR] feature.xml: different > {code} > Google suggests that it's about <baselineRepositories> and how the content compares to what's actually being built. I didn't even know such thing existed, let alone that we're using it. Do you know what's going on? > Or maybe [~rob.stryker] you know? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26036) Update bundled minishift.yaml and write unit tests for both version of CDK stack yaml files

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26036?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26036. --------------------------------- > Update bundled minishift.yaml and write unit tests for both version of CDK stack yaml files > ------------------------------------------------------------------------------------------- > > Key: JBIDE-26036 > URL: https://issues.jboss.org/browse/JBIDE-26036 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.6.0.AM2 > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Fix For: 4.9.0.AM1 > > > * Edit minishift.yaml file that resides in jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/resources to have corresponding content as jboss-stack/minishift.yaml file. We want to have the same content available when something fails to read stack's yaml file. > * Add new openshift.cdk.server unit tests for stack file (minishift.yaml online and bundled one) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26120) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [foundation]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26120?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-26120: --------------------------------------- Yeah, everything is now 4.9.0, but that's done now. > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26120 > URL: https://issues.jboss.org/browse/JBIDE-26120 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [foundation]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26120) For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [foundation]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26120?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-26120. --------------------------------- > For JBIDE 4.6.0.Final: Prepare for 4.6.0.Final / 12.0.0.GA [foundation] > ----------------------------------------------------------------------- > > Key: JBIDE-26120 > URL: https://issues.jboss.org/browse/JBIDE-26120 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: foundation > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.6.0.Final > > > For JBIDE 4.6.0.Final [foundation]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.6.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.6.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.6.0.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.80.0.Final-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.80.0.Final-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25921) MacOS machines with label mac_xhyve are not capable of running cdk.itests

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25921?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-25921. --------------------------------- > MacOS machines with label mac_xhyve are not capable of running cdk.itests > ------------------------------------------------------------------------- > > Key: JBIDE-25921 > URL: https://issues.jboss.org/browse/JBIDE-25921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, qa > Affects Versions: 4.5.3.Final > Environment: Mac OS High Sierra > Reporter: Ondrej Dockal > Assignee: Ondrej Dockal > Priority: Critical > Fix For: 4.9.0.AM1 > > > Recently, cdk.itests are not able to be run on Mac OS machines within jenkins with label mac_xhyve. > * -find out cause of instability- -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26137) Central page should display more than 5 RSS entries

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26137?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26137. ------------------------------- > Central page should display more than 5 RSS entries > --------------------------------------------------- > > Key: JBIDE-26137 > URL: https://issues.jboss.org/browse/JBIDE-26137 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.6.0.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: upstream > Fix For: 4.6.0.Final > > > No that the feed aggregate 3 data sources (developer.jboss.org, tools.jboss.org, developer.redhat.com), the Central page should display more than 5 entries -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26031) org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26031?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-26031. --------------------------------- No more configuration errors in jbosstools-vpe_master job. > org.jboss.tools.jst.web.kb.FaceletValidatorExclude references validator ids that do not exist in org.eclipse.jst.jsf > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26031 > URL: https://issues.jboss.org/browse/JBIDE-26031 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.6.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.6.0.AM3 > > > Two validator IDs are referenced which do not exist. > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.facelet.ui.FaceletHTMLValidator" but this id does not exist.{code} > {code} > 15:54:54 !MESSAGE Plug-in configuration error, extension "org.jboss.tools.jst.web.kb.FaceletValidatorExclude" > references validator id "org.eclipse.jst.jsf.ui.JSFNonELAttributeValueValidator" but this id does not exist.{code} > As seen in https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26296) Remove JBoss from maven.apt feature.properties

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26296?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-26296: ------------------------------------- Assignee: Nick Boldt (was: Martin Malina) > Remove JBoss from maven.apt feature.properties > ---------------------------------------------- > > Key: JBIDE-26296 > URL: https://issues.jboss.org/browse/JBIDE-26296 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.9.0.AM2 > > > In JBDS-4709 Nick removed all mentions of "JBoss by Red Hat" in feature.properties but there was just one occurrence left: > https://github.com/jbosstools/m2e-apt/blob/master/org.jboss.tools.maven.a... -- 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