[JBoss JIRA] Created: (JBDS-1577) using JBDS as updatesite on eclipse works, but causes outofmemory because of name change
by Max Rydahl Andersen (JIRA)
using JBDS as updatesite on eclipse works, but causes outofmemory because of name change
----------------------------------------------------------------------------------------
Key: JBDS-1577
URL: https://issues.jboss.org/browse/JBDS-1577
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.0.0.GA
Reporter: Max Rydahl Andersen
Not sure if this qualifies as a bug or a feature request but
I noticed that if I use JBDS 4 updatesite against plain Eclipse things seem to work great
until you restart (possible on the second restart) since then it suddenly has zero
extra memory allocated.
It only started working properly when using the jbdevstudio.app; thus my assumption is that
eclipse.ini is ignored and jbdevstudio.ini is looked for instead but this file is nowhere
to be found (except inside jbdevstudio.app)
Would be good if we could handle this situation more gracefully since the shortcuts users
uses still points to eclipse thus they will see it as JBDS running out of memory since when launching
it says JBDS.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (JBIDE-10535) 12 tests skipped in org.jboss.tools.ws.jaxrs.core
by Nick Boldt (Created) (JIRA)
12 tests skipped in org.jboss.tools.ws.jaxrs.core
-------------------------------------------------
Key: JBIDE-10535
URL: https://issues.jboss.org/browse/JBIDE-10535
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.Beta1
Reporter: Nick Boldt
Assignee: Brian Fitzpatrick
Fix For: 3.3.0.Beta1
After switching to newer target platform (JBIDE-10289), 12 tests are being skipped:
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
shoudCreateEndpointWhenAddingSubresourceLocatorMethodInSubresource
shouldAddResourceFieldWhenAddingFieldAnnotatedWithQueryParam
shouldDoNothingMethodWhenAddingAnotherAnnotationOnParameter
shouldDoNothingMethodWhenChangingAnotherAnnotationOnParameter
shouldDoNothingMethodWhenRemovingAnotherAnnotationOnParameter
shouldRemoveResourceWhenRemovingBinaryLib
shouldUpdateResourceMethodWhenAddingMatrixParamAnnotationOnParameter
shouldUpdateResourceMethodWhenAddingThrowsException
shouldUpdateResourceMethodWhenChangingMatrixParamAnnotationOnParameter
shouldUpdateResourceMethodWhenChangingThrowsException
shouldUpdateResourceMethodWhenRemovingMatrixParamAnnotationOnParameter
shouldUpdateResourceMethodWhenRemovingThrowsException
{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, 9 months
[JBoss JIRA] (JBIDE-12128) NPE when moving JAX-RS resource into another package
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-12128:
-------------------------------------
Summary: NPE when moving JAX-RS resource into another package
Key: JBIDE-12128
URL: https://issues.jboss.org/browse/JBIDE-12128
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.3.0.CR1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 3.3.0.CR1
Stacktrace is :
java.lang.NullPointerException
at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:587)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.internalCreateResourceMethod(JaxrsElementFactory.java:236)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.JaxrsElementFactory.createResource(JaxrsElementFactory.java:148)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAddition(JavaElementChangedProcessor.java:197)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedElement(JavaElementChangedProcessor.java:122)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedProcessor.processAffectedJavaElements(JavaElementChangedProcessor.java:75)
at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:56)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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, 9 months
[JBoss JIRA] (JBIDE-11586) ModeShape Tools JCR CND Editor Deletes Comments And Vendor Extensions
by Dan Florian (JIRA)
Dan Florian created JBIDE-11586:
-----------------------------------
Summary: ModeShape Tools JCR CND Editor Deletes Comments And Vendor Extensions
Key: JBIDE-11586
URL: https://issues.jboss.org/browse/JBIDE-11586
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: modeshape
Affects Versions: 3.3.0.Beta3
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 3.4.x
All comments and vendor extensions are thrown out by the CndImporter when a *.cnd file is parsed. The CndImporter class was copied over from the ModeShape project and ModeShape does not need or use comments and vendor extensions. Also, the CND Editor currently does not support editing or creating of either comments and vendor extensions.
At a minimum, the original comments and vendor extensions should be saved and written back out when the CND editor is saved. Ultimately, the CND Editor should support both constructs. Each comment should be related to the CND itself or to another CND element like a node type definition, property definition, of child node definition. When the related CND element is deleted, the comment should also be deleted.
--
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, 9 months
[JBoss JIRA] (JBIDE-12022) Cannot install JBoss BIRT integration from nightly update-site
by Jaroslav Jankovič (JIRA)
Jaroslav Jankovič created JBIDE-12022:
-----------------------------------------
Summary: Cannot install JBoss BIRT integration from nightly update-site
Key: JBIDE-12022
URL: https://issues.jboss.org/browse/JBIDE-12022
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt
Affects Versions: 3.3.0.CR1
Reporter: Jaroslav Jankovič
Assignee: Snjezana Peco
Priority: Blocker
Fix For: 3.3.0.CR1, 3.3.0.Final
When I was trying to install all features from JBT nightly update-site missing requirement was thrown:
{code}
Cannot complete the install because one or more required items could not be found.
Software being installed: JBoss BIRT Integration 1.3.0.v20120526-0223-H949-CR1 (org.jboss.tools.birt.feature.feature.group 1.3.0.v20120526-0223-H949-CR1)
Missing requirement: JBoss BIRT Core 1.3.0.v20120526-0223-H949-CR1 (org.jboss.tools.birt.core 1.3.0.v20120526-0223-H949-CR1) requires 'bundle org.eclipse.birt.integration.wtp.ui 0.0.0' but it could not be found
Cannot satisfy dependency:
From: JBoss BIRT Integration 1.3.0.v20120526-0223-H949-CR1 (org.jboss.tools.birt.feature.feature.group 1.3.0.v20120526-0223-H949-CR1)
To: org.jboss.tools.birt.core [1.3.0.v20120526-0223-H949-CR1]
{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, 9 months