April 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24240) Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24240?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24240: ------------------------------------ Since it's not strictly an update (but rather a patch) this behaviour is expected. We could add a NEW connector to Central if we're worried people won't find the patch. Or we could force the feature to be installed when Fuse is selected in Central, to ensure it's installed that way too. Or we could do both. WDYT, [~lhein] [~aurelien.pupier] [~jeffmaury] ? > Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x) > ----------------------------------------------------------------------------- > > Key: JBIDE-24240 > URL: https://issues.jboss.org/browse/JBIDE-24240 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.4.4.AM3, 4.4.4.Final > > Attachments: install-jbt-abridged-including-patch-feature.png, patched-in-devstudio.png, wtp383-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png, wtp383plugin-only-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png > > > the neon.3 contains a regression which is impacting a lot of m2e users and prevents Fuse Tooling to migrate to Neon.3 safely > I provided a patch to fix it and hope to have a new version of the plugin available soon, see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793#c9 > We will need to include this new version in the TP for JBoss Tools 4.4.4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24310) Add tycho.m2e 0.8.1 to Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24310?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24310: ------------------------------------ Available in Central as of 4.4.4.Final: !maven-tycho-0.8.1.png|thumbnail! > Add tycho.m2e 0.8.1 to Central > ------------------------------ > > Key: JBIDE-24310 > URL: https://issues.jboss.org/browse/JBIDE-24310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.4.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: maven-tycho-0.8.1.png > > > So that we can easily provide tycho.m2e 0.8.1 [1] to jbosstools and devstudio users, we should add it to the JBT/devstudio TPs, and make it available from Red Hat Central as a new connector. > [1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho... > This would also allow the Fuse tooling to depend on it from jbt/ds rather than it being downstream. > cc: [~jeffmaury] [~fbricon] [~aurelien.pupier] [~lhein] [~pleacu] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24310) Add tycho.m2e 0.8.1 to Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24310?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24310: ------------------------------- Attachment: maven-tycho-0.8.1.png > Add tycho.m2e 0.8.1 to Central > ------------------------------ > > Key: JBIDE-24310 > URL: https://issues.jboss.org/browse/JBIDE-24310 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central-update > Affects Versions: 4.4.4.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.Final > > Attachments: maven-tycho-0.8.1.png > > > So that we can easily provide tycho.m2e 0.8.1 [1] to jbosstools and devstudio users, we should add it to the JBT/devstudio TPs, and make it available from Red Hat Central as a new connector. > [1] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho... > This would also allow the Fuse tooling to depend on it from jbt/ds rather than it being downstream. > cc: [~jeffmaury] [~fbricon] [~aurelien.pupier] [~lhein] [~pleacu] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24240) Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x)

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24240?page=com.atlassian.jira.plugi... ] Lukáš Valach commented on JBIDE-24240: -------------------------------------- Verified, WST patch is installed as part of Abridged and BYOE and also present in Devstudio installed from jar installer. I also tried to update JBT 4.4.3 to 4.4.4 using "Check for update", it is the only case when WST patch wasn't installed. Is it a problem? User can install this patch additionaly. How to reproduce: # Install neon2 # Install JBT 4.4.3 form Eclipse Market Place # Add snapshot update site http://download.jboss.org/jbosstools/neon/snapshots/updates/ # Help -> Check for updates > Include newer version of wtp in JBT/devstudio Neon.3 target platform (4.63.x) > ----------------------------------------------------------------------------- > > Key: JBIDE-24240 > URL: https://issues.jboss.org/browse/JBIDE-24240 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.4.4.AM2 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 4.4.4.AM3, 4.4.4.Final > > Attachments: install-jbt-abridged-including-patch-feature.png, patched-in-devstudio.png, wtp383-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png, wtp383plugin-only-cannot-be-installed-in-EclipseNeon3JavaEE_EPP.png > > > the neon.3 contains a regression which is impacting a lot of m2e users and prevents Fuse Tooling to migrate to Neon.3 safely > I provided a patch to fix it and hope to have a new version of the plugin available soon, see > https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793#c9 > We will need to include this new version in the TP for JBoss Tools 4.4.4 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4361) BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop()

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4361?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4361: ----------------------------- Fix Version/s: 10.4.0.GA > BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop() > --------------------------------------------------------------------------- > > Key: JBDS-4361 > URL: https://issues.jboss.org/browse/JBDS-4361 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 10.4.0.AM3 > Environment: Fedora 24, > openjdk version "1.8.0_121", > devstudio-10.4.0.AM3-v20170410-1340-B413 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.4.0.GA > > Attachments: eclipse-log-CheckstyleUIPlugin.log > > > I saw this exception in eclipse log after installation of everything from RH Central. I see that you have met this problem in JBDS-2666 and jira was closed as 'can't reproduce'. > It seems that this error is reproducable using automated test of installation from RH Central \[1\], see builds 18-20, choose OS and open eclipse-log-startAfterInstall.log. This error is in all builds and on all systems. > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > !ENTRY net.sf.eclipsecs.ui 4 0 2017-04-12 13:10:03.802 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop() of bundle net.sf.eclipsecs.ui. > at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:850) > at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:946) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580) > at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.ExceptionInInitializerError > at net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop(CheckstyleUIPlugin.java:123) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:830) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:823) > ... 13 more > Caused by: java.lang.NullPointerException > at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:664) > at net.sf.eclipsecs.ui.CheckstyleUIPluginImages.<clinit>(CheckstyleUIPluginImages.java:95) > ... 18 more > Root exception: > java.lang.ExceptionInInitializerError > at net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop(CheckstyleUIPlugin.java:123) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:830) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:823) > at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:946) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580) > at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:664) > at net.sf.eclipsecs.ui.CheckstyleUIPluginImages.<clinit>(CheckstyleUIPluginImages.java:95) > ... 18 more > {code} > Log: [^eclipse-log-CheckstyleUIPlugin.log] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4361) BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop()

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4361?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4361: ----------------------------- Fix Version/s: (was: 10.4.0.AM3) > BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop() > --------------------------------------------------------------------------- > > Key: JBDS-4361 > URL: https://issues.jboss.org/browse/JBDS-4361 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 10.4.0.AM3 > Environment: Fedora 24, > openjdk version "1.8.0_121", > devstudio-10.4.0.AM3-v20170410-1340-B413 > Reporter: Lukáš Valach > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.4.0.GA > > Attachments: eclipse-log-CheckstyleUIPlugin.log > > > I saw this exception in eclipse log after installation of everything from RH Central. I see that you have met this problem in JBDS-2666 and jira was closed as 'can't reproduce'. > It seems that this error is reproducable using automated test of installation from RH Central \[1\], see builds 18-20, choose OS and open eclipse-log-startAfterInstall.log. This error is in all builds and on all systems. > \[1\] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > {code} > !ENTRY net.sf.eclipsecs.ui 4 0 2017-04-12 13:10:03.802 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Exception in net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop() of bundle net.sf.eclipsecs.ui. > at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:850) > at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:946) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580) > at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.ExceptionInInitializerError > at net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop(CheckstyleUIPlugin.java:123) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:830) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:823) > ... 13 more > Caused by: java.lang.NullPointerException > at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:664) > at net.sf.eclipsecs.ui.CheckstyleUIPluginImages.<clinit>(CheckstyleUIPluginImages.java:95) > ... 18 more > Root exception: > java.lang.ExceptionInInitializerError > at net.sf.eclipsecs.ui.CheckstyleUIPlugin.stop(CheckstyleUIPlugin.java:123) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:830) > at org.eclipse.osgi.internal.framework.BundleContextImpl$4.run(BundleContextImpl.java:1) > at java.security.AccessController.doPrivileged(Native Method) > at org.eclipse.osgi.internal.framework.BundleContextImpl.stop(BundleContextImpl.java:823) > at org.eclipse.osgi.internal.framework.EquinoxBundle.stopWorker0(EquinoxBundle.java:946) > at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.stopWorker(EquinoxBundle.java:314) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.decStartLevel(ModuleContainer.java:1661) > at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1580) > at org.eclipse.osgi.container.SystemModule.stopWorker(SystemModule.java:270) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule.stopWorker(EquinoxBundle.java:147) > at org.eclipse.osgi.container.Module.doStop(Module.java:636) > at org.eclipse.osgi.container.Module.stop(Module.java:498) > at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:202) > at org.eclipse.osgi.internal.framework.EquinoxBundle$SystemBundle$EquinoxSystemModule$1.run(EquinoxBundle.java:165) > at java.lang.Thread.run(Thread.java:745) > Caused by: java.lang.NullPointerException > at org.eclipse.ui.plugin.AbstractUIPlugin.imageDescriptorFromPlugin(AbstractUIPlugin.java:664) > at net.sf.eclipsecs.ui.CheckstyleUIPluginImages.<clinit>(CheckstyleUIPluginImages.java:95) > ... 18 more > {code} > Log: [^eclipse-log-CheckstyleUIPlugin.log] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4105: --------------------------------------- {quote}Yeah I understood that but any reason to put the correct metadata ie the expected behavior in Eclipse ?{quote} because we don't know what are the correct metadata > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Jeff MAURY commented on JBDS-4105: ---------------------------------- Yeah I understood that but any reason to put the correct metadata ie the expected behavior in Eclipse ? > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4364) Conflict org.testng.eclipse 6.9.13. vs 6.11.0.

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4364?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4364. ------------------------------ Resolution: Won't Fix It seems that devstudio loads newer bundle. I created simple TestNG test and it has passed. So we can ignore this error message. Closing. > Conflict org.testng.eclipse 6.9.13. vs 6.11.0. > ---------------------------------------------- > > Key: JBDS-4364 > URL: https://issues.jboss.org/browse/JBDS-4364 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.4.0.AM3 > Environment: OS: RHEL7 > RHSCL: http://download.eng.brq.redhat.com/rel-eng/RHSCL-2.4-RHEL-7-RC-1.0/compos... > Devstudio: rh-eclipse46-devstudio 10.4-0.20170421.0123.el7 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 10.4.0.GA > > > It is possible to update TestNG via RH Central. > # RH Central -> Software/Update > # Enable Early Access > # *Show installed* > # Find "TestNG" there is written "Installed, update available" > # Select TestNG and install updates > # Restart > # Then this error message will appear in the log: > {code} > !ENTRY org.testng.eclipse 4 0 2017-04-21 05:21:07.715 > !MESSAGE FrameworkEvent ERROR > !STACK 0 > org.osgi.framework.BundleException: Could not resolve module: org.testng.eclipse [1649] > Another singleton bundle selected: osgi.identity; osgi.identity="org.testng.eclipse"; type="osgi.bundle"; version:Version="6.11.0.201703011520"; singleton:="true" > {code} > Log: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Central constains org.testng.eclipse 6.11.0.201703011520, RPM contains 6.9.13.201701201452. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4105: --------------------------------------- {quote}Any reason we have put ignore instead of something else in those metadata ?{quote} Just to avoid error markers when a new project using it is created. > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 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 April 2017