[JBoss JIRA] (JBTIS-873) Follow name convetions for archive files from devstudio
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-873?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-873.
-----------------------------------
Verified with JBDS-IS 9.0.2 which contains
{code}
devstudio-integration-stack-9.0.2.GA-updatesite.jar
devstudio-integration-stack-9.0.2.GA-standalone-installer.jar
{code}
> Follow name convetions for archive files from devstudio
> -------------------------------------------------------
>
> Key: JBTIS-873
> URL: https://issues.jboss.org/browse/JBTIS-873
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 10.0.0.Alpha1
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 10.0.0.GA, 9.0.2.GA
>
>
> Currently, the name is
> {code}
> devstudio-integration-stack-10.0.0.Alpha1-SNAPSHOT-earlyaccess.zip
> {code}
> I suggest to follow name conventions from devstudio, e.g.
> {code}
> devstudio-integration-stack-10.0.0.Alpha1-updatesite.zip
> devstudio-integration-stack-10.0.0.Alpha1-updatesite-earlyaccess.zip
> devstudio-integration-stack-10.0.0.Alpha1-standalone-installer.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBTIS-872) Rename the name of the standalone installer
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-872?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-872.
-----------------------------------
Verified with JBDS-IS 9.0.2 which contains
{code}
devstudio-integration-stack-9.0.2.GA-updatesite.jar
devstudio-integration-stack-9.0.2.GA-standalone-installer.jar
{code}
> Rename the name of the standalone installer
> -------------------------------------------
>
> Key: JBTIS-872
> URL: https://issues.jboss.org/browse/JBTIS-872
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 4.0.0
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 10.0.0.GA, 9.0.2.GA
>
>
> Currently, the name is
> {code}
> devstudio-is-installer-9.0.2-SNAPSHOT.jar
> {code}
> I suggest to follow the convention from devstudio installer, e.g.
> {code}
> devstudio-integration-stack-9.0.2-SNAPSHOT-installer.jar
> devstudio-integration-stack-9.0.2-SNAPSHOT-standalone-installer.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23312) When an OS certificate is accepted, the preference is not always saved
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23312?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-23312:
-----------------------------------------------
I noticed that when we set a value to a preference store, we rely on Eclipse saving it automatically. Maybe that is not safe. This change in SSLCertificatesPreference may help.
{code}
private void saveItemsToPreference(List<Item> items) {
StringBuilder sb = new StringBuilder();
items.stream().forEach(i->sb.append(i.toPreferenceValue()));
getPreferenceStore().setValue(ALLOWED_CERTIFICATES, sb.toString());
if(getPreferenceStore() instanceof IPersistentPreferenceStore) {
try {
((IPersistentPreferenceStore)getPreferenceStore()).save();
} catch (IOException e) {
///ignore
}
}
}
{code}
[~jeffmaury], if you reproduce the issue, please try it.
> When an OS certificate is accepted, the preference is not always saved
> ----------------------------------------------------------------------
>
> Key: JBIDE-23312
> URL: https://issues.jboss.org/browse/JBIDE-23312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM1
> Reporter: Jeff MAURY
> Labels: openshift, openshift_v3, preferences
> Fix For: 4.4.2.AM3
>
>
> EXEC: clean up Openshift V3 SSL certificates
> EXEC: connect to Openshift
> ASSERT: the certificate dialog should pop up
> EXEC:accept the cerificate and select remember
> EXEC: stop Eclipse
> EXEC: start Eclipse
> EXEC: connect to Openshift
> ASSERT: the certificate dialog popups again
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23316) BrowserSim save screenshot fails with ArrayIndexOutOfBoundsException
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23316?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-23316:
-------------------------------
Fix Version/s: 4.4.2.AM2
> BrowserSim save screenshot fails with ArrayIndexOutOfBoundsException
> --------------------------------------------------------------------
>
> Key: JBIDE-23316
> URL: https://issues.jboss.org/browse/JBIDE-23316
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.4.2.AM2
> Reporter: Pavol Srna
> Fix For: 4.4.2.AM2
>
>
> {code}
> 2016-10-11 17:13:48.461:INFO::JavaFX Application Thread: Logging initialized @1366ms
> 2016-10-11 17:13:48.566:INFO:oejs.Server:JavaFX Application Thread: jetty-9.3.9.v20160517
> 2016-10-11 17:13:48.616:INFO:oejsh.ContextHandler:JavaFX Application Thread: Started o.e.j.s.ServletContextHandler@433defed{/,null,AVAILABLE}
> 2016-10-11 17:13:48.630:INFO:oejs.AbstractConnector:JavaFX Application Thread: Started ServerConnector@6f53b8a{HTTP/1.1,[http/1.1]}{0.0.0.0:64959}
> 2016-10-11 17:13:48.630:INFO:oejs.Server:JavaFX Application Thread: Started @1535ms
> Failed to execute runnable (java.lang.ArrayIndexOutOfBoundsException: 383097)
> Stack trace:
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ArrayIndexOutOfBoundsException: 383097)
> at org.eclipse.swt.SWT.error(SWT.java:4533)
> at org.eclipse.swt.SWT.error(SWT.java:4448)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> at org.jboss.tools.browsersim.ui.launch.BrowserSimRunner.main(BrowserSimRunner.java:127)
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 383097
> at org.eclipse.swt.graphics.Image.createRepresentaion(Image.java:1204)
> at org.eclipse.swt.graphics.Image.init(Image.java:1108)
> at org.eclipse.swt.graphics.Image.<init>(Image.java:429)
> at org.jboss.tools.browsersim.ui.menu.ScreenshotMenuCreator.takeScreenshot(ScreenshotMenuCreator.java:173)
> at org.jboss.tools.browsersim.ui.menu.ScreenshotMenuCreator.access$0(ScreenshotMenuCreator.java:138)
> at org.jboss.tools.browsersim.ui.menu.ScreenshotMenuCreator$1$1.run(ScreenshotMenuCreator.java:69)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> ... 3 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23316) BrowserSim save screenshot fails with ArrayIndexOutOfBoundsException
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-23316:
----------------------------------
Summary: BrowserSim save screenshot fails with ArrayIndexOutOfBoundsException
Key: JBIDE-23316
URL: https://issues.jboss.org/browse/JBIDE-23316
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: browsersim
Affects Versions: 4.4.2.AM2
Reporter: Pavol Srna
{code}
2016-10-11 17:13:48.461:INFO::JavaFX Application Thread: Logging initialized @1366ms
2016-10-11 17:13:48.566:INFO:oejs.Server:JavaFX Application Thread: jetty-9.3.9.v20160517
2016-10-11 17:13:48.616:INFO:oejsh.ContextHandler:JavaFX Application Thread: Started o.e.j.s.ServletContextHandler@433defed{/,null,AVAILABLE}
2016-10-11 17:13:48.630:INFO:oejs.AbstractConnector:JavaFX Application Thread: Started ServerConnector@6f53b8a{HTTP/1.1,[http/1.1]}{0.0.0.0:64959}
2016-10-11 17:13:48.630:INFO:oejs.Server:JavaFX Application Thread: Started @1535ms
Failed to execute runnable (java.lang.ArrayIndexOutOfBoundsException: 383097)
Stack trace:
org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.ArrayIndexOutOfBoundsException: 383097)
at org.eclipse.swt.SWT.error(SWT.java:4533)
at org.eclipse.swt.SWT.error(SWT.java:4448)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:185)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4024)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
at org.jboss.tools.browsersim.ui.launch.BrowserSimRunner.main(BrowserSimRunner.java:127)
Caused by: java.lang.ArrayIndexOutOfBoundsException: 383097
at org.eclipse.swt.graphics.Image.createRepresentaion(Image.java:1204)
at org.eclipse.swt.graphics.Image.init(Image.java:1108)
at org.eclipse.swt.graphics.Image.<init>(Image.java:429)
at org.jboss.tools.browsersim.ui.menu.ScreenshotMenuCreator.takeScreenshot(ScreenshotMenuCreator.java:173)
at org.jboss.tools.browsersim.ui.menu.ScreenshotMenuCreator.access$0(ScreenshotMenuCreator.java:138)
at org.jboss.tools.browsersim.ui.menu.ScreenshotMenuCreator$1$1.run(ScreenshotMenuCreator.java:69)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
... 3 more
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23160) Update m2e-wtp and m2eclipse-tycho in jbosstools and jbdevstudio target platforms (4.61.0.AM1-SNAPSHOT)
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23160?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23160.
--------------------------------
Verified in 4.4.2.AM2.
> Update m2e-wtp and m2eclipse-tycho in jbosstools and jbdevstudio target platforms (4.61.0.AM1-SNAPSHOT)
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23160
> URL: https://issues.jboss.org/browse/JBIDE-23160
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.AM3
> Reporter: Paul Leacu
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM2
>
>
> The 1.3.1 version of m2e-wtp has been mirrored as well as the 0.9.0 version of m2eclipse-tycho. Please update in jbosstools-multiple for Neon. Also - please change https -> http for the locus update site URL reference.
> {code}
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <unit id="org.eclipse.m2e.wtp.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jaxrs.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jpa.feature.feature.group" version="1.3.1.20160831-1005"/>
> <unit id="org.eclipse.m2e.wtp.jsf.feature.feature.group" version="1.3.1.20160831-1005"/>
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2e-wtp/1.3.1.2..."/>
> </location>
> <location includeAllPlatforms="false" includeConfigurePhase="true" includeMode="slicer" includeSource="true" type="InstallableUnit">
> <unit id="org.sonatype.tycho.m2e.feature.feature.group" version="0.9.0.201609061714"/>
> <repository location="http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-tycho..."/>
> </location>
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg edited comment on JBDS-4085 at 10/11/16 10:22 AM:
------------------------------------------------------------------
You could use a .options files in the directory from which you start eclipse (or provide it after the -debug option) to get more debugging information during startup. For more detailed information than that, I use a java profiler. I'll try reproducing your cases to see what's going on.
$ cat ~/.options
org.eclipse.equinox.p2.core/debug=true
org.eclipse.equinox.p2.core/reconciler=true
was (Author: rgrunber):
You could use a .options files in the directory from which you start eclipse (or provide it after the -debug option) to get more debugging information during startup. For more detailed information than that, I use a java profiler. I'll try reproducing your cases to see what's going on.
> unresolved bundles, slow initial start up
> -----------------------------------------
>
> Key: JBDS-4085
> URL: https://issues.jboss.org/browse/JBDS-4085
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Attachments: restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
> * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
> * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
> * "min" in the name means minimal install rh-eclipse46-devstudio
> * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
> * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4085) unresolved bundles, slow initial start up
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/JBDS-4085?page=com.atlassian.jira.plugin.... ]
Roland Grunberg commented on JBDS-4085:
---------------------------------------
You could use a .options files in the directory from which you start eclipse (or provide it after the -debug option) to get more debugging information during startup. For more detailed information than that, I use a java profiler. I'll try reproducing your cases to see what's going on.
> unresolved bundles, slow initial start up
> -----------------------------------------
>
> Key: JBDS-4085
> URL: https://issues.jboss.org/browse/JBDS-4085
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Reporter: Václav Kadlčík
> Attachments: restart-after-installing-m2e-wtp-jsf-stuff-from-Central.txt, restart-after-installing-m2e-wtp-jsf-stuff-from-Central_full.txt, unresolved-max.out, unresolved-mid.out, unresolved-min.out, workspace-max.log, workspace-mid.log, workspace-min.log
>
>
> Tested:
> * rh-eclipse46-devstudio-10.2-0.20161004.2205.el7.x86_64.rpm
> * rh-eclipse46 Beta (http://download-node-02.eng.bos.redhat.com/rel-eng/RHSCL-2.3-RHEL-7-Beta-...)
> rh-eclipse46 has its own unresolved bundles (https://bugzilla.redhat.com/show_bug.cgi?id=1381820). But when you add rh-eclipse46-devstudio, the number of unresolved symbols increases quite dramatically and initial start up times also get worse. (I guess that the two problems can be connected so I file them together but feel free to split them if I'm mistaken).
> I'm attaching "ss -s INSTALLED" and workspace logs for several scenarios:
> * "min" in the name means minimal install rh-eclipse46-devstudio
> * "mid" is for "yum install rh-eclipse46 rh-eclipse46-devstudio"
> * "max" is for "yum install 'rh-eclipse46*'" - all the available RPMs, including devstudio
> As for start up times, it looks like devstudio adds ~80s for one particular machine (Xeon with 16 cores 2.40GHz, 16 GB RAM). For example:
> initial start of rh-eclipse46: 40s
> same as above with rh-eclipse46-devstudio: 120s
> initial start of rh-eclipse46* except devstudio: 50s
> same as above with rh-eclipse46-devstudio: 140s
> Roland Grunberg managed to improve initial start up times in rh-eclise46 a few weeks ago (https://bugzilla.redhat.com/show_bug.cgi?id=1362178#c17). I don't know it it helps here but I'm linking it anyway...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months