[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, 11 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, 11 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, 11 months
[JBoss JIRA] (JBIDE-11624) Errors in error log when creating Java EE Project e
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-11624:
-----------------------------------------
Summary: Errors in error log when creating Java EE Project e
Key: JBIDE-11624
URL: https://issues.jboss.org/browse/JBIDE-11624
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: CDI, central, maven
Affects Versions: 3.3.0.Beta3
Reporter: Jaroslav Jankovič
Assignee: Alexey Kazakov
Fix For: 3.3.0.Beta3
When I am creating Java EE Project through JBT wizard (New -> Other -> JBoss Central -> Java EE Project), 2 errors in error log are thrown. It says: 'The variable jpaPlatform is not defined'. I understand that I have not set any database connection, but I would expect only warning messages in Markers view.
The stacktrace of error:
{code:borderStyle=solid}
org.eclipse.core.runtime.CoreException: The variable jpaPlatform is not defined
at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:65)
at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.AndExpression.evaluate(AndExpression.java:29)
at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
at org.eclipse.core.internal.expressions.EnablementExpression.evaluate(EnablementExpression.java:53)
at org.eclipse.jst.common.project.facet.core.libprov.internal.LibraryProvider.isEnabledFor(LibraryProvider.java:287)
at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.refresh(LibraryInstallDelegate.java:364)
at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate$2.handleEvent(LibraryInstallDelegate.java:132)
at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1326)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:343)
at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.installProjectFacet(FacetedProject.java:255)
at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installM2Facet(CDIProjectConfigurator.java:127)
at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.installDefaultFacets(CDIProjectConfigurator.java:141)
at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.configureInternal(CDIProjectConfigurator.java:98)
at org.jboss.tools.maven.cdi.configurators.CDIProjectConfigurator.mavenProjectChanged(CDIProjectConfigurator.java:113)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:752)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:724)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:847)
at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:280)
at org.eclipse.m2e.core.internal.project.registry.MavenProjectManager.refresh(MavenProjectManager.java:58)
at org.eclipse.m2e.core.internal.builder.MavenBuilder.build(MavenBuilder.java:120)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:728)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:199)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:239)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:292)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:295)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:351)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:374)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
{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, 11 months
[JBoss JIRA] (JBIDE-11721) Project location input is not validated in New Project Example wizard
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-11721:
---------------------------------------------
Summary: Project location input is not validated in New Project Example wizard
Key: JBIDE-11721
URL: https://issues.jboss.org/browse/JBIDE-11721
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 3.3.0.Beta2
Reporter: Viacheslav Kabanovich
Assignee: Snjezana Peco
EXECUTE: Open JBoss Central and click link 'HTML5 Project'.
EXECUTE: On wizard's second page, remove check at 'Use default Workspace location'
EXECUTE: Make input field 'Location' empty manually, if it does not become empty automatically.
ASSERT: Finish is disabled and wizard displays an error message.
FAILURE: Finish is enabled, no error message.
EXECUTE: Run finish with empty 'Location'. (That may not be possible when the validation is fixed.)
FAILURE: Wizard completes with many exceptions and displays window "'HTML5 Project' Project is now ready", "Show '/poh5/README.md' for further instructions", which results in more exceptions.
(Linux)
Repeat the first two steps, then
EXECUTE: Fill input field 'Location' with non-existing path "abc".
ASSERT: Finish is disabled and wizard displays an error message. (Compare with New Java project, or another standard project)
FAILURE: Finish is enabled, no error message.
EXECUTE: Run finish. (That may not be possible when the validation is fixed.)
NON-STANDARD: Wizard completes successfully, project is created in Eclipse installation folder.
--
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, 11 months
[JBoss JIRA] (JBIDE-11295) Creating/Editing domain in OpenShift Console view when user not connected
by Lucia Jelinkova (JIRA)
Lucia Jelinkova created JBIDE-11295:
---------------------------------------
Summary: Creating/Editing domain in OpenShift Console view when user not connected
Key: JBIDE-11295
URL: https://issues.jboss.org/browse/JBIDE-11295
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Lucia Jelinkova
Assignee: Xavier Coulon
Priority: Minor
Fix For: 3.3.0.CR1
When I click Create / Edit domain in OpenShift Console view while not connected to the OpenShift account and cancel credentials prompt dialog, the dialog for creating the domain appears. I am then asked for credentials and if I fill them an error message saying that the user already has domain appears.
In case the user is not logged in and cancels the credentials prompt dialog please do not show the Create domain dialog at all.
--
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, 11 months