[JBoss JIRA] (JBIDE-11930) springmvc is inaccessible
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-11930:
----------------------------------------
Summary: springmvc is inaccessible
Key: JBIDE-11930
URL: https://issues.jboss.org/browse/JBIDE-11930
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.0.CR1
Environment: JBT nightly May 22
Reporter: Rastislav Wagner
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.CR1
java.lang.reflect.InvocationTargetException
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:369)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: org.eclipse.core.runtime.CoreException: Unable to create project from archetype [org.jboss.spring.archetypes:spring-mvc-webapp:1.0.0.CR5 -> https://repository.jboss.org/nexus/content/repositories/jboss_releases_st...]
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:567)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$4.run(ArchetypeExamplesWizardPage.java:355)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizardPage$5.run(ArchetypeExamplesWizardPage.java:367)
... 1 more
Caused by: org.apache.maven.archetype.exception.UnknownArchetype: The desired archetype does not exist (org.jboss.spring.archetypes:spring-mvc-webapp:1.0.0.CR5)
at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:112)
at org.apache.maven.archetype.generator.DefaultArchetypeGenerator.generateArchetype(DefaultArchetypeGenerator.java:286)
at org.apache.maven.archetype.DefaultArchetype.generateProjectFromArchetype(DefaultArchetype.java:69)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:558)
... 4 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11743) NullPointerException in validation jobs
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-11743:
-------------------------------------
Summary: NullPointerException in validation jobs
Key: JBIDE-11743
URL: https://issues.jboss.org/browse/JBIDE-11743
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Reporter: Denis Golovin
Assignee: Alexey Kazakov
-- Error Details --
Date: Tue May 01 17:07:24 PDT 2012
Message:
Severity: Error
Product: Test Product to Control Tests Execution 3.2.0.qualifier (org.jboss.tools.tests.product)
Plugin: org.jboss.tools.common
Session Data:
eclipse.buildId=unknown
java.version=1.7.0
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.jboss.tools.tests.product
Command-line arguments: -product org.jboss.tools.tests.product -data /home/eskimo/Projects/jbds-build/designtime-workspace-jbds-m5 -dev file:/home/eskimo/Projects/jbds-build/jbosstools-src/.metadata/.plugins/org.eclipse.pde.core/JBoss Tools/dev.properties -debug /home/eskimo/Projects/jbds-build/jbosstools-src/.metadata/.plugins/org.eclipse.pde.core/JBoss Tools/.options -os linux -ws gtk -arch x86_64
Exception Stack Trace:
org.jboss.tools.common.validation.JBTValidationException
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:101)
at org.eclipse.wst.validation.internal.operations.ValidatorJob.run(ValidatorJob.java:78)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Caused by: java.lang.NullPointerException
at org.jboss.tools.common.validation.ValidationContext.getAllValidators(ValidationContext.java:76)
at org.jboss.tools.common.validation.ValidationContext.init(ValidationContext.java:93)
at org.jboss.tools.common.validation.ValidationContext.<init>(ValidationContext.java:43)
at org.jboss.tools.common.validation.ContextValidationHelper.getValidationContextManager(ContextValidationHelper.java:176)
at org.jboss.tools.common.validation.ContextValidationHelper.getValidationContextManager(ContextValidationHelper.java:168)
at org.jboss.tools.common.validation.ValidatorManager.validateInJob(ValidatorManager.java:65)
... 2 more
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11545) compile failed in org.jboss.ide.eclipse.archives.ui when run against Juno TP
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-11545:
----------------------------------
Summary: compile failed in org.jboss.ide.eclipse.archives.ui when run against Juno TP
Key: JBIDE-11545
URL: https://issues.jboss.org/browse/JBIDE-11545
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Archives
Affects Versions: 3.3.0.Beta3
Reporter: Nick Boldt
Assignee: Rob Stryker
Priority: Critical
Fix For: 3.3.0.Beta3
{code}
[INFO] org.jboss.ide.eclipse.archives.ui ................. FAILURE [0.476s]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.14.1:compile (default-compile) on project org.jboss.ide.eclipse.archives.ui: Compilation failure: Compilation failure:
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_trunk.soa-tooling.juno-continuous/sources/archives/plugins/org.jboss.ide.eclipse.archives.ui/src/main/org/jboss/ide/eclipse/archives/ui/views/ProjectArchivesCommonView.java:[29,0]
[ERROR] import org.eclipse.ui.views.properties.IPropertySheetPage;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.ui.views.properties.IPropertySheetPage cannot be resolved
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_trunk.soa-tooling.juno-continuous/sources/archives/plugins/org.jboss.ide.eclipse.archives.ui/src/main/org/jboss/ide/eclipse/archives/ui/views/ProjectArchivesCommonView.java:[30,0]
[ERROR] import org.eclipse.ui.views.properties.PropertySheetPage;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.ui.views.properties.PropertySheetPage cannot be resolved
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_trunk.soa-tooling.juno-continuous/sources/archives/plugins/org.jboss.ide.eclipse.archives.ui/src/main/org/jboss/ide/eclipse/archives/ui/views/ProjectArchivesCommonView.java:[165,0]
[ERROR] if( adapter == IPropertySheetPage.class )
[ERROR] ^^^^^^^^^^^^^^^^^^
[ERROR] IPropertySheetPage cannot be resolved to a type
[ERROR] /qa/hudson_ws/workspace/jbosstools-3.3_trunk.soa-tooling.juno-continuous/sources/archives/plugins/org.jboss.ide.eclipse.archives.ui/src/main/org/jboss/ide/eclipse/archives/ui/views/ProjectArchivesCommonView.java:[166,0]
[ERROR] return new PropertySheetPage();
[ERROR] ^^^^^^^^^^^^^^^^^
[ERROR] PropertySheetPage cannot be resolved to a type
[ERROR] 4 problems (4 errors)
{code}
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.ju...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11464) JBossWS-CXF runtime is not recognized in JBDS
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-11464:
-----------------------------------------
Summary: JBossWS-CXF runtime is not recognized in JBDS
Key: JBIDE-11464
URL: https://issues.jboss.org/browse/JBIDE-11464
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.Beta2
Environment: JBDS 5.0.0 Beta1, java version "1.6.0_29", fedora 15-64b, SOA-P 5.2.0 ER6
Reporter: Jaroslav Jankovič
Assignee: Brian Fitzpatrick
Fix For: 3.3.0.Beta3, 3.3.0.Final
After installing jbossws-cxf-installer in SOA-P 5.2.0 ER6 I tried to create Web Service with wizard and wsconsume.sh script in server's bin folder. Both of them passed - classes are correctly generated and javadoc in classes contains "Apache CXF 2.2.12-patch-02" which is correct information.
The problem is, SOA-P 5.2.0 ER6 with jbossws-cxf installed is not recognized when trying to add in CXF Runtime option in preferences page. In my opinion, this is a bug, because as I noted, both wizard and script correctly generates web service with CXF runtime installed in SOA-P server.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11783) seam.core test failures
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBIDE-11783:
--------------------------------------
Summary: seam.core test failures
Key: JBIDE-11783
URL: https://issues.jboss.org/browse/JBIDE-11783
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI
Affects Versions: 3.3.0.CR1
Reporter: Alexey Kazakov
Assignee: Viacheslav Kabanovich
Fix For: 3.3.0.CR1
I can't reproduce it every time. But I can reproduce it pretty often (~50% cases).
{code}
-------------------------------------------------------------------------------
Test set: org.jboss.tools.cdi.core.test.CDICoreAllTests
-------------------------------------------------------------------------------
Tests run: 432, Failures: 9, Errors: 0, Skipped: 0, Time elapsed: 97.756 sec <<< FAILURE!
(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.026 sectestAlternativesInDependentProjects2(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.004 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects2(DependentProjectTest.java:168)
testAlternativesInDependentProjects3(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects3(DependentProjectTest.java:184)
testAlternativesInDependentProjects4_1(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects4_1(DependentProjectTest.java:200)
testAlternativesInDependentProjects4_2(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sectestAlternativesInDependentProjects5(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects5(DependentProjectTest.java:234)
testAlternativesInDependentProjects6(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects6(DependentProjectTest.java:250)
testAlternativesInDependentProjects7(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects7(DependentProjectTest.java:265)
testAlternativesInDependentProjects8(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects8(DependentProjectTest.java:280)
testIndirectDependency(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0 sectestProjectDependencyLoading(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sectestDependentProject(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0 sectestScopeFromParentProject(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:214)
at junit.framework.Assert.assertNotNull(Assert.java:207)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getProducer(DependentProjectTest.java:138)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testScopeFromParentProject(DependentProjectTest.java:105)
testAlternativesInDependentProjects(org.jboss.tools.cdi.core.test.DependentProjectTest) Time elapsed: 0.001 sec <<< FAILURE!
junit.framework.AssertionFailedError: Wrong number of the beans expected:<1> but was:<0>
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.failNotEquals(Assert.java:283)
at junit.framework.Assert.assertEquals(Assert.java:64)
at junit.framework.Assert.assertEquals(Assert.java:195)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:436)
at org.jboss.tools.cdi.core.test.DependentProjectTest.getInjectionPointField(DependentProjectTest.java:425)
at org.jboss.tools.cdi.core.test.DependentProjectTest.testAlternativesInDependentProjects(DependentProjectTest.java:152)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] (JBIDE-11574) The ModeShape Tools JCR CND Editor Should Have A Property Definition Value Constraint Editor
by Dan Florian (JIRA)
Dan Florian created JBIDE-11574:
-----------------------------------
Summary: The ModeShape Tools JCR CND Editor Should Have A Property Definition Value Constraint Editor
Key: JBIDE-11574
URL: https://issues.jboss.org/browse/JBIDE-11574
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: modeshape
Affects Versions: 3.3.0.Beta3
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.4.x
Currently the CND Editor allows any string as a value constraint. However, value constraints have a certain syntax based on the property type. Making it easier for a user to enter/edit value constraints would be a very nice thing to have. Therefore, when adding or editing value constraints the CND editor should display the appropriate controls to facilitate entering a value constraint for the selected property type.
Below are the general rules for each property type. See JCR specification for additional rules and guidelines.
Value Constraint Rules/Syntax:
Strings, URI - must be a regular expression pattern in accordance to the java.util.regex.Pattern syntax.
Name, Reference, Weak Reference - must be a JCR Name (Qualified Name)
Boolean - only allow one constraint of either "true" or "false" (though most do not support constraints on boolean)
Path - must be an absolute or relative path that optionally has a last segment of "*"
Numerics, Date, Binary - must use the JCR range syntax of '[min,max]', '(min,max)', '(min,max]', or '[min,max)'. The "min" or the "max" may be empty indicating there is no restriction in that direction.
A single constraint with a single value can be used to indicate the the property value is a constant. Or multiple constraints each with a single value indicates the property value must be one of those enumerated values.
CndValidator should be changed to validate the value constraints based on the type of the property and the value constraint syntax/rules. If value constraints exist for a property, then the CndValidator should also make sure default values meet at least one of those value constraints.
For Date properties, maybe the value constraint editor could enforce the ISO 8601:2000 format of sYYYY-MM-DDThh:mm:sssTZD.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months