May 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-14663) Source lookup dialog shown twice on maven projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14663?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-14663: -------------------------------- Assignee: Fred Bricon (was: Snjezana Peco) > Source lookup dialog shown twice on maven projects > -------------------------------------------------- > > Key: JBIDE-14663 > URL: https://issues.jboss.org/browse/JBIDE-14663 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.1.0.Beta1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: respin-b > Fix For: 4.1.0.Beta1 > > > Source lookup dialog is shown twice on maven projects : http://screencast.com/t/3yESat96FIw > I think our source lookup should ignore projects with the maven nature, since a m2e's source lookup mechanism is already running in the background. > If maven nature is enabled AND source is set but missing THEN, it'd be ok to show our own stuff -- 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-14657) Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version'

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14657?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14657: ----------------------------------- Fix Version/s: 4.1.0.Beta2 > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > --------------------------------------------------------------------- > > Key: JBIDE-14657 > URL: https://issues.jboss.org/browse/JBIDE-14657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Fix For: 4.1.0.Beta2 > > Attachments: JSF_Servletversion.png > > > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > (screen caption attached) -- 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-14657) Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version'

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14657?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-14657: -------------------------------------- Assignee: Daniel Azarov > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > --------------------------------------------------------------------- > > Key: JBIDE-14657 > URL: https://issues.jboss.org/browse/JBIDE-14657 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF > Affects Versions: 4.1.0.Beta1 > Reporter: Michelle Murray > Assignee: Daniel Azarov > Fix For: 4.1.0.Beta2 > > Attachments: JSF_Servletversion.png > > > Typo in new JSF project wizard: 'ServletVersion' -> 'Servlet Version' > (screen caption attached) -- 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] (JBDS-2644) Wrong version & build info in About Dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2644?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-2644: ------------------------------------- this means that in com.jboss.jbds.product ant script was not executed during build for some reason: {code}<execution> <id>process-about-mapping</id> <phase>package</phase> <goals> <goal>run</goal> </goals> <configuration> ... </execution>{code} > Wrong version & build info in About Dialog > ------------------------------------------ > > Key: JBDS-2644 > URL: https://issues.jboss.org/browse/JBDS-2644 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, updatesite > Affects Versions: 7.0.0.Beta1 > Reporter: Stefan Bunciak > Assignee: Denis Golovin > Priority: Critical > Labels: respin-b > Fix For: 7.0.0.Beta1 > > > Updating from 7.0.0.Beta1 to 7.0.0.Beta1a via *update site* caused that version, build id, build date variables are not filled in About Dialog: > {code} > JBoss Developer Studio > Version: @product.releaseNumber@ > Build id: @product.buildQualifier@ > Build date: @product.buildTimeStamp@ > {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-14671) h2 database driver creation problems/questions

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14671?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-14671: ---------------------------------------- Seems to be a bug of Eclipse Data Tools. > h2 database driver creation problems/questions > ---------------------------------------------- > > Key: JBIDE-14671 > URL: https://issues.jboss.org/browse/JBIDE-14671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Tomas Remes > Attachments: error.log > > > I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ??? > I tried to use "Generic JDBC driver" option for this and basically I wasn't able to do that, because of following error: > {noformat} > An error has occurred. See error log for more details. > Widget is disposed > {noformat} > Reproducible by following steps: > 1. Choose "Generic JDBC driver" > 2. Click "Add" button. (you need to choose db type again) > 3. Switch to "JAR list" tab. > 4. Add h2 driver jar (e.g. the one from EAP 6.1). > 5. You need to specify "Drive class definiton". > 6. Go with "org.h2.Driver". > 7. Notice the error. -- 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-14671) h2 database driver creation problems/questions

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14671?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-14671: ----------------------------------- Component/s: upstream > h2 database driver creation problems/questions > ---------------------------------------------- > > Key: JBIDE-14671 > URL: https://issues.jboss.org/browse/JBIDE-14671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Beta1 > Reporter: Tomas Remes > Attachments: error.log > > > I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ??? > I tried to use "Generic JDBC driver" option for this and basically I wasn't able to do that, because of following error: > {noformat} > An error has occurred. See error log for more details. > Widget is disposed > {noformat} > Reproducible by following steps: > 1. Choose "Generic JDBC driver" > 2. Click "Add" button. (you need to choose db type again) > 3. Switch to "JAR list" tab. > 4. Add h2 driver jar (e.g. the one from EAP 6.1). > 5. You need to specify "Drive class definiton". > 6. Go with "org.h2.Driver". > 7. Notice the error. -- 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] (JBDS-2647) installer : replace Sun reference with Oracle

by Fred Bricon (JIRA)

