June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3071: ---------------------------------- PR 196 pushed and building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.product_ma... >2247 > JBDS Installer shouldn't contain source features/plugins > -------------------------------------------------------- > > Key: JBDS-3071 > URL: https://issues.jboss.org/browse/JBDS-3071 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 8.0.0.Beta3 > > > {quote} > So the basic JBDS installer is 70MB fatter. From my understanding it's because we now ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor stuff. > Fair enough. But do we *really* need to add all the source features/plugins to the installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't we provide them via an other way? (p2 only). > I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is cheap and d/l speeds are faster but that's not an excuse. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3071 at 6/30/14 1:11 PM: ----------------------------------------------------------- Actually, Central/EA sites do NOT contain jst.jsdt, but EA does include: * Arquillian (and Sapphire) * AngularJS (and Tern) * VJET (and Jetty) jst.jsdt is currently only in JBT afaict. So this too is an improvement. New PR to remove things that were in the JBDS update site but which are not included in the installer: https://github.com/jbdevstudio/jbdevstudio-product/pull/201 Removed items include: * org.jboss.tools.vpe.cordovasim.feature (and source) * org.jboss.tools.maven.jbosspackaging.feature (and source) * org.jboss.tools.common.mylyn.feature (and source) Problem w/ removing these is that the JBDS Central plugin.xml requirs all three of them in these connectors: * JBoss Hybrid Mobile Tools + CordovaSim * JBoss Tools Maven Packaging Configurator * Mylyn support for reporting JBoss JIRAs and Red Hat Bugzillas So if we remove them, then those connectors can't be installed in JBDS. Possible workarounds: a) do nothing and accept that for offline installs, you need the update site (not the installer) + central zip; also accept that the installer != update site b) put these 3 features in the installer so that the installer contents == the update site contents (except for sources) c) move these 3 features into the JBDS TP; this is bad because it creates an ugly dependency chain: JBDS -> JBDS TP -> JBT -> JBT TP... every time JBT rebuilds, we need to update the version of org.jboss.tools.* in the JBDS TP d) move these 3 features into the Central TP; this is bad in that as in (c) we would have to keep updating the Central TP each time there's a new JBT release... but we already have this problem because of Arquillian being included in the EA TP. So... I'd vote for (b) [easiest] or (d) [cleanest but requires more maintenance when we push out milestones]. was (Author: nickboldt): Actually, Central/EA sites do NOT contain jst.jsdt, but EA does include: * Arquillian (and Sapphire) * AngularJS (and Tern) * VJET (and Jetty) jst.jsdt is currently only in JBT afaict. So this too is an improvement. New PR to remove things that were in the JBDS update site but which are not included in the installer: https://github.com/jbdevstudio/jbdevstudio-product/pull/201 Removed items include: * org.jboss.tools.vpe.cordovasim.feature (and source) * org.jboss.tools.maven.jbosspackaging.feature (and source) * org.jboss.tools.common.mylyn.feature (and source) > JBDS Installer shouldn't contain source features/plugins > -------------------------------------------------------- > > Key: JBDS-3071 > URL: https://issues.jboss.org/browse/JBDS-3071 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 8.0.0.Beta3 > > > {quote} > So the basic JBDS installer is 70MB fatter. From my understanding it's because we now ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor stuff. > Fair enough. But do we *really* need to add all the source features/plugins to the installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't we provide them via an other way? (p2 only). > I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is cheap and d/l speeds are faster but that's not an excuse. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17724: ----------------------------------- Component/s: server > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17725) Cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 to Beta2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17725?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17725: ----------------------------------- Component/s: build > Cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 to Beta2 > ----------------------------------------------------------------------- > > Key: JBIDE-17725 > URL: https://issues.jboss.org/browse/JBIDE-17725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Marek Novotny > > I cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 > Build id: Beta1-v20140408-2350-B93 > Build date: 20140408-2350 > I got the following error while tried Check update on JBoss Central: > {noformat} > Some sites could not be found. See the error log for more detail. > No repository found at http://download.jboss.org/jbosstools/updates/development/luna/. > No repository found at https://devstudio.jboss.com/updates/8.0-development/. > No repository found at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/. > {noformat} > All three URLs are valid update sites or should be. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3071: ---------------------------------- Actually, Central/EA sites do NOT contain jst.jsdt, but EA does include: * Arquillian (and Sapphire) * AngularJS (and Tern) * VJET (and Jetty) jst.jsdt is currently only in JBT afaict. So this too is an improvement. New PR to remove things that were in the JBDS update site but which are not included in the installer: https://github.com/jbdevstudio/jbdevstudio-product/pull/201 Removed items include: * org.jboss.tools.vpe.cordovasim.feature (and source) * org.jboss.tools.maven.jbosspackaging.feature (and source) * org.jboss.tools.common.mylyn.feature (and source) > JBDS Installer shouldn't contain source features/plugins > -------------------------------------------------------- > > Key: JBDS-3071 > URL: https://issues.jboss.org/browse/JBDS-3071 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 8.0.0.Beta3 > > > {quote} > So the basic JBDS installer is 70MB fatter. From my understanding it's because we now ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor stuff. > Fair enough. But do we *really* need to add all the source features/plugins to the installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't we provide them via an other way? (p2 only). > I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is cheap and d/l speeds are faster but that's not an excuse. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17720) Can't install ADT from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17720?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17720: ------------------------------------ Building https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >= 2903 > Can't install ADT from Central > ------------------------------ > > Key: JBIDE-17720 > URL: https://issues.jboss.org/browse/JBIDE-17720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.2.0.Beta3 > > Attachments: ADT23.0-installed-prompts-for-new-SDK-install.png, adtinstallationerror0.png, adtinstallationerror1.png > > > Installation tests are failing to install Android Development Tools from Central. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17725) Cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 to Beta2

