[JBoss JIRA] (JBIDE-12574) Support multiple domains in OpenShift UI
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12574?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-12574 at 10/9/13 8:59 AM:
-------------------------------------------------------------------
The OpenShift Explorer now shows the domains and offers context menu items to create, rename and remove them:
!multi-domain-in-explorer.png!
was (Author: adietish):
The OpenShift Explorer now supports multiple domains:
!multi-domain-in-explorer.png!
> Support multiple domains in OpenShift UI
> ----------------------------------------
>
> Key: JBIDE-12574
> URL: https://issues.jboss.org/browse/JBIDE-12574
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Alpha2
> Reporter: Xavier Coulon
> Assignee: Andre Dietisheim
> Fix For: 4.2.0.Alpha1
>
> Attachments: multi-domain-in-explorer.png
>
>
> The OpenShift Explorer view should display a node for the domain between the user and his applications (relevant is support for multiple domains was added)
--
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, 6 months
[JBoss JIRA] (JBIDE-15643) Page is just simply rendered in VPE editor
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-15643:
-----------------------------------
Summary: Page is just simply rendered in VPE editor
Key: JBIDE-15643
URL: https://issues.jboss.org/browse/JBIDE-15643
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: visual-page-editor-core
Affects Versions: 4.1.0.Final
Reporter: Vlado Pakan
Assignee: Yahor Radtsevich
Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1
Not sure if this is not supported or if it's a bug. Thing is that page is not rendered with style but only very simple. See real output and output in VPE editor.
--
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, 6 months
[JBoss JIRA] (JBIDE-15132) Have Maven projects automatically apply project defined code style, formatting and templates
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15132?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-15132:
--------------------------------
Fix Version/s: LATER
> Have Maven projects automatically apply project defined code style, formatting and templates
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-15132
> URL: https://issues.jboss.org/browse/JBIDE-15132
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Environment: Eclipse
> Reporter: Sanne Grinovero
> Fix For: LATER
>
>
> Very often we need to re-import Maven projects, and m2 reconfigures it *almost* all correctly. Latest Eclipse even auto-shares the git repository, which solved one very annoying and repetitive step, but there is one left:
> most of our projects use a custom formatting rule, code cleanup rules, and templates to generate some common elements like the project specific copyright headers.
> For example Hibernate recommends to download three files from:
> https://community.jboss.org/wiki/ContributingToHibernateUsingEclipse
> these need to be imported in eclipse, and applied to each project.
> Nowadays I need to re-apply these each and every time M2 needs to reconfigure the project; it would be absolutely amazing if I could commit these three files in the project and refer to them from my pom.xml?
> We already have something like that working for checkstyle: m2 detects the need to download a plugin, and applies the custom rules. But that's not enough.
> Benefit:
> not just our own time, but also make life of each and every occasional contributor much easier to get started.
--
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, 6 months