October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18489) JavaModelException while editing code in sample project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-18489: ------------------------------------- Summary: JavaModelException while editing code in sample project Key: JBIDE-18489 URL: https://issues.jboss.org/browse/JBIDE-18489 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.2.0.CR1 Reporter: Xavier Coulon Not sure what are the steps to reproduce this problem, but here's what I had in the Error Log while testing on a sample project: {code} Java Model Exception: Java Model Status [listenToEvents(BikeStation) [in BikeStationRefreshServiceTest [in [Working copy] BikeStationRefreshServiceTest.java [in org.sample.citibikenyc.service [in src/test/java [in citibikesnyc]]]]] does not exist] at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:568) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280) at org.eclipse.jdt.internal.core.SourceMethod.getReturnType(SourceMethod.java:188) at org.jboss.tools.cdi.internal.core.impl.BeanMember.getTypeDeclaration(BeanMember.java:67) at org.jboss.tools.cdi.internal.core.impl.BeanMember.setMember(BeanMember.java:50) at org.jboss.tools.cdi.internal.core.impl.BeanMethod.setMethod(BeanMethod.java:68) at org.jboss.tools.cdi.internal.core.impl.ClassBean.cleanCache(ClassBean.java:642) at org.jboss.tools.cdi.internal.core.impl.CDIProject.rebuildBeans(CDIProject.java:1270) at org.jboss.tools.cdi.internal.core.impl.CDIProject.update(CDIProject.java:1172) at org.jboss.tools.cdi.internal.core.impl.definition.DefinitionContext.applyWorkingCopy(DefinitionContext.java:419) at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:247) at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:734) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246) at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:299) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:302) at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:358) at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:381) at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143) at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18485) NPE if repository definition doesnt contain <releases> or <snapshots>

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18485?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18485: -------------------------------- Assignee: Rastislav Wagner > NPE if repository definition doesnt contain <releases> or <snapshots> > --------------------------------------------------------------------- > > Key: JBIDE-18485 > URL: https://issues.jboss.org/browse/JBIDE-18485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.2.0.CR1 > Reporter: Rastislav Wagner > Assignee: Rastislav Wagner > Priority: Critical > Fix For: 4.2.0.CR2 > > > {code} > java.lang.NullPointerException > at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.updateRepository(AddRepositoryDialog.java:624) > at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.selectProfile(AddRepositoryDialog.java:957) > at org.jboss.tools.maven.ui.wizard.AddRepositoryDialog.createDialogArea(AddRepositoryDialog.java:306) > at org.eclipse.jface.dialogs.TitleAreaDialog.createContents(TitleAreaDialog.java:161) > at org.eclipse.jface.window.Window.create(Window.java:435) > at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1101) > at org.eclipse.jface.window.Window.open(Window.java:797) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.openEditRepositoryDialog(ConfigureMavenRepositoriesWizardPage.java:1287) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage.access$9(ConfigureMavenRepositoriesWizardPage.java:1268) > at org.jboss.tools.maven.ui.wizard.ConfigureMavenRepositoriesWizardPage$5.widgetSelected(ConfigureMavenRepositoriesWizardPage.java:407) > 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:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.jboss.tools.maven.ui.preferences.ConfiguratorPreferencePage$2.widgetSelected(ConfiguratorPreferencePage.java:156) > 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:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:832) > at org.eclipse.jface.window.Window.open(Window.java:808) > at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:221) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:66) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:519) > 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$5.handleEvent(ActionContributionItem.java:420) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3831) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3441) > 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(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.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18430) Update Thym release on TP [4.2.0 CR2]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18430?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18430: ------------------------------------ New mirror http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > Update Thym release on TP [4.2.0 CR2] > ------------------------------------- > > Key: JBIDE-18430 > URL: https://issues.jboss.org/browse/JBIDE-18430 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.CR1 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR2 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201409261806) > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-2730: -------------------------------------- What's interesting is also to see how it affects downloads from Europe as well. Please descibe the installation scenarios that you'll be trying so I can also evaluate the effect of Akamai there. > Faster download of updatesite content via akamai > ------------------------------------------------ > > Key: JBDS-2730 > URL: https://issues.jboss.org/browse/JBDS-2730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: requirements, updatesite > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.GA > > > The updatesite used by marketplace should be behind akamai for smoother/faster download. > Investigate using akamai/download.jboss.org backed storage. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18430) Update Thym release on TP [4.2.0 CR2]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18430?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18430 at 10/2/14 9:17 AM: ------------------------------------------------------------- JBIDE-17865 will require another update of THyM. was (Author: mickael_istria): JBIIDE-17865 will require another update of THyM. > Update Thym release on TP [4.2.0 CR2] > ------------------------------------- > > Key: JBIDE-18430 > URL: https://issues.jboss.org/browse/JBIDE-18430 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.0.CR1 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR2 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201409261806) > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17253) Server download wizard: T&Cs failed to be accepted

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17253?page=com.atlassian.jira.plugi... ] Jiri Pallich updated JBIDE-17253: --------------------------------- Priority: Major (was: Critical) > Server download wizard: T&Cs failed to be accepted > -------------------------------------------------- > > Key: JBIDE-17253 > URL: https://issues.jboss.org/browse/JBIDE-17253 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Michelle Murray > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > Attachments: Server_downloadT&C.png > > > 1. In Download Runtimes wizard, on JBoss.org Terms and Conditions page. > 2. Select 'Australia'. > 3. Click 'Accept Now'. > >> Error message= Unable to accept terms and conditions: Server returned HTTP response code: 400 for URL: https://www.jboss.org/download-manager/rest/tc-accept > >> Screenshot attached > Unable to proceed any further with download wizard. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2730) Faster download of updatesite content via akamai

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2730?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2730: ---------------------------------- Initial test results for Akamai staging server (devstudio.redhat.com.edgekey-staging.net): {quote} Ping tests show Akamai'd server is 1.5-2x faster than external facing server. Initial performance test results, downloading a 123M zip file VPN speed: 2.55MB/s, 48 s Public speed: 781KB/s, 2m42s Akamai'd speed (#1): 1.18MB/s, 1m45s Akamai'd speed (#2): 1.30MB/s, 95s Akamai'd speed (#3-4): 2.80-3.17MB/s, 39-44s Akamai'd speed (#5): 1.43MB/s, 86s So performance for large files is at least 2x faster than the current non-Akamai'd speed, but averages slower than the internal VPN speed Need to do some JBDS install tests (multiple small file test) next, but initial tests == very good. {quote} > Faster download of updatesite content via akamai > ------------------------------------------------ > > Key: JBDS-2730 > URL: https://issues.jboss.org/browse/JBDS-2730 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: requirements, updatesite > Reporter: Burr Sutter > Assignee: Nick Boldt > Priority: Critical > Labels: JBDS80_Approved_Scope > Fix For: 8.0.0.GA > > > The updatesite used by marketplace should be behind akamai for smoother/faster download. > Investigate using akamai/download.jboss.org backed storage. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18456) Central connectors linked to earlyaccess URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18456?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-18456. ------------------------------ Resolution: Done This was done yesterday. For example: https://github.com/jbosstools/jbosstools-discovery/commit/ff63540ff88bccd... https://github.com/jbosstools/jbosstools-discovery/commit/b1a8e3e457eb43b... Also done in master: https://github.com/jbosstools/jbosstools-discovery/commit/2811e7e04f18197... https://github.com/jbosstools/jbosstools-discovery/commit/794128979e1c1f8... > Central connectors linked to earlyaccess URLs > --------------------------------------------- > > Key: JBIDE-18456 > URL: https://issues.jboss.org/browse/JBIDE-18456 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.0.CR1 > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.2.0.CR2 > > > Some connectors on Central are actually linking to Early Access URLs. They should point to the main URL (8.0-staging/). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18457) EAP 6.1 fails to start on Windows 7 - stuck on Starting

by Jiri Pallich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18457?page=com.atlassian.jira.plugi... ] Jiri Pallich updated JBIDE-18457: --------------------------------- Priority: Major (was: Critical) > EAP 6.1 fails to start on Windows 7 - stuck on Starting > ------------------------------------------------------- > > Key: JBIDE-18457 > URL: https://issues.jboss.org/browse/JBIDE-18457 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.CR2 > > > This is followup of Brian's comments in JBIDE-16066 where he couldn't get EAP 6.1 to start on Windows 7. I tried the same and get the same result. Everything works fine on my mac. > 1. Start JBDS 8.0.0.CR1 > 2. Download EAP 6.1 via runtime detection > 3. Start the server > In my case, at first I got "Starting jboss-eap-6.1: (0 %)" in the status bar and nothing else for like 5 minutes, then the server console showed up and showed: > {code} > 15:28:51,082 INFO [org.jboss.modules] (main) JBoss Modules version 1.2.0.Final-redhat-1 > 15:28:51,704 INFO [org.jboss.msc] (main) JBoss MSC version 1.0.4.GA-redhat-1 > 15:28:51,824 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting > {code} > And with this the status bar changed to 100 % and the progress view shows: > Preparing launch deletage. > It's been like this at least 5 minutes now. The server is not started. > I checked with Brian and he just didn't witness the first part where there was no console, but he did get what I got after 5 minutes - his server was stuck and would never really start. > ATM I only tried this the one way - EAP 6.1 downloaded via runtime detection. > In my case I have Oracle jdk 1.8, in Brian's case it was 1.7, so it doesn't seem to matter. > Right now I haven't tried other server versions. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15291) xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ...

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15291?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-15291 at 10/2/14 9:11 AM: -------------------------------------------------------------- Unfortunately I'm not able to reproduce this issue on Fedora 19 64 bit KDE was (Author: vpakan): Unfortunately I'm not able to reproduce this issue > xulrunner under 64bit Linux produce "NSSUTIL_3.13 not found" and blocks marketplace, m2e connector discovery ... > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-15291 > URL: https://issues.jboss.org/browse/JBIDE-15291 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core, xulrunner > Affects Versions: 4.1.0.Final > Environment: Linux 3.8.13-gentoo #1 SMP Sun Jun 23 23:34:36 CEST 2013 x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux > IcedTea JDK 7.2.4.1 > eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz > Reporter: Jochen Buchholz > Assignee: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.1.Final > > Attachments: .log, click-on-jbosscentral-button.png, frozen-marketplace.png, gentoo.png, internal-error1.png, m2e-connectors.png > > > I installed the eclipse standard kepler and go to market place. I choose JBoss developer studio 7.0.0 GA and install it via marketplace. After the restart I choose File->Import->Maven->"checkout Maven Projects from SCM" and click on the "Find out more SCM connectors in the m2e Marketplace. I got the error: "Failed to discover all connectors." > I cant Use the Marketplace anymore, because he is frozen while load the content. > In the error log I found this line: > Caused by: java.io.IOException: /mnt/usb/eclipse/plugins/org.mozilla.xulrunner.gtk.linux.x86_64_1.9.2.19pre/xulrunner/libnssutil3.so: version `NSSUTIL_3.13' not found (required by /usr/lib64/libnss3.so) > like in the old issue JBIDE-10628 reported also by me > Developer Studio is unusable under 64bit Linux. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 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 October 2014