[JBoss JIRA] (JBIDE-16093) NPEs when compiling wildfly codebase
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-16093:
----------------------------------------
Assignee: Snjezana Peco
> 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
> 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 Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16093?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16093:
-------------------------------------
Attachment: npes-building-wildfly.png
npes-building-wildfly-2.png
.log
> 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
> 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 Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-16093:
----------------------------------------
Summary: 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
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-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 commented on JBIDE-16027:
------------------------------------
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-16082) Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16082?page=com.atlassian.jira.plugi... ]
Paul Richardson commented on JBIDE-16082:
-----------------------------------------
For Information:
Tested Teiid Designer with the Luna M3 target platform (4.40.0.Alpha1-SNAPSHOT) by modifying the [teiid-designer.target|https://github.com/phantomjinx/teiid-designer/blob/...] (a direct copy of the JBT-IS base target, kept in the codebase for historical reasons).
Found a single build issue due to an API incompatibility between Kepler and Luna:
{code}
[ERROR] ResourceLocator.validateHomeFolder( folderLocationValue );
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] The method validateHomeFolder(String, ResourceIdentifiers) in the type
ResourceLocator is not applicable for the arguments (String)
[ERROR] 1 problem (1 error)
{code}
This concerns the org.eclipse.datatools.connectivity.oda.flatfile.ResourceLocator class. The Kepler version of the validateHomeFolder method does the following:
{code}
if ( homeFolder == null )
throw new InvalidResourceException( InvalidResourceException.ERROR_EMPTY_RESOURCE,
Messages.getString( "connection_MISSING_HOMEFOLDER" ) ); //$NON-NLS-1$
File file = new File( homeFolder );
if ( !file.exists( ) )
throw new InvalidResourceException( InvalidResourceException.ERROR_INVALID_RESOURCE,
Messages.getString( "connection_CANNOT_OPEN_FLAT_FILE_DB_DIR" ) //$NON-NLS-1$
+ homeFolder );
{code}
To continue the same functionality of the validateHomeFolder method between Kepler and Luna, its therefore straightforward to code around this incompatibility by performing the method's File existence test directly within Designer's code.
It is noted that the Luna version of validateHomeFolder is more complex, see [here|http://git.eclipse.org/c/datatools/org.eclipse.datatools.enablement....], hence this functionality may be preferred once Luna is established and Kepler is deprecated.
This may help others who come across this particular API breakage.
> Prevent JBoss Tools 4.1 and JBDS 7.x from installing into Luna due to platform/API incompatibilities
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16082
> URL: https://issues.jboss.org/browse/JBIDE-16082
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, forge, hibernate, server, testing-tools
> Affects Versions: 4.1.1.CR1
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> We already know (from JBIDE-15639) that components like Arquillian, Forge, Server, and Hibernate will not compile with Luna dependencies due to the fact that the upstream projects on which they depend have changed in incompatible ways.
> Therefore, JBT 4.2 / JBDS 8 is being built to *ONLY work with Luna*.
> But the converse should be true, too: we don't want users installing JBT 4.1 / JBDS 7.x onto Luna and ending up with something that *doesn't work*, even if it can be installed that way.
> *Solution:*
> Update manifest.mf files to PREVENT installing key parts of JBT 4.1 / JBDS 7.x into Luna, so that no user will hit this problem.
--
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] (JBDS-2723) Fix issues found while using jsf, jsf+richfaces, springmvc, html5, livereload and browsersim
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2723?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-2723:
------------------------------------
http://download.eng.brq.redhat.com/released/JBossWFK/2.4.0/jboss-wfk-2.4....
> Fix issues found while using jsf, jsf+richfaces, springmvc, html5, livereload and browsersim
> --------------------------------------------------------------------------------------------
>
> Key: JBDS-2723
> URL: https://issues.jboss.org/browse/JBDS-2723
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: jsf, requirements, visual-page-editor-core
> Reporter: Burr Sutter
> Assignee: Radim Hopp
> Fix For: 7.1.0.GA
>
>
> Should verify we do not have broken/missing pieces when doing development on our examples - including spring based demos.
> Look at WFK demos for issues. See JBIDE-15289 for examples.
--
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-15884) Allow the runBrowserSim command to accept a URL as a parameter
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15884?page=com.atlassian.jira.plugi... ]
Vineet Reynolds updated JBIDE-15884:
------------------------------------
Affects Version/s: 4.1.0.Final
> Allow the runBrowserSim command to accept a URL as a parameter
> --------------------------------------------------------------
>
> Key: JBIDE-15884
> URL: https://issues.jboss.org/browse/JBIDE-15884
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
>
> Apologies for not setting the Affect version; I'm not sure which JBIDE version is affected.
> When creating a cheatsheet in JBDS 7.0.1.GA (for JDF-497), I'm using the {{org.jboss.tools.vpe.browsersim.eclipse.commands.runBrowserSim}} command in the cheatsheet. This launches BrowserSim successfully (when I'm in the correct perspective). However, BrowserSim navigates to about:blank so the cheatsheet requires users to manually key in the URL. It would be nice to have the launch URL specified as a configurable value.
--
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 Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16087?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-16087:
-----------------------------------------
[~fbricon], live reload integration was enabled. I also tried switching perspectives to see if it mattered.
I'll try the suggestion offered by [~snjeza] later today.
> 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