[JBoss JIRA] (JBIDE-22279) Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22279?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22279:
-------------------------------
Description:
Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed:
{code} Software being installed: Mylyn Context Connector: Plug-in Development 3.18.0.v20151013-1847 (org.eclipse.mylyn.pde_feature.feature.group 3.18.0.v20151013-1847)
Software currently installed: Mylyn Context Connector: Java Development 3.19.0.v20160111-2059 (org.eclipse.mylyn.java_feature.feature.group 3.19.0.v20160111-2059)
{code}
Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again.
was:
Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed.
Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again.
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22279
> URL: https://issues.jboss.org/browse/JBIDE-22279
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update, target-platform, upstream
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide22279.png
>
>
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed:
> {code} Software being installed: Mylyn Context Connector: Plug-in Development 3.18.0.v20151013-1847 (org.eclipse.mylyn.pde_feature.feature.group 3.18.0.v20151013-1847)
> Software currently installed: Mylyn Context Connector: Java Development 3.19.0.v20160111-2059 (org.eclipse.mylyn.java_feature.feature.group 3.19.0.v20160111-2059)
> {code}
> Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22279) Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22279?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22279:
-------------------------------
Story Points: 2
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-22279
> URL: https://issues.jboss.org/browse/JBIDE-22279
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central-update, target-platform, upstream
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide22279.png
>
>
> Cannot install all of DS Central into DS 10.0.0.Alpha1 on Neon.0.M6 (BYOE), as Central includes an older version of o.e.mylyn, 3.18 but 3.19 is already installed:
> {code} Software being installed: Mylyn Context Connector: Plug-in Development 3.18.0.v20151013-1847 (org.eclipse.mylyn.pde_feature.feature.group 3.18.0.v20151013-1847)
> Software currently installed: Mylyn Context Connector: Java Development 3.19.0.v20160111-2059 (org.eclipse.mylyn.java_feature.feature.group 3.19.0.v20160111-2059)
> {code}
> Opening this issue just as a reminder to check that we're using the same version of Neon/Mylyn in Central & TP so we don't hit this problem again.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22038) Errors on startup with Java 9
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22038?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22038:
----------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Errors on startup with Java 9
> -----------------------------
>
> Key: JBIDE-22038
> URL: https://issues.jboss.org/browse/JBIDE-22038
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.3.1.CR1
> Reporter: Jan Richter
> Assignee: Snjezana Peco
> Fix For: 4.4.0.Alpha2
>
>
> Starting fresh JBT/JBDS with Java 9 results in an error dialog popping up with these two errors:
> {noformat}An internal error occurred during: "Update project wizard list".
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:38)
> at org.jboss.tools.project.examples.internal.FavoriteExampleManager.<init>(FavoriteExampleManager.java:31)
> at org.jboss.tools.project.examples.internal.ProjectExamplesActivator.getFavoriteExampleManager(ProjectExamplesActivator.java:1064)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.collectFavorites(GettingStartedHtmlPage.java:282)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$5$2.run(GettingStartedHtmlPage.java:273)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 6 more{noformat}
> {noformat}An internal error occurred during: "Download quickstarts list".
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:396)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:273)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getCategories(ProjectExampleUtil.java:263)
> at org.jboss.tools.project.examples.internal.ProjectExampleXmlProvider.getExamples(ProjectExampleXmlProvider.java:28)
> at org.jboss.tools.project.examples.internal.ProjectExampleManager.getExamples(ProjectExampleManager.java:60)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$RefreshQuickstartsJob.run(GettingStartedHtmlPage.java:102)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 7 more{noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22110) Unexpected error when cancelling installation (using D&D to Central)
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22110?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-22110:
----------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Unexpected error when cancelling installation (using D&D to Central)
> --------------------------------------------------------------------
>
> Key: JBIDE-22110
> URL: https://issues.jboss.org/browse/JBIDE-22110
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central-update
> Affects Versions: 4.3.1.CR1
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Fix For: 4.4.0.Alpha2
>
>
> Screencast: https://youtu.be/LObzeMo8TDw
> Cancelling installation in phase "Retrieving listing" causes 3 unexpected errors:
> {noformat}
> java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:86)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:157)
> at org.eclipse.mylyn.internal.discovery.core.util.WebUtil.download(WebUtil.java:66)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:223)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor121.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.mylyn.internal.discovery.core.util.P2TransportService.download(P2TransportService.java:84)
> ... 8 more
> Caused by: org.eclipse.core.runtime.OperationCanceledException
> at org.eclipse.core.internal.jobs.JobManager.join(JobManager.java:999)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:359)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> ... 12 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3872) rename JBoss perspective?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3872?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3872:
----------------------------------
In terms of how to learn what type of user is installing DS... for the DS installer and the DP installer, we could add a page that asks the user into which perspective (collection of views & their default layout) they'd like to start DS: Containers, Java, JavaEE, JavaScript, Integration Stack).
For Marketplace and BYOE installs, we could provide a feature for each perspective and let users simply choose the feature that maps to the perspective they want to use on first start. I'm thinking these features would simply be wrappers for a p2.inf instruction to set a different default perspective for the first start. After that they can just CTRL-3 / CMD-3 and find the other perspectives they might want to use.
We could also use these "perspective features" the way that they exist in JBDS IS, in that they allow a user to cherry-pick which actual pieces of functionality to install from the Marketplace:
* JBoss Business Process and Rules Development (BPEL, BPMN2, jBPM, Drools, Guvnor)
* JBoss Data Virtualization Development (ModeShape, Teiid Designer)
* JBoss Fuse Development (Fuse tooling related to Camel route development)
* JBoss Integration and SOA Development (deprecated in JBDS IS 9.0)
If we wanted to bifurcate DS into smaller installable chunks, we could consider doing a similar thing, but I'd need to know that the functional blocks are, what they'd be called, and which features would be included in each block. (Yes, features can be shared across multiple blocks.)
Please note that I'm *not* suggesting we provide 4 or 5 different DS or DP installers; rather, I'm saying that we can provide the option for users to customize their Marketplace install (smaller footprint installed into Eclipse) but the installer-based installs will still install everything to disk, with the only customization option being the choice of initial perspective.
> rename JBoss perspective?
> -------------------------
>
> Key: JBDS-3872
> URL: https://issues.jboss.org/browse/JBDS-3872
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 10.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.0.0.Alpha2
>
> Attachments: icon-titlebar-jbds10.png
>
>
> Should we rename the default perspective that opens OOTB in devstudio so it's not the "JBoss Perspective? Reason I ask is that it's the first word you see in the titlebar when you fire up DS for the first time:
> !icon-titlebar-jbds10.png!
> We're rebranding Central, the product, and everything in Devstudio. Should we also rename the JBoss perspective?
> cc: [~fbricon] [~akazakov]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months