[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19342:
-----------------------------------
Component/s: (was: build)
> Update code to cope with generics added to org.eclipse.core.runtime package API
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19342
> URL: https://issues.jboss.org/browse/JBIDE-19342
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, discovery, forge, freemarker, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Fred Bricon
> Priority: Minor
> Fix For: 4.3.x
>
>
> We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API.
> From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html :
> {quote}
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021
> Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25
> Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common:
> 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)"
> 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented.
> 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All)
> 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature.
> Typical change:
> Old:
> {code}
> public Object getAdapter(Class adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return getCompilationUnit();
> return null;
> }
> {code}
> New:
> {code}
> public <T> T getAdapter(Class<T> adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return adapter.cast(getCompilationUnit());
> return null;
> }
> {code}
> 5. Update implementations of IAdapterFactory
> Hint for 4. & 5.:
> - Open Type Hierarchy on IAdaptable, etc.
> - In the view menu, select a working set that contains your projects
> - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19342:
-----------------------------------
Issue Type: Enhancement (was: Task)
> Update code to cope with generics added to org.eclipse.core.runtime package API
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19342
> URL: https://issues.jboss.org/browse/JBIDE-19342
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, build, cdi, cdi-extensions, central, common/jst/core, cordovasim, discovery, forge, freemarker, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Fred Bricon
> Priority: Minor
> Fix For: 4.3.x
>
>
> We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API.
> From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html :
> {quote}
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021
> Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25
> Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common:
> 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)"
> 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented.
> 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All)
> 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature.
> Typical change:
> Old:
> {code}
> public Object getAdapter(Class adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return getCompilationUnit();
> return null;
> }
> {code}
> New:
> {code}
> public <T> T getAdapter(Class<T> adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return adapter.cast(getCompilationUnit());
> return null;
> }
> {code}
> 5. Update implementations of IAdapterFactory
> Hint for 4. & 5.:
> - Open Type Hierarchy on IAdaptable, etc.
> - In the view menu, select a working set that contains your projects
> - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-19342:
-----------------------------------
Priority: Minor (was: Major)
> Update code to cope with generics added to org.eclipse.core.runtime package API
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19342
> URL: https://issues.jboss.org/browse/JBIDE-19342
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, build, cdi, cdi-extensions, central, common/jst/core, cordovasim, discovery, forge, freemarker, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing
> Affects Versions: 4.3.0.Alpha2
> Reporter: Fred Bricon
> Priority: Minor
> Fix For: 4.3.x
>
>
> We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API.
> From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html :
> {quote}
> See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021
> Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25
> Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common:
> 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)"
> 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented.
> 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All)
> 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature.
> Typical change:
> Old:
> {code}
> public Object getAdapter(Class adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return getCompilationUnit();
> return null;
> }
> {code}
> New:
> {code}
> public <T> T getAdapter(Class<T> adapter) {
> if (ICompilationUnit.class.equals(adapter))
> return adapter.cast(getCompilationUnit());
> return null;
> }
> {code}
> 5. Update implementations of IAdapterFactory
> Hint for 4. & 5.:
> - Open Type Hierarchy on IAdaptable, etc.
> - In the view menu, select a working set that contains your projects
> - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy)
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19416) JBDS update site zip should not include both packed and unpacked artifacts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19416?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19416:
----------------------------------------
The goal of the update-site zip is to provide to users an update-site to deploy locally. With such use-case, they will benefit from keeping both packed and unpacked jars.
I don't think it's worth trying to save some MB on the zip, since this approach would also introduce a risk of too important divergence between zip and actual site we deploy.
I'm for closing it as invalid.
> JBDS update site zip should not include both packed and unpacked artifacts
> --------------------------------------------------------------------------
>
> Key: JBIDE-19416
> URL: https://issues.jboss.org/browse/JBIDE-19416
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: updatesite
> Affects Versions: 4.2.3.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.3.x
>
>
> JBDS 8.1.0.Beta1 update site zip is 524M and contains both packed (.pack.gz) and regular jars; no need to include both. Ideally we'd include ONLY the packed ones.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18813:
--------------------------------
Sprint: Sprint #1 April 2015
> Convert JBoss Central to an HTML5 page
> --------------------------------------
>
> Key: JBIDE-18813
> URL: https://issues.jboss.org/browse/JBIDE-18813
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.3.0.Beta1
>
> Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, Central design concept E.bmml, Central design concept E.png, Design concept C - Search centric layout.bmml, Design concept C - Search centric layout.png, Design Concept D - categories across top.bmml, Design Concept D - categories across top.bmml, Design Concept D - categories across top.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, JBossCentral_DesignC_HighFidelity_InitialState.png, JBossCentral_DesignC_HighFidelity_SearchState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_InitialState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_SearchState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_StarterHover.png, JBossCentral_DesignC_HighFidelity_StarterHover.png, Screen Shot 2015-01-16 at 4.38.58 PM.png
>
>
> Central Page requires new capabilities :
> - needs more customization (display content depending on user preferences)
> - needs to scale with JBDS-IS, Fuse content
> - access to more examples, with filtering capabilities
> Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach :
> - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
> - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years