September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15493) Cleanup as.classpath.core plugin organization

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15493?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-15493. --------------------------------- Resolution: Done pushed to master. Just a re-org. No new features. > Cleanup as.classpath.core plugin organization > --------------------------------------------- > > Key: JBIDE-15493 > URL: https://issues.jboss.org/browse/JBIDE-15493 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Much of the code should be internal, so this needs to be cleaned up a bit. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15493) Cleanup as.classpath.core plugin organization

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15493: ----------------------------------- Summary: Cleanup as.classpath.core plugin organization Key: JBIDE-15493 URL: https://issues.jboss.org/browse/JBIDE-15493 Project: Tools (JBoss Tools) Issue Type: Task Components: server Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 4.2.0.Alpha1 Much of the code should be internal, so this needs to be cleaned up a bit. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15363) CLONE - NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15363?page=com.atlassian.jira.plugi... ] Jakub Niedermertl closed JBIDE-15363. ------------------------------------- ok, closing Version: 7.1.0.Alpha1 Build id: Alpha1-v20130909-0132-B378 > CLONE - NullPointerException reported in Eclipse Error view after using "Materialize Library..." on uninitialized classpath container > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15363 > URL: https://issues.jboss.org/browse/JBIDE-15363 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, maven > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.1.1.Alpha1 > > > {code} > org.eclipse.e4.core.di.InjectionException: java.lang.NullPointerException > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:63) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499) > 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.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:850) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:743) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:727) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:662) > 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:601) > 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) > Caused by: java.lang.NullPointerException > at org.jboss.tools.common.jdt.ui.buildpath.dialog.MaterializeLibraryDialog.<init>(MaterializeLibraryDialog.java:102) > at org.jboss.tools.common.jdt.ui.buildpath.handlers.MaterializeLibraryHandler.execute(MaterializeLibraryHandler.java:80) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > 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:601) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56) > ... 37 more{code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15203) Error publishing html files to WildFly on Windows (WildFly locks deployed files)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15203?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-15203. --------------------------------- Fix Version/s: 4.0.0.Final (was: 4.1.x) Resolution: Done Fixed since WildFly 8.0.0 alpha3 > Error publishing html files to WildFly on Windows (WildFly locks deployed files) > -------------------------------------------------------------------------------- > > Key: JBIDE-15203 > URL: https://issues.jboss.org/browse/JBIDE-15203 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.CR1 > Environment: Win 7 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.0.0.Final > > > Created a simple maven web app, deployed onto a WildFly 8.0.0.Alpha2. The edited an index.html file and got > {noformat} > Error renaming D:\Dev\servers\wildfly-8.0.0.Alpha2\standalone\tmp\tmp8284536747609996823.html to D:\Dev\servers\wildfly-8.0.0.Alpha2\standalone\deployments\w.war\index.html. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {noformat} > Obviously the filesystem is identical. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15203) Error publishing html files to WildFly on Windows (WildFly locks deployed files)

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15203?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15203: -------------------------------- Component/s: upstream > Error publishing html files to WildFly on Windows (WildFly locks deployed files) > -------------------------------------------------------------------------------- > > Key: JBIDE-15203 > URL: https://issues.jboss.org/browse/JBIDE-15203 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.1.0.CR1 > Environment: Win 7 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.0.0.Final > > > Created a simple maven web app, deployed onto a WildFly 8.0.0.Alpha2. The edited an index.html file and got > {noformat} > Error renaming D:\Dev\servers\wildfly-8.0.0.Alpha2\standalone\tmp\tmp8284536747609996823.html to D:\Dev\servers\wildfly-8.0.0.Alpha2\standalone\deployments\w.war\index.html. > This may be caused by your server's temporary deploy directory being on a different filesystem than the final destination. > You may adjust these settings in the server editor. > {noformat} > Obviously the filesystem is identical. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-386: ------------------------------------- Assignee: Michelle Murray (was: Fred Bricon) > Review: Devs to review Maven Tools content spec > ----------------------------------------------- > > Key: TOOLSDOC-386 > URL: https://issues.jboss.org/browse/TOOLSDOC-386 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - Maven Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > Attachments: MavenTools_contentspec.pdf > > > Please review the content spec of the Maven Tools chapter from a technical viewpoint: > 1) Is the info about features correct? > 2) Are any features missing? > The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts. > For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later. > The content spec is available here as a pdf. Alternatively, the content spec is also available at: > https://mojo.redhat.com/docs/DOC-19224 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-386) Review: Devs to review Maven Tools content spec

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-386?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-386: ------------------------------------------ Thanks for the feedback [~fbricon] - particularly filling in the gaps and correcting me where I had terminology wrong. I am going to update the content spec based on this and will probably be back with questions. > Review: Devs to review Maven Tools content spec > ----------------------------------------------- > > Key: TOOLSDOC-386 > URL: https://issues.jboss.org/browse/TOOLSDOC-386 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - Maven Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Fred Bricon > Fix For: 4.2.0 > > Attachments: MavenTools_contentspec.pdf > > > Please review the content spec of the Maven Tools chapter from a technical viewpoint: > 1) Is the info about features correct? > 2) Are any features missing? > The content spec will be used to write the Maven Tools chapter in the JBDS User Guide. It is important that any issues are resolved before writing starts. > For ease of tracking by docs, please give feedback as comments in this JIRA. Estimated page and graphics counts will be added by docs later. > The content spec is available here as a pdf. Alternatively, the content spec is also available at: > https://mojo.redhat.com/docs/DOC-19224 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2623: ----------------------------- Attachment: 2623-p2browser-shows-datanucleus-missing.png Curiously, the new site does not show the datanucleus plugin: !2623-p2browser-shows-datanucleus-missing.png! [~mickael_istria] what else do we need to do here? > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.x > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15488) Web Service Tester doesn't work with https and self-signed certificate

by Juergen Zimmermann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15488?page=com.atlassian.jira.plugi... ] Juergen Zimmermann commented on JBIDE-15488: -------------------------------------------- Sorry, there is nothing else - no single line in the eclipse log file. > Web Service Tester doesn't work with https and self-signed certificate > ---------------------------------------------------------------------- > > Key: JBIDE-15488 > URL: https://issues.jboss.org/browse/JBIDE-15488 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Juergen Zimmermann > Assignee: Brian Fitzpatrick > > If I test a RESTful Web Service on WildFly 8 which is configured for https, then I just this error message in the response body (for both GET and POST requests): > {code} > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15492) Use new ExpressionResolver API in Foundation

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-15492: ----------------------------------- Summary: Use new ExpressionResolver API in Foundation Key: JBIDE-15492 URL: https://issues.jboss.org/browse/JBIDE-15492 Project: Tools (JBoss Tools) Issue Type: Task Components: central Affects Versions: 4.2.0.Alpha1 Reporter: Rob Stryker Assignee: Fred Bricon Fix For: 4.2.0.Alpha1 Deprecate or remove central's expression resolver and make use of the version in foundation. -- 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, 7 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 September 2013