[JBoss JIRA] (JBIDE-16140) Investigate usage of Jenkins folder plugin
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16140?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16140:
----------------------------------------
I just had a look at Folders. When it comes to factorization and templating, there is nothing. Such features are actually part of Cloudbees Template plugin ( http://www.cloudbees.com/jenkins-enterprise-by-cloudbees-features-templat... ), which is not OSS.
Folders are basically namespace-aware/parenting views, with some ability to copy a whole folder (and its jobs) to create a new stream. Folders act like namespaces, so there is no need to suffix jobs depending on the stream as long as they are not part of the same folder.
IMO, for our case, Folders would somehow make it easier to "branch" new streams from master. While using it, it just appears that all mechanism we have relying in views and stream suffix conventions is just a workaround to provide exactly what Folders provide. I feel like it's worth using it instead of Views.
> Investigate usage of Jenkins folder plugin
> ------------------------------------------
>
> Key: JBIDE-16140
> URL: https://issues.jboss.org/browse/JBIDE-16140
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Mickael Istria
>
> Cloudbees released their folder plugin, which is about factorizing jobs configuration, as an OSS plugin: http://blog.cloudbees.com/2013/10/cloudbees-folders-plugin-now-open-sourc...
> We should investigate on whether it would help to use to manage JBT/JBDS jobs.
--
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-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 updated JBIDE-16135:
------------------------------------
Description:
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 javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
was:
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|tumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|tumbnail! !hover-xhtmleditor.png|tumbnail!
*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 javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> 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 javalement links to length() and CharSequence:
> !javadoc.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-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 updated JBIDE-16135:
------------------------------------
Description:
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|tumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|tumbnail! !hover-xhtmleditor.png|tumbnail!
*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 javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
was:
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|tumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|tumbnail! !hover-xhtml-editor.png|tumbnail!
*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 javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> 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|tumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|tumbnail! !hover-xhtmleditor.png|tumbnail!
> *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 javalement links to length() and CharSequence:
> !javadoc.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-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 updated JBIDE-16135:
------------------------------------
Attachment: hover-xhtmleditor.png
hover-javaeditor.png
el-ca-add-info-javaeditor.png
> 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|tumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|tumbnail! !hover-xhtml-editor.png|tumbnail!
> *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 javalement links to length() and CharSequence:
> !javadoc.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-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 updated JBIDE-16135:
------------------------------------
Description:
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|tumbnail!
4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
!hover-javaeditor.png|tumbnail! !hover-xhtml-editor.png|tumbnail!
*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 javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
was:
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!
*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 javalement links to length() and CharSequence:
!javadoc.png|thumbnail!
> 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: 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|tumbnail!
> 4. Same look and functionality for Tooltips (Hovers) in Java and JBossTools Editors:
> !hover-javaeditor.png|tumbnail! !hover-xhtml-editor.png|tumbnail!
> *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 javalement links to length() and CharSequence:
> !javadoc.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-16153) Enable Cordova tests in continuous build
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-16153:
--------------------------------------
Summary: Enable Cordova tests in continuous build
Key: JBIDE-16153
URL: https://issues.jboss.org/browse/JBIDE-16153
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: aerogear-hybrid, build
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 4.2.0.Alpha1
There is a TestSuite available in jbosstools-aerogear. It should be run by default with a "mvn clean verify" and then enabled on Jenkins.
--
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