April 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (TOOLSDOC-311) Review: Devs to review OpenShift Tools chapter for JBDS 7.0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-311?page=com.atlassian.jira.plug... ] Andre Dietisheim commented on TOOLSDOC-311: ------------------------------------------- *Procedure 1.3. Create a Domain* {quote} 1. In the OpenShift Explorer tab, right-click the connection and click Create or Edit Domain. {quote} The application creation wizard will prompt you for the domain name if there's none yet. You can but you dont have to get to *OpenShift Explorer* and *Create or Edit Domain*. > Review: Devs to review OpenShift Tools chapter for JBDS 7.0 > ----------------------------------------------------------- > > Key: TOOLSDOC-311 > URL: https://issues.jboss.org/browse/TOOLSDOC-311 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > > Please review the content of the OpenShift chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > The chapter has been sent to you by email as pdf. Please let me know if you would prefer an alternative format or delivery point for reviewing. > Screenshots are currently missing and will be added closer to GA. > Please give feedback as comments in this JIRA. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-311) Review: Devs to review OpenShift Tools chapter for JBDS 7.0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-311?page=com.atlassian.jira.plug... ] Andre Dietisheim commented on TOOLSDOC-311: ------------------------------------------- *1.2.6. Manage SSH Keys* {quote} In the Public Key field, type the location of the public key file or click Browse to navigate to the file {quote} You actually can't type, you can only browse. The text field for the filename is read-only. > Review: Devs to review OpenShift Tools chapter for JBDS 7.0 > ----------------------------------------------------------- > > Key: TOOLSDOC-311 > URL: https://issues.jboss.org/browse/TOOLSDOC-311 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > > Please review the content of the OpenShift chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > The chapter has been sent to you by email as pdf. Please let me know if you would prefer an alternative format or delivery point for reviewing. > Screenshots are currently missing and will be added closer to GA. > Please give feedback as comments in this JIRA. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14079) Weinre in browsersim slow/not-informative

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14079?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14079: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Component/s: browsersim > Weinre in browsersim slow/not-informative > ----------------------------------------- > > Key: JBIDE-14079 > URL: https://issues.jboss.org/browse/JBIDE-14079 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > BrowerSim weinre seems to load *very* slowly and there is just a big white dialog shown while it do so. > I initially thought it was broken but after 4-5 attempts it suddenly showed up. > Problem is users has no idea what is actually going on. > Could we: > A) show a progress monitor (even a fake one would be useful) > B) show what url the dialog is visiting (that gives a hint it is waiting) > C) have a link/info button explaining you can configure weinre in preferences > Ca) have a dialog pop up on initial start of weinre explaining it will inject weinre and go to client url X which can be configured in the preferences...and then a "Do not ask me again" checkbox for future usage. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14079) Weinre in browsersim slow/not-informative

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14079?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14079: --------------------------------------------- putting on Beta1 + fixing component. > Weinre in browsersim slow/not-informative > ----------------------------------------- > > Key: JBIDE-14079 > URL: https://issues.jboss.org/browse/JBIDE-14079 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Max Rydahl Andersen > Fix For: 4.1.0.Beta1 > > > BrowerSim weinre seems to load *very* slowly and there is just a big white dialog shown while it do so. > I initially thought it was broken but after 4-5 attempts it suddenly showed up. > Problem is users has no idea what is actually going on. > Could we: > A) show a progress monitor (even a fake one would be useful) > B) show what url the dialog is visiting (that gives a hint it is waiting) > C) have a link/info button explaining you can configure weinre in preferences > Ca) have a dialog pop up on initial start of weinre explaining it will inject weinre and go to client url X which can be configured in the preferences...and then a "Do not ask me again" checkbox for future usage. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-311) Review: Devs to review OpenShift Tools chapter for JBDS 7.0

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-311?page=com.atlassian.jira.plug... ] Andre Dietisheim commented on TOOLSDOC-311: ------------------------------------------- *Procedure 1.2. Generate and Upload SSH Keys to OpenShift* {quote} 6. In the Private Key field, type a name for the private key file. 7. In the Private Key Passphrase field, type a passphrase for use in accessing the private key. 8. In the Public Key field, type a name for the public key file. T ypically the file name of the public key is that of the private key with .pub appended. {quote} *Private Key* and *Public Key* were relabeled to *Private Key File Name* and *Public Key File Name* in JBIDE-13447 > Review: Devs to review OpenShift Tools chapter for JBDS 7.0 > ----------------------------------------------------------- > > Key: TOOLSDOC-311 > URL: https://issues.jboss.org/browse/TOOLSDOC-311 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: User Guide - OpenShift Tools > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Andre Dietisheim > > Please review the content of the OpenShift chapter from a technical viewpoint: > 1) Are features correctly documented? > 2) Are there any features that are missing? > The chapter has been sent to you by email as pdf. Please let me know if you would prefer an alternative format or delivery point for reviewing. > Screenshots are currently missing and will be added closer to GA. > Please give feedback as comments in this JIRA. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14072) Messaging for JPP 6 in JBDS plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14072?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14072: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Component/s: Portal/GateIn > Messaging for JPP 6 in JBDS plugin > ---------------------------------- > > Key: JBIDE-14072 > URL: https://issues.jboss.org/browse/JBIDE-14072 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Portal/GateIn > Affects Versions: 4.0.2.Final, 4.1.0.Beta1 > Environment: All > Reporter: Divya Mehra > Priority: Minor > Fix For: 4.1.0.Beta1 > > > Starting from GateIn 3.5/JPP 6.0, Maven quick starts would be the recommended way to bootstrap a portal project. > Older technology, for example JSF 1.2 and Rich Faces 3 portlets, would not work if deployed on GateIn 3.5/JPP 6.0 (or later versions). > It is desirable that we message prominently in the JBDS plugin for portal that the developer should use the quick starts (instead of the plugin) for deployments on GateIn 3.5/JPP 6.0 or later versions. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14072) Messaging for JPP 6 in JBDS plugin

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14072?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14072: --------------------------------------------- Wondering where in the UI we could put this - facets are not strong enough to express this kind of "mismatch". Snjezana, any suggestions ? > Messaging for JPP 6 in JBDS plugin > ---------------------------------- > > Key: JBIDE-14072 > URL: https://issues.jboss.org/browse/JBIDE-14072 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Portal/GateIn > Affects Versions: 4.0.2.Final, 4.1.0.Beta1 > Environment: All > Reporter: Divya Mehra > Priority: Minor > Fix For: 4.1.0.Beta1 > > > Starting from GateIn 3.5/JPP 6.0, Maven quick starts would be the recommended way to bootstrap a portal project. > Older technology, for example JSF 1.2 and Rich Faces 3 portlets, would not work if deployed on GateIn 3.5/JPP 6.0 (or later versions). > It is desirable that we message prominently in the JBDS plugin for portal that the developer should use the quick starts (instead of the plugin) for deployments on GateIn 3.5/JPP 6.0 or later versions. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14120) Can not debug OSGI Bundles deployed in JBoss EAP 6.1 with JBossTools 4.0.1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14120?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14120: ---------------------------------------- Fix Version/s: 4.1.x I've pinged [~thomas.diesler] to get input on this. > Can not debug OSGI Bundles deployed in JBoss EAP 6.1 with JBossTools 4.0.1 > -------------------------------------------------------------------------- > > Key: JBIDE-14120 > URL: https://issues.jboss.org/browse/JBIDE-14120 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.0.1.Final > Reporter: Thomas Wiesner > Fix For: 4.1.x > > Attachments: eclipse_juno_jboss_tools_4.0.1_osgi_debug, scr.zip, standalone.xml > > > Starting JBoss EAP 6.1 in debug mode with JBoss Tools 4.0.1 in eclipse juno runs into following exception: > [0m[0m16:54:53,618 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "de.ebcot.osgi.web.war" (runtime-name: "de.ebcot.osgi.web.war") > [0m[0m16:54:53,618 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "de.ebcot.osgi.core.jar" (runtime-name: "de.ebcot.osgi.core.jar") > [0m[0m16:54:53,777 INFO [org.jboss.osgi.framework] (MSC service thread 1-2) JBOSGI011006: OSGi Framework - 2.1.0.CR12 > [0m[31m16:54:53,789 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC00001: Failed to start service jboss.deployment.unit."de.ebcot.osgi.core.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."de.ebcot.osgi.core.jar".PARSE: JBAS018733: Failed to process phase PARSE of deployment "de.ebcot.osgi.core.jar" > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:127) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1811) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1746) [jboss-msc-1.0.4.GA.jar:1.0.4.GA] > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) [rt.jar:1.7.0_05] > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) [rt.jar:1.7.0_05] > at java.lang.Thread.run(Thread.java:722) [rt.jar:1.7.0_05] > Caused by: java.lang.NullPointerException > at org.jboss.as.osgi.service.FrameworkActivator.activate(FrameworkActivator.java:76) > at org.jboss.as.osgi.deployment.FrameworkActivateProcessor.deploy(FrameworkActivateProcessor.java:72) > at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:120) [jboss-as-server-7.2.0.Alpha1-redhat-4.jar:7.2.0.Alpha1-redhat-4] > ... 5 more > https://community.jboss.org/thread/223957?tstart=0 -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14339) The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14339?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14339: ---------------------------------------- Fix Version/s: 4.1.0.Beta1 Component/s: Webservices > The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page. > -------------------------------------------------------------------------------------------- > > Key: JBIDE-14339 > URL: https://issues.jboss.org/browse/JBIDE-14339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Mustafa Musaji > Fix For: 4.1.0.Beta1 > > Attachments: JBDS_WS_Error.png, JBDS_WS_Error_config.png > > > Using the Web Services Tools to generate client stubs etc I always seem to get the error "The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page." > See attached screen shots which shows I have it configured (correctly from what I can tell) -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14339) The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page.

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14339?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14339: --------------------------------------------- Besides the error looking wrong, NULL is for sure not expected in an error message. Should be "is empty" or something similar. > The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page. > -------------------------------------------------------------------------------------------- > > Key: JBIDE-14339 > URL: https://issues.jboss.org/browse/JBIDE-14339 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Webservices > Reporter: Mustafa Musaji > Fix For: 4.1.0.Beta1 > > Attachments: JBDS_WS_Error.png, JBDS_WS_Error_config.png > > > Using the Web Services Tools to generate client stubs etc I always seem to get the error "The JBoss WS Runtime Location is NULL. Please set the location on JBoss WS preferences page." > See attached screen shots which shows I have it configured (correctly from what I can tell) -- 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, 11 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 April 2013