January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13351: ---------------------------------- Description: Follow 1. New->Other->JBoss Tools->Configure MavenRepositories ConfigureMavenRepositoriesWizard.java Wizard banner has wrong high less than 66 pixels !ConfigureMavenRepositories.png! 2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..." EditNexusRepositoryDialog.java Dialog should have a banner: !NewRepositoryDialog.png! 3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories" Dialog should have a banner: !ConfigureMavenRepositories2.png! was: Follow 1. New->Other->JBoss Tools->Configure MavenRepositories ConfigureMavenRepositoriesWizard.java Wizard banner has wrong high less than 66 pixels !ConfigureMavenRepositories.png! 2. Window->Preferences Tools->Remote Repositories, button "Add..." EditNexusRepositoryDialog.java Dialog should have a banner: !NewRepositoryDialog.png! > Dialogs look and fill problems > ------------------------------ > > Key: JBIDE-13351 > URL: https://issues.jboss.org/browse/JBIDE-13351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Trivial > Fix For: 4.1.x > > Attachments: ADDJBossToolsRuntimeDialog.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, EditServletClassDialog.png, EditTLDFilesDialog.png, NewRepositoryDialog.png, NewTemplateDialog.png > > > Follow > 1. New->Other->JBoss Tools->Configure MavenRepositories > ConfigureMavenRepositoriesWizard.java > Wizard banner has wrong high less than 66 pixels > !ConfigureMavenRepositories.png! > 2. Window->Preferences, JBoss Tools->Remote Repositories, button "Add..." > EditNexusRepositoryDialog.java > Dialog should have a banner: > !NewRepositoryDialog.png! > 3. Window->Preferences, JBoss Tools->JBoss Maven Integration, button "Configure Maven Repositories" > Dialog should have a banner: > !ConfigureMavenRepositories2.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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13351: ---------------------------------- Description: Follow 1. New->Other->JBoss Tools->Configure MavenRepositories ConfigureMavenRepositoriesWizard.java Wizard banner has wrong high less than 66 pixels !ConfigureMavenRepositories.png! 2. Window->Preferences Tools->Remote Repositories, button "Add..." EditNexusRepositoryDialog.java Dialog should have a banner: !NewRepositoryDialog.png! was: Follow dialogs should have a banner: All dialogs can be found in Preferences (menu Window->Preferences) 1. JBoss Tools->Remote Repositories, button "Add..." EditNexusRepositoryDialog.java ConfigureMavenRepositoriesWizard.java !NewRepositoryDialog.png! 2. JBoss Tools->Web->Visual Page Editor->Code Templates, button "New..." !NewTemplateDialog.png! 3. JBoss Tools->Web->Visual Page Editor->Code Templates, button "Import..." > Dialogs look and fill problems > ------------------------------ > > Key: JBIDE-13351 > URL: https://issues.jboss.org/browse/JBIDE-13351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Trivial > Fix For: 4.1.x > > Attachments: ADDJBossToolsRuntimeDialog.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, EditServletClassDialog.png, EditTLDFilesDialog.png, NewRepositoryDialog.png, NewTemplateDialog.png > > > Follow > 1. New->Other->JBoss Tools->Configure MavenRepositories > ConfigureMavenRepositoriesWizard.java > Wizard banner has wrong high less than 66 pixels > !ConfigureMavenRepositories.png! > 2. Window->Preferences Tools->Remote Repositories, button "Add..." > EditNexusRepositoryDialog.java > Dialog should have a banner: > !NewRepositoryDialog.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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13336) create target platform using Kepler dependencies

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13336?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13336 at 1/9/13 4:54 PM: ------------------------------------------------------------ JDT Core thing is a red herring and can prolly be ignored. -But org.sonatype.m2e.mavenarchiver 0.15.0 depending on org.eclipse.m2e <1.2 is a real problem, since the version of m2e in Kepler is 1.3. [~fbricon] can we get a rebuild of org.sonatype.m2e.mavenarchiver (or is there something newer?) which runs with m2e 1.3?- http://repository.tesla.io:8081/nexus/content/sites/m2e.extras/m2eclipse-... pulled to http://download.jboss.org/jbosstools/updates/m2e-extensions/m2e-mavenarch... for use in TP generation. Looks like its MANIFEST.MF should work w/ m2e < 2.0. We also need a new version of com.atlassian.connector.eclipse.monitor.ui which does not depend on org.eclipse.update.ui, because as [1] states, "This bundle is obsolete." [1] http://git.eclipse.org/c/platform/eclipse.platform.git/tree/update/org.ec... was (Author: nickboldt): JDT Core thing is a red herring and can prolly be ignored. But org.sonatype.m2e.mavenarchiver 0.15.0 depending on org.eclipse.m2e <1.2 is a real problem, since the version of m2e in Kepler is 1.3. [~fbricon] can we get a rebuild of org.sonatype.m2e.mavenarchiver (or is there something newer?) which runs with m2e 1.3? We also need a new version of com.atlassian.connector.eclipse.monitor.ui which does not depend on org.eclipse.update.ui, because as [1] states, "This bundle is obsolete." [1] http://git.eclipse.org/c/platform/eclipse.platform.git/tree/update/org.ec... > create target platform using Kepler dependencies > ------------------------------------------------ > > Key: JBIDE-13336 > URL: https://issues.jboss.org/browse/JBIDE-13336 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > Attachments: multiple.target, multiple.target_update_hints.txt > > > Along with the refactoring we talked about doing in JBIDE-13232, it's time to create a new Kepler M4 target platform. > I've pulled mirrors for the three largest pieces: Kepler M4, Eclipse 4.3M4, WTP 3.5M4: > http://download.jboss.org/jbosstools/updates/requirements/kepler/20121221... > http://download.jboss.org/jbosstools/updates/requirements/eclipse/S-4.3M4... > http://download.jboss.org/jbosstools/updates/requirements/webtools/S-3.5.... > Do you need anything else mirrored? If so bounce this to me and I'll get the bits copied to download.jboss.org for you. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13351: ---------------------------------- Attachment: ConfigureMavenRepositories.png ConfigureMavenRepositories2.png > Dialogs look and fill problems > ------------------------------ > > Key: JBIDE-13351 > URL: https://issues.jboss.org/browse/JBIDE-13351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Trivial > Fix For: 4.1.x > > Attachments: ADDJBossToolsRuntimeDialog.png, BrowseFontDialog.png, ConfigureMavenRepositories.png, ConfigureMavenRepositories2.png, EditServletClassDialog.png, EditTLDFilesDialog.png, NewRepositoryDialog.png, NewTemplateDialog.png > > > Follow dialogs should have a banner: > All dialogs can be found in Preferences (menu Window->Preferences) > 1. JBoss Tools->Remote Repositories, button "Add..." > EditNexusRepositoryDialog.java > ConfigureMavenRepositoriesWizard.java > !NewRepositoryDialog.png! > 2. JBoss Tools->Web->Visual Page Editor->Code Templates, button "New..." > !NewTemplateDialog.png! > 3. JBoss Tools->Web->Visual Page Editor->Code Templates, button "Import..." -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13254) In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13254?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-13254: ---------------------------------------- seam gen generate a plain Java project with Seam builder. It's not enough for code assist in XHTMLs. The project must be a dynamic web project too. When you create a project via new Web Seam Project then we create a dynamic web project with JSF and Seam facets. When you import a maven seam project then maven wst/jsf/seam integration plugins configure the project properly. So this is an issue of seam-gen which generate a plain eclipse java project instead of dynamic web project with JSF and Seam facets. > In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13254 > URL: https://issues.jboss.org/browse/JBIDE-13254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, UpStream > Affects Versions: 3.3.1, 4.0.0.Beta2 > Environment: WFK 2.1.0.CR2 Seam.2.3.0.Final-redhat-1, JBDS 5.0.1.GA, JBDS 6.0.0.Beta2a > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > After importing a Seam 2.3 seam-gen generated project in JBDS, the EL completion for Seam Messages doesn't work. > This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS. > > Actual results: > Even though the "messages" component is suggested, no actual messages from the properties files are suggested. A warning is shown for e.g #{messages['org.jboss.seam.NotLoggedIn']}. > Expected results: > Messages from messages_xx.properties should be suggested without warnings. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13254) In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13254?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-13254: ----------------------------------- Component/s: UpStream > In Seam 2.3 seam-gen generated project imported in JBDS, EL completion for Seam Messages doesn't work > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13254 > URL: https://issues.jboss.org/browse/JBIDE-13254 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam 2, UpStream > Affects Versions: 3.3.1, 4.0.0.Beta2 > Environment: WFK 2.1.0.CR2 Seam.2.3.0.Final-redhat-1, JBDS 5.0.1.GA, JBDS 6.0.0.Beta2a > Reporter: Ron Šmeral > Assignee: Alexey Kazakov > Fix For: 4.1.0.Alpha1 > > > After importing a Seam 2.3 seam-gen generated project in JBDS, the EL completion for Seam Messages doesn't work. > This works OK for a Seam project created in JBDS and for a Maven project imported to JBDS. > > Actual results: > Even though the "messages" component is suggested, no actual messages from the properties files are suggested. A warning is shown for e.g #{messages['org.jboss.seam.NotLoggedIn']}. > Expected results: > Messages from messages_xx.properties should be suggested without warnings. -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13351) Dialogs look and fill problems

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13351?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13351: ---------------------------------- Description: Follow dialogs should have a banner: All dialogs can be found in Preferences (menu Window->Preferences) 1. JBoss Tools->Remote Repositories, button "Add..." EditNexusRepositoryDialog.java ConfigureMavenRepositoriesWizard.java !NewRepositoryDialog.png! 2. JBoss Tools->Web->Visual Page Editor->Code Templates, button "New..." !NewTemplateDialog.png! 3. JBoss Tools->Web->Visual Page Editor->Code Templates, button "Import..." was: Follow dialogs should have a banner: All dialogs can be found in Preferences (menu Window->Preferences) 1. JBoss Tools->JBoss Tools Runtime Detection, button "Add", BTW it should be "Add..." !ADDJBossToolsRuntimeDialog.png! 2. JBoss Tools->Web->Editors->JSF Flow Diagram, buttons "Browse..." !BrowseFontDialog.png! 3. JBoss Tools->Remote Repositories, button "Add..." !NewRepositoryDialog.png! 4. JBoss Tools->Web->Visual Page Editor->Code Templates, button "New..." !NewTemplateDialog.png! 5. JBoss Tools->Web->Visual Page Editor->Code Templates, button "Import..." > Dialogs look and fill problems > ------------------------------ > > Key: JBIDE-13351 > URL: https://issues.jboss.org/browse/JBIDE-13351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JSF, runtime-detection, Seam 2, Visual Page Editor Templates > Affects Versions: 4.1.0.Alpha1 > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Priority: Trivial > Fix For: 4.1.x > > Attachments: ADDJBossToolsRuntimeDialog.png, BrowseFontDialog.png, EditServletClassDialog.png, EditTLDFilesDialog.png, NewRepositoryDialog.png, NewTemplateDialog.png > > > Follow dialogs should have a banner: > All dialogs can be found in Preferences (menu Window->Preferences) > 1. JBoss Tools->Remote Repositories, button "Add..." > EditNexusRepositoryDialog.java > ConfigureMavenRepositoriesWizard.java > !NewRepositoryDialog.png! > 2. JBoss Tools->Web->Visual Page Editor->Code Templates, button "New..." > !NewTemplateDialog.png! > 3. JBoss Tools->Web->Visual Page Editor->Code Templates, button "Import..." -- 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10861) "use existing" project is not setting selection based on current selection for start of wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10861?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10861: ------------------------------------------ setting to *Minor* since JBIDE-10546 is the even better improvement IMHO. This here is an additional improvement compared to it. > "use existing" project is not setting selection based on current selection for start of wizard > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-10861 > URL: https://issues.jboss.org/browse/JBIDE-10861 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.x > > > rght click existing project -> new openshift app -> type in details, on the project config page that existing project should be preselected when "unchecking" create new 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10861) "use existing" project is not setting selection based on current selection for start of wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10861?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10861: ------------------------------------- Priority: Minor (was: Major) > "use existing" project is not setting selection based on current selection for start of wizard > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-10861 > URL: https://issues.jboss.org/browse/JBIDE-10861 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.x > > > rght click existing project -> new openshift app -> type in details, on the project config page that existing project should be preselected when "unchecking" create new 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

13 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-10546) Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10546?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10546: ------------------------------------------ Jelastic Eclipse plugins do the same. They provide entries in the context menu of a project: http://blog.jelastic.com/2012/11/13/jelastic-integration-with-eclipse/ Even they they should not add those to the root of the context menu. The should nest them into *Configure* or something. > Add ability to import an existing application to OpenShift through the 'Configure' item within the context menu of an application > --------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10546 > URL: https://issues.jboss.org/browse/JBIDE-10546 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Isaac Rooskov > Assignee: Xavier Coulon > Fix For: 4.0.x > > > The 3.3.0.M5 new and noteworthy information highlights the ability to take an application that exists in the workspace and port it to OpenShift; however it has to be done through the OpenShift application creation wizard. > A more intuitive place for this ability to be might be within the context menu of an application in the workspace. The option to 'Import to OpenShift' could sit under the 'Configure' menu item. -- 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

13 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013