February 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-16607) Seam 2.3 Portlet deployment error on JPP 6

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16607?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-16607: ----------------------------------- Summary: Seam 2.3 Portlet deployment error on JPP 6 (was: Seam 2.3 Potlet deployment error on JPP 6) > Seam 2.3 Portlet deployment error on JPP 6 > ------------------------------------------ > > Key: JBIDE-16607 > URL: https://issues.jboss.org/browse/JBIDE-16607 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: jpp61-server-log > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16607) Seam 2.3 Portlet deployment error on JPP 6

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16607?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16607: -------------------------------------- Assignee: Snjezana Peco [~snjeza], could you please take a look? > Seam 2.3 Portlet deployment error on JPP 6 > ------------------------------------------ > > Key: JBIDE-16607 > URL: https://issues.jboss.org/browse/JBIDE-16607 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: jpp61-server-log > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16545) cannot install SpringIDE 3.4 in Central to JBT 4.2.Alpha2 (Eclipse Luna 4.4M5)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16545?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16545: ------------------------------------ New mirror created from latest nightly CI build. Tried the 3.5.0.M2 build but it was missing an IU. http://download.jboss.org/jbosstools/updates/requirements/springide/3.5.0... We don't mirror AJDT, just the org.springframework.ide.eclipse.ajdt.feature, which I assume pulls in what it needs from the Luna site (or our mirror / TP) directly. > cannot install SpringIDE 3.4 in Central to JBT 4.2.Alpha2 (Eclipse Luna 4.4M5) > ------------------------------------------------------------------------------ > > Key: JBIDE-16545 > URL: https://issues.jboss.org/browse/JBIDE-16545 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.Beta1 > > Attachments: spring-in-central.png > > > Spring IDE 3.4 depends on Eclipse Kepler, and the AJDT feature won't install to Luna: > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: Spring IDE AJDT Integration (optional) 3.4.0.201310051539-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.4.0.201310051539-RELEASE) > Missing requirement: AspectJ Development Tools Core 2.2.3.e43x-RELEASE-20130627-0800 (org.eclipse.ajdt.core 2.2.3.e43x-RELEASE-20130627-0800) requires 'bundle org.eclipse.jdt.core [3.9.0,3.9.9)' but it could not be found > Cannot satisfy dependency: > From: AspectJ Development Tools 2.2.3.e43x-RELEASE-20130627-0800 (org.eclipse.ajdt.feature.group 2.2.3.e43x-RELEASE-20130627-0800) > To: org.eclipse.ajdt.core [2.2.3.e43x-RELEASE-20130627-0800] > Cannot satisfy dependency: > From: Spring IDE AJDT Integration (optional) 3.4.0.201310051539-RELEASE (org.springframework.ide.eclipse.ajdt.feature.feature.group 3.4.0.201310051539-RELEASE) > To: org.eclipse.ajdt.feature.group 0.0.0{code} > Remediation option: > !spring-in-central.png! > Should we remove the AJDT feature from Central? -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16614) skipRevisionCheckWhenPublishing is misleading in aggregators

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-16614: -------------------------------------- Summary: skipRevisionCheckWhenPublishing is misleading in aggregators Key: JBIDE-16614 URL: https://issues.jboss.org/browse/JBIDE-16614 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: build Affects Versions: 4.2.0.Alpha2 Reporter: Mickael Istria Fix For: 4.2.0.Beta1 As the *aggregate* and devstudio-product_* are only run for good reasons (change in a component, or change in aggregation repository - category.xml and other, there is no reason why using the skipRevisionCheckWhenPublishing, which is furthermore a bit error prone and misleading (some manual builds are ignored whereas there has been changes). -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16579) Warning " Please select a Hybrid Mobile Engine " is displayed always

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16579?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16579: --------------------------------- Summary: Warning " Please select a Hybrid Mobile Engine " is displayed always (was: Warnig " Please select a Hybrid Mobile Engine " is displayed always) Original Estimate: 0 minutes Remaining Estimate: 0 minutes > Warning " Please select a Hybrid Mobile Engine " is displayed always > -------------------------------------------------------------------- > > Key: JBIDE-16579 > URL: https://issues.jboss.org/browse/JBIDE-16579 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Reporter: Vlado Pakan > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Open New Hybrid Mobile project dialog > 2. Fill proper data on first page and go to page with Cordova engines > ASSERT: Warning " Please select a Hybrid Mobile Engine " is displayed > 3. Select Cordova Engine > ERROR: Warning " Please select a Hybrid Mobile Engine " is displayed -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15109) Use static web nature for Hybrid Project Types

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15109?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15109: -------------------------------------- This does not bring the benefits we expected > Use static web nature for Hybrid Project Types > ---------------------------------------------- > > Key: JBIDE-15109 > URL: https://issues.jboss.org/browse/JBIDE-15109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.0.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Investigate the use of static web nature on hybrid mobile project types. This may at least help with some of the HTML wizards. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15109) Use static web nature for Hybrid Project Types

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15109?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-15109: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes > Use static web nature for Hybrid Project Types > ---------------------------------------------- > > Key: JBIDE-15109 > URL: https://issues.jboss.org/browse/JBIDE-15109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.0.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Investigate the use of static web nature on hybrid mobile project types. This may at least help with some of the HTML wizards. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15109) Use static web nature for Hybrid Project Types

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15109?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-15109. ---------------------------------- Resolution: Rejected > Use static web nature for Hybrid Project Types > ---------------------------------------------- > > Key: JBIDE-15109 > URL: https://issues.jboss.org/browse/JBIDE-15109 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.1.0.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Investigate the use of static web nature on hybrid mobile project types. This may at least help with some of the HTML wizards. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16257) Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16257?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-16257: -------------------------------------- The plug-in discovery wizard showing installed plugin Device after the changes. > Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-16257 > URL: https://issues.jboss.org/browse/JBIDE-16257 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Assignee: Gorkem Ercan > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > Attachments: showinstalled.png > > > In JBoss Central Software/Updates tab, can select 'show installed' check box and already installed components are shown as disabled (greyed out). > A similar feature should be added to Cordova plug-in Discovery wizard. As at the moment if you have installed a plug-in and then search for it in discovery wizard, the wizard shows nothing to inform you why is isn't listed - user has to make an assumption that it's because they have already installed it rather than say typed the wrong text in the search field. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16257) Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16257?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-16257. ---------------------------------- Resolution: Done > Cordova Plug-in Discovery wizard should have option to show already installed plug-ins as disabled > --------------------------------------------------------------------------------------------------- > > Key: JBIDE-16257 > URL: https://issues.jboss.org/browse/JBIDE-16257 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Assignee: Gorkem Ercan > Labels: new_and_noteworthy > Fix For: 4.2.0.Beta1 > > Attachments: showinstalled.png > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > In JBoss Central Software/Updates tab, can select 'show installed' check box and already installed components are shown as disabled (greyed out). > A similar feature should be added to Cordova plug-in Discovery wizard. As at the moment if you have installed a plug-in and then search for it in discovery wizard, the wizard shows nothing to inform you why is isn't listed - user has to make an assumption that it's because they have already installed it rather than say typed the wrong text in the search field. -- 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, 2 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 February 2014