June 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-14305: ------------------------------ Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Final) > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.CR1 > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-14305: ------------------------------ Fix Version/s: 4.1.0.Final (was: 4.1.0.Beta2) Priority: Minor (was: Blocker) Affects Version/s: (was: 4.1.0.Final) If there is no more input on this before the codefreeze for 4.1.0.Final I will resolve it as 'Cannot reproduce issue'. > Error popup when runing schema ddl with Hibernate Configurations > ----------------------------------------------------------------- > > Key: JBIDE-14305 > URL: https://issues.jboss.org/browse/JBIDE-14305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: labdoui labdoui > Assignee: Koen Aers > Priority: Minor > Fix For: 4.1.0.Final > > > Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema > to reproduce the problem just explore the database from hibernate console > java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V > at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133) > at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26) > at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476) > at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116) > at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107) > at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63) > at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106) > at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13751) Hibernate Provider for 4.2.x

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13751?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-13751: ------------------------------ Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > Hibernate Provider for 4.2.x > ---------------------------- > > Key: JBIDE-13751 > URL: https://issues.jboss.org/browse/JBIDE-13751 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Reporter: Juergen Zimmermann > Assignee: Koen Aers > Fix For: 4.1.0.CR1 > > > JBossAS 7.2 resp the upcoming EAP 6.1 contains Hibernate 4.2.CR1. For realistic testing it would be nice if Hibernate 4.2 could be selected (in addition to 3.5, 3.6, and 4.0). -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14855) p2.mirrorsURL are kept on mirro

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-14855: -------------------------------------- Summary: p2.mirrorsURL are kept on mirro Key: JBIDE-14855 URL: https://issues.jboss.org/browse/JBIDE-14855 Project: Tools (JBoss Tools) Issue Type: Task Components: target-platform Reporter: Mickael Istria Fix For: 4.1.0.CR1 When we mirror sites using the "format" argument (to keep the original repository layout with .pack.gz as siblings) it also keep the p2.mirrorsURL attribute. This is not bad per se, but since the mirrors are often not correctly sync'd with the Eclipse repositories/our mirrors, it leads to build failure. Current workaround is to remove them by end in content.jar and artifact.jar. We should think about removing this, for example as part of the remove-references script. -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14852) test failures in Seam (JavaEE)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14852?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-14852: -------------------------------------- Assignee: Viacheslav Kabanovich > test failures in Seam (JavaEE) > ------------------------------ > > Key: JBIDE-14852 > URL: https://issues.jboss.org/browse/JBIDE-14852 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.1.0.Beta2 > Reporter: Nick Boldt > Assignee: Viacheslav Kabanovich > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-javaee_master/404/testReport/} > >>> org.jboss.tools.seam.core.test.SerializationTest.testCleanBuild 2.3 sec 1 > Error Message > expected:<95> but was:<21> > Stacktrace > junit.framework.AssertionFailedError: expected:<95> but was:<21> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:234) > at junit.framework.Assert.assertEquals(Assert.java:241) > at junit.framework.TestCase.assertEquals(TestCase.java:409) > at org.jboss.tools.seam.core.test.SerializationTest.testCleanBuild(SerializationTest.java:143) > >>> org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute 3.9 sec 53 > Error Message > Validator failed to report an error in component org.jboss.seam.core.init1 > Stacktrace > junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1 > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:106) > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14852) test failures in Seam (JavaEE)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14852?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14852: ----------------------------------- Fix Version/s: 4.1.0.CR1 > test failures in Seam (JavaEE) > ------------------------------ > > Key: JBIDE-14852 > URL: https://issues.jboss.org/browse/JBIDE-14852 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.1.0.Beta2 > Reporter: Nick Boldt > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.CR1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-javaee_master/404/testReport/} > >>> org.jboss.tools.seam.core.test.SerializationTest.testCleanBuild 2.3 sec 1 > Error Message > expected:<95> but was:<21> > Stacktrace > junit.framework.AssertionFailedError: expected:<95> but was:<21> > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.failNotEquals(Assert.java:329) > at junit.framework.Assert.assertEquals(Assert.java:78) > at junit.framework.Assert.assertEquals(Assert.java:234) > at junit.framework.Assert.assertEquals(Assert.java:241) > at junit.framework.TestCase.assertEquals(TestCase.java:409) > at org.jboss.tools.seam.core.test.SerializationTest.testCleanBuild(SerializationTest.java:143) > >>> org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute 3.9 sec 53 > Error Message > Validator failed to report an error in component org.jboss.seam.core.init1 > Stacktrace > junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1 > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:106) > {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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14105) org.jboss.tools.seam.xml.test.SeamXMLModelTest JUnit Test failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14105?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14105: ----------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > org.jboss.tools.seam.xml.test.SeamXMLModelTest JUnit Test failure > ----------------------------------------------------------------- > > Key: JBIDE-14105 > URL: https://issues.jboss.org/browse/JBIDE-14105 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2 > Affects Versions: 4.1.0.Alpha1 > Reporter: Victor Rubezhny > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.CR1 > > > The Following JUnit Test fails constantly for at least 12 last runs on both jbosstools-javaee_41 and jbosstools-javaee_master jobs. > {code} > Failed > org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute (from org.jboss.tools.seam.xml.test.SeamXMLAllTests) > Failing for the past 16 builds (Since #352 ) > Took 7.7 sec. > add description > Error Message > Validator failed to report an error in component org.jboss.seam.core.init1 > Stacktrace > junit.framework.AssertionFailedError: Validator failed to report an error in component org.jboss.seam.core.init1 > at junit.framework.Assert.fail(Assert.java:57) > at junit.framework.Assert.assertTrue(Assert.java:22) > at junit.framework.TestCase.assertTrue(TestCase.java:192) > at org.jboss.tools.seam.xml.test.SeamXMLModelTest.testDebugAttribute(SeamXMLModelTest.java:106) > {code} > See: > [jbosstools-javaee_41|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/vie...] > [jbosstools-javaee_master|https://jenkins.mw.lab.eng.bos.redhat.com/hudson...] -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14390) JSF 'New Project' preferences and wizard should have matching labels for the same fields

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14390?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14390: ----------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > JSF 'New Project' preferences and wizard should have matching labels for the same fields > ---------------------------------------------------------------------------------------- > > Key: JBIDE-14390 > URL: https://issues.jboss.org/browse/JBIDE-14390 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Alpha2 > Reporter: Michelle Murray > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.CR1 > > Attachments: JSF_NewProjectPreferences.png, JSF_NewProjectWizard1.png, JSF_NewProjectWizard2.png > > > 1. Window>Preferences>JBoss Tools>Web>JSF>Project, New Project tab has the following labels (screen capture attached): > * Version > * Project Template > * Use Default Path > * Projects Root > * Servlet Version > 2. File>New>Project>JBoss Tools Web>JSF>JSF Project wizard, page 1 and 2 have the following labels (screen captures attached): > * Use default path > * Location > * JSF Environment > * Template > * ServletVersion > List 1 and 2 refer to the same things but use different labels. The labels should be identical. I would suggest changing: > In preferences: > Version -> JSF Version > Use Default Path -> Use default path > Projects Root -> Location > In the wizard: > JSF Environment -> JSF Version > Template -> Project Template > ServletVersion -> Servlet Version -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13636) references in jsf tooling to struts

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13636?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13636: ----------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > references in jsf tooling to struts > ----------------------------------- > > Key: JBIDE-13636 > URL: https://issues.jboss.org/browse/JBIDE-13636 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: struts/shale > Reporter: Max Rydahl Andersen > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.CR1 > > Attachments: StrutsArtifacts.txt > > > seeing many hits with grep in jsf to struts. > Note sre if these are just for struts html tags (which would be ok to keep) but why is there so much struts in xmodel files etc. from within jsf ? -- 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

12 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14606) Struts Tiles File

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14606?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14606: ----------------------------------- Fix Version/s: 4.1.0.CR1 (was: 4.1.0.Beta2) > Struts Tiles File > ----------------- > > Key: JBIDE-14606 > URL: https://issues.jboss.org/browse/JBIDE-14606 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: struts/shale > Reporter: Burr Sutter > Assignee: Viacheslav Kabanovich > Fix For: 4.1.0.CR1 > > > Struts has been removed from JBDS 7 but there is still a Struts wizard. > http://screencast.com/t/wbjEF5vGBg -- 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

12 years, 10 months

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 June 2013