[JBoss JIRA] (JBTIS-982) org.sonatype.tycho.m2e plug-in missing from integration stack
by Brian Fitzpatrick (JIRA)
Brian Fitzpatrick created JBTIS-982:
---------------------------------------
Summary: org.sonatype.tycho.m2e plug-in missing from integration stack
Key: JBTIS-982
URL: https://issues.jboss.org/browse/JBTIS-982
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: Fuse IDE
Affects Versions: 10.0.0.Alpha1
Reporter: Brian Fitzpatrick
Assignee: Paul Leacu
Priority: Blocker
Fix For: 10.0.0.CR1
Based on FUSETOOLS-2170, we have discovered that the org.sonatype.tycho.m2e plug-in is missing from the Integration Stack.
Can we add it back? It disappeared sometime after September 9.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBTIS-981) NumberFormatException if you select more features to install
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-981?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-981:
----------------------------------
The problem here was that I didn't set the size fields in the json files (IS side). This has now been corrected. See:
http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta...
http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta...
I'll wait until after devstudiois 10.0.0.GA is final before checking this in.
> NumberFormatException if you select more features to install
> ------------------------------------------------------------
>
> Key: JBTIS-981
> URL: https://issues.jboss.org/browse/JBTIS-981
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Environment: devstudio-is-installer-10.0.0-SNAPSHOT.jar
> devstudio-is-runtime-installer-10.0.0-SNAPSHOT.jar
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> {code}
> java.lang.NumberFormatException: For input string: "null"
> at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
> at java.lang.Long.parseLong(Long.java:589)
> at java.lang.Long.parseLong(Long.java:631)
> at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.calculateAggregateSize(DiskSpaceCheckPanel.java:71)
> at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.getInstallationSize(DiskSpaceCheckPanel.java:94)
> at com.jboss.devstudio.core.installer.DiskSpaceCheckPanel.panelActivate(DiskSpaceCheckPanel.java:36)
> at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475)
> at com.izforge.izpack.installer.InstallerFrame.skipPanel(InstallerFrame.java:1401)
> at com.jboss.devstudio.core.installer.UpdatePacksPanel.panelActivate(UpdatePacksPanel.java:25)
> at com.izforge.izpack.installer.InstallerFrame.switchPanel(InstallerFrame.java:864)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1475)
> at com.izforge.izpack.installer.InstallerFrame.navigateNext(InstallerFrame.java:1443)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionPerformed(InstallerFrame.java:1585)
> at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
> at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348)
> at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
> at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
> at java.awt.Component.processMouseEvent(Component.java:6535)
> at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
> at java.awt.Component.processEvent(Component.java:6300)
> at java.awt.Container.processEvent(Container.java:2236)
> at java.awt.Component.dispatchEventImpl(Component.java:4891)
> at java.awt.Container.dispatchEventImpl(Container.java:2294)
> at java.awt.Component.dispatchEvent(Component.java:4713)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4888)
> at java.awt.LightweightDispatcher.processMouseEvent(Container.java:4525)
> at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4466)
> at java.awt.Container.dispatchEventImpl(Container.java:2280)
> at java.awt.Window.dispatchEventImpl(Window.java:2750)
> at java.awt.Component.dispatchEvent(Component.java:4713)
> at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
> at java.awt.EventQueue.access$500(EventQueue.java:97)
> at java.awt.EventQueue$3.run(EventQueue.java:709)
> at java.awt.EventQueue$3.run(EventQueue.java:703)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:86)
> at java.awt.EventQueue$4.run(EventQueue.java:731)
> at java.awt.EventQueue$4.run(EventQueue.java:729)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:76)
> at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
> at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
> at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
> at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23463:
-----------------------------------------------
[~jcantrill], please take a look at the pull request.
> Properties: Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: exit-code-0.png
>
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
> steps:
> # EXEC: create an application via a s2i template
> # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
> # EXEC: in Properties: select "Pods" tab.
> # ASSERT: a build pod is appearing
> # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods
> Result:
> The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
> !exit-code-0.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-23463 at 11/8/16 1:42 PM:
------------------------------------------------------------------------
Method com.openshift.internal.restclient.model.Pod.getStatus() declares in javadoc that "The logic of the method is a copied from 'podStatus' function of [app/scripts/filters/resources.js] of [openshift/origin-web-console]".
However, it is not exactly so.
In resources.js, first 'state.terminated.reason' is checked, and if not empty, returned. Only otherwise 'signal' and 'exitCode' are checked, in that order.
In Pod, container states ids are put into HashMap POD_STATUS_CONTAINER_STATES and Pod.getContainerStatusStringIfExist() iterates over them. But HashMap does not save the order of keys.
Then, one simple solution is to replace HashMap with List<String[]> where String[] has 2 elements, [0] - id, [1] - value (human-friendly label).
was (Author: scabanovich):
Method com.openshift.internal.restclient.model.Pod.getStatus() declares in javadoc that "The logic of the method is a copied from 'podStatus' function of [app/scripts/filters/resources.js] of [openshift/origin-web-console]".
However, it is not exactly so.
In resources.js, first 'state.terminated.reason' is checked, and if not empty, returned. Only otherwise 'signal' and 'exitCode' are checked, in that order.
In Pod, container states ids are put into HashMap POD_STATUS_CONTAINER_STATES and Pod.getContainerStatusStringIfExist() iterates over them. But HashMap does not save the order of keys.
Then, one simple solution is to replace HashMap with List<String[]> where String[] has 2 elements, [0] - id, [1] - value.
> Properties: Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: exit-code-0.png
>
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
> steps:
> # EXEC: create an application via a s2i template
> # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
> # EXEC: in Properties: select "Pods" tab.
> # ASSERT: a build pod is appearing
> # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods
> Result:
> The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
> !exit-code-0.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23463) Properties: Build pod has state of exit code 0 instead of correct status completed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23463?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23463:
-----------------------------------------------
Method com.openshift.internal.restclient.model.Pod.getStatus() declares in javadoc that "The logic of the method is a copied from 'podStatus' function of [app/scripts/filters/resources.js] of [openshift/origin-web-console]".
However, it is not exactly so.
In resources.js, first 'state.terminated.reason' is checked, and if not empty, returned. Only otherwise 'signal' and 'exitCode' are checked, in that order.
In Pod, container states ids are put into HashMap POD_STATUS_CONTAINER_STATES and Pod.getContainerStatusStringIfExist() iterates over them. But HashMap does not save the order of keys.
Then, one simple solution is to replace HashMap with List<String[]> where String[] has 2 elements, [0] - id, [1] - value.
> Properties: Build pod has state of exit code 0 instead of correct status completed
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-23463
> URL: https://issues.jboss.org/browse/JBIDE-23463
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM3
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.x
>
> Attachments: exit-code-0.png
>
>
> When I create a new OpenShift 3 application from a template, there is a running build. Once a build pod is completed, it has status "Completed". But now it Pods tabbed properties it contains status "Exit Code: 0" which is not user friendly and it broke integration tests.
> steps:
> # EXEC: create an application via a s2i template
> # EXEC: in OpenShift explorer: select the connection that you used to create the application and open up the "Properties view"
> # EXEC: in Properties: select "Pods" tab.
> # ASSERT: a build pod is appearing
> # EXEC: wait until the build pod is terminated and then look at its "Status" in the Properties > Pods
> Result:
> The status for the pod is reported with a "Exit Code: 0" (if successfully terminated, "Exit Code: 1" otherwise)
> !exit-code-0.png!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4165) Invalid Java Version '1.8.0.111' error in console when Java VM is not detected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4165?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4165:
--------------------------------
Fix Version/s: 10.2.0.AM3
(was: 10.2.0.GA)
> Invalid Java Version '1.8.0.111' error in console when Java VM is not detected
> ------------------------------------------------------------------------------
>
> Key: JBDS-4165
> URL: https://issues.jboss.org/browse/JBDS-4165
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Environment: Windows
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM3
>
>
> When Java is not installed, installer use version from requirements-${platfrom}.json. Then during selecting/deselection DevStudio install validation for required Java VM item triggered and that fails with error because java version in requirements.json have wrong format
> {code}C:\p\rh\dpi\node_modules\angular\angular.js:13920 TypeError: Invalid Version: 1.8.0.111
> at new SemVer (C:\p\rh\dpi\node_modules\semver\semver.js:293)
> at compare (C:\p\rh\dpi\node_modules\semver\semver.js:566)
> at Function.lt (C:\p\rh\dpi\node_modules\semver\semver.js:600)
> at Function.LT (version.js:44)
> {code}
> at JdkInstall.validateVersion (jdk-install.js:119)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4165) Invalid Java Version '1.8.0.111' error in console when Java VM is not detected
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4165?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4165:
--------------------------------
Fix Version/s: 10.2.0.GA
(was: 10.2.0.AM3)
> Invalid Java Version '1.8.0.111' error in console when Java VM is not detected
> ------------------------------------------------------------------------------
>
> Key: JBDS-4165
> URL: https://issues.jboss.org/browse/JBDS-4165
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.AM3
> Environment: Windows
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM3
>
>
> When Java is not installed, installer use version from requirements-${platfrom}.json. Then during selecting/deselection DevStudio install validation for required Java VM item triggered and that fails with error because java version in requirements.json have wrong format
> {code}C:\p\rh\dpi\node_modules\angular\angular.js:13920 TypeError: Invalid Version: 1.8.0.111
> at new SemVer (C:\p\rh\dpi\node_modules\semver\semver.js:293)
> at compare (C:\p\rh\dpi\node_modules\semver\semver.js:566)
> at Function.lt (C:\p\rh\dpi\node_modules\semver\semver.js:600)
> at Function.LT (version.js:44)
> {code}
> at JdkInstall.validateVersion (jdk-install.js:119)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Jeff MAURY edited comment on JBDS-4133 at 11/8/16 1:16 PM:
-----------------------------------------------------------
Managed to get rid of the error using my updated PR. The patched JAR was copied into dropins. See Eclipse OSGI Console !image-2016-11-08-19-07-53-492.png|thumbnail!
Link to the [PR|https://github.com/jbosstools/jbosstools-webservices/pull/256]
was (Author: jeffmaury):
Managed to get rid of the error using my updated PR. The patched JAR was copied into dropins. See Eclipse OSGI Console !image-2016-11-08-19-07-53-492.png|thumbnail!
Link to the PR!
> org.jboss.tools.ws.jaxrs.core :: error occurred during JAX-RS Metamodel build - java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, target-platform, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Fix For: 10.2.0.GA
>
> Attachments: image-2016-11-08-19-07-53-492.png, lucene3.5corevs.5.4.1analyzers-common.png, lucene3.5corevs.5.4.1queryparser.png, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, TEST-org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.xml
>
>
> I'm getting this problem after running the HTML5 quickstart. I've installed this [1] version of the rpm.
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2016-10-26 16:22:07.578
> !MESSAGE An internal error occurred during: "JAX-RS Metamodel build...".
> !STACK 0
> java.lang.NoClassDefFoundError: org/apache/lucene/analysis/standard/StandardAnalyzer
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.<init>(JaxrsMetamodel.java:163)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsMetamodel.create(JaxrsMetamodel.java:278)
> at org.jboss.tools.ws.jaxrs.core.metamodel.domain.JaxrsMetamodelLocator.get(JaxrsMetamodelLocator.java:120)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedBuildJob.run(ResourceChangedBuildJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: org.apache.lucene.analysis.standard.StandardAnalyzer cannot be found by org.jboss.tools.ws.jaxrs.core_1.9.2.v20161011-1002
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 5 more
> {code}
> [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months