[JBoss JIRA] (JBIDE-17836) Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17836?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-17836:
----------------------------------
Fix Version/s: 4.2.0.CR1
> Arquillian: error logged when deselecting JBOSS_AS_REMOTE_7.X maven profile
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17836
> URL: https://issues.jboss.org/browse/JBIDE-17836
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
> Attachments: screencast.ogv
>
>
> When I have JBOSS_AS_REMOTE_7.X profile selected in the launch configuration and I deselect it and select some other profile, the following error is logged in error log:
> {code}
> /home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist
> Java Model Exception: Java Model Status [/home/ljelinko/.m2/repository/org/jboss/as/jboss-as-build-config/7.1.1.Final/jboss-as-build-config-7.1.1.Final.jar does not exist]
> at org.eclipse.jdt.internal.core.JavaElement.newNotPresentException(JavaElement.java:534)
> at org.eclipse.jdt.internal.core.JarPackageFragmentRoot.getUnderlyingResource(JarPackageFragmentRoot.java:215)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder_(PackageFragmentRootTools.java:82)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools.isFolder(PackageFragmentRootTools.java:74)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:65)
> at org.eclipse.jpt.common.core.internal.utility.PackageFragmentRootTools$IsFolder.evaluate(PackageFragmentRootTools.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:80)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.next(FilteringIterator.java:68)
> at org.eclipse.jpt.common.utility.internal.iterator.TransformationIterator.next(TransformationIterator.java:54)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath_(SimpleJavaResourceLocator.java:144)
> at org.eclipse.jpt.common.core.internal.resource.SimpleJavaResourceLocator.getWorkspacePath(SimpleJavaResourceLocator.java:135)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.MavenResourceLocator.getWorkspacePath(MavenResourceLocator.java:137)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.getPersistenceXml(JpaProjectConfigurator.java:119)
> at org.eclipse.m2e.wtp.jpa.internal.configurators.JpaProjectConfigurator.configure(JpaProjectConfigurator.java:92)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:477)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:470)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:408)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:321)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:166)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:142)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:96)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1344)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:318)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:304)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:286)
> at org.eclipse.m2e.profiles.core.internal.management.ProfileManager.updateActiveProfiles(ProfileManager.java:87)
> at org.eclipse.m2e.profiles.ui.internal.actions.ProfileSelectionHandler$UpdateProfilesJob.runInWorkspace(ProfileSelectionHandler.java:319)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17749) Update AngularJS-eclipse in Central Early Access to version 0.4.0.201407021517
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17749?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17749:
----------------------------------------
Note that this PR can be tried locally, for example by:
* "mvn clean install" it
* Take a JBDS Beta3, update the jbdevstudio/studio/jbdevstudio.ini to add the following line
{code}
-Djboss.discovery.directory.url=file:/home/mistria/git/jbosstools-discovery/jbosstools/org.jboss.tools.central.discovery/target/discovery-site/jbosstools-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/core/4.2.luna/
-Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
{code}
* Try to install AngularJS
I could reproduce installation issue of JBIDE-17838 with current Central URL, and after applying this fix, I could install AngularJS.
[~vpakan]: would you mind to give it a try to validate this as a good fix?
> Update AngularJS-eclipse in Central Early Access to version 0.4.0.201407021517
> ------------------------------------------------------------------------------
>
> Key: JBIDE-17749
> URL: https://issues.jboss.org/browse/JBIDE-17749
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: discovery, target-platform
> Affects Versions: 4.2.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Priority: Critical
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Beta3
>
> Attachments: AngularJS16x16.png, AngularJS32x32.png
>
>
> We should provide an ability to install latest AngularJS-eclipse v.0.4.0.201407021517 through Central
> There is no released or latest stable version, so we should take a copy from http://oss.opensagres.fr/angularjs-eclipse/0.4.0-SNAPSHOT/ Update Site.
> [~nickboldt], please let me know if you need something more that just a link to Update Site.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17839) Cannot change jbossHome property in Arquillian launcher
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17839?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-17839:
-------------------------------------
Assignee: Snjezana Peco
> Cannot change jbossHome property in Arquillian launcher
> -------------------------------------------------------
>
> Key: JBIDE-17839
> URL: https://issues.jboss.org/browse/JBIDE-17839
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.2.0.Beta3
> Reporter: Lucia Jelinkova
> Assignee: Snjezana Peco
> Priority: Critical
>
> When I change jbossHome property in the launch configuration dialog, it is saved in arquillian.properties file. However, when I actually run the test, the following error occurs.
> {code}
> java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
> at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:160)
> at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:111)
> at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97)
> at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52)
> at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93)
> at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
> at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
> at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
> at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:156)
> ... 10 more
> Caused by: java.lang.RuntimeException: Unknown arquillian container attribute[jbossHome] with value[/home/ljelinko/programs/server/jbossas/jboss-as-7.1.1.Final]
> at org.jboss.arquillian.config.impl.extension.PropertiesParser$Container.handle(PropertiesParser.java:274)
> at org.jboss.arquillian.config.impl.extension.PropertiesParser$Handler.handle(PropertiesParser.java:354)
> at org.jboss.arquillian.config.impl.extension.PropertiesParser.addProperties(PropertiesParser.java:99)
> at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:56)
> 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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.ManagerImpl.start(ManagerImpl.java:261)
> at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.<init>(EventTestRunnerAdaptor.java:56)
> ... 15 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-17838:
-----------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
> 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
>
> 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.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17838) Make discovery-site a Maven module
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17838?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17838:
----------------------------------------
[~nickboldt] Assigning to you for review and for evaluation of impact on the publish script.
> 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
>
> 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.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17744) IndexOutOfBound exception
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17744?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-17744.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140706-0939-B172
> IndexOutOfBound exception
> -------------------------
>
> Key: JBIDE-17744
> URL: https://issues.jboss.org/browse/JBIDE-17744
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> {code}
> Java Model Exception: Java Model Status [Index out of bounds]
> at org.eclipse.jdt.internal.core.Openable.codeSelect(Openable.java:158)
> at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:377)
> at org.eclipse.jdt.internal.core.CompilationUnit.codeSelect(CompilationUnit.java:371)
> at org.jboss.tools.ws.jaxrs.ui.navigation.JaxrsNameBindingHyperlinkDetector.getSelectedElements(JaxrsNameBindingHyperlinkDetector.java:95)
> at org.jboss.tools.ws.jaxrs.ui.navigation.JaxrsNameBindingHyperlinkDetector.detectHyperlinks(JaxrsNameBindingHyperlinkDetector.java:70)
> at org.eclipse.ui.texteditor.HyperlinkDetectorRegistry$HyperlinkDetectorDelegate.detectHyperlinks(HyperlinkDetectorRegistry.java:80)
> at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:289)
> at org.eclipse.jface.text.hyperlink.HyperlinkManager.findHyperlinks(HyperlinkManager.java:261)
> at org.eclipse.jface.text.hyperlink.HyperlinkManager.mouseMove(HyperlinkManager.java:469)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:212)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> 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.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17724:
-------------------------------------
Thanks for the help [~snjeza] I'll be looking into it today.
> Changes cause full redeployment of exploded WAR
> -----------------------------------------------
>
> Key: JBIDE-17724
> URL: https://issues.jboss.org/browse/JBIDE-17724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: Windows 8.1 x64
> Java 7u51 x64
> Luna x64
> Reporter: Cody Lerum
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
>
> After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final
> This prevents any updating of JSF resources or debugging java code.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17839) Cannot change jbossHome property in Arquillian launcher
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-17839:
---------------------------------------
Summary: Cannot change jbossHome property in Arquillian launcher
Key: JBIDE-17839
URL: https://issues.jboss.org/browse/JBIDE-17839
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.2.0.Beta3
Reporter: Lucia Jelinkova
Priority: Critical
When I change jbossHome property in the launch configuration dialog, it is saved in arquillian.properties file. However, when I actually run the test, the following error occurs.
{code}
java.lang.RuntimeException: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:160)
at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:111)
at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:97)
at org.jboss.arquillian.test.spi.TestRunnerAdaptorBuilder.build(TestRunnerAdaptorBuilder.java:52)
at org.jboss.arquillian.junit.Arquillian.run(Arquillian.java:93)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:459)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:675)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:382)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:192)
Caused by: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at org.jboss.arquillian.test.spi.SecurityActions.newInstance(SecurityActions.java:156)
... 10 more
Caused by: java.lang.RuntimeException: Unknown arquillian container attribute[jbossHome] with value[/home/ljelinko/programs/server/jbossas/jboss-as-7.1.1.Final]
at org.jboss.arquillian.config.impl.extension.PropertiesParser$Container.handle(PropertiesParser.java:274)
at org.jboss.arquillian.config.impl.extension.PropertiesParser$Handler.handle(PropertiesParser.java:354)
at org.jboss.arquillian.config.impl.extension.PropertiesParser.addProperties(PropertiesParser.java:99)
at org.jboss.arquillian.config.impl.extension.ConfigurationRegistrar.loadConfiguration(ConfigurationRegistrar.java:56)
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.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
at org.jboss.arquillian.core.impl.ManagerImpl.start(ManagerImpl.java:261)
at org.jboss.arquillian.test.impl.EventTestRunnerAdaptor.<init>(EventTestRunnerAdaptor.java:56)
... 15 more
{code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17745) NPE while editing ParamConverterProvider
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17745?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-17745.
-----------------------------------
Verified with JBDS 8.0.0 Beta3-v20140706-0939-B172
> NPE while editing ParamConverterProvider
> ----------------------------------------
>
> Key: JBIDE-17745
> URL: https://issues.jboss.org/browse/JBIDE-17745
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Environment: JBoss WebServices Tools 1.7.0.Beta3-v20140702-0157-B560
> Reporter: Radoslav Rábara
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> This issues happened while I was editing ParamConverterProvider but I was not able to reproduce this issue any more.
> {code}
> org.jboss.tools.common.validation.JBTValidationException
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.addMarker(JaxrsMetamodelValidator.java:624)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validatePathParamAnnotation(JaxrsResourceMethodValidatorDelegate.java:414)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.validateNoUnboundPathParamAnnotationValues(JaxrsResourceMethodValidatorDelegate.java:316)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:94)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsResourceMethodValidatorDelegate.internalValidate(JaxrsResourceMethodValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:81)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:61)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.AbstractJaxrsElementValidatorDelegate.validate(AbstractJaxrsElementValidatorDelegate.java:1)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:494)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:433)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-17724:
---------------------------------------
The issue can be reproduced in the following way:
- create a project using the Java EE Web Project wizard
- create a Maven JAR project
- add the Maven project as a dependency to the Java EE Web project
After that, the web project is redeployed whenever editing an *xhtml file.
The issue happens because JBoss AS forces republishing if there is a zipped submodule.
Changing Application Reload Pattern doesn't help.
The issue doesn't happen on Kepler
A possible patch: https://github.com/jbosstools/jbosstools-server/pull/246
> Changes cause full redeployment of exploded WAR
> -----------------------------------------------
>
> Key: JBIDE-17724
> URL: https://issues.jboss.org/browse/JBIDE-17724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: Windows 8.1 x64
> Java 7u51 x64
> Luna x64
> Reporter: Cody Lerum
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
>
> After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final
> This prevents any updating of JSF resources or debugging java code.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months