[JBoss JIRA] (JBIDE-19750) Install grinder fails to run on RHEL7: No more handles!
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19750:
----------------------------------------
[~fbricon]: We go "no more handles" error on RHEL7 related to web browser since central is HTML5. Are you aware of anything specific to do in order to have it working on RHEL7? /cc [~ibuziuk] [~kmarmaliykov]
> Install grinder fails to run on RHEL7: No more handles!
> -------------------------------------------------------
>
> Key: JBIDE-19750
> URL: https://issues.jboss.org/browse/JBIDE-19750
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> {code}
> 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301.
> ...
> 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
> 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec
> 13:43:18
> 13:43:18 Testcase: testInstall took 252.166 sec
> {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests.
> Wondering if ...
> a) passing through a different *swt.browser.DefaultType*, &/or
> b) using a newer SWTBot (which works with Luna [1] now?)
> ... might help.
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (LOCUS-13) Build number in qualifier are against reproducible version qualifier
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/LOCUS-13?page=com.atlassian.jira.plugin.s... ]
Mickael Istria commented on LOCUS-13:
-------------------------------------
Agreement is that we can remove BUILD_ALIAS from the OSGi bundle versions, but we still need to keep independent and -SNAPSHOT versions for the Locus site.
> Build number in qualifier are against reproducible version qualifier
> --------------------------------------------------------------------
>
> Key: LOCUS-13
> URL: https://issues.jboss.org/browse/LOCUS-13
> Project: JBoss Tools Locus
> Issue Type: Enhancement
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 1.2.0
>
>
> We did set up git-based reproducible qualifiers but in the other end, we have the qualifier always changing because it contains the BUILD_NUMBER.
> Those metadata should not be part of the qualifier, but should instead be in a future index.html, or attached to the Maven artifact.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19769) Check if the project is already present in the workspace
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19769?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19769:
----------------------------------------
I did try some possible scenarios to reproduce this, but could see the same message.
Do you have some steps to reproduce?
> Check if the project is already present in the workspace
> --------------------------------------------------------
>
> Key: JBIDE-19769
> URL: https://issues.jboss.org/browse/JBIDE-19769
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
> Attachments: existing-projects.png
>
>
> At the moment the project is attempted to import even if it is already in the workspace. It is OK that it is detected but it should be marked as already imported in the wizard table and it should not be imported again.
> At the moment, this is logged into Error log:
> {code}
> org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /home/ljelinko/workspaces/workspace/RemoteSystemsTempFiles
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:294)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:222)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.searchAndImportChildrenProjectsRecursively(OpenFolderCommand.java:173)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:230)
> at org.eclipse.ui.internal.wizards.datatransfer.NestedProjectsWizardPage$10.run(NestedProjectsWizardPage.java:258)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/RemoteSystemsTempFiles' already exists.
> at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:313)
> at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:300)
> at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:51)
> at org.eclipse.core.internal.resources.Project.create(Project.java:268)
> at org.eclipse.core.internal.resources.Project.create(Project.java:252)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.createOrImportProject(OpenFolderCommand.java:331)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:285)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19769) Check if the project is already present in the workspace
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19769?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-19769:
--------------------------------------
Assignee: Mickael Istria
> Check if the project is already present in the workspace
> --------------------------------------------------------
>
> Key: JBIDE-19769
> URL: https://issues.jboss.org/browse/JBIDE-19769
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
> Attachments: existing-projects.png
>
>
> At the moment the project is attempted to import even if it is already in the workspace. It is OK that it is detected but it should be marked as already imported in the wizard table and it should not be imported again.
> At the moment, this is logged into Error log:
> {code}
> org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /home/ljelinko/workspaces/workspace/RemoteSystemsTempFiles
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:294)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:222)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.searchAndImportChildrenProjectsRecursively(OpenFolderCommand.java:173)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:230)
> at org.eclipse.ui.internal.wizards.datatransfer.NestedProjectsWizardPage$10.run(NestedProjectsWizardPage.java:258)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/RemoteSystemsTempFiles' already exists.
> at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:313)
> at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:300)
> at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:51)
> at org.eclipse.core.internal.resources.Project.create(Project.java:268)
> at org.eclipse.core.internal.resources.Project.create(Project.java:252)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.createOrImportProject(OpenFolderCommand.java:331)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:285)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19769) Check if the project is already present in the workspace
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19769?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19769:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
> Check if the project is already present in the workspace
> --------------------------------------------------------
>
> Key: JBIDE-19769
> URL: https://issues.jboss.org/browse/JBIDE-19769
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
> Attachments: existing-projects.png
>
>
> At the moment the project is attempted to import even if it is already in the workspace. It is OK that it is detected but it should be marked as already imported in the wizard table and it should not be imported again.
> At the moment, this is logged into Error log:
> {code}
> org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /home/ljelinko/workspaces/workspace/RemoteSystemsTempFiles
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:294)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:222)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.searchAndImportChildrenProjectsRecursively(OpenFolderCommand.java:173)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:230)
> at org.eclipse.ui.internal.wizards.datatransfer.NestedProjectsWizardPage$10.run(NestedProjectsWizardPage.java:258)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
> Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/RemoteSystemsTempFiles' already exists.
> at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:313)
> at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:300)
> at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:51)
> at org.eclipse.core.internal.resources.Project.create(Project.java:268)
> at org.eclipse.core.internal.resources.Project.create(Project.java:252)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.createOrImportProject(OpenFolderCommand.java:331)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:285)
> ... 5 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19750) Install grinder fails to run on RHEL7: No more handles!
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19750:
----------------------------------------
With those property set, we now get
{code}
09:00:43 !MESSAGE Internal browser is not available: No more handles [MOZILLA_FIVE_HOME='/qa/tools/opt/firefox-5'] (java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons:
09:00:43 /qa/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/ba86289f/eclipse/configuration/org.eclipse.osgi/705/0/.cp/libswt-mozilla-gtk-4517.so: libxpcom.so: cannot open shared object file: No such file or directory
09:00:43 no swt-mozilla-gtk in java.library.path
09:00:43 /qa/services/hudson/.swt/lib/linux/x86_64/libswt-mozilla-gtk-4517.so: libxpcom.so: cannot open shared object file: No such file or directory
09:00:43 Can't load library: /qa/services/hudson/.swt/lib/linux/x86_64/libswt-mozilla-gtk.so
09:00:43 )
{code}
> Install grinder fails to run on RHEL7: No more handles!
> -------------------------------------------------------
>
> Key: JBIDE-19750
> URL: https://issues.jboss.org/browse/JBIDE-19750
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> {code}
> 16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group 2.2.1.201402241301.
> ...
> 13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
> 13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec
> 13:43:18
> 13:43:18 Testcase: testInstall took 252.166 sec
> {code} - https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for `testInstall.groovy` but it must not have passed through to the eclipse install process, as the above error suggests.
> Wondering if ...
> a) passing through a different *swt.browser.DefaultType*, &/or
> b) using a newer SWTBot (which works with Luna [1] now?)
> ... might help.
> [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19771:
----------------------------------------
Suggested change upstream: https://git.eclipse.org/r/47293
[~ljelinko] Can you please have a look at this change to suggest improvements or vote +1 ?
> Improve Available detectors dialog
> ----------------------------------
>
> Key: JBIDE-19771
> URL: https://issues.jboss.org/browse/JBIDE-19771
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: available-detectors.png
>
>
> At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned.
> Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19771:
-----------------------------------
Fix Version/s: 4.3.0.Beta1
> Improve Available detectors dialog
> ----------------------------------
>
> Key: JBIDE-19771
> URL: https://issues.jboss.org/browse/JBIDE-19771
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Beta1
>
> Attachments: available-detectors.png
>
>
> At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned.
> Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-19771:
--------------------------------------
Assignee: Mickael Istria
> Improve Available detectors dialog
> ----------------------------------
>
> Key: JBIDE-19771
> URL: https://issues.jboss.org/browse/JBIDE-19771
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Minor
> Attachments: available-detectors.png
>
>
> At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned.
> Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months