April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19741) jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19741?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19741: ------------------------------------ Reason I suggest we de-dupe here is that the jbosstools-src.zip is over 300M in size, and 141M of that is from javaee's included jars. (I could also just filter out the jars, but then the tests' sources won't match what's actually in github.) I'm less concerned with cluttered history / large .git folder footprint than with making our published artifacts as small & efficient as possibru. > jbosstools-javaee contains 141M of duplicate jars in its tests' projects and resources - can we minimize this? > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19741 > URL: https://issues.jboss.org/browse/JBIDE-19741 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi, jsp/jsf/xml/html source editing, seam2 > Reporter: Nick Boldt > Attachments: jars.in.javaee.list.of.dupes.with.counts.txt, jars.in.javaee.txt > > > There are 141M of binaries in the jbosstools-javaee source tree. > See attached files for details. Would it be possible to pull these jars from Maven instead of having as many as *19* copies of the same jar in the source repo? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19745) rename jbosstools-build-ci 4.3.x to jbosstools-4.3.x

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-19745: ------------------------------------------- Summary: rename jbosstools-build-ci 4.3.x to jbosstools-4.3.x Key: JBIDE-19745 URL: https://issues.jboss.org/browse/JBIDE-19745 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Max Rydahl Andersen 4.3.x is not following the convention all other repos has. lets get it renamed to jbosstools-4.3.x to avoid confusion and document in readme on master that its a legacy branch only kept there for old builds. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Len DiMaggio (JIRA)

