[JBoss JIRA] (JBDS-4193) Build Bundle Installer for macOS
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4193?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4193.
-----------------------------
Tried with last build and got it to work just fine. Closing.
> Build Bundle Installer for macOS
> --------------------------------
>
> Key: JBDS-4193
> URL: https://issues.jboss.org/browse/JBDS-4193
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Environment: macOS
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.GA
>
>
> Current configuration supports only build for online installer. Build should be migrated from building using cli build command and configuration defined in package.json to electron-builder API. That would let to build online and then bundled installer just by calling builder with dynamic configuration.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23049) Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23049?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23049.
---------------------------------
I just tried this now with Neon.1a and JBT 4.4.0.Final staging update site (install all) and I cannot replicate it. So closing.
> Error in org.jboss.tools.common.mylyn after installing JBossTools in Eclipse Neon.1 RC2
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-23049
> URL: https://issues.jboss.org/browse/JBIDE-23049
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.4.1.Final
> Environment: Eclipse SDK
> Version: Neon.1 (4.6.1)
> Build id: M20160824-0059
> JBoss Tools from update site:
> http://download.jboss.org/jbosstools/neon/snapshots/updates/
> org.jboss.tools.common.mylyn:
> 3.8.1.v20160607-2053
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Fix For: 4.4.2.AM2
>
>
> An error is shown in error log after installing JBoss Tools in Eclipse Neon.1 RC2:
> {code:java}
> Unexpected error while loading repository template extensions
> Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'bugzilla'
> {code}
> Stacktrace:
> {code:java}
> An exception stack trace is not available.
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-22897) ZipException below JarAccess.getContent (thrown in ZipFile.read)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22897?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22897.
---------------------------------
I agree that the error message is reasonable. Closing.
> ZipException below JarAccess.getContent (thrown in ZipFile.read)
> ----------------------------------------------------------------
>
> Key: JBIDE-22897
> URL: https://issues.jboss.org/browse/JBIDE-22897
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common
> Affects Versions: 4.3.0.Final
> Reporter: Automated Error Reporting Bot
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.2.AM2
>
>
> The following problem was reported via the automated error reporting:
> Message: Exception occurs when reading C:\Users\d18r6979550\.m2\repository\org\jboss\resteasy\resteasy-client\3.0.14.Final\resteasy-client-3.0.14.Final.jar
> {noformat}
> java.util.zip.ZipException: invalid LOC header (bad signature)
> at java.util.zip.ZipFile.read(null:-2)
> at java.util.zip.ZipFile.access$1400(null:-1)
> at java.util.zip.ZipFile$ZipFileInputStream.read(null:-1)
> at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(null:-1)
> at java.util.zip.InflaterInputStream.read(null:-1)
> at java.io.BufferedInputStream.fill(null:-1)
> at java.io.BufferedInputStream.read1(null:-1)
> at java.io.BufferedInputStream.read(null:-1)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.getContent(JarAccess.java:235)
> at org.jboss.tools.common.model.filesystems.impl.JarAccess.isTextEntry(JarAccess.java:266)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.createFileObject(JarFolderImpl.java:95)
> at org.jboss.tools.common.model.filesystems.impl.JarFolderImpl.loadChildren(JarFolderImpl.java:78)
> at org.jboss.tools.common.model.impl.RegularObjectImpl.getChildren(RegularObjectImpl.java:73)
> at org.jboss.tools.jst.web.kb.internal.scanner.LibraryScanner.parse(LibraryScanner.java:92)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.doProcess(ClassPathMonitor.java:105)
> at org.jboss.tools.jst.web.kb.internal.scanner.ClassPathMonitor.process(ClassPathMonitor.java:76)
> at org.jboss.tools.jst.web.kb.internal.KbProject.load(KbProject.java:362)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolveStorage(KbProject.java:315)
> at org.jboss.tools.jst.web.kb.internal.KbProject.resolve(KbProject.java:330)
> at org.jboss.tools.jst.web.kb.KbProjectFactory.getKbProject(KbProjectFactory.java:72)
> at org.jboss.tools.cdi.core.CDICoreNature._loadProjectDependencies(CDICoreNature.java:678)
> at org.jboss.tools.cdi.core.CDICoreNature.loadProjectDependenciesFromKBProject(CDICoreNature.java:674)
> at org.jboss.tools.cdi.core.CDICoreNature.loadProjectDependencies(CDICoreNature.java:665)
> at org.jboss.tools.cdi.core.CDICorePlugin.getCDI(CDICorePlugin.java:167)
> at org.jboss.tools.cdi.core.CDIUtil.enableCDI(CDIUtil.java:149)
> at org.jboss.tools.cdi.internal.core.project.facet.CDIFacetInstallDelegate.execute(CDIFacetInstallDelegate.java:66)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:324)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2241)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installCDIFacet(CDIProjectConfigurator.java:174)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installDefaultFacets(CDIProjectConfigurator.java:162)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configureInternal(CDIProjectConfigurator.java:108)
> at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configure(CDIProjectConfigurator.java:87)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:168)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:136)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:68)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:62)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:77)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> Bundles:
> | org.eclipse.core.jobs | 3.7.0.v20150330-2103 | 3.8.0.v20160509-0411 |
> | org.eclipse.core.resources | 3.10.1.v20150725-1910 | 3.11.0.v20160503-1608 |
> | org.eclipse.core.runtime | 3.11.1.v20150903-1804 | 3.12.0.v20160606-1342 |
> | org.eclipse.jdt | 3.11.2.v20160212-1500 | 3.12.0.v20160606-1100 |
> | org.eclipse.jdt.core | 3.11.2.v20160128-0629 | 3.12.0.v20160516-2131 |
> | org.eclipse.jdt.ui | 3.11.2.v20151123-1510 | 3.12.0.v20160525-1829 |
> | org.eclipse.jface | 3.11.1.v20160128-1644 | 3.12.0.v20160518-1929 |
> | org.eclipse.jface.text | 3.11.0.v20160505-1301 | 3.11.0.v20160505-1301 |
> | org.eclipse.m2e.core | 1.6.3.20160209-1446 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.core.ui | 1.6.3.20160209-1446 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.jdt | 1.7.0.20160603-1933 | 1.7.0.20160603-1933 |
> | org.eclipse.m2e.wtp | 1.2.1.20150819-2220 | 1.3.0.20160530-2310 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.eclipse.ui.navigator | 3.6.100.v20160518-1929 | 3.6.100.v20160518-1929 |
> | org.eclipse.wst.common.project.facet.core | 1.4.300.v201111030423 | 1.4.300.v201111030423 |
> | org.eclipse.wst.jsdt.core | 2.0.0.v201605251700 | 2.0.0.v201605251700 |
> | org.eclipse.wst.sse.ui | 1.3.401.v201510130005 | 1.3.500.v201605120129 |
> | org.eclipse.wst.validation | 1.2.700.v201508251749 | 1.2.700.v201508251749 |
> | org.jboss.tools.batch.core | 1.8.0.Final-v20160610-0126-B1 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.cdi.core | 1.7.1.Final-v20160330-2256-B84 | 1.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.common | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.el.core | 3.8.0.Final-v20160610-1533-B7 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.model | 3.7.1.Final-v20160408-2358-B112 | 3.8.1.v20160607-2053 |
> | org.jboss.tools.common.model.ui | 3.8.0.Final-v20160610-1533-B7 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.common.validation | 3.7.1.Final-v20160408-2358-B112 | 3.8.0.Final-v20160610-1533-B7 |
> | org.jboss.tools.jsf | 3.7.1.Final-v20160330-2256-B84 | 3.8.0.Final-v20160610-0126-B1 |
> | org.jboss.tools.jst.web | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> | org.jboss.tools.jst.web.kb | 3.7.1.Final-v20160331-0256-B96 | 3.8.1.v20160607-2115 |
> | org.jboss.tools.jst.web.ui | 3.8.0.Final-v20160609-2146-B2 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.maven.cdi | 1.7.1.Final-v20160401-1059-B103 | 1.8.0.Final-v20160613-2000-B8 |
> Operating Systems:
> | Linux | 3.10.0.22 | 4.6.4.fc24 |
> | MacOSX | 10.11.5 | 10.11.6 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/5729a811e4b0a54983...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21857 at 11/29/16 4:53 AM:
-----------------------------------------------------------------
Few observations. After starting debugging JMX is still disconnected, probably this should get fixed. After restarting a module, when incompatible HCR change is done, debugger still say it is out of sync, even though module has been redeployed on a remote server successfully. Steps to reproduce updated further for more detailed steps to reproduce.
was (Author: mlabuda):
Few observations. After starting debugging JMX is still disconnected, probably this should get fixed. After restarting a module, when incompatible HCR change is done, debugger still say it is out of sync, even though module has been redeployed on a remote server successfully.
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21857 at 11/29/16 4:52 AM:
-----------------------------------------------------------------
Few observations. After starting debugging JMX is still disconnected, probably this should get fixed. After restarting a module, when incompatible HCR change is done, debugger still say it is out of sync, even though module has been redeployed on a remote server successfully.
was (Author: mlabuda):
Few observations. After starting debugging JMX is still disconnected, probably this should get fixed. After restarting a module, when a noncompatible HCR change is done, debugger still say it is out of sync, even though module has been redeployed on a remote server.
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-21857) Hot code replacement doesn't work on OpenShift
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21857?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-21857:
----------------------------------
Steps to Reproduce:
EXEC: Create a new OpenShift EAP 6.4 application. Open New OpenShift application wizard, select eap64-basic-s2i template, proceed to next wizard page, change CONTEXT_DIR param to helloworld, click Finish and let import application to your workspace once you are prompted.
EXEC: Create a new OpenShift 3 server adapter for the application.
ASSERT: There is a started server adapter for the application in Servers view.
EXEC: Restart server adapter in debug mode.
ASSERT: Server adapter is in debug mode, synchronized.
EXEC: Expand server adapter.
ASSERT: JMX is connected (bug JBIDE-21857, if it is disconnected, double click on the button and wait to connect).
EXEC: Rename method or add a field to class (e.g. in HelloService) = do HCR incompatible change in class structure.
EXEC: Save editor.
ASSERT: Dialog warning about failed HCR is shown.
EXEC: Click button Restart buttons in Hot Code Replace Failed dialog.
ASSERT: Module is deployed on a remote server.
RESULT: Debugger is out of sync.
EXPECTED RESULT: Debugger is back to sync.
EXEC: Make a HCR compatible change (in method body e.g. change returned message).
EXEC: Save editor.
RESULT: Hot Code Replace Failed dialog is shown.
EXPECTED RESULT: Change is propagated successfully, there is no HCR Failed dialog and debugger is in sync.
was:
ASSERT: Have a running OpenShift java application on OpenShift with a server adapter. For example the one instantiated by eap64-basic-template.
EXEC: Create a new OpenShift 3 server adapter for the application.
EXEC: Restart server adapter in debug mode.
EXEC: Rename method or add a field to class.
ASSERT: Dialog warning about failed HCR is shown.
EXEC: Reload the module.
EXEC: Make change HCR compatible (e.g. method body).
RESULT: HCR compatible change hasn't take effect.
EXPECTED RESULT: Upon module restart and HCR compatible change this change will be visible, debugger get back to sync.
> Hot code replacement doesn't work on OpenShift
> ----------------------------------------------
>
> Key: JBIDE-21857
> URL: https://issues.jboss.org/browse/JBIDE-21857
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final, 4.4.3.AM1, 4.5.0.AM1
>
> Attachments: HCRFailure.zip
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4196) MSI installed OpenJDK detection does not work
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4196?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4196.
-----------------------------
Verified in B249.
> MSI installed OpenJDK detection does not work
> ---------------------------------------------
>
> Key: JBDS-4196
> URL: https://issues.jboss.org/browse/JBDS-4196
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Environment: Windows
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Critical
> Labels: regression
> Fix For: 10.2.0.GA
>
>
> Installer first tries to find OpenJDK in windows registry. It indicates if there is OpenJDK installed from MSI installer. If there is MSI installed OpenJDK, the user is not allowed install OpenJDK delivered with DevSuite Installer, because update is not supported for all OpenJDK builds and install over older version could fail.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months