by Marek Novotny (JIRA)

Marek Novotny created JBIDE-17725: ------------------------------------- Summary: Cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 to Beta2 Key: JBIDE-17725 URL: https://issues.jboss.org/browse/JBIDE-17725 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Marek Novotny I cannot update from JBoss Developer Studio Version: 8.0.0.Beta1 Build id: Beta1-v20140408-2350-B93 Build date: 20140408-2350 I got the following error while tried Check update on JBoss Central: {noformat} Some sites could not be found. See the error log for more detail. No repository found at http://download.jboss.org/jbosstools/updates/development/luna/. No repository found at https://devstudio.jboss.com/updates/8.0-development/. No repository found at http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/. {noformat} All three URLs are valid update sites or should be. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17720) Can't install ADT from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17720?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-17720: ---------------------------------- Assignee: Nick Boldt > Can't install ADT from Central > ------------------------------ > > Key: JBIDE-17720 > URL: https://issues.jboss.org/browse/JBIDE-17720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.2.0.Beta3 > > Attachments: ADT23.0-installed-prompts-for-new-SDK-install.png, adtinstallationerror0.png, adtinstallationerror1.png > > > Installation tests are failing to install Android Development Tools from Central. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-17724: ---------------------------------- Summary: Changes cause full redeployment of exploded WAR Key: JBIDE-17724 URL: https://issues.jboss.org/browse/JBIDE-17724 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.2.0.Beta2 Environment: Windows 8.1 x64 Java 7u51 x64 Luna x64 Reporter: Cody Lerum After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17720) Can't install ADT from Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17720?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17720: ------------------------------- Attachment: ADT23.0-installed-prompts-for-new-SDK-install.png With PR https://github.com/jbosstools/jbosstools-discovery/pull/181 applied locally, I could install ADT from local discovery site: {code} -Djboss.discovery.directory.url=http://localhost:8080/jbosstools/org.jboss.tools.central.discovery.earlyaccess/target/discovery-site/jbosstools-directory.xml -Djboss.discovery.site.url=http://localhost:8080/jbosstools/org.jboss.tools.central.discovery.earlyaccess/target/discovery-site/ -Djboss.discovery.earlyaccess.site.url=http://localhost:8080/jbosstools/org.jboss.tools.central.discovery.earlyaccess/target/discovery-site/ {code} Result: !ADT23.0-installed-prompts-for-new-SDK-install.png! > Can't install ADT from Central > ------------------------------ > > Key: JBIDE-17720 > URL: https://issues.jboss.org/browse/JBIDE-17720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Mickael Istria > Fix For: 4.2.0.Beta3 > > Attachments: ADT23.0-installed-prompts-for-new-SDK-install.png, adtinstallationerror0.png, adtinstallationerror1.png > > > Installation tests are failing to install Android Development Tools from Central. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 11 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2014