Len DiMaggio created TOOLSDOC-640: ------------------------------------- Summary: Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS Key: TOOLSDOC-640 URL: https://issues.jboss.org/browse/TOOLSDOC-640 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Feature Request Components: General documentation issues Affects Versions: 4.3.0.Final Reporter: Len DiMaggio Assignee: Misha Ali Fix For: 4.3.0.Final This is related to: https://issues.jboss.org/browse/JBIDE-19716 The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19036) Cleanup Central TP

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19036?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19036. ------------------------------ > Cleanup Central TP > ------------------ > > Key: JBIDE-19036 > URL: https://issues.jboss.org/browse/JBIDE-19036 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: discovery > Affects Versions: 4.2.1.Final > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > It seems that the jbtcentral targetplatform contains some features that are already included in JBT and JBDS. Namely: > * org.jboss.tools.forge.feature.feature.group > * org.jboss.tools.forge.m2e.feature.feature.group > So those features should probably trimmed out of the target platform. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19744) jbosstools-build has both 4.2.x and 4.2.X and with different content

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-19744: ------------------------------------------- Summary: jbosstools-build has both 4.2.x and 4.2.X and with different content Key: JBIDE-19744 URL: https://issues.jboss.org/browse/JBIDE-19744 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.2.3.Final Reporter: Max Rydahl Andersen Priority: Critical Both https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.X and https://github.com/jbosstools/jbosstools-build/tree/jbosstools-4.2.x exist. The difference is shown here: https://github.com/jbosstools/jbosstools-build/compare/jbosstools-4.2.x..... indicating that 4.2.x builds are *not* using the released version of TP to build against - only snapshot (which should not be there if TP was released) We should get the 4.2.X deleted, but before we do - what do we do about the missing commit on 4.2.x ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-35) Add jboss-dmr 1.3.0.Final to locus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/LOCUS-35?page=com.atlassian.jira.plugin.s... ] Mickael Istria updated LOCUS-35: -------------------------------- Summary: Add jboss-dmr 1.3.0.Final to locus (was: Add jboss-dmr 1.2.2.Final to locus) > Add jboss-dmr 1.3.0.Final to locus > ---------------------------------- > > Key: LOCUS-35 > URL: https://issues.jboss.org/browse/LOCUS-35 > Project: JBoss Tools Locus > Issue Type: Feature Request > Reporter: Fred Bricon > Assignee: Mickael Istria > Fix For: 1.2.0 > > > We need to have provide jboss-dmr 1.2.2.Final as part of locus http://search.maven.org/#artifactdetails%7Corg.jboss%7Cjboss-dmr%7C1.2.2.... > {noformat}<dependency> > <groupId>org.jboss</groupId> > <artifactId>jboss-dmr</artifactId> > <version>1.2.2.Final</version> > </dependency>{noformat} > This will be consumed by foundation, server, central and probably other components -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3431) Update JBDS support matrix to include only major version of EAP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3431?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3431: ---------------------------------- Would this change affect only 8.x and 9.x (moving forward) or be retroactive to earlier versions of JBDS/JBDS IS too? Note I can update the community doc too, if we want: https://community.jboss.org/wiki/MatrixOfSupportedPlatformsRuntimesAndTec... > Update JBDS support matrix to include only major version of EAP > --------------------------------------------------------------- > > Key: JBDS-3431 > URL: https://issues.jboss.org/browse/JBDS-3431 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation > Affects Versions: 8.1.0.GA > Reporter: Mustafa Musaji > Assignee: Misha Ali > > Update this page https://access.redhat.com/articles/427493 > So that we only include the major versions of EAP supported > I.e. 4.x, 5.x and 6.x -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-19704: ------------------------------------- I think simple pages should be displayed correctly and we should not confuse users with different rendering in Visual part of Visual/Source tab of VPE and Visual tab of VPE. > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19743) Execution of criteria query shows <null> result

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-19743: ------------------------------------ Summary: Execution of criteria query shows <null> result Key: JBIDE-19743 URL: https://issues.jboss.org/browse/JBIDE-19743 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 4.3.0.Beta1 Environment: JBDS 9.0.0.Beta1 - nightly 20150430, L64 Reporter: Jiri Peterka Priority: Blocker Fix For: 4.3.0.Beta1 There is null result after executing Criteria query: {code} !ENTRY org.jboss.tools.hibernate.runtime.common 4 0 2015-04-30 15:16:16.562 !MESSAGE org.hibernate.impl.CriteriaImpl.setMaxResults() !STACK 0 java.lang.NoSuchMethodException: org.hibernate.impl.CriteriaImpl.setMaxResults() at java.lang.Class.getMethod(Class.java:1773) at org.jboss.tools.hibernate.runtime.common.Util.invokeMethod(Util.java:39) at org.jboss.tools.hibernate.runtime.common.AbstractCriteriaFacade.list(AbstractCriteriaFacade.java:39) 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:483) at bsh.Reflect.invokeMethod(Unknown Source) at bsh.Reflect.invokeObjectMethod(Unknown Source) at bsh.BSHPrimarySuffix.doName(Unknown Source) at bsh.BSHPrimarySuffix.doSuffix(Unknown Source) at bsh.BSHPrimaryExpression.eval(Unknown Source) at bsh.BSHPrimaryExpression.eval(Unknown Source) at bsh.Interpreter.eval(Unknown Source) at bsh.Interpreter.eval(Unknown Source) at bsh.Interpreter.eval(Unknown Source) at org.hibernate.eclipse.console.common.JavaPage.setSession(JavaPage.java:73) at org.hibernate.eclipse.console.common.HibernateExtension$3.execute(HibernateExtension.java:127) at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) at org.hibernate.eclipse.console.common.HibernateExtension.execute(HibernateExtension.java:189) at org.hibernate.eclipse.console.common.HibernateExtension.executeCriteriaQuery(HibernateExtension.java:123) at org.hibernate.console.ConsoleConfiguration.executeBSHQuery(ConsoleConfiguration.java:313) at org.hibernate.eclipse.criteriaeditor.CriteriaEditor.executeQuery(CriteriaEditor.java:142) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.execute(ExecuteQueryAction.java:82) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.run(ExecuteQueryAction.java:55) at org.eclipse.jface.action.Action.runWithEvent(Action.java:473) at org.hibernate.eclipse.console.actions.ExecuteQueryAction.runWithEvent(ExecuteQueryAction.java:59) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:462) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4477) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1322) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1346) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1331) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1116) at org.jboss.reddeer.core.handler.WidgetHandler$4.run(WidgetHandler.java:332) at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:193) at org.jboss.reddeer.core.util.Display$VoidResultRunnable.run(Display.java:1) at org.jboss.reddeer.core.util.Display$ErrorHandlingRunnable.run(Display.java:159) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3790) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1112) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:993) at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) at org.jboss.reddeer.eclipse.core.UITestApplication.start(UITestApplication.java:47) 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:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) 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:483) 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) at org.eclipse.equinox.launcher.Main.main(Main.java:1438) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19697: ---------------------------------------- The preference in oomph are probably not stored in the regular preference format, so looking for the file may not be enough. There are 2 parts of Oomph: recording and storing preferences, and applying them to a new instance. Disabling the preference recorder only covers the first part. I don't know whether the part about restoring preferences can be controlled. > org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19697 > URL: https://issues.jboss.org/browse/JBIDE-19697 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.3.0.Alpha2 > Reporter: Martin Malina > Assignee: Snjezana Peco > Attachments: preference-recorder.png > > > When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs' > Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs > {code} > This is inside the file: > {code} > $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat > eclipse.preferences.version=1 > runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n > {code} > It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen? > I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now. > Can somebody explain what's going on? > Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015