[JBoss JIRA] (JBIDE-16027) Build Error when using DS security module and @Secured @Stereotype annotation
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16027?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16027 at 11/23/13 4:23 PM:
--------------------------------------------------------------
FYI, after committed change here, build is red.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
Following builds #132 and #133 are blue, so we're probably fine here.
was (Author: nickboldt):
FYI, after committed change here, build is red.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> Build Error when using DS security module and @Secured @Stereotype annotation
> -----------------------------------------------------------------------------
>
> Key: JBIDE-16027
> URL: https://issues.jboss.org/browse/JBIDE-16027
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi-extensions
> Affects Versions: 4.1.0.Final, 4.1.1.Beta1
> Environment: Win 7 / 64-bit Eclipse Kepler SR1 / 32-bit Java 1.7.0_25
> Reporter: Rainer Schön
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> When using {{(a)Secured(DecisionVoter.class)}} concept for authorization, each build ends with following build error if the method is annotated with a {{@Secured @Stereotype}} created annotation:
> {quote}
> eclipse.buildId=4.3.0.M20130911-1000
> java.version=1.7.0_25
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_CH
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product
> Error
> Tue Nov 19 13:36:27 CET 2013
> Errors running builder 'CDI (Context and Dependency Injection) Builder' on project 'ee7-web-ds-security'.
> java.lang.NullPointerException
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.findAnnotationAnnotatedWithSecurityBindingType(DeltaspikeSecurityExtension.java:161)
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.addSecurityMember(DeltaspikeSecurityExtension.java:117)
> at org.jboss.tools.cdi.deltaspike.core.DeltaspikeSecurityExtension.processAnnotatedMember(DeltaspikeSecurityExtension.java:106)
> at org.jboss.tools.cdi.internal.core.impl.definition.TypeDefinition.init(TypeDefinition.java:72)
> at org.jboss.tools.cdi.internal.core.impl.definition.AbstractMemberDefinition.setAnnotatable(AbstractMemberDefinition.java:64)
> at org.jboss.tools.cdi.internal.core.impl.definition.AbstractTypeDefinition.setType(AbstractTypeDefinition.java:69)
> at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:79)
> at org.jboss.tools.cdi.internal.core.scanner.CDIBuilderDelegate.build(CDIBuilderDelegate.java:48)
> at org.jboss.tools.cdi.core.CDICoreBuilder.invokeBuilderDelegates(CDICoreBuilder.java:326)
> at org.jboss.tools.cdi.core.CDICoreBuilder.fullBuild(CDICoreBuilder.java:261)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:221)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:733)
> 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:53)
> {quote}
> When using the {{@SecurityBindingType}} concept for authorization or the {{@Secured}} annotation directly, the build passes with no error.
> In any case, even if the build reports this error, the app is compiled correctly and deploys and works as it should.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16099) Archives can't be created for Wildfly integration tests
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16099?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-16099 at 11/23/13 1:49 PM:
--------------------------------------------------------------------
yes the wildfly integration tests are arquillian tests and thus require a widlfly server. As far as I could understand in a quick review the integration test launch a server via ant-scripts and deploy/test via arquillian
was (Author: adietish):
yes the wildfly integration tests are arquillian tests and thus require a widlfly server.
> Archives can't be created for Wildfly integration tests
> -------------------------------------------------------
>
> Key: JBIDE-16099
> URL: https://issues.jboss.org/browse/JBIDE-16099
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.Alpha2
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
>
> The Arquillian validator can't analyze some projects (Wildfly integration tests, for instance). I suppose such projects require some server at runtime.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16093:
---------------------------------------
The Java Builder fails because the Arquillian validator catches Exception when creating an archive, but Throwable (java.lang.NoClassDefFoundError, for instance) can also be thrown.
I have fixed the issue. Now, Wildfly projects are built correctly.
The Arquillian validator logs a warning if it can't create an archive.
The Arquillian validator runs only for those projects that have the Arquillian nature. Before, it ran for any project that had an Arqullian JUnit test. This will improve performance when importing a big distribution similar to Wildfly, but a user will have to add the Arquillian nature to a project if he wants to use the Eclipse Arquillian features.
The Arquillian validator won't run when importing the Wildfly distribution.
The Arquillian validator can't analyze some projects (Wildfly integration tests, for instance). I suppose such projects require some server at runtime. I have created JBIDE-16099.
The PRs:
https://github.com/jbosstools/jbosstools-arquillian/pull/36 - master
https://github.com/jbosstools/jbosstools-arquillian/pull/37 - jbosstools-4.1.x
https://github.com/jbosstools/jbosstools-arquillian/pull/38 - jbosstools-4.1.1.x
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16093:
----------------------------------
Labels: respin-a (was: )
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: respin-a
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-16093:
-------------------------------------
Assignee: Max Rydahl Andersen (was: Snjezana Peco)
Max,
Could you please review.
> NPEs when compiling wildfly codebase
> ------------------------------------
>
> Key: JBIDE-16093
> URL: https://issues.jboss.org/browse/JBIDE-16093
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-a
> Fix For: 4.1.1.CR1, 4.2.0.Alpha1
>
> Attachments: .log, npes-building-wildfly-2.png, npes-building-wildfly.png
>
>
> When having arquillian org.jboss.tools.arquillian.core_1.0.5.CR1-v20131116-1823-B79 installed and building the wildfly workspace I run into several NPEs caused by arquillian.
> !npes-building-wildfly.png!
> !npes-building-wildfly-2.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16099) Archives can't be created for Wildfly integration tests
by Snjezana Peco (JIRA)
Snjezana Peco created JBIDE-16099:
-------------------------------------
Summary: Archives can't be created for Wildfly integration tests
Key: JBIDE-16099
URL: https://issues.jboss.org/browse/JBIDE-16099
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: testing-tools
Affects Versions: 4.1.1.Alpha2
Reporter: Snjezana Peco
Assignee: Snjezana Peco
The Arquillian validator can't analyze some projects (Wildfly integration tests, for instance). I suppose such projects require some server at runtime.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16087) The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16087?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16087:
---------------------------------------
If the current selection doesn't contain a valid server, you can choose the first valid server.
You can also add a parameter to the command if you know what server should be used.
> The command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy fails when executed via a cheatsheet
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16087
> URL: https://issues.jboss.org/browse/JBIDE-16087
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Fix For: 4.2.x
>
>
> When I embed the following command in an Eclipse cheatsheet for JDF-497 :
> {noformat}
> <command
> required="false"
> serialization="org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy"/>
> {noformat}
> it fails with the following error:
> {noformat}
> !ENTRY org.eclipse.ui.cheatsheets 4 0 2013-11-21 22:50:34.494
> !MESSAGE The command did not complete successfully.
> !STACK 0
> org.eclipse.core.commands.NotHandledException: There is no handler to execute for command org.jboss.tools.livereload.openInWebBrowserViaLiveReloadProxy
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:512)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.cheatsheets.CommandRunner.executeCommand(CommandRunner.java:81)
> at org.eclipse.ui.internal.cheatsheets.data.CheatSheetCommand.execute(CheatSheetCommand.java:44)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:506)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem.runExecutable(CoreItem.java:501)
> at org.eclipse.ui.internal.cheatsheets.views.CheatSheetViewer.runPerformExecutable(CheatSheetViewer.java:1046)
> at org.eclipse.ui.internal.cheatsheets.views.CoreItem$1.linkActivated(CoreItem.java:89)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.ImageHyperlink.handleActivate(ImageHyperlink.java:199)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> 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:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {noformat}
> I'm not sure if this command is available for use in a cheatsheet, but I thought I'd report it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months