January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16124) "Add Arquillian Profiles" does nothing

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16124?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16124: --------------------------------------- The issue happens when a selected project isn't an Arquillian project. I have fixed the issue by disabling all the buttons on the Arquillian tab for that case. > "Add Arquillian Profiles" does nothing > -------------------------------------- > > Key: JBIDE-16124 > URL: https://issues.jboss.org/browse/JBIDE-16124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > -- 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-16124) "Add Arquillian Profiles" does nothing

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16124?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-16124: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 > "Add Arquillian Profiles" does nothing > -------------------------------------- > > Key: JBIDE-16124 > URL: https://issues.jboss.org/browse/JBIDE-16124 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Affects Versions: 4.1.1.CR1 > Reporter: Andre Dietisheim > Assignee: Snjezana Peco > Fix For: 4.2.0.Alpha2 > > -- 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-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Nick Boldt edited comment on JBIDE-3509 at 1/6/14 11:28 AM: ------------------------------------------------------------ [~grdryn]: The fact that there's even a partial chunk of JBoss Tools available OOTB in Fedora is awesome! Probably should have said that up front. :D When you're next looking to add more subprojects, feel free to bug me or the team leads in #jbosstools on Freenode. I might be able to find time to contribute something myself, if you can help me get started. You might also like this interdependency table / chart: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html (It's subject to change as we attempt to solve the SWT/Xulrunner/Webkit problems now facing the JBoss Tools 4.2 / Luna release.) Thanks again for contributing this to Fedora, and congrats on being employed full time. (Too bad we didn't hire you.) :D was (Author: nickboldt): When you're next looking to add more subprojects, feel free to bug me or the team leads in #jbosstools on Freenode. You might also like this: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html (subject to change as we attempt to solve the SWT/Xulrunner/Webkit problems now facing the JBoss Tools 4.2 / Luna release) > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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-3509) Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-3509?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBIDE-3509: ----------------------------------- When you're next looking to add more subprojects, feel free to bug me or the team leads in #jbosstools on Freenode. You might also like this: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html (subject to change as we attempt to solve the SWT/Xulrunner/Webkit problems now facing the JBoss Tools 4.2 / Luna release) > Monitor progress of JBT packaging as .rpm for Fedora: http://fedoraproject.org/wiki/JBoss > ----------------------------------------------------------------------------------------- > > Key: JBIDE-3509 > URL: https://issues.jboss.org/browse/JBIDE-3509 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Priority: Optional > Fix For: LATER > > Attachments: eclipse-jbosstools-openshift-in-dropins.png, eclipse-jbosstools-server.png > > > John Ford (John64 on Freenode), a college student from Seneca, has expressed interest in packaging JBT for Fedora. This is a placeholder to track that progress as it relates to the JBT 3.0.0 release, possibly as part of Fedora 11? > Details: http://fedoraproject.org/wiki/JBoss -- 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] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2669 at 1/6/14 10:55 AM: ----------------------------------------------------------- +1 to Mickael's idea. So we would therefore have one of these two: *Option A* {quote} com.jboss.jbds.product => *com.jboss.devstudio.product.plugin* com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package* {quote} *Option B* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package* {quote} Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this? *Option C* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package* {quote} was (Author: nickboldt): +1 to Mickael's idea. So we would therefore have one of these two: *Option A* {quote} com.jboss.jbds.product => *com.jboss.devstudio.product.plugin* com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package* {quote} *Option B* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package* {quote} Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package" this? *Option C* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package* {quote} > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2669 at 1/6/14 10:56 AM: ----------------------------------------------------------- +1 to Mickael's idea. Also like Denis' idea of switching to com.redhat.jbdevstudio instead of com.jboss.devstudio, but not sure if we're allowed to use a com.redhat namespace. So we would therefore have something like this: *Option A* {quote} com.jboss.jbds.product => *com.jboss.devstudio.product.plugin* com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package* {quote} *Option B* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package* {quote} Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this? *Option C* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package* {quote} [~maxandersen] [~dgolovin] [~mickael_istria] WDYT? was (Author: nickboldt): +1 to Mickael's idea. So we would therefore have one of these two: *Option A* {quote} com.jboss.jbds.product => *com.jboss.devstudio.product.plugin* com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package* {quote} *Option B* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package* {quote} Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package", like this? *Option C* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package* {quote} > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2669: ---------------------------------- +1 to Mickael's idea. So we would therefore have one of these two: *Option A* {quote} com.jboss.jbds.product => *com.jboss.devstudio.product.plugin* com.jboss.jbds.product.feature => *com.jboss.devstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.jboss.devstudio.product.package* {quote} *Option B* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.product.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.core.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.product.package* {quote} Perhaps simpler would be to drop "core" and "product" in favour of just using "plugin", "feature", and "package" this? *Option C* {quote} com.jboss.jbds.product => *com.redhat.jbdevstudio.plugin* com.jboss.jbds.product.feature => *com.redhat.jbdevstudio.feature* com.jboss.jbds.all and com.jboss.jbds.product.product => *com.redhat.jbdevstudio.package* {quote} > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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] (JBDS-2866) CordovaSim Debugger

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2866?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2866: ----------------------------------- Do you have a HD version of this video? It is hard to see the differences due to the low resolution. For instance, it would appear that you are not using the JS editors in Eclipse but some 3rd party window for JS editing. > CordovaSim Debugger > ------------------- > > Key: JBDS-2866 > URL: https://issues.jboss.org/browse/JBDS-2866 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: browsersim, requirements > Reporter: Burr Sutter > Assignee: Ilya Buziuk > Attachments: DevToolsMenu.png > > > The current FireBug Lite in CordovaSim has the following limitations: > 1) When using LiveReload, the window closes with every reload > 2) Various "page load" events with console.log statements are not visible in FireBug Lite console, like having console.log() in your deviceready > http://screencast.com/t/RRGhV9PV > Note: I forgot to add the Console Cordova plugin, not sure if that is necessary but the window closes, so not sure how I would see the message -- 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-6184) Error while adding re-deployments on EAP-5

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6184?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-6184. -------------------------------- Resolution: Done > Error while adding re-deployments on EAP-5 > ------------------------------------------ > > Key: JBIDE-6184 > URL: https://issues.jboss.org/browse/JBIDE-6184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.1.0.GA > Reporter: Libor Zoubek > Assignee: Rob Stryker > Priority: Minor > Fix For: 3.2.0.Final, 3.1.1 > > Attachments: JBIDE-6184_jbt.patch, server.log > > > Steps to reproduce: > 1. create EAR (with application.xml) > 2. create web project 1 and add it to EAR > 3. deploy EAR on EAP-5.0.GA (4.3 is not affected by this issue) > 4. Create web project 2 add add it to EAR > You should get same exception as attached in server.log > Adapter is then in bad state, clicking on Full Republish on EAR in server view does not even help to get project 2 deployed. The only way is to remove and add EAR to server -- 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-6184) Error while adding re-deployments on EAP-5

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-6184?page=com.atlassian.jira.plugin... ] Rob Stryker closed JBIDE-6184. ------------------------------ > Error while adding re-deployments on EAP-5 > ------------------------------------------ > > Key: JBIDE-6184 > URL: https://issues.jboss.org/browse/JBIDE-6184 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 3.1.0.GA > Reporter: Libor Zoubek > Assignee: Rob Stryker > Priority: Minor > Fix For: 3.1.1, 3.2.0.Final > > Attachments: JBIDE-6184_jbt.patch, server.log > > > Steps to reproduce: > 1. create EAR (with application.xml) > 2. create web project 1 and add it to EAR > 3. deploy EAR on EAP-5.0.GA (4.3 is not affected by this issue) > 4. Create web project 2 add add it to EAR > You should get same exception as attached in server.log > Adapter is then in bad state, clicking on Full Republish on EAR in server view does not even help to get project 2 deployed. The only way is to remove and add EAR to server -- 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 January 2014