October 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12823) Compilation error in JSF project

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-12823: -------------------------------------- Summary: Compilation error in JSF project Key: JBIDE-12823 URL: https://issues.jboss.org/browse/JBIDE-12823 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.0.0.Alpha2 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.0.0.Beta1 1. Open Eclipse 2. Create a new JSF project (2.0 or 2.1) - JSFKickStartWithoutLibs using New JSF Project wizard 3. FAILURE: User.java has compilation errors since javax.* can't be found. 4. Clean/re-build the project. Compilation errors are gone. 5. Create one more JSF project. Now there are no errors. 6. Close Eclipse. Open it again. Steps 2-5 are reproducible again. Not sure that's a bug of JSF Tools. Maybe it's an upstream bug. -- 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, 4 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-12707) Maven workspace project dependencies are not identified during maven conversion

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12707: ----------------------------------- Summary: Maven workspace project dependencies are not identified during maven conversion Key: JBIDE-12707 URL: https://issues.jboss.org/browse/JBIDE-12707 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 4.0.0.Alpha2 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Beta1 When converting a project to maven, if one of the dependencies is already a maven project opened in the workspace, it should be identified as such. Ex : - create a java project - create a dynamic web project - add the java project to the web project build path - convert the java project to maven - convert the web project to maven ASSERT : the java project dependency should be identified with its maven GAV -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12819) README.md doesn't open for imported maven projects which name differs from artifactId

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-12819: ----------------------------------- Summary: README.md doesn't open for imported maven projects which name differs from artifactId Key: JBIDE-12819 URL: https://issues.jboss.org/browse/JBIDE-12819 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, project-examples Affects Versions: 4.0.0.Alpha1 Reporter: Fred Bricon Assignee: Fred Bricon Fix For: 4.0.0.Beta1 While trying to import some zipped quickstarts from https://github.com/jboss-jdf/jboss-as-quickstart, the README.md never opens if the project name differs from the project artifactId -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] (JBIDE-12788) Missing http://java.sun.com/xml/ns/javaee/web-facesconfig_2_1.xsd in the catalog

by Marek Schmidt (JIRA)

Marek Schmidt created JBIDE-12788: ------------------------------------- Summary: Missing http://java.sun.com/xml/ns/javaee/web-facesconfig_2_1.xsd in the catalog Key: JBIDE-12788 URL: https://issues.jboss.org/browse/JBIDE-12788 Project: Tools (JBoss Tools) Issue Type: Bug Components: JSF Affects Versions: 4.0.0.Alpha2 Environment: JBDS 6.0.0.Alpha2c, Seam2.3.0.Final Reporter: Marek Schmidt Assignee: Alexey Kazakov The http://java.sun.com/xml/ns/javaee/web-facesconfig_2_1.xsd from JSF 2.1 does not appear to be in the catalog, which causes a JSF 2.1 faces-config.xml to generate XML validation problems, as java.sun.com doesn't serve this file either: {noformat} Referenced file contains errors (http://java.sun.com/xml/ns/javaee/web-facesconfig_2_1.xsd). {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

