[JBoss JIRA] (TOOLSDOC-447) Explain how to configure SSL options for connecting to Enterprise Servers.
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-447?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-447:
-------------------------------------
Assignee: Suz Dorfield (was: Michelle Murray)
> Explain how to configure SSL options for connecting to Enterprise Servers.
> --------------------------------------------------------------------------
>
> Key: TOOLSDOC-447
> URL: https://issues.jboss.org/browse/TOOLSDOC-447
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: User Guide - OpenShift Tools
> Affects Versions: 4.1.1
> Environment: Build Name: 22443, User Guide-7.1
> Build Date: 11-12-2013 15:10:49
> Topic ID: 25166-566980 [Latest]
> Reporter: Eric Rich
> Assignee: Suz Dorfield
> Priority: Minor
> Fix For: 4.1.1, 4.2.0.Beta1
>
> Original Estimate: 30 minutes
> Remaining Estimate: 30 minutes
>
> Title: Customizing Overview
> Describe the issue:
> It would be good to explain configuration options for connecting to multiple or different Enterprise Servers.
> Also explaining how to manage your SSL certificates or update them for connection to Enterprise Servers or Online would be helpful.
> Suggestions for improvement:
> Additional information:
--
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
10 years, 4 months
[JBoss JIRA] (TOOLSDOC-454) Generate Release Notes doc for JBDS 8.0.0CR1/GA
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-454?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-454:
-------------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta1)
> Generate Release Notes doc for JBDS 8.0.0CR1/GA
> -----------------------------------------------
>
> Key: TOOLSDOC-454
> URL: https://issues.jboss.org/browse/TOOLSDOC-454
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.CR1
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> Doc sections:
> 1. Introduction to Red Hat JBoss Developer Studio
> 1.1. About Red Hat JBoss Developer Studio
> 1.2. Use Cases of JBoss Developer Studio
> 2. About this Release
> 3. New Features
> 4. Resolved Issues
> 5. Known Issues
> 6. Apply this Release
--
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
10 years, 4 months
[JBoss JIRA] (TOOLSDOC-453) Generate Release Notes doc for JBDS 8.0.0Beta2
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-453?page=com.atlassian.jira.plug... ]
Michelle Murray updated TOOLSDOC-453:
-------------------------------------
Fix Version/s: 4.2.0.Beta2
(was: 4.2.0.Beta1)
> Generate Release Notes doc for JBDS 8.0.0Beta2
> ----------------------------------------------
>
> Key: TOOLSDOC-453
> URL: https://issues.jboss.org/browse/TOOLSDOC-453
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Release Notes
> Reporter: Michelle Murray
> Assignee: Michelle Murray
> Fix For: 4.2.0.Beta2
>
> Original Estimate: 6 hours
> Remaining Estimate: 6 hours
>
> Doc sections:
> 1. Introduction to Red Hat JBoss Developer Studio
> 1.1. About Red Hat JBoss Developer Studio
> 1.2. Use Cases of JBoss Developer Studio
> 2. About this Release
> 3. New Features
> 4. Resolved Issues
> 5. Known Issues
> 6. Apply this Release
--
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
10 years, 4 months
[JBoss JIRA] (JBIDE-16343) "Materialize Libraries" is not obvious
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16343?page=com.atlassian.jira.plugi... ]
Burr Sutter commented on JBIDE-16343:
-------------------------------------
I think one of the challenges is the word "library" - it is not really a word used in Java dev, nor in Maven world.
Jars, artifacts, dependencies, archives, etc are more often used.
> "Materialize Libraries" is not obvious
> --------------------------------------
>
> Key: JBIDE-16343
> URL: https://issues.jboss.org/browse/JBIDE-16343
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Fred Bricon
> Fix For: 4.2.x
>
>
> While looking at [~fbricon] doing a demo I (and [~FroMage] and [~xcoulon]) felt that "Materialize Libraries" is not a clear name for what it does.
> Why not renaming it to "Copy libraries into Project..." or "Turn into Libraries inside project..." ?
--
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
10 years, 4 months
[JBoss JIRA] (JBIDE-16376) Disabled "fetch-zips" on aggregate
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16376?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-16376.
------------------------------
Job is blue and local builds are too. Closing.
> Disabled "fetch-zips" on aggregate
> ----------------------------------
>
> Key: JBIDE-16376
> URL: https://issues.jboss.org/browse/JBIDE-16376
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.Alpha2
>
>
> As a consequence of changes for JBIDE-16309, the Maven mojo which fetches zip from aggregate files doesn't work any more.
> So I disabled it (added fetch-zips-for-aggregate.skip=true ). We should decide whether to keep this or not. It seems to me that so far, the individual zips have not been used often, so we may be able to get rid of 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
10 years, 4 months
[JBoss JIRA] (JBIDE-16417) Exceptions when "Configure->Add Arquilian Support ..." executed on broken maven project
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16417?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-16417:
-------------------------------------
Assignee: Snjezana Peco
> Exceptions when "Configure->Add Arquilian Support ..." executed on broken maven project
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-16417
> URL: https://issues.jboss.org/browse/JBIDE-16417
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: testing-tools
> Reporter: Denis Golovin
> Assignee: Snjezana Peco
>
> Wizard fails to show preview on step 5 (see stacktrace below)
> {code}java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:422)
> at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.run(RefactoringWizardDialog2.java:331)
> at org.eclipse.ltk.ui.refactoring.RefactoringWizard.createChange(RefactoringWizard.java:663)
> at org.eclipse.ltk.ui.refactoring.RefactoringWizard.computeUserInputSuccessorPage(RefactoringWizard.java:502)
> at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.computeSuccessorPage(UserInputWizardPage.java:74)
> at org.eclipse.ltk.ui.refactoring.UserInputWizardPage.getNextPage(UserInputWizardPage.java:114)
> at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.nextOrPreviewPressed(RefactoringWizardDialog2.java:497)
> at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2.access$2(RefactoringWizardDialog2.java:494)
> at org.eclipse.ltk.internal.ui.refactoring.RefactoringWizardDialog2$1.widgetSelected(RefactoringWizardDialog2.java:693)
> 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:4421)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation$1.run(RefactoringWizardOpenOperation.java:187)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:202)
> at org.eclipse.ltk.ui.refactoring.RefactoringWizardOpenOperation.run(RefactoringWizardOpenOperation.java:122)
> at org.jboss.tools.arquillian.ui.internal.commands.AddArquillianCommandHandler.execute(AddArquillianCommandHandler.java:48)
> at org.jboss.tools.arquillian.ui.internal.commands.AddArquillianCommandHandler.execute(AddArquillianCommandHandler.java:38)
> 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.GeneratedMethodAccessor83.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> 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:163)
> 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:222)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:851)
> 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.Display.sendEvent(Display.java:4421)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:611)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:565)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:154)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2346)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> Root exception:
> java.lang.NullPointerException
> at org.jboss.tools.arquillian.ui.internal.refactoring.AddArquillianSupportRefactoring.createChange(AddArquillianSupportRefactoring.java:154)
> at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:124)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2346)
> at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
> {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
10 years, 4 months
[JBoss JIRA] (JBIDE-2720) Need 64-bit windows support
by David Gisbey (JIRA)
[ https://issues.jboss.org/browse/JBIDE-2720?page=com.atlassian.jira.plugin... ]
David Gisbey commented on JBIDE-2720:
-------------------------------------
R6034 error with both Intel iCLS Client and Intel OpenCL SDK on Windows 8.1 64bit
I got it Visual Editor working OK by renaming instances of msvcr90.dll to msvcr90.dll.bad in the following locations:
c:\Program Files\Intel\iCLS Client
c:\Program Files (x86)\Intel\iCLS Client
c:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64
c:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86
The clash seems to happen because all of these are listed in my PATH environment variable.
After these renames, process explorer->find DLL for msvcr90.dll shows all running processes loading msvcr90.dll from the Windows Side-by-Side repository under c:\Windows\WinSxS
The javaw.exe process is now running an amd64 version of msvcr90.dll.
javaw.exe is also loading msvcr100.dll loaded from c:\Program Files\Java\jdk1.7.0_51\jre\bin
It would be better to fix the missing manifest, but in the meantime this seems to work without having to uninstall anything and doesn't seem to have broken any of the Intel stuff components, which I expect will still work as long as there is a suitable msvcr90.dll on the system.
> Need 64-bit windows support
> ---------------------------
>
> Key: JBIDE-2720
> URL: https://issues.jboss.org/browse/JBIDE-2720
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 2.1.0.GA, 2.1.1, 2.1.2, 3.0.0.alpha
> Reporter: Samuel Mendenhall
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: .mozconfig, buildlog1.log, buildlog1_x86_short.log, buildlog2.log, buildlog2_x86_short.log, buildlog3.log, build_error_when_run_x64.bat.txt, build_log_win_sdk6.log.txt, build_log_win_sdk7.log.txt, c-runtime-error.png, mozconfig1, mozconfig2, vpe-win-jdk64.png
>
>
> If you use a 64-bit JVM, the XULRunner parts of JBoss Tools does not load.
> We should look into providing a xulrunner for Windows 64-bit.
> *Update:*
> In JBoss Tools 4.1.0 and JBoss Developer Studio 7.0.0 XULRunner for 64-bit Windows is provided via experimental update site: http://download.jboss.org/jbosstools/updates/integration/kepler/core/xulr...
> {color:red}*Known problems:*{color}
> * XULRunner for 64-bit Windows is incompatible with Intel OpenCL SDK
> *If you get [R6034 error|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=1277169...] you may:*
> * Try to uninstall Intel OpenCL SDK
> * *OR* Disable XULRunner by adding the option {{-Dorg.jboss.tools.vpe.loadxulrunner=false}} to the {{eclipse.ini}} (or {{jbdevstudio.ini}} if you use JBoss Developer Studio)
> If you do not have Intel OpenCL SDK installed but still getting the R6034 error, we will very appreciate if you run Process Explorer as described in [this comment|https://issues.jboss.org/browse/JBIDE-2720?focusedCommentId=12772...] and help us to find conflicting library.
--
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
10 years, 4 months