[JBoss JIRA] (JBIDE-16077) CLONE - when hyperlinked file does not exist offer to create one
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16077?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16077.
-------------------------------
Verified with JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> CLONE - when hyperlinked file does not exist offer to create one
> ----------------------------------------------------------------
>
> Key: JBIDE-16077
> URL: https://issues.jboss.org/browse/JBIDE-16077
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: new_and_noteworthy, respin-a
> Fix For: 4.1.1.CR1
>
> Attachments: CreateFileHyperlink.png, CreateMissingFile1.png, CreateMissingFile1.png, CreateMissingFile2.png, Question.png
>
>
> When Ctrl+clicking on app.js in this snippet:
> <script type="text/javascript" src="js/app.js"></script>
> And the file js/app.js does not exist eclipse just "blinks".
> Better if we could offer creating the file, even just a blank/empty one.
> The same goes for image and css references, all those would be nice not having to go through the full ctrl+N wizard to just create such files.
> *Details:*
> Implemented new hyperlink detector which works for follow files: xml, htm, html, jsp, xhtml.
> Hyperlink detector searches in text nodes and attribute values for string which ends with ".js", ".css", ".jsp", ".htm", ".html" and ".xhtml". Hyperlink detector tries to consider that string as a file name and tries to find that file in a project. If there is no such file, hyperlink detector makes hyperlink which offer to create missing file:
> File '<filename>' does not exist. Click here to create.
> Note: name of hyperlink is visible only if there are two or more hyperlinks for the same text region.
> If you click on this hyperlink follow dialog will appear:
> !CreateMissingFile1.png!
> If you select checkbox and press OK, wizard will appear:
> !CreateMissingFile2.png!
> If you press button Finish wizard will create the file
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16017) CLONE - Validation problem in faces-config.xml for JSF 2.2 projects
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16017?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-16017.
-------------------------------
Verified with JBDS7.1.0.CR1 CR1-v20131124-0717-B560
> CLONE - Validation problem in faces-config.xml for JSF 2.2 projects
> -------------------------------------------------------------------
>
> Key: JBIDE-16017
> URL: https://issues.jboss.org/browse/JBIDE-16017
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.1.Beta1
> Reporter: Alexey Kazakov
> Assignee: Alexey Kazakov
> Labels: respin-a
> Fix For: 4.1.1.CR1
>
>
> 1. Create a JSF 2.2 KickStart project (or a dynamic web project with JSF 2.2. facet).
> 2. There is an error in problems view:
> Referenced file contains errors (file:/home/igels/Projects/jbt-4.0/contribution/jbosstools-jst/plugins/org.jboss.tools.jst.web/catalog/web-facesconfig_2_2.xsd). For more information, right click on the message in the Problems View and select "Show Details..."
> Is it a real problem in the web-facesconfig_2_2.xsd we bundle with JBT or maybe it's an upstream problem with WTP XML validation?
> BTW, http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd is already registered in XML Catalog by WTP. There is no need to keep our own version in XML Catalog:
> {code}
> Entry element: URI
> Location: dtdsAndSchemas/web-facesconfig_2_2.xsd in jar file home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar
> URI: jar:file:/home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/.bundle_pool/plugins/org.eclipse.jst.standard.schemas_1.2.100.v201305161752.jar!/dtdsAndSchemas/web-facesconfig_2_2.xsd
> Key type: Namespace name
> Key: http://xmlns.jcp.org/xml/ns/javaee/web-facesconfig_2_2.xsd
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-15304) NullPointerExceptions in JAX-RS doesn't report what project is affected
by Radoslav Rábara (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15304?page=com.atlassian.jira.plugi... ]
Radoslav Rábara closed JBIDE-15304.
-----------------------------------
Verified in JBDS 7.1.0 CR1-v20131124-0717-B560
> NullPointerExceptions in JAX-RS doesn't report what project is affected
> -----------------------------------------------------------------------
>
> Key: JBIDE-15304
> URL: https://issues.jboss.org/browse/JBIDE-15304
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
>
>
> I've seen this exception happens many times when I have several projects imported out of JBoss Central:
> {code}java.lang.NullPointerException
> at org.jboss.tools.ws.jaxrs.core.jdt.JavaMethodSignaturesVisitor.visit(JavaMethodSignaturesVisitor.java:105)
> at org.eclipse.jdt.core.dom.MethodDeclaration.accept0(MethodDeclaration.java:489)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.TypeDeclaration.accept0(TypeDeclaration.java:484)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.eclipse.jdt.core.dom.ASTNode.acceptChildren(ASTNode.java:2585)
> at org.eclipse.jdt.core.dom.CompilationUnit.accept0(CompilationUnit.java:220)
> at org.eclipse.jdt.core.dom.ASTNode.accept(ASTNode.java:2514)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:674)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.mergeAST(CompilationUnitsRepository.java:113)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanDelta(JavaElementDeltaScanner.java:119)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementDeltaScanner.scanAndFilterEvent(JavaElementDeltaScanner.java:71)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.run(JavaElementChangedBuildJob.java:54)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedBuildJob.execute(JavaElementChangedBuildJob.java:41)
> at org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElementChangedListener.elementChanged(JavaElementChangedListener.java:69)
> at org.eclipse.jdt.internal.core.DeltaProcessor$4.run(DeltaProcessor.java:1682)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.core.DeltaProcessor.notifyListeners(DeltaProcessor.java:1672)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fireReconcileDelta(DeltaProcessor.java:1524)
> at org.eclipse.jdt.internal.core.DeltaProcessor.fire(DeltaProcessor.java:1483)
> at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:769)
> at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:788)
> at org.eclipse.jdt.internal.core.CompilationUnit.reconcile(CompilationUnit.java:1247)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:126)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.access$0(JavaReconcilingStrategy.java:108)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy$1.run(JavaReconcilingStrategy.java:89)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.reconcile(JavaReconcilingStrategy.java:87)
> at org.eclipse.jdt.internal.ui.text.java.JavaReconcilingStrategy.initialReconcile(JavaReconcilingStrategy.java:178)
> at org.eclipse.jdt.internal.ui.text.CompositeReconcilingStrategy.initialReconcile(CompositeReconcilingStrategy.java:114)
> at org.eclipse.jdt.internal.ui.text.JavaCompositeReconcilingStrategy.initialReconcile(JavaCompositeReconcilingStrategy.java:136)
> at org.eclipse.jface.text.reconciler.MonoReconciler.initialProcess(MonoReconciler.java:105)
> at org.eclipse.jdt.internal.ui.text.JavaReconciler.initialProcess(JavaReconciler.java:406)
> at org.eclipse.jface.text.reconciler.AbstractReconciler$BackgroundThread.run(AbstractReconciler.java:173)
> {code}
> couldn't catch exact steps to replicate, because I have many projects in workspace and log entry doesn't provide additional info about project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16104) SSH keys wizard: Unreachable host error: error gets hidden by wizard, wizard wont tell you about error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16104?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16104:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have an account on an OpenShift server that is only reachable via proxy (ex. console.itos.redhat.com)
# ASSERT: make sure that you have the connection defined in OpenShift Explorer
# EXEC: remove proxy from Eclipse preferences
# EXEC: select your connection in Explorer and pick "Manage SSH keys"
Result:
!error-loading-keys.png!
appears but is hidden by the keys wizard which is immediately coming up and shows no errors:
!error-loading-keys.png!
keys wizard is not showing any error
!no-error-in-keys-wizard.png!
was:
# ASSERT: make sure that you have an account on an OpenShift server that is only reachable via proxy (ex. console.itos.redhat.com)
# ASSERT: make sure that you have the connection defined in OpenShift Explorer
# EXEC: remove proxy from Eclipse preferences
# EXEC: select your connection in Explorer and pick "Manage SSH keys"
Result:
* !error-loading-keys.png!
appears but is hidden by the keys wizard which is immediately coming up and shows no errors:
!error-loading-keys.png!
* keys wizard is not showing any error
!no-error-in-keys-wizard.png!
> SSH keys wizard: Unreachable host error: error gets hidden by wizard, wizard wont tell you about error
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16104
> URL: https://issues.jboss.org/browse/JBIDE-16104
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: error-loading-keys.png, no-error-in-keys-wizard.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months
[JBoss JIRA] (JBIDE-16104) SSH keys wizard: Unreachable host error: error gets hidden by wizard, wizard wont tell you about error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16104?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16104:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure that you have an account on an OpenShift server that is only reachable via proxy (ex. console.itos.redhat.com)
# ASSERT: make sure that you have the connection defined in OpenShift Explorer
# EXEC: remove proxy from Eclipse preferences
# EXEC: select your connection in Explorer and pick "Manage SSH keys"
Result:
* !error-loading-keys.png!
appears but is hidden by the keys wizard which is immediately coming up and shows no errors:
!error-loading-keys.png!
* keys wizard is not showing any error
!no-error-in-keys-wizard.png!
> SSH keys wizard: Unreachable host error: error gets hidden by wizard, wizard wont tell you about error
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16104
> URL: https://issues.jboss.org/browse/JBIDE-16104
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.1.CR1
> Reporter: Andre Dietisheim
> Fix For: 4.2.x
>
> Attachments: error-loading-keys.png, no-error-in-keys-wizard.png
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 5 months