November 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-17281) parent/pom.xml build/plugins should reference plugins defined build/pluginManagement

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17281?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17281: ------------------------------------ Since the one PR [1] on this topic is ancient (May 2014!) I'm inclined to close it and request that we instead either start a new one, or start moving individual requirements from plugins to pluginManagement one by one so it's easier to review & apply. [1] https://github.com/jbosstools/jbosstools-build/pull/143 [~dgolovin] WDYT? > parent/pom.xml build/plugins should reference plugins defined build/pluginManagement > ------------------------------------------------------------------------------------ > > Key: JBIDE-17281 > URL: https://issues.jboss.org/browse/JBIDE-17281 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Optional > Fix For: 4.4.x > > > The Idea is to move all what we have in build/plugins to build/pluginManagement and leave only plugins with groupId and artifactid in build/plugins. It would let to do further clean up and reduce clutter in jbosstools modules like: > - remove <version>${tychoVersion}</version> > - move jacoco plugin to tests/pom.xml > - move update site manipulations to site/pom.xml > - move ant task runner configuration to parent/pom.xml#pluginManagement node for easy reuse > - etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15332: ------------------------------------ PR has sat idle/ignored for a while now. Meanwhile we implemented skipTestsOrITests and did some refactoring of long-running ITests (the ones that depend on requirements). So... is this still needed? Or can we close / reject this? [~mickael_istria] [~rob.stryker] [~maxandersen] ? > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: LATER > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19081) Use simpler Surefire include/exclude pattern in parent pom

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19081?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19081: ------------------------------------ Do we still want to change the default include/exclude for what test classes are run, and apply that change in 4.4.x/10.0? See https://github.com/jbosstools/jbosstools-build/pull/167 for the last attempt to solve this, and its discussion. > Use simpler Surefire include/exclude pattern in parent pom > ---------------------------------------------------------- > > Key: JBIDE-19081 > URL: https://issues.jboss.org/browse/JBIDE-19081 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.4.x > > > 1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude: > {code} > include = *Test*, *Test, *TestCase > exclude = *Abstract* > {code} > 2. If that causes test failures because running incorrectly named > abstract stuff, they can refactor, add their own root pom overrides, use > a TestSuite, or use @Ignore in test classes. > 3. If the count of tests run suddenly DROPS because the pattern isn't > running the correct # of tests, they can add their own root pom > overrides, or use a TestSuite. > Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs (OS X only)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3263: ---------------------------------- PR https://github.com/jbosstools/jbosstools-build/pull/180 was not applied. [~kmarmaliykov] I can apply it in master and 4.3.x branch if it's still needed/useful. Please advise. > Remove JSF Visual/Source and Preview Tabs (OS X only) > ----------------------------------------------------- > > Key: JBDS-3263 > URL: https://issues.jboss.org/browse/JBDS-3263 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 9.0.0.CR1 > > > Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs. > http://www.screencast.com/t/wettTf6s6cU > http://www.screencast.com/t/zur1sCXmZ -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17838: ------------------------------- Fix Version/s: 4.4.x (was: 4.2.x) > Make discovery-site a Maven module > ---------------------------------- > > Key: JBIDE-17838 > URL: https://issues.jboss.org/browse/JBIDE-17838 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, discovery > Affects Versions: 4.2.0.Beta3 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.x > > > Currently, the discovery-site is generated under on of the discovery plugin. Since it's a real artifact that we copy, deploy and that depends on several modules, it would probably be easier to maintain the discovery project if we create a dedicated module for the discovery site. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21105) Deprecate BIRT

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-21105: -------------------------------------- Does QE test it manually or using any integration automated tests? Len DiMaggio? ------> Manual tests - Martin Malina is the QE owner. > Deprecate BIRT > -------------- > > Key: JBIDE-21105 > URL: https://issues.jboss.org/browse/JBIDE-21105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: birt, target-platform > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Alpha1 > > Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.png > > > {quote} > (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there > (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site > (2015-11-17 11:43:21) nickboldt: because Birt needs it > (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars > (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ? > (2015-11-17 11:43:44) maxandersen: afaik birt is dead. > (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik. > (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4? > (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy. > (2015-11-17 11:44:38) akazakov: +1 > (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in. > (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/ > (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/ > {quote} > So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > But we could also just use the old one from Mars.0: > http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201... > Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL. > *DISCUSS*. > *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21127) Can't add "Table&Columns" while using hibernate plug in Eclipse