13 years, 4 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-12790) Broken tests after common validation rework

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12790: ------------------------------------- Summary: Broken tests after common validation rework Key: JBIDE-12790 URL: https://issues.jboss.org/browse/JBIDE-12790 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Webservices Affects Versions: 4.0.0.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 Some JUnit tests fail after work was done on common-validation -- 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, 4 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-12814) "Could not resolve bindings form method" when editing REST service

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12814: ----------------------------------------- Summary: "Could not resolve bindings form method" when editing REST service Key: JBIDE-12814 URL: https://issues.jboss.org/browse/JBIDE-12814 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Alpha2 Reporter: Jaroslav Jankovič Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12835) JAX-RS problem markers are not removed when JAX-RS support is removed on project

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12835: ------------------------------------- Summary: JAX-RS problem markers are not removed when JAX-RS support is removed on project Key: JBIDE-12835 URL: https://issues.jboss.org/browse/JBIDE-12835 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Beta1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.CR1 Have a project with JAX-RS problems. Remove the JAX-RS support. The problem markers are still there, they were not deleted. -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12817) NPE when adding JAX-RS support

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12817: ----------------------------------------- Summary: NPE when adding JAX-RS support Key: JBIDE-12817 URL: https://issues.jboss.org/browse/JBIDE-12817 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 4.0.0.Alpha2 Reporter: Jaroslav Jankovič Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-12806) Refresh annotation locations in the JAX-RS Metamodel after QuickFix is applied

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-12806: ------------------------------------- Summary: Refresh annotation locations in the JAX-RS Metamodel after QuickFix is applied Key: JBIDE-12806 URL: https://issues.jboss.org/browse/JBIDE-12806 Project: Tools (JBoss Tools) Issue Type: Task Components: Webservices Affects Versions: 4.0.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.0.0.Beta1 Step to reproduce: 1. Create a new annotation as below (package declaration is omited): {code} import javax.ws.rs.HttpMethod; @HttpMethod("PATCH") public @interface PATCH { } {code} Assert: The JAX-RS validator should report 2 problems: missing @Target annotation and missing @Retention annotation. 2- Use the available QuickFix to add the @Retention annotation Assert: code is now as below: {code} import javax.ws.rs.HttpMethod; import java.lang.annotation.Retention; import java.lang.annotation.RetentionPolicy; @Retention(RetentionPolicy.RUNTIME) @HttpMethod("PATCH") public @interface PATCH { } {code} Assert: the missing @Target annotation problem should be reported under the 'PATCH' type name as before FAIL : the marker location in the document was not updated, the problem is now somewhere under the 'import java.lang.annotation.Retention' declaration. Also, the lack of location update can also cause this kind of error: !ENTRY org.jboss.tools.common 4 0 2012-10-05 10:34:09.357 !MESSAGE Wrong offset [195] of the problem marker [The HTTP Method should have a @Target(ElementType.METHOD) annotation on its type.] for resource: /poh5/src/main/java/org/jboss/tools/example/html5/rest/PATCH.java !STACK 0 org.eclipse.jface.text.BadLocationException at org.eclipse.jface.text.TreeLineTracker.fail(TreeLineTracker.java:1055) at org.eclipse.jface.text.TreeLineTracker.lineByOffset(TreeLineTracker.java:267) at org.eclipse.jface.text.TreeLineTracker.getLineNumberOfOffset(TreeLineTracker.java:1137) at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161) at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:915) at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:397) at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:428) at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:495) at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:349) at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:369) at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:387) at org.jboss.tools.common.validation.ValidationErrorManager.addError(ValidationErrorManager.java:374) at org.jboss.tools.common.validation.TempMarkerManager.addProblem(TempMarkerManager.java:116) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.AbstractJaxrsElementValidatorDelegate.addProblem(AbstractJaxrsElementValidatorDelegate.java:54) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsHttpMethodValidatorDelegate.validateTargetAnnotation(JaxrsHttpMethodValidatorDelegate.java:78) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsHttpMethodValidatorDelegate.validate(JaxrsHttpMethodValidatorDelegate.java:45) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:255) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:170) at org.jboss.tools.ws.jaxrs.core.internal.metamodel.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:120) at org.jboss.tools.common.validation.ValidatorManager.validate(ValidatorManager.java:117) at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:81) at org.eclipse.wst.validation.internal.core.ValidatorLauncher.start(ValidatorLauncher.java:77) at org.eclipse.wst.validation.Validator$V1.validate(Validator.java:768) at org.eclipse.wst.validation.Validator.validate(Validator.java:405) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:704) at org.eclipse.wst.validation.internal.ValManager$1.visit(ValManager.java:665) at org.eclipse.wst.validation.internal.ValManager.accept(ValManager.java:810) at org.eclipse.wst.validation.internal.ValManager.validate(ValManager.java:669) at org.eclipse.wst.validation.internal.ValidationRunner.execute(ValidationRunner.java:134) at org.eclipse.wst.validation.internal.ValidationRunner.validate(ValidationRunner.java:68) at org.eclipse.wst.validation.ui.internal.ManualValidationRunner.runInWorkspace(ManualValidationRunner.java:83) at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) 10: -- 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, 4 months

2
6
0 / 0

[JBoss JIRA] (JBIDE-12593) Improve quick fixes for @HttpMethod validation errors

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-12593: ----------------------------------------- Summary: Improve quick fixes for @HttpMethod validation errors Key: JBIDE-12593 URL: https://issues.jboss.org/browse/JBIDE-12593 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Webservices Affects Versions: 4.0.0.Alpha1 Reporter: Jaroslav Jankovič Assignee: Xavier Coulon Fix For: 4.0.0.Alpha1 If I have this annotation: {code} @HttpMethod(value = "METHOD") public @interface MyAnnot { } {code} there are two errors in markers view: * The HTTP Method should have a @Retention(RetentionPolicy.RUNTIME) annotation on its type. * The HTTP Method should have a @Target(ElementType.METHOD) annotation on its type. For @Target marker there is quick fix providing adding @Target annotation into class. However there is no such quick fix for @Retention marker, only "Configure Problem Severity" is offered. There should be definitely similar quick fix as for @Target marker. -- 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, 4 months

2
5
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 October 2012