[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 [~bbrodt]
I can't use CI (nightly) builds in the beta release of the IS. Can you rebuild bpmn2-modeler with a Beta1 or some other suffix??
Please check bpel as well - Eclipse won't let me see the features there - it's only accessible from within Eclipse as a p2 repo.
Thanks!
--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-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ]
Max Rydahl Andersen commented on TOOLSDOC-696:
----------------------------------------------
I don't have news on when next public release of CDK will happen so I expect for Beta2 things will be the same as for Beta1.
I would wait.
> Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
> -----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-696
> URL: https://issues.jboss.org/browse/TOOLSDOC-696
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1
> Build Date: 18-12-2015 22:13:00
> Topic ID: 44506-773485 [Latest]
> Reporter: Len DiMaggio
> Assignee: Misha Ali
>
> Title: New Features
> Describe the issue:
> The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes:
> '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...'
> But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release.
> Can we also add a screenshot?
> Suggestions for improvement:
> Additional information:
--
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 Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-21474:
----------------------------------------
Summary: 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
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] (JBIDE-21462) Project wizard: cancel button stops the job but wont cleanup resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21462?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21462:
------------------------------------------
[~xiazhao2015] no I wouldnt remove the cancel. Imagine that your server becomes unreachable and you would have to wait until the job timeouts. You would prefer to be able to cancel the job I would argue. I agree that it's not all evident that the project that was created is still there and might lead to the wizard error upon hitting "FInish" again. I think that we should remove the project if it was created. Agree?
> Project wizard: cancel button stops the job but wont cleanup resources
> ----------------------------------------------------------------------
>
> Key: JBIDE-21462
> URL: https://issues.jboss.org/browse/JBIDE-21462
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
> OS: Fedora 17 & MAC OS 10
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21462) Project wizard: cancel button stops the job but wont cleanup resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21462?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21462:
-------------------------------------
Description: In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created. (was: Cancel button did not work in create project wizard of Jboss Developer Studio )
> Project wizard: cancel button stops the job but wont cleanup resources
> ----------------------------------------------------------------------
>
> Key: JBIDE-21462
> URL: https://issues.jboss.org/browse/JBIDE-21462
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
> OS: Fedora 17 & MAC OS 10
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> In project wizard, hitting the cancel button stops the job but wont cleanup the project (-resources) that were created.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21462) Project wizard: cancel button stops the job but wont cleanup resources
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21462?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21462:
-------------------------------------
Summary: Project wizard: cancel button stops the job but wont cleanup resources (was: Cancel button did not work in create project wizard of Jboss Developer Studio)
> Project wizard: cancel button stops the job but wont cleanup resources
> ----------------------------------------------------------------------
>
> Key: JBIDE-21462
> URL: https://issues.jboss.org/browse/JBIDE-21462
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Environment: OpenShift 3 Tools: 3.1.0.Beta2-v20160114-1935-B149
> OS: Fedora 17 & MAC OS 10
> Reporter: Xia Zhao
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> Cancel button did not work in create project wizard of Jboss Developer Studio
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ]
Martin Malina commented on TOOLSDOC-696:
----------------------------------------
I'm not sure, but in my opinion it's still a bit too early even for Beta2 - I'm not even sure there will be a new beta of CDK 2 available by that time . Currently we're using internal builds which is not something that end users can use. I would hold this off even longer. [~maxandersen], what do you think?
> Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
> -----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-696
> URL: https://issues.jboss.org/browse/TOOLSDOC-696
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1
> Build Date: 18-12-2015 22:13:00
> Topic ID: 44506-773485 [Latest]
> Reporter: Len DiMaggio
> Assignee: Misha Ali
>
> Title: New Features
> Describe the issue:
> The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes:
> '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...'
> But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release.
> Can we also add a screenshot?
> Suggestions for improvement:
> Additional information:
--
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 Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3582?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3582:
--------------------------------
Attachment: 1453206771791.log
> 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
> 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 Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3582?page=com.atlassian.jira.plugin.... ]
Martin Malina updated JBDS-3582:
--------------------------------
Description:
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!
was:
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.
!jbds-installer-ea.png!
> 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
> Attachments: 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