[JBoss JIRA] Created: (JBIDE-8991) Modeshape Connection Failed.
by Pavol Srna (JIRA)
Modeshape Connection Failed.
----------------------------
Key: JBIDE-8991
URL: https://issues.jboss.org/browse/JBIDE-8991
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.3.0.M1
Environment: jbosstools-3.3.0.M1a.aggregate-Update-2011-05-11_15-56-28-H2359.zip, eclipse indigo M6a, linux 32bit
Reporter: Pavol Srna
Assignee: Dan Florian
Priority: Blocker
Fix For: 3.3.0.M2
Connection failed. Error Message: org.codehaus.jettison.json.JSONException: JSONObject["metadata"] not found.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8962) Creating a maven project from the jboss-javaee6-webapp fails due to unsatisfied constraints for CDI
by Fred Bricon (JIRA)
Creating a maven project from the jboss-javaee6-webapp fails due to unsatisfied constraints for CDI
---------------------------------------------------------------------------------------------------
Key: JBIDE-8962
URL: https://issues.jboss.org/browse/JBIDE-8962
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.3.0.M1
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.M2
Create a new maven project using the jboss-javaee6-webapp archetype fails with the following error :
{noformat}
One or more constraints have not been satisfied.
Constraints for CDI (Contexts and Dependency Injection) 1.0 have not been met.
{noformat}
The CDI Facet depends on the Web Module OR the EJB Module Facet. The CDI configurator is declared as secondary to the Java configurator AND the wtp configurator. So it's called BEFORE the WTP configurator, which is responsible for adding the Web or EJB facets.
It needs to try adding the CDI facet only if Web or EJB is already configured, instead of just logging an exception.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8455) NPE in HibernateProjectConfigurator when importing maven or mavenArchetype project example
by Snjezana Peco (JIRA)
NPE in HibernateProjectConfigurator when importing maven or mavenArchetype project example
------------------------------------------------------------------------------------------
Key: JBIDE-8455
URL: https://issues.jboss.org/browse/JBIDE-8455
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.2.0.Final
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 3.3.0.M1
If you import the Weld Java EE 6 example, you will face the following exception:
!ENTRY org.hibernate.eclipse.console 4 4 2011-02-20 22:54:41.156
!MESSAGE Could not activate Hibernate nature on projectjboss-javaee6-webapp
!SUBENTRY 1 org.hibernate.eclipse.console 4 150 2011-02-20 22:54:41.156
!MESSAGE org.eclipse.core.runtime.CoreException: Problems encountered while setting project description.
!STACK 1
org.eclipse.core.runtime.CoreException: Problems encountered while setting project description.
at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1212)
at org.eclipse.core.internal.resources.Project.setDescription(Project.java:1238)
at org.hibernate.eclipse.console.utils.ProjectUtils.addProjectNature(ProjectUtils.java:133)
at org.hibernate.eclipse.console.utils.ProjectUtils.toggleHibernateOnProject(ProjectUtils.java:104)
at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.configureInternal(HibernateProjectConfigurator.java:55)
at org.jboss.tools.maven.hibernate.configurators.HibernateProjectConfigurator.mavenProjectChanged(HibernateProjectConfigurator.java:67)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.mavenProjectChanged(ProjectConfigurationManager.java:646)
at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:636)
at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:767)
at org.maven.ide.eclipse.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:346)
at org.maven.ide.eclipse.project.MavenProjectManager.refresh(MavenProjectManager.java:65)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:209)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:146)
at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.createArchetypeProject(ProjectConfigurationManager.java:481)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$1.run(ArchetypeExamplesWizard.java:73)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1975)
at org.jboss.tools.maven.project.examples.wizard.ArchetypeExamplesWizard$2.run(ArchetypeExamplesWizard.java:85)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months
[JBoss JIRA] Created: (JBIDE-8003) DeltaCloud: move #deleteKey to Key
by Andre Dietisheim (JIRA)
DeltaCloud: move #deleteKey to Key
----------------------------------
Key: JBIDE-8003
URL: https://issues.jboss.org/browse/JBIDE-8003
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: deltacloud
Affects Versions: 3.2.0.CR1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 3.2.x
The DeltaCloud class currently has a method #deleteKey. The Deltacloud server reports available actions on objects and does so with Keys. This approach is perfect REST style as it offers links to available actions.
Keys currently have a destroy action and deltacloud tools do unmarshall this correctly. The tools implementation should therefore remove #deleteKey from the DeltaCloud class and offer such a method on the key that then delegates to the appropriate (destroy-) action.
The current tools implementation already offers this approach for instances but took a shortcut with Keys to have higher prio items for CR1 implemented.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 9 months