[JBoss JIRA] (JBDS-4121) Run DevSuite Installer with Elevated privileges on Mac OSX
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4121?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-4121:
-------------------------------------
Attached macOS app that runs included app with admin privileges.
> Run DevSuite Installer with Elevated privileges on Mac OSX
> ----------------------------------------------------------
>
> Key: JBDS-4121
> URL: https://issues.jboss.org/browse/JBDS-4121
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Environment: Mac OS X
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: DevSuite.zip
>
>
> During installation PATH environment variable should be updated. For example to make permanent changes for PATH variable /etc/paths file should be modified and that requires administrative privileges.
> For Alpha release we could be running installer with sudo
> {code}sudo open DevSuite.app{code}
> Another option to investigate is using AppleScript and run the same shell script above with elevated privileges like this
> {code}do shell script «open DevSuite.app» with administrator privileges{code}
> that would trigger standard UI Dialog requesting user login/password with administrative privileges. This should be included int DevSuite.app package configuration after it is assembled by electron packages.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4121) Run DevSuite Installer with Elevated privileges on Mac OSX
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4121?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4121:
--------------------------------
Attachment: DevSuite.zip
> Run DevSuite Installer with Elevated privileges on Mac OSX
> ----------------------------------------------------------
>
> Key: JBDS-4121
> URL: https://issues.jboss.org/browse/JBDS-4121
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.2.0.AM2
> Environment: Mac OS X
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: DevSuite.zip
>
>
> During installation PATH environment variable should be updated. For example to make permanent changes for PATH variable /etc/paths file should be modified and that requires administrative privileges.
> For Alpha release we could be running installer with sudo
> {code}sudo open DevSuite.app{code}
> Another option to investigate is using AppleScript and run the same shell script above with elevated privileges like this
> {code}do shell script «open DevSuite.app» with administrator privileges{code}
> that would trigger standard UI Dialog requesting user login/password with administrative privileges. This should be included int DevSuite.app package configuration after it is assembled by electron packages.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBIDE-23208) SSLCertificatesPreference.isValid(String): Could not parse
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23208?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23208:
------------------------------------------
[~mmalina] could you please provide steps so that a user (like me), which doesnt run your env can replicate this?
> SSLCertificatesPreference.isValid(String): Could not parse
> ----------------------------------------------------------
>
> Key: JBIDE-23208
> URL: https://issues.jboss.org/browse/JBIDE-23208
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Martin Malina
> Fix For: 4.4.x
>
>
> When I start CDK and OpenShift connection is established, I get this in the Error Log view:
> org.jboss.tools.openshift.ui
> SSLCertificatesPreference.isValid(String): Could not parse 'Čt, 20 Zář 2018 12:54:07' in format E, d MMM yyyy HH:mm:ss
> An exception stack trace is not available.
> As you can see, the date is localized. I think this started happening after I updated to macOS Sierra last night - I never noticed it before. If we can figure out where the parsing is happening, perhaps we can come up with a switch for using english date here.
> Env:
> devstudio-10.2.0.AM1-v20160920-0457-B6061-installer-standalone.jar
> cdk 2.2.rc5
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4133:
------------------------------------
Assignee: Xavier Coulon (was: Nick Boldt)
> Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Fix For: 10.2.0.AM3
>
>
> Snippet from log attached to JBDS-4131:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-21 14:55:03.519
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477058103380-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> And
> {code}
> !ENTRY org.eclipse.help.base 4 0 2016-10-21 14:32:21.719
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610121400 [389]. Please use an index built with Lucene 5 or higher.
> {code}
> then 100s of errors like this:
> {code}
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_preferencePages.html cannot be opened.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4133) Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4133?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4133:
---------------------------------
Priority: Critical (was: Major)
> Help docs cannot be opened: org.apache.lucene.index.IndexFormatTooOldException - got 2.0.3, want 5.0+
> -----------------------------------------------------------------------------------------------------
>
> Key: JBDS-4133
> URL: https://issues.jboss.org/browse/JBDS-4133
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 10.2.0.AM3
>
>
> Snippet from log attached to JBDS-4131:
> {code}
> !ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-21 14:55:03.519
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477058103380-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){code}
> And
> {code}
> !ENTRY org.eclipse.help.base 4 0 2016-10-21 14:32:21.719
> !MESSAGE Error trying to consume Lucene index from bundle org.eclipse.wst.sse.doc.user_1.1.100.v201610121400 [389]. Please use an index built with Lucene 5 or higher.
> {code}
> then 100s of errors like this:
> {code}
> !MESSAGE Help document /org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_ui_preferencePages.html cannot be opened.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-4014:
------------------------------------
Resolution: (was: Done)
Assignee: Mat Booth (was: Alexey Kazakov)
Let's keep it open until we don't merge the [~mat.booth]'s patch to github/master.
BTW, has the new patch which uses Product ID been created/applied?
> Track rh-eclipse46-devstudio-*.rpm version usage
> ------------------------------------------------
>
> Key: JBDS-4014
> URL: https://issues.jboss.org/browse/JBDS-4014
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: rpm, usage
> Reporter: Alexey Kazakov
> Assignee: Mat Booth
> Priority: Critical
> Fix For: 10.2.0.AM3
>
>
> We need to distinguish the following use cases:
> 1) Devstudio installed via RPM
> 2) Devstudio installed via P2 but on top of the "base" eclipse rpm
> 3) Devstudio installed traditionally (jar installer or p2)
> As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4014:
---------------------------------
Priority: Major (was: Critical)
> Track rh-eclipse46-devstudio-*.rpm version usage
> ------------------------------------------------
>
> Key: JBDS-4014
> URL: https://issues.jboss.org/browse/JBDS-4014
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: rpm, usage
> Reporter: Alexey Kazakov
> Assignee: Mat Booth
> Fix For: 10.2.0.AM3
>
>
> We need to distinguish the following use cases:
> 1) Devstudio installed via RPM
> 2) Devstudio installed via P2 but on top of the "base" eclipse rpm
> 3) Devstudio installed traditionally (jar installer or p2)
> As a bonus we could want to track if the DTS + devstudio rpms were both installed.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4131:
----------------------------------
JAX-RS error details:
{code}
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}
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months
[JBoss JIRA] (JBDS-4131) Can't import example project after RPM installation on RHEL 7
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4131?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4131 at 10/26/16 4:57 PM:
------------------------------------------------------------
JAX-RS error details - see JBDS-4133:
{code}
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}
was (Author: nickboldt):
JAX-RS error details:
{code}
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}
> Can't import example project after RPM installation on RHEL 7
> -------------------------------------------------------------
>
> Key: JBDS-4131
> URL: https://issues.jboss.org/browse/JBDS-4131
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm
> Affects Versions: 10.2.0.AM3
> Environment: RHEL Server 7.2.
> Reporter: Lukáš Valach
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: DevstudiErrorLog.txt, devstudio10.2.wtf.png, devstudio10.2.wtf2.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-lucene-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132-wagon-provider-error.png, html5-project-quickstart-working-after-update-to-m2e171-m2ewtp132.png, import_wizard.png, maven-wizard-devstudio10.2-rpm-busted.png, maven.importer.error.log, rh-eclipse46-devstudio.repo
>
>
> During the test of RPM installation on RHEL 7 I noticed that I can't import HTML5 example project from central. Only the window with message "Refreshing project examples" appear for a while and then nothing happens.
> There is one warning and many errors in Error Log View.
> Error log export: [^DevstudiErrorLog.txt]
> I also tried to import project from file system, but there isn't the "Existing Maven Project" option in the import wizard. [^import_wizard.png]
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
9 years, 5 months