Fred Bricon created JBDS-2647: --------------------------------- Summary: installer : replace Sun reference with Oracle Key: JBDS-2647 URL: https://issues.jboss.org/browse/JBDS-2647 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 7.0.0.Beta1 Reporter: Fred Bricon Priority: Minor Fix For: 7.0.0.Beta2 When installing JBDS via the installer, some panel says : {quote}JBoss Developer Studio works with Java 6 and has been tested with OpenJDK, Sun and Apple JDK.{quote} should be {quote}JBoss Developer Studio works with Java 6 and has been tested with OpenJDK, Oracle and Apple JDK.{quote} You might also want to say "works with Java 6 and higher" -- 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-14670) Automatically notify browsers after user edited a file, even *before* saving it

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-14670: ------------------------------------- Summary: Automatically notify browsers after user edited a file, even *before* saving it Key: JBIDE-14670 URL: https://issues.jboss.org/browse/JBIDE-14670 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: livereload Affects Versions: 4.1.0.Beta2 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.1.0.Beta2 The idea is to notify the livereload server which in turn will notify browser that are connected to the proxy to access local files. when the browser will send a request to the proxy, this latter one will not return the content of the resource on the FS but rather, it will first check if there's an open editor for that resource and then, it will send the working copy instead. This should be an option in the LiveReload Proxy Configuration -- 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] (JBDS-2646) Cannot deploy created Seam2.2 project to EAP 5.2

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-2646?page=com.atlassian.jira.plugin.... ] Alexey Kazakov resolved JBDS-2646. ---------------------------------- Fix Version/s: 7.0.0.Beta1 Resolution: Duplicate Issue Duplicates JBIDE-14624 > Cannot deploy created Seam2.2 project to EAP 5.2 > ------------------------------------------------ > > Key: JBDS-2646 > URL: https://issues.jboss.org/browse/JBDS-2646 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: seam > Affects Versions: 7.0.0.Beta1 > Reporter: Tomas Remes > Fix For: 7.0.0.Beta1 > > > Cannot deploy created Seam2.2 project to EAP 5.2, because of following exception, which is caused by wrong web.xml webapps tag values: > {noformat} > org.jboss.deployers.spi.DeploymentException: Error creating managed object for vfsfile:/home/tremes/EAP/ER6/jboss-eap-5.2/jboss-as/server/default/deploy/testproject.war/ > at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:362) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:322) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:294) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.deploy(AbstractParsingDeployerWithOutput.java:234) > at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454) > at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172) > at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113) > at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348) > at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652) > at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082) > at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826) > at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556) > at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789) > at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699) > at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117) > at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409) > at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) > at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) > at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) > at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) > at java.lang.Thread.run(Thread.java:722) > Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203) > at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:168) > at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:189) > at org.jboss.xb.util.JBossXBHelper.parse(JBossXBHelper.java:166) > at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:137) > at org.jboss.deployers.vfs.spi.deployer.SchemaResolverDeployer.parse(SchemaResolverDeployer.java:121) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:304) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parseAndInit(AbstractVFSParsingDeployer.java:286) > at org.jboss.deployers.vfs.spi.deployer.AbstractVFSParsingDeployer.parse(AbstractVFSParsingDeployer.java:203) > at org.jboss.deployers.spi.deployer.helpers.AbstractParsingDeployerWithOutput.createMetaData(AbstractParsingDeployerWithOutput.java:348) > ... 27 more > Caused by: org.jboss.xb.binding.JBossXBRuntimeException: Element {http://xmlns.jcp.org/xml/ns/javaee}web-app is not bound as a global element. > at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.startElement(SundayContentHandler.java:660) > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHandler.startElement(SaxJBossXBParser.java:401) > at org.apache.xerces.parsers.AbstractSAXParser.startElement(Unknown Source) > at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) > at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) > at org.apache.xerces.impl.XMLNSDocumentScannerImpl$NSContentDispatcher.scanRootElementHook(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) > at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) > at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) > at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) > at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) > at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) > ... 36 more > {noformat} -- 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-14603) Cannot install Mylyn connector from central - failure blocks other plugin installs

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14603?page=com.atlassian.jira.plugi... ] Len DiMaggio resolved JBIDE-14603. ---------------------------------- Resolution: Done The problem is resolved in: Version: 7.0.0.Beta1 Build id: Beta1-v20130526-0839-B241 Build date: 20130526-0839 > Cannot install Mylyn connector from central - failure blocks other plugin installs > ---------------------------------------------------------------------------------- > > Key: JBIDE-14603 > URL: https://issues.jboss.org/browse/JBIDE-14603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.1.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Priority: Blocker > Labels: respin-a > Fix For: 4.1.0.Beta1 > > Attachments: .log > > > After installing this plugin from Central: > Mylyn Tasks Connector: Bugzilla 3.9.0.I20130319-0842 org.eclipse.mylyn.bugzilla_feature.feature.group > After eclipse restarts, accessing Central raises this error: An internal error occurred during: > "Update project wizard list". org.eclipse.mylyn.commons.core.CoreUtil.newXmlReader()Lorg/xml/sax/XMLReader; > And any attempt to install additional plugins fail with the same error: Unexpected exception: > org.eclipse.mylyn.commons.core.CoreUtil.newXmlReader()Lorg/xml/sax/XMLReader; org.eclipse.mylyn.commons.core.CoreUtil.newXmlReader()Lorg/xml/sax/XMLReader; org.eclipse.mylyn.commons.core.CoreUtil.newXmlReader()Lorg/xml/sax/XMLReader; org.eclipse.mylyn.commons.core.CoreUtil.newXmlReader()Lorg/xml/sax/XMLReader; -- 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 May 2013