[JBoss JIRA] (JBIDE-17613) IWAB0014E Unexpected exception occurred
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17613?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick resolved JBIDE-17613.
---------------------------------------
Labels: (was: respin-a)
Resolution: Done
Cannot reproduce locally with current code - am waiting to see if it's reproducible in the Beta3 build.
> IWAB0014E Unexpected exception occurred
> ---------------------------------------
>
> Key: JBIDE-17613
> URL: https://issues.jboss.org/browse/JBIDE-17613
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: upstream, webservices
> Affects Versions: 4.2.0.Beta1
> Environment: OS: Microsoft Windows [versão 6.1.7601]
> JBoss Development Tools 8.0.0 Beta1
> wildfly-8.1.0.CR1
> Reporter: Jiri Peterka
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.Beta3
>
> Attachments: CommonComponents.xsd, FaultType.xsd, jbosstools-diagnostics-20140514154412.zip, VistoriaServiceMessageV1_0.xsd, VistoriaServiceSoap11V1_0.wsdl, VistoriaServiceV1_0.wsdl
>
>
> I try to generate the classes from a WSDL that is composed with the import of a seccond WSDL and an error happens.
> IWAB0014E Unexpected exception occurred.
>
> java.lang.NullPointerException
> at org.eclipse.jst.ws.internal.common.J2EEUtils.isComponentAssociated(J2EEUtils.java:1000)
> at org.eclipse.jst.ws.internal.common.J2EEUtils.isComponentAssociated(J2EEUtils.java:987)
> at org.eclipse.jst.ws.internal.consumption.command.common.AssociateModuleWithEARCommand.execute(AssociateModuleWithEARCommand.java:55)
> at org.eclipse.jst.ws.internal.consumption.ui.extension.PreClientAssembleCommand.execute(PreClientAssembleCommand.java:79)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.runCommand(CommandFragmentEngine.java:419)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.visitTop(CommandFragmentEngine.java:359)
> at org.eclipse.wst.command.internal.env.core.fragment.CommandFragmentEngine.moveForwardToNextStop(CommandFragmentEngine.java:254)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager$6.run(SimpleCommandEngineManager.java:294)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:466)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:374)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1059)
> at org.eclipse.wst.command.internal.env.ui.widgets.SimpleCommandEngineManager.runForwardToNextStop(SimpleCommandEngineManager.java:264)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.runForwardToNextStop(WizardPageManager.java:91)
> at org.eclipse.wst.command.internal.env.ui.widgets.WizardPageManager.performFinish(WizardPageManager.java:262)
> at org.eclipse.wst.command.internal.env.ui.widgets.DynamicWizard.performFinish(DynamicWizard.java:382)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:636)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.wst.command.internal.env.ui.widgets.popup.DynamicPopupWizard.run(DynamicPopupWizard.java:130)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:251)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1061)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4172)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3761)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:147)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:630)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:574)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:133)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:103)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:378)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:232)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1462)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-16066) Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16066?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick updated JBIDE-16066:
--------------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Top-Down WS deployment isn't successful when selecting Start/Test service in Web Service dialog
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-16066
> URL: https://issues.jboss.org/browse/JBIDE-16066
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.1.CR1
> Environment: JBDS 7.1.0 CR1, EAP-6.1
> Reporter: Radoslav Rábara
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.0.CR1
>
> Attachments: topDownServer.log
>
>
> Deployment isn't successful when Top-Down web service is created with slider level selected to "Start service" or "Test service". Project is deployed to the server but the service endpoint isn't added so the service is not accessible.
> It works with other slider levels and all levels works when the server isn't started before the web service is created.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3083) ensure HTML paths to images & css work on new filemgmt server host
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3083:
--------------------------------
Summary: ensure HTML paths to images & css work on new filemgmt server host
Key: JBDS-3083
URL: https://issues.jboss.org/browse/JBDS-3083
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: updatesite
Affects Versions: 8.0.0.Beta2
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 8.0.0.Beta3
To support migrating from wallace to filemgmt, the website has to properly render all html pages, including images and css. Currently, due to absolute path references, not all pages render correctly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3072) Cannot update from JBDS 8.0.0.Beta1 to Beta2
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3072?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3072:
----------------------------------
If we care we could look at http://git.eclipse.org/c/m2e-wtp/org.eclipse.m2e.wtp.git/tree/org.eclipse... for a way to make Alpha (before refactoring) -> Beta1 (after refactoring) -> Beta3 update work (using `update.matchExp` directive), but until someone complains I don't really care if we break Alpha users.
More important that Beta3 fixes the "can't Check for updates" issue, and we don't delay the code freeze. :D
> Cannot update from JBDS 8.0.0.Beta1 to Beta2
> --------------------------------------------
>
> Key: JBDS-3072
> URL: https://issues.jboss.org/browse/JBDS-3072
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: build
> Affects Versions: 8.0.0.Beta2
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 8.0.0.Beta3
>
> Attachments: beta2c-site-added.png, update-beta1-to-beta2c.png
>
>
> {code}
> Your original request has been modified.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Seam Integration" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Mobile Browser Simulator" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Portlet" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "Maven Integration for Eclipse JDT APT" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration (Experimental)" is already installed, so an update will be performed instead.
> "JBoss OpenShift Tools" is already installed, so an update will be performed instead.
> "JBoss Runtime Seam Detector" is already installed, so an update will be performed instead.
> "Seam 3 Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> Software currently installed: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> Only one of the following can be installed at once:
> JBoss Developer Studio Project Examples 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.project.examples 8.0.0.Beta1-v20140408-2350-B93)
> JBoss Developer Studio Project Examples 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.project.examples 8.0.0.Beta2-v20140613-0252-B130)
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta1-v20140408-2350-B93]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Core Features) 8.0.0.Beta2-v20140613-0252-B130 (com.jboss.devstudio.core.feature.feature.group 8.0.0.Beta2-v20140613-0252-B130)
> To: com.jboss.devstudio.core.project.examples [8.0.0.Beta2-v20140613-0252-B130]
> Cannot satisfy dependency:
> From: JBoss Developer Studio (Branded Product) 8.0.0.Beta1-v20140408-2350-B93 (com.jboss.devstudio.core.package 8.0.0.Beta1-v20140408-2350-B93)
> To: com.jboss.devstudio.core.feature.feature.group [8.0.0.Beta1-v20140408-2350-B93]
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17748) Update TP with Tern.java v.0.4.0.201407021311
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17748?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17748:
---------------------------------------
Building locally to verify
> Update TP with Tern.java v.0.4.0.201407021311
> ---------------------------------------------
>
> Key: JBIDE-17748
> URL: https://issues.jboss.org/browse/JBIDE-17748
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.2.0.Beta3
> Reporter: Victor Rubezhny
> Assignee: Nick Boldt
> Fix For: 4.2.0.Beta3
>
>
> *Need to switch jst.jsdt to the latest tested Tern v.0.3.0. It contains few important fixes regarding cintent assist initialization and Node.js preferences like:*
> - https://github.com/angelozerr/tern.java/pull/72 -NPE in ImageResource.registerImageDescriptor()
> - https://github.com/angelozerr/tern.java/pull/80 - An embedded install of Node.js should be used by default
> - https://github.com/angelozerr/tern.java/pull/87 - Find a way to configure Tern Modules that are default for Nature Adapters defined on a project
> *Reason:*
> jbosstools-jst is going to provide integration between torn.java and jsdt. torn.java is going to be used to improve JavaScript support
> *License and owner:*
> - Root License is EPL. Owner is Angelo ZERR.
> -- core
> --- org.json.simple - EPL (included into torn-feature below)
> ---- lib/json-simple-1.1.1.jar - Apache License 2.0 (see http://www.apache.org/licenses/LICENSE-2.0.txt)
> --- org.mozilla.javascript
> ---- lib/js.jar - Mozilla Public License Version 2.0 (see http://mozilla.org/MPL/2.0/)
> --- tern.core - EPL (included into tern-feature below)
> --- tern.server.nodejs - EPL (included into tern-server-nodejs-feature below)
> ---- tern.server.nodejs/node_modules/tern/LICENSE
> ----- node_modules/acorn/LICENSE
> ------ node_modules/codemirror/LICENSE
> ------ node_modules/glob/LICENSE
> ------- node_modules/inherits/LICENSE
> ------ node_modules/minimatch/LICENSE
> ------- node_modules/lru-cache/LICENSE
> ------- node_modules/sigmund/LICENSE
> ----- node_modules/typescript/LICENSE - Apache License v. 2.0
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> -- eclipse
> --- tern.eclipse.ide.core - EPL (included into tern-feature below)
> --- tern.eclipse.ide.jsdt - EPL (included into tern-jsdt-feature below)
> --- tern.eclipse.ide.server.nodejs.core - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.ui - EPL (included into tern-server-nodejs-feature below)
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86 - Supposed to be EPL but it is not included anywhere yet
> ---- node-v0.10.22-linux-x86.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.linux.gtk.x86_64 - EPL (included into tern.eclipse.linux.gtk.x86.feature below)
> ---- node-v0.10.22-linux-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm/LICENSE - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.macosx.cocoa.x86_64 - EPL (included into tern.eclipse.macosx.cocoa.x86_64.feature below)
> ---- node-v0.10.22-macosx-x86_64.zip has several LICENSE files inside (download)
> ----- LICENSE
> ----- lib/node_modules/npm - The Artistic License 2.0
> ----- lib/node_modules/npm/node_modules/*/LICENSE
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.server.nodejs.embed.win32.win32.x86_64 - EPL (include into tern.eclipse.win32.win32.x86.feature below)
> ---- node-v0.10.22-win32-x86_64.zip has no LICENSE files inside (download)
> ----- node-v0.10.22-win32-x86_64/node.exe - see http://nodejs.org/download/ for licensing information for node.exe.
> --- tern.eclipse.ide.tools.core - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.tools.ui - EPL (included into tern.eclipse.ide.tools.feature below)
> --- tern.eclipse.ide.ui - EPL (included into tern-feature below)
> --- tern.eclipse - EPL (included into tern-feature below)
> -- update-site
> --- tern-feature - EPL (see licens.httml)
> --- tern-jsdt-feature - EPL (see licens.httml)
> --- tern-server-nodejs-feature - EPL (see licens.httml)
> --- tern.eclipse.ide.tools.feature - EPL (see plicense.html)
> --- tern.eclipse.linux.gtk.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.macosx.cocoa.x86_64.feature - EPL (see license.html)
> --- tern.eclipse.win32.win32.x86.feature - EPL (see license.html)
> *Original repo:*
> http://oss.opensagres.fr/tern.repository/0.4.0-SNAPSHOT/
> *JBoss mirror:*
> http://downloads.jboss.org/jbosstools/updates/requirements/tern.java-0.4....
> *Sources:*
> https://github.com/angelozerr/tern.java
> *Affected projects:*
> jbosstools-jst
> jbosstools-aerogear
>
> *Include in JBDS:*
> No
> *Type of dependency:*
> distribution
> *List of bundles added/removed:*
> TBD: need to update PR to use features
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17610) In JBoss Central rename 'Enable Early Access' check box
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17610?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17610:
------------------------------------
Reopen JBIDE-17527 to capture request to append more content into the popup dialog.
> In JBoss Central rename 'Enable Early Access' check box
> -------------------------------------------------------
>
> Key: JBIDE-17610
> URL: https://issues.jboss.org/browse/JBIDE-17610
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Labels: early-access
> Fix For: 4.2.0.Beta3
>
>
> The label for the 'Enable Early Access' check box (JBIDE-17392) should be changed.
> It should be labelled 'Show Early Access'.
> * This makes it consistent with the 'Show Installed' check box
> * And by selecting the check box you aren't actually _enabling_ Early Access features - you are merely showing them and still have to install them
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17610) In JBoss Central rename 'Enable Early Access' check box
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17610?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-17610.
------------------------------
> In JBoss Central rename 'Enable Early Access' check box
> -------------------------------------------------------
>
> Key: JBIDE-17610
> URL: https://issues.jboss.org/browse/JBIDE-17610
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.2.0.Beta2
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Labels: early-access
> Fix For: 4.2.0.Beta3
>
>
> The label for the 'Enable Early Access' check box (JBIDE-17392) should be changed.
> It should be labelled 'Show Early Access'.
> * This makes it consistent with the 'Show Installed' check box
> * And by selecting the check box you aren't actually _enabling_ Early Access features - you are merely showing them and still have to install them
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[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 closed JBDS-3071.
----------------------------
Closing, nothing left to verify. Installer is smaller as sources are no longer included.
> 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)
11 years, 9 months