[JBoss JIRA] (JBIDE-21215) snapshot updatesite having issues
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21215?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21215:
---------------------------------------
Works for me now. I tried Abridged JBT. Maybe it has been fixed already?
> snapshot updatesite having issues
> ---------------------------------
>
> Key: JBIDE-21215
> URL: https://issues.jboss.org/browse/JBIDE-21215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
>
> running updates from: http://download.jboss.org/jbosstools/mars/snapshots/updates/
> I get this error:
> {quote}
> An error occurred while collecting items to be installed
> session context was:(profile=_Users_max_products_eclipse_jee-mars3_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.jboss.tools.common,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.el.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.resref.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.text.xml,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.validation,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.checkup,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.ui,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.cdk.server,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.core,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.ui,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.stacks.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.usage,2.1.1.Beta1-v20151204-0542-B55
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.cdk.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.express.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.feature,3.1.0.Beta1-v20151205-0342-B106
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20750) Slow Memory Leak in JSF tools
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20750?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-20750:
--------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Slow Memory Leak in JSF tools
> -----------------------------
>
> Key: JBIDE-20750
> URL: https://issues.jboss.org/browse/JBIDE-20750
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.3.1.Beta1
>
> Attachments: .log, heap-snapshot1.png, heap-snapshot2.png, mem-usage.png, oom1.png, oom2.png
>
>
> Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
> Attached screenshot list:
> 1. GC overhead limit exceeded error [^oom1.png];
> 2. Heap Memory Usage timeline [^mem-usage.png];
> 3. Heap Memory Objects filtered for "org.jboss.tools" [^heap-snapshot2.png];
> 4. Heap Memory Objects none filtered [^heap-snapshot1.png];
> 5. OOM Dialog [^oom2.png]ж
> 6. [^.log]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21221) Slow Memory Leak in JSF tools
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-21221:
-----------------------------------
Summary: Slow Memory Leak in JSF tools
Key: JBIDE-21221
URL: https://issues.jboss.org/browse/JBIDE-21221
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: jsf
Affects Versions: 4.3.0.CR1
Reporter: Denis Golovin
Assignee: Viacheslav Kabanovich
Priority: Critical
Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
Attached screenshot list:
1. GC overhead limit exceeded error [^oom1.png];
2. Heap Memory Usage timeline [^mem-usage.png];
3. Heap Memory Objects filtered for "org.jboss.tools" [^heap-snapshot2.png];
4. Heap Memory Objects none filtered [^heap-snapshot1.png];
5. OOM Dialog [^oom2.png]ж
6. [^.log]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21221) Slow Memory Leak in JSF tools
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21221?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-21221:
--------------------------------
Fix Version/s: (was: 4.3.1.Beta1)
> Slow Memory Leak in JSF tools
> -----------------------------
>
> Key: JBIDE-21221
> URL: https://issues.jboss.org/browse/JBIDE-21221
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
> Attached screenshot list:
> 1. GC overhead limit exceeded error [^oom1.png];
> 2. Heap Memory Usage timeline [^mem-usage.png];
> 3. Heap Memory Objects filtered for "org.jboss.tools" [^heap-snapshot2.png];
> 4. Heap Memory Objects none filtered [^heap-snapshot1.png];
> 5. OOM Dialog [^oom2.png]ж
> 6. [^.log]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21221) Slow Memory Leak in JSF tools
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21221?page=com.atlassian.jira.plugi... ]
Vlado Pakan resolved JBIDE-21221.
---------------------------------
Resolution: Done
> Slow Memory Leak in JSF tools
> -----------------------------
>
> Key: JBIDE-21221
> URL: https://issues.jboss.org/browse/JBIDE-21221
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.CR1
> Reporter: Denis Golovin
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
>
> Opening then closing jsf projects slowly consumes heap memory, whish leads to slowing down overal performance and eventually to GC overhead limit exceeded exceptions.
> Attached screenshot list:
> 1. GC overhead limit exceeded error [^oom1.png];
> 2. Heap Memory Usage timeline [^mem-usage.png];
> 3. Heap Memory Objects filtered for "org.jboss.tools" [^heap-snapshot2.png];
> 4. Heap Memory Objects none filtered [^heap-snapshot1.png];
> 5. OOM Dialog [^oom2.png]ж
> 6. [^.log]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-21113.
-------------------------------
Verified with JBDS 9.1.0.Beta1-v20151208-2104-B170.
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21113
> URL: https://issues.jboss.org/browse/JBIDE-21113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.Beta1
>
>
> When adding a JSF phase listener to faces-config.xml
> {code}
> <lifecycle>
> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener>
> </lifecycle>
> {code}
> You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}}
> In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html
> In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener.
> The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21220) Incorrect JSF Phase Listener Warning
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21220?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-21220:
--------------------------------
Fix Version/s: (was: 4.3.1.Beta1)
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21220
> URL: https://issues.jboss.org/browse/JBIDE-21220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> When adding a JSF phase listener to faces-config.xml
> {code}
> <lifecycle>
> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener>
> </lifecycle>
> {code}
> You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}}
> In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html
> In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener.
> The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21113) Incorrect JSF Phase Listener Warning
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21113?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-21113:
--------------------------------
Fix Version/s: (was: 4.4.0.Alpha1)
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21113
> URL: https://issues.jboss.org/browse/JBIDE-21113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.1.Beta1
>
>
> When adding a JSF phase listener to faces-config.xml
> {code}
> <lifecycle>
> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener>
> </lifecycle>
> {code}
> You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}}
> In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html
> In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener.
> The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21220) Incorrect JSF Phase Listener Warning
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21220?page=com.atlassian.jira.plugi... ]
Vlado Pakan resolved JBIDE-21220.
---------------------------------
Resolution: Done
> Incorrect JSF Phase Listener Warning
> ------------------------------------
>
> Key: JBIDE-21220
> URL: https://issues.jboss.org/browse/JBIDE-21220
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.3.0.Final
> Environment: Mars.1
> Java 8
> Reporter: Cody Lerum
> Assignee: Viacheslav Kabanovich
> Fix For: 4.4.0.Alpha1
>
>
> When adding a JSF phase listener to faces-config.xml
> {code}
> <lifecycle>
> <phase-listener>com.demo.web.jsf.JsfCdiPhaseListener</phase-listener>
> </lifecycle>
> {code}
> You are presented a warning that {{phase-listener references to "com.demo.web.jsf.JsfCdiPhaseListener" that does not extend javax.faces.event.PhaseListener}}
> In reality you cannot extend javax.faces.event.PhaseListener you must implement it. So this check should be looking for implements rather than extends. See http://balusc.omnifaces.org/2006/09/debug-jsf-lifecycle.html
> In java 8 at least you get a compiler error if you try and extend avax.faces.event.PhaseListener.
> The type PhaseListener cannot be the superclass of JsfCdiPhaseListener; a superclass must be a class
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months