February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13664: ---------------------------------------- Description: tracing options in .options in openshiftclient is not showing up and if you enable it explicitly by using -debug .options and .options contains: You get: "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. Application Started: 37798 log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info." was:tracing options in .options in openshiftclient is not showing up > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > tracing options in .options in openshiftclient is not showing up and if you enable it explicitly by using > -debug .options > and .options contains: > You get: > "SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder". > SLF4J: Defaulting to no-operation (NOP) logger implementation > SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details. > Application Started: 37798 > log4j:WARN No appenders could be found for logger (com.openshift.internal.client.RestService). > log4j:WARN Please initialize the log4j system properly. > log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up not is logging working when configured

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13664: ---------------------------------------- Summary: tracing options for openshift client not showing up not is logging working when configured (was: tracing options for openshift client not showing up) > tracing options for openshift client not showing up not is logging working when configured > ------------------------------------------------------------------------------------------ > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > > tracing options in .options in openshiftclient is not showing up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12784) IllegalArgumentException after importing HTML5 project from JBoss Central

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12784?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-12784: ----------------------------------- This seems to be a problem in Dali that has been fixed in Kepler and thus in 4.1.x. Feel free to reopen if there is a real compelling reason for this to be fixed in 4.0.x. > IllegalArgumentException after importing HTML5 project from JBoss Central > ------------------------------------------------------------------------- > > Key: JBIDE-12784 > URL: https://issues.jboss.org/browse/JBIDE-12784 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, UpStream > Affects Versions: 4.0.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Koen Aers > Priority: Minor > Fix For: 4.0.x > > > {code}duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)){code} > Stack trace: > {code} > java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)) > at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95) > at org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource.addResourceModelListener(JpaXmlResource.java:264) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:579) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:552) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1683) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:254) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1668) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1860) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1852) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1835) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1646) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1638) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:684) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:670) > at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12784) IllegalArgumentException after importing HTML5 project from JBoss Central

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12784?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-12784. ------------------------------- Fix Version/s: (was: 4.1.0.Alpha1) Resolution: Won't Fix > IllegalArgumentException after importing HTML5 project from JBoss Central > ------------------------------------------------------------------------- > > Key: JBIDE-12784 > URL: https://issues.jboss.org/browse/JBIDE-12784 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, UpStream > Affects Versions: 4.0.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Koen Aers > Priority: Minor > Fix For: 4.0.x > > > {code}duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)){code} > Stack trace: > {code} > java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)) > at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95) > at org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource.addResourceModelListener(JpaXmlResource.java:264) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:579) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:552) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1683) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:254) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1668) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1860) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1852) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1835) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1646) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1638) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:684) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:670) > at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12784) IllegalArgumentException after importing HTML5 project from JBoss Central

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12784?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-12784: ----------------------------------- Remove fix version 4.1.0.Alpha1 because the problem was fixed in Dali > IllegalArgumentException after importing HTML5 project from JBoss Central > ------------------------------------------------------------------------- > > Key: JBIDE-12784 > URL: https://issues.jboss.org/browse/JBIDE-12784 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, UpStream > Affects Versions: 4.0.0.Alpha2 > Reporter: Stefan Bunciak > Assignee: Koen Aers > Priority: Minor > Fix For: 4.0.x > > > {code}duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)){code} > Stack trace: > {code} > java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[00-32-60-DB](HibernateJpaProject[01-74-D9-59](poh5)) > at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95) > at org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource.addResourceModelListener(JpaXmlResource.java:264) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:579) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:552) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1683) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:254) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1668) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1860) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1852) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1835) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1646) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1638) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:684) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:670) > at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12704) Erroneous description in forge console update screen

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12704?page=com.atlassian.jira.plugi... ] Koen Aers resolved JBIDE-12704. ------------------------------- Resolution: Done > Erroneous description in forge console update screen > ---------------------------------------------------- > > Key: JBIDE-12704 > URL: https://issues.jboss.org/browse/JBIDE-12704 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, updatesite > Affects Versions: 4.0.0.Alpha2 > Reporter: George Gastaldi > Assignee: Koen Aers > Priority: Trivial > Fix For: 4.1.0.Alpha1, 4.0.1.Final > > > The current description for Forge Console when selecting to update is: > {panel} > Plugins for using Seam Forge from within Eclipse. > {panel} > It should be: > {panel} > Plugins for using JBoss Forge from within Eclipse. > {panel} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-12743) Forge tools should add new projects created with forge to the current working set(s)

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12743?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-12743: ------------------------------ Fix Version/s: 4.1.0.Alpha2 (was: 4.1.0.Alpha1) > Forge tools should add new projects created with forge to the current working set(s) > ------------------------------------------------------------------------------------ > > Key: JBIDE-12743 > URL: https://issues.jboss.org/browse/JBIDE-12743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.0.0.Alpha1 > Reporter: Lincoln Baxter III > Assignee: Koen Aers > Priority: Minor > Fix For: 4.0.x, 4.1.0.Alpha2 > > > It would be nice if new projects created with forge were added to the current working set automatically (or prompted for one,) so that it doesn't look like the project is "missing" upon creation when working in a working set. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13664: ------------------------------------------- Summary: tracing options for openshift client not showing up Key: JBIDE-13664 URL: https://issues.jboss.org/browse/JBIDE-13664 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen tracing options in .options in openshiftclient is not showing up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-13664: ---------------------------------------- Assignee: Andre Dietisheim > tracing options for openshift client not showing up > --------------------------------------------------- > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > tracing options in .options in openshiftclient is not showing up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13664) tracing options for openshift client not showing up

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13664?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13664: ------------------------------------- Affects Version/s: 4.1.0.Alpha1 > tracing options for openshift client not showing up > --------------------------------------------------- > > Key: JBIDE-13664 > URL: https://issues.jboss.org/browse/JBIDE-13664 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > > tracing options in .options in openshiftclient is not showing up -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2013