by Steve Ebersole (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21127?page=com.atlassian.jira.plugi... ] Steve Ebersole updated JBIDE-21127: ----------------------------------- Project: Tools (JBoss Tools) (was: Hibernate Integration) Key: JBIDE-21127 (was: HIBERNATE-150) Workflow: GIT Pull Request workflow (was: classic default workflow) Security: (was: Security Issue) > Can't add "Table&Columns" while using hibernate plug in Eclipse > --------------------------------------------------------------- > > Key: JBIDE-21127 > URL: https://issues.jboss.org/browse/JBIDE-21127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Environment: eclipse.buildId=4.4.0.I20140606-1215 > java.version=1.8.0_25 > java.vendor=Oracle Corporation > BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US > Framework arguments: -product org.eclipse.epp.package.jee.product > Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product > Reporter: hu tang > Assignee: Steve Ebersole > Priority: Minor > > I used hibernate plug(JBoss Tool) in "eclipse-jee-luna-R-win32-x86_64", when I tried to add "Table&Columns" in "Hibernate Reverse Engineering Editor". It threw out an exception "Unhandled event loop exception", the details as below: I tried to reinstall both eclipse and hibernate plug but not work. > java.lang.NullPointerException > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock.doAdd(TablePropertiesBlock.java:209) > at org.hibernate.eclipse.mapper.editors.reveng.TablePropertiesBlock$1.widgetSelected(TablePropertiesBlock.java:127) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135) > 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:382) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) > at java.lang.reflect.Method.invoke(Unknown Source) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603) > at org.eclipse.equinox.launcher.Main.run(Main.java:1465) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21126) break o.j.t.cdi.deltaspike.core dependency on o.j.t.cdi.seam.solder.core

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21126?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21126: ----------------------------------- Fix Version/s: 4.4.0.Alpha1 > break o.j.t.cdi.deltaspike.core dependency on o.j.t.cdi.seam.solder.core > ------------------------------------------------------------------------ > > Key: JBIDE-21126 > URL: https://issues.jboss.org/browse/JBIDE-21126 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi-extensions > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Since seam3 isnt part of default install, this dependency should be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21126) break o.j.t.cdi.deltaspike.core dependency on o.j.t.cdi.seam.solder.core

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21126?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21126: -------------------------------------- Assignee: Viacheslav Kabanovich > break o.j.t.cdi.deltaspike.core dependency on o.j.t.cdi.seam.solder.core > ------------------------------------------------------------------------ > > Key: JBIDE-21126 > URL: https://issues.jboss.org/browse/JBIDE-21126 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdi-extensions > Affects Versions: 4.3.0.Final > Reporter: Rastislav Wagner > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.Beta1, 4.4.0.Alpha1 > > > Since seam3 isnt part of default install, this dependency should be removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19645) Remove seam 3 features from JBDS install

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19645?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19645. ---------------------------------- Fix Version/s: 4.3.0.Final (was: 4.3.1.Beta1) Resolution: Done > Remove seam 3 features from JBDS install > ---------------------------------------- > > Key: JBIDE-19645 > URL: https://issues.jboss.org/browse/JBIDE-19645 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions, central, updatesite > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.Final > > Attachments: jbds8alpha2-features-cdi-seam.png, jbds8alpha2-plugins-cdi.png, jbds8alpha2-plugins-seam.png, jbt43alpha2-features-cdi.png, jbt43alpha2-features-seam.png, jbt43alpha2-plugins-cdi.png, jbt43alpha2-plugins-seam-3-and-seam3.png, validation.png > > > Burr has requested we also remove Seam 3. So I've assumed we'll do it the same way we did for Seam 2: > * remove from CoreTools categories on update sites > * remove from JBDS core.feature > * create new connectors in JBT and JBDS Central > [~burrsutter] [~maxandersen] please confirm this is the path you want taken for all the renaming features with "seam" in their name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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 November 2015