[JBoss JIRA] (JBTIS-471) Unify component versions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-471:
----------------------------------
Either it's an identical rebuild that just adds the suffix, or he forgot to upversion to 1.0.6.
Looks like the master branch is 1.0.6.qualifier / 1.0.6-SNAPSHOT (for neon, and JDK 8) [1], while the mars branch is at 1.0.5.qualifier / 1.0.5-SNAPSHO (requires JDK 6) [0].
http://git.eclipse.org/c/bpel/org.eclipse.bpel.git/commit/?id=43aa3f65772...
http://git.eclipse.org/c/bpel/org.eclipse.bpel.git/log/?h=mars
Unclear from the commit log whether the stuff in the mars branch should be at 1.0.6 and master at 1.1.0, or if the commits in mars branch are irrelevant, and the old 1.0.5.Final was really just a pre-Final, with this new build being "more close to Final".
> Unify component versions
> ------------------------
>
> Key: JBTIS-471
> URL: https://issues.jboss.org/browse/JBTIS-471
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 8.0.3.GA
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Attachments: junit4.8vs4.12.png
>
>
> Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as
> BPMN2 1.1.3.Final
> Fuse 7.3.1.v20150728-1330-H54-Final
> Teiid Designer 9.0.3.Final-v20150728-2029-B1148
> I suggest to use the format used by Teiid Designer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21433) Application wizard: No projects nor server templates when launched from explorer context menu
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21433?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21433.
---------------------------------
Verified in nigthly build of JBDS with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153.
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21433
> URL: https://issues.jboss.org/browse/JBIDE-21433
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor81.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21443) NullPointerException when trying to import a BuildConfig as a new application from OpenShift 3
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21443?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-21443.
---------------------------------
Verifed in nigthly build of JBDS with OpenShift tools plugin of version 3.1.0.Beta2-v20160119-1135-B153.
> NullPointerException when trying to import a BuildConfig as a new application from OpenShift 3
> ----------------------------------------------------------------------------------------------
>
> Key: JBIDE-21443
> URL: https://issues.jboss.org/browse/JBIDE-21443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: OSX
> JBDS
> OpenShift origin 1.1.0.1
> Reporter: Akram Ben Aissi
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Labels: import_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: eclipse.log
>
>
> When trying to import a project from a BuildConfig (right clic import as new project), I get a NullPointerException after clicking Finish.
> Same issue occurs when clicking next, and changing the destination folder for anything that exists or does not exist
> eclipse.log is attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-471) Unify component versions
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-471:
----------------------------------
Hey again [~bbrodt] -
I'm currently picking up a bpel 1.0.5.Final from last August. Are you sure this is 1.0.5?
--P
> Unify component versions
> ------------------------
>
> Key: JBTIS-471
> URL: https://issues.jboss.org/browse/JBTIS-471
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 8.0.3.GA
> Reporter: Andrej Podhradsky
> Assignee: Robert (Bob) Brodt
> Attachments: junit4.8vs4.12.png
>
>
> Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as
> BPMN2 1.1.3.Final
> Fuse 7.3.1.v20150728-1330-H54-Final
> Teiid Designer 9.0.3.Final-v20150728-2029-B1148
> I suggest to use the format used by Teiid Designer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TOOLSDOC-667) Document how to use the EAP online maven repo
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-667?page=com.atlassian.jira.plug... ]
Martin Malina commented on TOOLSDOC-667:
----------------------------------------
[~supriya.bharadwaj], the beginning seems a bit repetitive:
{quote}
This article provides details for new and existing JBoss Developer Studio users who need to configure a fresh install of JBoss Developer Studio or upgrade the versions of JBoss EAP or JBoss Web Framework Kit in use.
{quote}
And a bit later:
{quote}
This article is intended for new and existing JBoss Developer Studio users who need to configure a fresh install of JBoss Developer Studio or upgrade the versions of JBoss EAP or JBoss Web Framework Kit in use.
{quote}
A. Download, Install and Set Up JBoss Developer Studio and JBoss EAP using a Single Installer
Note: If you want to install a different JBoss EAP version, you must first install JBoss Developer Studio and then you can download, install, and set up JBoss EAP from within the IDE as detailed later.
- this is not true. There is no such requirement that you must install JBDS first and only then you can get the EAP binary. Instead, I would put it this way:
{quote}
Note: If you want to install a different JBoss EAP version, you can either download it from within the IDE (see B.) or install it separately and then follow the instructions in C.
{quote}
And now we get to the subject of this JIRA - instructions about the online maven repo: I'm sorry, but I find it confusing. You have this:
{quote}
Alternatively, you can use the online repository by selecting redhat-ga-repository in the drop down menu in the Add Maven Repository dialog, in the Profile ID field. This will add https://maven.repository.redhat.com/ga to your settings.xml taking care of all the dependencies.
{quote}
But this belongs to the instructions on how to configure offline maven repo, not to the previous paragraph - Specify Maven settings.xml File Location. So at least put this information in the correct place. But maybe it would be better start from the beginning saying that there are two options - either set up a downloaded maven repo, or set up the online repo.
> Document how to use the EAP online maven repo
> ---------------------------------------------
>
> Key: TOOLSDOC-667
> URL: https://issues.jboss.org/browse/TOOLSDOC-667
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Affects Versions: 4.3.0.Final
> Reporter: Martin Malina
> Assignee: Supriya Bharadwaj
> Fix For: 4.3.0.Final
>
>
> In TOOLSDOC-499 it was mentioned that we have a guide that explains how to add jboss enterprise maven repositories, but it would be nice to also mention the alternative of using the online repo.
> From TOOLSDOC-499:
> {quote}
> Alternatively, you can use the online repository: In the Add Maven Repository dialog, in the Profile ID field at the top, select "redhat-techpreview-all-repository" in the drop down menu. This will add http://maven.repository.redhat.com/techpreview/all/ to your settings.xml and that should satisfy the dependencies.
> {quote}
> Something similar could be added in a box in this doc:
> https://access.redhat.com/articles/1160993#ConfigureMaven
> (or a similar doc for JBDS 9 once it's ready)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21474) Hibernate libraries are not being validated
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21474?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-21474:
--------------------------------------
Assignee: Koen Aers
[~koen.aers] please review.
> Hibernate libraries are not being validated
> -------------------------------------------
>
> Key: JBIDE-21474
> URL: https://issues.jboss.org/browse/JBIDE-21474
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.3.1.Beta1
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> enablement of HibernateUserLibraryValidator is not correctly defined in o.j.t.hibernate.jpt.core plugin.xml which causes this exception
> {code}
> org.eclipse.core.runtime.CoreException: No property tester contributes a property org.eclipse.jpt.jpa.core.jpaPlatformGroup to type class org.eclipse.jpt.jpa.core.internal.libprov.JpaUserLibraryProviderInstallOperationConfig
> at org.eclipse.core.internal.expressions.TypeExtensionManager.getProperty(TypeExtensionManager.java:127)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:97)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:75)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:31)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:55)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig.isEnabled_(LibraryValidatorConfig.java:86)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig.isEnabled(LibraryValidatorConfig.java:72)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig$IsEnabled.evaluate(LibraryValidatorConfig.java:121)
> at org.eclipse.jpt.common.core.internal.libval.LibraryValidatorConfig$IsEnabled.evaluate(LibraryValidatorConfig.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.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:79)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.<init>(FilteringIterator.java:56)
> at org.eclipse.jpt.common.utility.internal.iterator.IteratorTools.filter(IteratorTools.java:886)
> at org.eclipse.jpt.common.utility.internal.iterable.FilteringIterable.iterator(FilteringIterable.java:48)
> at org.eclipse.jpt.common.core.internal.libprov.JptUserLibraryProviderInstallOperationConfig.validate(JptUserLibraryProviderInstallOperationConfig.java:42)
> at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.validate(LibraryInstallDelegate.java:528)
> at org.eclipse.jst.common.project.facet.ui.libprov.LibraryFacetPropertyPage.performValidation(LibraryFacetPropertyPage.java:385)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage.performValidation(JptProjectPropertiesPage.java:448)
> at org.eclipse.jst.common.project.facet.ui.libprov.LibraryFacetPropertyPage.updateValidation(LibraryFacetPropertyPage.java:346)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage.validate(JptProjectPropertiesPage.java:396)
> at org.eclipse.jpt.common.ui.internal.properties.JptProjectPropertiesPage$ValidationListener.modelChanged(JptProjectPropertiesPage.java:390)
> at org.eclipse.jpt.common.utility.model.listener.AbstractChangeListener.modelChanged(AbstractChangeListener.java:101)
> at org.eclipse.jpt.common.utility.model.listener.AbstractChangeListener.propertyChanged(AbstractChangeListener.java:53)
> at org.eclipse.jpt.common.utility.internal.model.ChangeSupport.firePropertyChanged_(ChangeSupport.java:526)
> at org.eclipse.jpt.common.utility.internal.model.ChangeSupport.firePropertyChanged(ChangeSupport.java:491)
> at org.eclipse.jpt.common.utility.internal.model.SingleAspectChangeSupport.firePropertyChanged(SingleAspectChangeSupport.java:156)
> at org.eclipse.jpt.common.utility.internal.model.AbstractModel.firePropertyChanged(AbstractModel.java:189)
> at org.eclipse.jpt.common.utility.internal.model.value.BufferedModifiablePropertyValueModel.reset(BufferedModifiablePropertyValueModel.java:271)
> at org.eclipse.jpt.common.utility.internal.model.value.BufferedModifiablePropertyValueModel.setValue(BufferedModifiablePropertyValueModel.java:139)
> at org.eclipse.jpt.common.ui.internal.swt.bindings.BooleanButtonModelBinding.buttonSelected(BooleanButtonModelBinding.java:173)
> at org.eclipse.jpt.common.ui.internal.swt.bindings.BooleanButtonModelBinding$ButtonSelectionListener.widgetSelected(BooleanButtonModelBinding.java:127)
> 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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.dialogs.PropertyDialogAction.run(PropertyDialogAction.java:157)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> 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:497)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3582) JBDS installer refuses to use JDK 1.9 early access
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3582?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3582:
---------------------------------
Fix Version/s: 9.1.0.Beta2
> JBDS installer refuses to use JDK 1.9 early access
> --------------------------------------------------
>
> Key: JBDS-3582
> URL: https://issues.jboss.org/browse/JBDS-3582
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 9.1.0.Beta2
>
> Attachments: 1453206771791.log, jbds-installer-ea.png
>
>
> It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
> We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
> If I installed using jdk 8 and then changed jbdevstudio.ini to point to /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/bin/java , JBDS fails to start at all. See the log attached.
> !jbds-installer-ea.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3582) JBDS installer refuses to use JDK 1.9 early access
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3582?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov closed JBDS-3582.
--------------------------------
Resolution: Duplicate Issue
Duplicates JBDS-3581
> JBDS installer refuses to use JDK 1.9 early access
> --------------------------------------------------
>
> Key: JBDS-3582
> URL: https://issues.jboss.org/browse/JBDS-3582
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.Beta1
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 9.1.0.Beta2
>
> Attachments: 1453206771791.log, jbds-installer-ea.png
>
>
> It turns out that recent builds of Oracle JDK 1.9 EA started reported version of 9-EA instead of just 9. Consequently, our JBDS installer refuses to set this jdk during installation - it doesn't support this version.
> We need to make sure that it's possible to install JBDS with JDK 1.9 EA. I think for version 9 we currently display a warning - so 9-EA should be the same.
> If I installed using jdk 8 and then changed jbdevstudio.ini to point to /Library/Java/JavaVirtualMachines/jdk-9.jdk/Contents/Home/bin/java , JBDS fails to start at all. See the log attached.
> !jbds-installer-ea.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months