[JBoss JIRA] Created: (JBIDE-5620) Error when deleting more than one project via Web Projects view
by Vlado Pakan (JIRA)
Error when deleting more than one project via Web Projects view
---------------------------------------------------------------
Key: JBIDE-5620
URL: https://jira.jboss.org/jira/browse/JBIDE-5620
Project: Tools (JBoss Tools)
Issue Type: Bug
Affects Versions: 3.1.0.CR1
Environment: JBoss Developer Studio: Version: 3.0.0.CR1
Java Sun JDK 1.5
Reporter: Vlado Pakan
Attachments: deleteError.png
When deleting more than one project via Web Projects only first selected project is deleted and then Error Dialog is displayed.
See attached file.
When more projects are deleting via Package Explorer everything works fine.
Steps to reproduce:
1. Create 2 JSF Projects
2. Select these 2 new JSF Projects in Web Projects view and press <Delete>
3. First project disappear from Web Project view and then Error Dialog is displayed
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBIDE-5013) Don't remove "\" from property file
by Krasimir Goutcev (JIRA)
Don't remove "\" from property file
-----------------------------------
Key: JBIDE-5013
URL: https://jira.jboss.org/jira/browse/JBIDE-5013
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 3.1.0.M4
Reporter: Krasimir Goutcev
Attachments: prop1.png, prop2.png
Here is an example of the contents of a properties file:
# a comment
! a comment
a = a string
b = a string with escape sequences \t \n \r \\ \" \' \ (space) \u0123
c = a string with a continuation line \
continuation line
Now if you put something like
key = a string with a continuation line \
continuation line
next time when you open file will see:
key = a string with a continuation line continuation line
Second:
Now "Add property" is :see pic1
why not to be: see pic2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBIDE-5036) JDT Internal Error connected with JBossAS while java method renaming
by Daniel Azarov (JIRA)
JDT Internal Error connected with JBossAS while java method renaming
---------------------------------------------------------------------
Key: JBIDE-5036
URL: https://jira.jboss.org/jira/browse/JBIDE-5036
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.1.0.M3
Reporter: Daniel Azarov
Assignee: Rob Stryker
Testcase:
1. Create jsf KickStart project
2. Open \JavaSource\demo\User.java in java editor
3. Select getName() method name
4. Mouse right click
5. Select Refactor->Rename
6. Type new name, "getName2" for instance
7. Press Enter
FAIL:
java.lang.reflect.InvocationTargetException
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:91)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist]
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113)
at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143)
at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224)
at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
... 1 more
Root exception:
Java Model Exception: Java Model Status [1.0.com.sun.tools.xjc.reader.xmlschema.bindinfo [in C:\JBoss\jboss-4.2.0.GA\client\jaxb-xjc.jar] does not exist]
at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:502)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246)
at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:504)
at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:240)
at org.eclipse.jdt.internal.core.SourceRefElement.generateInfos(SourceRefElement.java:107)
at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:515)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:252)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:238)
at org.eclipse.jdt.internal.core.BinaryMethod.getFlags(BinaryMethod.java:113)
at org.eclipse.jdt.internal.corext.util.JavaModelUtil.isVisibleInHierarchy(JavaModelUtil.java:240)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:407)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.uniteWithSupertypes(RippleMethodFinder2.java:403)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.createUnionFind(RippleMethodFinder2.java:384)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.findAllRippleMethods(RippleMethodFinder2.java:196)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getAllRippleMethods(RippleMethodFinder2.java:168)
at org.eclipse.jdt.internal.corext.refactoring.rename.RippleMethodFinder2.getRelatedMethods(RippleMethodFinder2.java:161)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.initializeMethodsToRename(RenameMethodProcessor.java:236)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameMethodProcessor.doCheckFinalConditions(RenameMethodProcessor.java:360)
at org.eclipse.jdt.internal.corext.refactoring.rename.RenameVirtualMethodProcessor.doCheckFinalConditions(RenameVirtualMethodProcessor.java:143)
at org.eclipse.jdt.internal.corext.refactoring.rename.JavaRenameProcessor.checkFinalConditions(JavaRenameProcessor.java:46)
at org.eclipse.ltk.core.refactoring.participants.ProcessorBasedRefactoring.checkFinalConditions(ProcessorBasedRefactoring.java:224)
at org.eclipse.ltk.core.refactoring.CheckConditionsOperation.run(CheckConditionsOperation.java:85)
at org.eclipse.ltk.core.refactoring.CreateChangeOperation.run(CreateChangeOperation.java:121)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800)
at org.eclipse.ltk.internal.ui.refactoring.WorkbenchRunnableAdapter.run(WorkbenchRunnableAdapter.java:87)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months
[JBoss JIRA] Created: (JBDS-1084) Weird unresolved dependencies in JBDS
by Brian Fitzpatrick (JIRA)
Weird unresolved dependencies in JBDS
-------------------------------------
Key: JBDS-1084
URL: https://jira.jboss.org/jira/browse/JBDS-1084
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: integration
Affects Versions: 3.0.0.CR2
Reporter: Brian Fitzpatrick
Assignee: Max Rydahl Andersen
While working out some weird issues with Smooks, Nick discovered that we had some bizarre missing dependencies. And we aren't able to see who they're coming from...
The list includes the following... Any ideas? Wasn't sure who to assign this to, but NIck suggested that we create a JIRA so these issues don't get lost.
javax.transaction_1.1.1.v200909161740.jar
javax.persistence_1.99.0.v200906021518.jar
org.eclipse.dltk.debug_1.0.0.v20090613-1432.jar
com.caucho.hessian_3.1.3.jar
org.eclipse.dltk.formatter_1.0.1.v20090903-2153.jar
org.eclipse.dltk.launching_1.0.1.v20090910-1601.jar
org.eclipse.dltk.core_1.0.1.v20090910-1601.jar
org.eclipse.dltk.ruby.ui_1.0.0.v20090613-1432.jar
org.eclipse.dltk.ruby.formatter_1.0.0.v20090617-1157.jar
org.eclipse.dltk.ruby.core_1.0.0.v20090613-1432.jar
com.lowagie.itext_1.5.4.v20090305
org.eclipse.persistence.antlr_1.1.2.v20090612-r4475.jar
org.eclipse.net4j.util_2.0.0.v200906160348.jar
org.eclipse.net4j.spring_0.7.1.v200610271244
org.eclipse.persistence.asm_1.1.2.v20090612-r4475.jar
org.eclipse.dltk.ui_1.0.1.v20090903-2153.jar
org.eclipse.persistence.jpa_1.1.2.v20090612-r4475.jar
org.eclipse.persistence.core_1.1.2.v20090612-r4475.jar
org.eclipse.net4j.jms.api_1.0.8.v200902231136
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 5 months