[JBoss JIRA] (JBIDE-16135) EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16135?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-16135:
-----------------------------------------
Moved new classes in org.jboss.tools.el.ui to internal package since they're not an API.
> EL Content Assist in Java Editor: Make Content Assistant Additional Info window to support URLs.
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16135
> URL: https://issues.jboss.org/browse/JBIDE-16135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Final
> Reporter: Victor Rubezhny
> Assignee: Victor Rubezhny
> Priority: Minor
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: el-ca-add-info-javaeditor.png, hover-javaeditor.png, hover-xhtmleditor.png, html.png, javadoc.png
>
>
> EL could be used in String values in Java classes, so the same Additional Info is to be shown for Content Assist in Java Editor as well as in Tooltips (Hovers).
> There are two kinds of links which we should support:
> 1. External HTML links (<a href="http://..."> or <a href="https://...">). Such links are supposed to be opened in the default web browser:
> !html.png|thumbnail!
> *Note:* we don't have such links in our content assist. This screenshot is just an example how it will look like if we add any <a> to a description message.
> 2. Internal links to JavaElement (used in JSF EL). It works in the same way as Eclipse JDT content assist does. Such links are supposed to be opened in SWT web browser (in the same description window):
> !javadoc.png|thumbnail!
> 3. Links and Java-like Additional Info in Java Editor (for ELs in Java Strings):
> !el-ca-add-info-javaeditor.png|thumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|thumbnail! !hover-xhtmleditor.png|thumbnail!
> *Steps to test:*
> 1. Make sure JDK sources are available in Eclipse
> 2. Create a JSF 2 KickStart project.
> 3. Open greeting.xhtml
> 4. Type #\{user.name.l and press Ctrl+Space
> 5. Select length
> 6. There should be a description dialog with java element links to length() and CharSequence:
> !javadoc.png|thumbnail!
> EL Content Assist in Java Strings:
> 7. Use the project created at steps 1-2.
> 8. Open User.java.
> 9. Reveal String getName() method and add the following line before the return statement:
> {code}String x = "#{user.}";{code}
> 10. Set the text cursor after 'user.' and press Ctrl-Space
> 11. Select 'name'
> 12. There should be a description dialog with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'
> !el-ca-add-info-javaeditor.png|thumbnail!
> Tooltips in Java Editor:
> 13. Apply the 'name' proposal.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-javaeditor.png|thumbnail!
> Tooltips in JBoss Editors:
> 16. Open inputname.xhtm
> 17. Reveal '#\{user.name\}' EL in editor.
> 14. Point the mouse cursor over 'name' in EL and wait for a second.
> 15. There should be a hover dialog opened with java element links to package 'demo', classes 'String' and 'User', and methods 'getName()' and 'setName()'.
> !hover-xhtmleditor.png|thumbnail!
--
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, 4 months
[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-15381:
------------------------------------
Sorry for the confusion. Looks like I need to switch update sites.
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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, 4 months
[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-15381:
-----------------------------------------------
Yes, it is from cdi-api.jar, version 1.1.0.
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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, 4 months
[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15381:
----------------------------------------
[~clerum] JBT 4.1.1.CR1 does not support CDI 1.1.
This issue was fixed in master branch for the coming 4.2.0.Alpha1
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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, 4 months
[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed
by Cody Lerum (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Cody Lerum commented on JBIDE-15381:
------------------------------------
Can you confirm yours is javax.enterprise.inject.Vetoed and not the Seam Solder Vetoed?
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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, 4 months
[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Len DiMaggio resolved JBDS-2710.
--------------------------------
Resolution: Done
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 7.1.0.GA
>
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> *New* connectors for JBDS 7.1:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100 - JBDS-2724, JBDS-2752 :: Approved, will be in 7.1.0.Beta1
> * m2e-wro4j 1.0.2 connector - JBDS-2577 :: Approved for 7.1.0.CR1
> The current list of connectors in 7.0 *which can be / have been updated* in 7.1 are:
> *Beta1*
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774 :: Approved, will be in 7.1.0.Beta1 (affects JBT/JBDS/Central TP)
> * pmd/4.0.0.v20130510-1000 --> 4.0.1 - JBIDE-14902, JBIDE-15353 :: Approved, will be in 7.1.0.Beta1
> * testng/6.8.1.20130330_0839/ --> 6.8.6.20130914_0724 - JBDS-2415, JBDS-2800 :: Approved, will be in 7.1.0.Beta1 (affects JBDS installer/Central TP)
> *CR1*
> * VJET 0.10.0.x --> 0.10.0.201309201624 - JBIDE-14764, JBIDE-15677 (0.10.0.201309201624 will appear in CR1)
> * eclipsecs/5.6.0.201209221626 (Removed in JBIDE-14799 due to Kepler incompatibility) --> 5.6.1.201306282206 - JBIDE-15128, JBIDE-15129 (added for CR1)
> * springide/3.3.0.201307091516-RELEASE --> 3.4.0.201310051539-RELEASE - JBDS-2690¥, JBDS-2691¥, JBDS-2802, JBDS-2808, JBDS-2719
> * gwt/3.2.3.v201304260926-rel-r42 --> 3.4.2.v201310081834-rel-*r43 ONLY* - JBDS-2486, JBDS-2801 (affects JBT/JBDS/Central TP)
> *CR1 or GA, TBD*
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> These are currently unchanged since December when we released JBDS 6.0.0:
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> ** Could move up to 2.1.1.201307101628 or 2.1.2.201310__ if we want... - http://wiki.eclipse.org/SWTBot#Latest_snapshot_build
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.0.0.GA, and therefore would not block 7.1.0, but might be fixed by upgrading to SpringIDE 3.4.
--
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, 4 months
[JBoss JIRA] (JBIDE-15381) Support annotation @Vetoed
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15381?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-15381:
-----------------------------------------------
I cannot reproduce it.
1. Create class UserSession, producer with type UserSession in another class, and injection point with type UserSession.
Injection point is marked with "Multiple beans ..." - correct.
2. Annotate class UserSession with @Vetoed. Injection point is not marked and resolves to the producer - correct.
3. Remove annotation @Vetoed. Marker "Multiple beans ..." appears again - correct.
4. Move definition of producer into class UserSession. Marker remains - correct.
5. Annotate class UserSession with @Vetoed. Marker appears "No bean is eligible ..." - correct.
> Support annotation @Vetoed
> --------------------------
>
> Key: JBIDE-15381
> URL: https://issues.jboss.org/browse/JBIDE-15381
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi
> Reporter: Viacheslav Kabanovich
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> If class is anotated @Vetoed or if its package is annotated @Vetoed, then it is excluded from managed beans.
> Test with archive.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/CDIArchivesTest
> 2. Open class test.a.Test
> 3. Check that injection @Inject Venus venus; is not satisfied because class test.d.planets.Venus in lib2/cdiastro.jar is annotated @Vetoed.
> 4. Check that injection @Inject Sirius sirius; is not satisfied because package test.d.stars in lib2/cdiastro.jar is annotated @Vetoed. (jar file contains sources to check that).
> Test with sources.
> 1. Import project /org.jboss.tools.cdi.core.test/projects/tck1.1
> 2. Open class org.jboss.jsr299.tck.tests.jbt.vetoed.Injections
> 3. Check that @Inject Pond pond; is not satisfied because org.jboss.jsr299.tck.tests.jbt.vetoed.Pond is annotated @Vetoed.
> 4. Check that @Inject Black black; is not satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas is annotated @Vetoed (see package-info.java).
> 5. Check that @Inject Caspian caspian; is satisfied because package org.jboss.jsr299.tck.tests.jbt.vetoed.seas.inner is not annotated @Vetoed although it is a subpackage of an annotated package.
> 6. Check that @Inject Pond.Creek creek; is satisfied because class Pond.Creek is not annotated @Vetoed although it is a nested class in an annotated class.
--
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, 4 months