[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-17676:
------------------------------------
Attachment: angularjs-highlighting.png
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-17676:
------------------------------------
Attachment: angularjs-ca-in-expressions.png
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-17676:
------------------------------------
Attachment: jbt-html-ca-in-attributes.png
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-17676:
------------------------------------
Attachment: angularjs-hyperlink.png
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Victor Rubezhny updated JBIDE-17676:
------------------------------------
Attachment: jbt-html-hyperlink.png
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, angularjs-ca-in-expressions.png, angularjs-highlighting.png, angularjs-hyperlink.png, jbt-html-ca-in-attributes.png, jbt-html-hyperlink.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-17676:
-----------------------------------------
*What we have for Angular.js and how to test*
_Required settings and project properties_
1. Follow steps from JBIDE-16544 to import angular phonecat project, Do not copy the project files when importing (You should be able to pick up the changes made in #2 in your JBT)
2. In git switch your angular phonecat project to branch 'step-5'
{code}
$ cd angular-phonecat
$ git checkout step-5
{code}
... and then refresh the project in JBT due to pick up the changes.
In following 'steps' the pages are splitter into templates, so editors may not to work on them.
3. Convert the project to JavaScript Project (Project Properties -> Configure -> Convert to JavaScript Project
4. Add 'AngularJS module to Tern in order to make anguler-related stuff enabled on the project. In order to do that you should enable 'JBoss Experimental configuration' in Window -> Preferences -> General -> Capabilities first, then enable 'angilar' module in Project properties -> Tern -> Modules.
OK. Your test project should be configured now.
_How to test and what editors can do_
_1. Highlighting_
AngularJS Editor highlights Angular-related attributes and Angular Expressions, while JBoss Tools HTML Editor doesn't:
!angularjs-highlighting.png|thumbnail!
_2. Content Assist in Angular Attribute values_
Both, AngularJS and JBoss Tools HTML Editors show content Assist in Angular attribute values.
So, you can use it in AngularJS Editor:
!angularjs-ca-in-attributes.png|thumbnail!
... as well as in JBoss Tools HTML Editor:
!jbt-html-ca-in-attributes.png|thumbnail!
_3. Content Assist in Angular Expressions_
AngularJS Editor shows content Assist in Angular expressoins, while JBoss Tools HTML Editor doesn't:
!angularjs-ca-in-expressions.png|thumbnail!
_4. Hyperlinks in Angular Attrubute values_
Hyperlinking works for Angular Attribute values (where it's possible) in both, AngularJS and JBoss Tools HTML Editors.
So, you can do hyperlink in AngularJS Editor:
!angularjs-hyperlilnk.png|thumbnail!
... as well as in JBoss Tools HTML Editor:
!jbt-html-hyperlink.png|thumbnail!
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17877) Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17877?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17877:
----------------------------------
Assignee: Xavier Coulon (was: Denis Golovin)
> Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17877
> URL: https://issues.jboss.org/browse/JBIDE-17877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Xavier Coulon
> Fix For: 4.2.0.CR1
>
>
> Exception below was fixed by checking instance of target obect before casting to IType see JBIDE-17716 and skipping the rest of the code.
> Do we need to do something extra in this case?
> {code}
> org.jboss.tools.common
> Error
> Mon Jun 30 12:28:44 CEST 2014
> org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> org.jboss.tools.common.validation.JBTValidationException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> Caused by: java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:79)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.getReturnType(JdtUtils.java:1143)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1067)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:1037)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.recordAST(CompilationUnitsRepository.java:112)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.getAST(CompilationUnitsRepository.java:76)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:413)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17877) Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17877?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-17877:
---------------------------------------
Just use test case from issue this one related to and use class from my comment. As a result you should see exception from description in Error Log View.
> Classe with unbounded type parameter triggers "TypeParameter cannot be cast to IType" exceptions
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17877
> URL: https://issues.jboss.org/browse/JBIDE-17877
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.2.0.CR1
>
>
> Exception below was fixed by checking instance of target obect before casting to IType see JBIDE-17716 and skipping the rest of the code.
> Do we need to do something extra in this case?
> {code}
> org.jboss.tools.common
> Error
> Mon Jun 30 12:28:44 CEST 2014
> org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> org.jboss.tools.common.validation.JBTValidationException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:187)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:205)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validateString(AsYouTypeValidatorManager.java:200)
> at org.jboss.tools.common.validation.java.JavaDirtyRegionProcessor.endProcessing(JavaDirtyRegionProcessor.java:498)
> at org.eclipse.wst.sse.ui.internal.reconcile.DirtyRegionProcessor$BackgroundThread.run(DirtyRegionProcessor.java:697)
> Caused by: java.lang.ClassCastException: org.eclipse.jdt.internal.core.TypeParameter cannot be cast to org.eclipse.jdt.core.IType
> at org.jboss.tools.ws.jaxrs.core.jdt.SourceType.from(SourceType.java:79)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.getReturnType(JdtUtils.java:1143)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignature(JdtUtils.java:1067)
> at org.jboss.tools.ws.jaxrs.core.jdt.JdtUtils.resolveMethodSignatures(JdtUtils.java:1037)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.recordAST(CompilationUnitsRepository.java:112)
> at org.jboss.tools.ws.jaxrs.core.jdt.CompilationUnitsRepository.getAST(CompilationUnitsRepository.java:76)
> at org.jboss.tools.ws.jaxrs.ui.internal.validation.JaxrsMetamodelValidator.validate(JaxrsMetamodelValidator.java:413)
> at org.jboss.tools.common.validation.AsYouTypeValidatorManager.validate(AsYouTypeValidatorManager.java:183)
> ... 4 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17964:
---------------------------------------------
[~pleacu] examples of "solutions" on eclipse marketplace is Talend: http://marketplace.eclipse.org/content/talend-esb-studio-standard-edition and Bonita http://marketplace.eclipse.org/content/bonita-bpm
Notice how they look like normal entries and is possible to be found in both web and eclipse UI - but just dont have a separate updatesite.
This is how I suggest for JBDS IS 7 we make an entry and provide screenshots/info on how to install it.
We can still add tags to dev studio entries so they show up too to make them easy to get to.
If we wanted to make it installable directly we would need to consider/solve:
1) only have one updatesite url that the entry can point to (if we only put integrationstack current url into the entry users will not get access to jboss central nor updates to JBDS - at least not in a consistent manner)
2) we see alot of value in being on the top 10 list - if we start spreading it to integration stack - is that helping our EAP/JavaEE needs and how about JBoss Developer progress that we would be dropping in this list ?
3) if integration stack becomes separate entry, how about the subparts ? like Fuse and Teeid - should they too ? Who will test/maintain these - marketplace does not do any consistency checks etc. its all up to us to make sure things work. QE would need to test these additional mechanisms and which one of these would we document ?
4) In JBDS 8, Fuse integrates jmx with server tooling and JBDS 8.1 or 9 Fabric8 might need to move down too. Giving more consistency to users and simpler code to maintain - but making how JBDSIS gets delivered and what dependencies it different than JBDS 7.
in any case - #1 alone is not something that is trivial/free to change in JBDS 7.
JBDS 8.next or/and JBDS 9 timeframe we could look at doing something smarter.
* Like have the installers (JBDS-3087) install them together (requires more QE, release coordination - JBDSIS is no longer "just" an addon)
* Look at reducing "core jbds" to something even smaller (need to hear what features are considered "not relevant")
* Utilize the drag'n'drop feature we have for JBDSIS installs.
* Have JBDSIS installation info show up as the first thing after install if it is present.
> add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-17964
> URL: https://issues.jboss.org/browse/JBIDE-17964
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: marketplace
> Affects Versions: 4.1.2.Final
> Reporter: Lars Heinemann
> Assignee: Nick Boldt
> Fix For: 4.1.2.Final
>
>
> Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months