July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16993) quickfixes for the issues arquillian editor finds

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16993?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-16993. ----------------------------------- Verified JBT 4.2.0 beta3 > quickfixes for the issues arquillian editor finds > ------------------------------------------------- > > Key: JBIDE-16993 > URL: https://issues.jboss.org/browse/JBIDE-16993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta3 > > Attachments: jbide-16993.png > > > I get a warnings when using the arquillian editor about me missing certain artifacts, missing profiles etc. > Might be because I dont have a pom.xml but could there be some quickfixes are explanation of what the user is expected to do ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17536) JBoss Tools Core Nightly update site fails to install if a new build is published during install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17536: ------------------------------------ Or get multiple people to make noise. Even though software isn't a democracy (as I was recently reminded) there's still the Will Of The Crowd to consider. And this: http://superherowallpapers10.net/wp-content/uploads/images/5c/v-for-vende... :D > JBoss Tools Core Nightly update site fails to install if a new build is published during install > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-17536 > URL: https://issues.jboss.org/browse/JBIDE-17536 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Beta2 > Reporter: Martin Malina > Assignee: Nick Boldt > Fix For: 4.2.0.Beta3 > > > When you install JBT nightly from http://download.jboss.org/jbosstools/updates/nightly/core/master/ into Eclipse and during the build, a new nightly build replaces the old one, you can get a failure like this: > {code}http://download.jboss.org/jbosstools/updates/nightly/core/master/features/org.jboss.tools.wtp.runtimes.tomcat.feature_1.1.0.Beta3-v20140603-0027-B526.jar cannot be found{code} > This is because during your install, the old jars were replaced with the new jars, i.e. different filenames. > I'm not sure if it's something we really need to fix, it's open for discussion. But it happened to me yesterday and it wasn't the first time, so I'm throwing it on the table. > Nick offered this alternative: > install from a specific build folder instead of the "latest nightly" > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > http://download.jboss.org/jbosstools/builds/nightly/core/master/2014-06-0... > But obviously that's just a workaround, not a real solution. > One way this could be achieved is this: plugins/ and features/ would contain jars from both the latest and previous builds. This way if you start installing (latest=build N) and in the middle of your installation there is a new build (N+1), there would still be jars for both N and N+1 builds. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2922) Epic to cover issues related to 3rd party content that does not fit in specific epic

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2922?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2922: ---------------------------------- Assuming this is a dupe of JBDS-2869, because there is no description or and there are no issues contained in this epic. > Epic to cover issues related to 3rd party content that does not fit in specific epic > ------------------------------------------------------------------------------------ > > Key: JBDS-2922 > URL: https://issues.jboss.org/browse/JBDS-2922 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2922) Epic to cover issues related to 3rd party content that does not fit in specific epic

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2922?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2922. ---------------------------- Resolution: Duplicate Issue > Epic to cover issues related to 3rd party content that does not fit in specific epic > ------------------------------------------------------------------------------------ > > Key: JBDS-2922 > URL: https://issues.jboss.org/browse/JBDS-2922 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 8.0.0.GA > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17073) Run configurations - stop button does not work

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17073?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-17073. ----------------------------------- Works in JBT 4.2.0 beta3 > Run configurations - stop button does not work > ---------------------------------------------- > > Key: JBIDE-17073 > URL: https://issues.jboss.org/browse/JBIDE-17073 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta3 > > > The stop button on Arquillian's Run configuration does not work (the server does not stop) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17700) Cannot deploy jsf war with eclipse luna and jboss 7.1.x

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17700: --------------------------------------------- [~olpf] could you run Help > Report a problem... and generate the zip and atttach it ? We really would like to see what you have installed to be able to reproduce this. all our attempts have failed yet so looking to see if you might have something installed we don't. > Cannot deploy jsf war with eclipse luna and jboss 7.1.x > ------------------------------------------------------- > > Key: JBIDE-17700 > URL: https://issues.jboss.org/browse/JBIDE-17700 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge, maven, server > Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place) > Reporter: Oliver Pfau > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.2.0.Beta3 > > Attachments: pom.xml > > > When I publish my war to jboss 7.1 the following error occurs: > An internal error occurred during: "Publishing to JBoss AS 7.1...". > Could not initialize class de.schlichtherle.io.ArchiveControllers -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17074) Order Arquillian profiles alphabetically

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17074?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-17074. ----------------------------------- Verified JBT 4.2.beta3 > Order Arquillian profiles alphabetically > ---------------------------------------- > > Key: JBIDE-17074 > URL: https://issues.jboss.org/browse/JBIDE-17074 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta3 > > > When adding Arquillian profile via right click -> Configure -> Add Arquillian Profiles these should be sorted alphabetically. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17595) Launch configuration crashes with WELD SE 1.1

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17595?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-17595. ----------------------------------- Verified JBT Beta3 > Launch configuration crashes with WELD SE 1.1 > --------------------------------------------- > > Key: JBIDE-17595 > URL: https://issues.jboss.org/browse/JBIDE-17595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.2.0.Beta2 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.0.Beta3 > > > When I add WELD SE 1.1 maven profile to the arquillian test launcher in Run as dialog it crashes (dialog disappears and cannot be open again) with the following error: > {code} > org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NoClassDefFoundError: org/jboss/weld/bootstrap/api/Bootstrap) > at org.eclipse.swt.SWT.error(SWT.java:4441) > at org.eclipse.swt.SWT.error(SWT.java:4356) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:139) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3781) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3419) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1152) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1033) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:635) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:578) > 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:379) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:233) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > 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) > Caused by: java.lang.NoClassDefFoundError: org/jboss/weld/bootstrap/api/Bootstrap > at java.lang.Class.forName0(Native Method) > at java.lang.Class.forName(Class.java:270) > at org.jboss.tools.arquillian.core.internal.util.ArquillianUtility.newInstance(ArquillianUtility.java:467) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.addContainerProperties(ArquillianUIUtil.java:527) > at org.jboss.tools.arquillian.ui.internal.utils.ArquillianUIUtil.getArquillianProperties(ArquillianUIUtil.java:482) > at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab.initializeFrom(ArquillianTab.java:639) > at org.jboss.tools.arquillian.ui.internal.launcher.ArquillianTab$1$1.run(ArquillianTab.java:151) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136) > ... 24 more > Caused by: java.lang.ClassNotFoundException: org.jboss.weld.bootstrap.api.Bootstrap > at java.lang.ClassLoader.findClass(ClassLoader.java:531) > at org.jboss.tools.arquillian.core.internal.classpath.ArquillianClassLoader.findClass(ArquillianClassLoader.java:217) > at java.lang.ClassLoader.loadClass(ClassLoader.java:425) > at java.lang.ClassLoader.loadClass(ClassLoader.java:358) > ... 33 more > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17547) Unable to download Seam 2.3 via JBoss Runtime Detection Download

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17547?page=com.atlassian.jira.plugi... ] Jiri Peterka closed JBIDE-17547. -------------------------------- Verified with JBDS 8.0.0.Beta3, GNU/Linux 64 > Unable to download Seam 2.3 via JBoss Runtime Detection Download > ---------------------------------------------------------------- > > Key: JBIDE-17547 > URL: https://issues.jboss.org/browse/JBIDE-17547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, upstream > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.B2a, L64 > Reporter: Jiri Peterka > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.2.0.Beta3 > > > An internal error occurred during: "Download 'JBoss Seam 2.3.0". > String index out of range: -1 > Relevant stacktrace : > {noformat} > java.lang.StringIndexOutOfBoundsException: String index out of range: -1 > at java.lang.String.substring(String.java:1954) > at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeOperationUtility.getNextUnusedFilename(DownloadRuntimeOperationUtility.java:56) > at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeOperationUtility.getDestinationFile(DownloadRuntimeOperationUtility.java:89) > at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeOperationUtility.downloadRemoteRuntime(DownloadRuntimeOperationUtility.java:194) > at org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimeOperationUtility.downloadAndInstall(DownloadRuntimeOperationUtility.java:155) > at org.jboss.tools.runtime.ui.internal.wizard.FinalizeRuntimeDownloadFragment$9.run(FinalizeRuntimeDownloadFragment.java:583) > {noformat} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17804) Missing Seam preference page when running on Java 6

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-17804: --------------------------------------- Summary: Missing Seam preference page when running on Java 6 Key: JBIDE-17804 URL: https://issues.jboss.org/browse/JBIDE-17804 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection, seam2 Affects Versions: 4.2.0.Beta3 Environment: java-6-openjdk-amd64, Ubuntu 12.04 Reporter: Radoslav Rábara Priority: Blocker Fix For: 4.2.0.Beta3 Seam preference page is missing when JBDS is running on Java 6. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014