September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15484) Provide support for scaled app when tailing log files

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15484?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15484: ------------------------------------------ When inspecting the whole thing in all details we found out that the current implementation is wrong/not working. We add in the *--gears* option in Eclipse to the tail command which is wrong and has no effect. The *--gears* option in the *rhc* command line utility is consumbed by the command line utility, not the tail command that it sends to the backend(s). When using the *rhc* cmd line you're giving the *--gears* option to the rhc ruby client: {code} rhc ssh --gears 'tail -f jbosseap/logs/*'; {code} The ruby client then opens concurrent connections to all gears of the given application and concatenates the outputs to a single stream: {code:title=rhc/lib/rhc/commands/ssh.rb} if options.gears groups = rest_client.find_application_gear_groups(options.namespace, app_name) run_on_gears(command.join(' '), groups) 0 {code} {code:title=rhc/lib/rhc/ssh_helpers.rb} def run_on_gears(command, gears, opts={}, &block) debug "Executing #{command} on each of #{gears.inspect}" MultipleGearTask.new(command, gears, {:limit => options.limit, :always_prefix => options.always_prefix, :raw => options.raw}.merge(opts)).run(&block) end {code} {code:title=rhc/lib/rhc/ssh_helpers.rb} def run(&block) out = nil Net::SSH::Multi.start( :concurrent_connections => @opts[:limit], :on_error => lambda{ |server| $stderr.puts "Unable to connect to gear #{server}" } ) do |session| {code} Our implementation should do the same. It should go and get all gears and run tail on each gear, eventually having consoles for each gear. > Provide support for scaled app when tailing log files > ----------------------------------------------------- > > Key: JBIDE-15484 > URL: https://issues.jboss.org/browse/JBIDE-15484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. > The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy > See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2623: ---------------------------------- I asked Mickael: {quote} On JBDS-2623 I noticed that the new SpringIDE 3.3 site, after we fixed the metadata, does not list the no-longer-partial IU when browsed w/ the p2 browser. See attached. Is this OK (bug in the p2 browser?), or do you think there's something else we need to do in the build.xml script? https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/j... {quote} And he replied: {quote} p2-browser is pretty basic and is just a TreeViewer for an IMetadataRepository. I don't think there can be such a bug. So it seems like this IU is not part of the repository. It looks like the p2.remove.iu did work and removed the IU, but the p2.publish.featuresAndBundles probably didn't. I tend to think that it is not such a big deal since neither the TP nor Central seems to require this IU. {quote} So to verify, I did this: 1. unpack /home/nboldt/tmp/Eclipse_Bundles/eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz 2. launch Eclipse in a new workspace 3. Install JBoss Central Community feature 1.2.0.Final-v20130719-2050-B70 from http://download.jboss.org/jbosstools/updates/stable/kepler/ 4. restart when prompted 5. launch Central, search for Spring IDE connector, and install it. 6. On restart, the only console message logged is this, which seems trivial and not a problem: {code} !ENTRY org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-25 10:02:08.875 !MESSAGE Result of converting legacy STS 2.x workspace preferences to 3.x !SUBENTRY 1 org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-25 10:02:08.875 !MESSAGE Converted legacy STS plugin preferences !SUBENTRY 1 unknown 0 0 2013-09-25 10:02:08.875 !MESSAGE OK !SUBENTRY 1 org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-25 10:02:08.876 !MESSAGE Converted legacy Roo plugin state locations !SUBENTRY 1 org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-25 10:02:08.876 !MESSAGE Converted legacy STS plugin state locations {code} Therefore I think we're good here. Next step is to release this new TP at the same time we release Alpha2. > Create target platform for mirrored parts of Central / 3rd Party Extras > ----------------------------------------------------------------------- > > Key: JBDS-2623 > URL: https://issues.jboss.org/browse/JBDS-2623 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream > Affects Versions: 7.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.Alpha2, 7.1.0.Beta1 > > Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png > > > As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central. > Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files. > In future, we would: > * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org] > * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa] > * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com] > * add a whole new aggregate for old + new content -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Sande Gilda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Sande Gilda commented on JBDS-2727: ----------------------------------- [~snjeza]: I merged your commit, but I'm still not seeing the links on the right to open the line numbers. I am using JDBS 7.0.0.GA. I am on PTO starting today until next week and don't have time to look into this. I'm not sure why I'm not seeing the arrow links. > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15521) CordovaSim: need to implement SplashScreen plugin

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-15521: ----------------------------------- Summary: CordovaSim: need to implement SplashScreen plugin Key: JBIDE-15521 URL: https://issues.jboss.org/browse/JBIDE-15521 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: browsersim Reporter: Ilya Buziuk Assignee: Ilya Buziuk Fix For: 4.2.x SplashScreen API doc( http://docs.phonegap.com/en/3.0.0/cordova_splashscreen_splashscreen.md.ht... ) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2727) Cheatsheets for JBoss Central archetypes

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-2727?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-2727: ------------------------------------- I can't reproduce the issue using the master branch. There is a bug in the cheatsheet. All the commands are required which isn't correct. No one command, but org.jboss.tools.project.examples.cheatsheet.getProjectForCheatsheet should be required. I have created https://github.com/jboss-developer/jboss-eap-quickstarts/pull/636, but it is not related to "the links to line numbers for the Java classes". How did you test? > Cheatsheets for JBoss Central archetypes > ---------------------------------------- > > Key: JBDS-2727 > URL: https://issues.jboss.org/browse/JBDS-2727 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: central, requirements > Reporter: Burr Sutter > Attachments: CHEATSHEET-CONTRIBUTING.html, CHEATSHEET-CONTRIBUTING.md > > > Our archetypes should have cheatsheets when imported/opened into eclipse. > Priority > 1) HTML5 - cheatsheet should focus the end-user's attention on index.html, editable in the VPE, with the jQuery Mobile Palette, it should also describe LiveReload setup and BrowserSim > 2) Java EE Web - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should describe the JPA Member.java, the relationship between MemberController.java and index.xhtml, the purpose of MemberResourceRESTService.java and JaxRsActivator.java > Basically walk the user through the flow of events (from the UI to the backend) in the application > 3) RichFaces - cheatsheet should focus the end-user's attention on index.xhtml, editable in the VPE, with the JSF/RichFaces Palette. It should also describe resources/components/memberForm.xhtml and its use of <rich:validator/> and that tag's relationship with the JPA beanvalidations -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15499: --------------------------------------- {quote} "if some other client adds other operations, DND won't work" ...do you mean if a third client does it will break or if just we do it ? {quote} If the third client does it, our DND can break. {quote} could we just override mpc and if mpc is installed delegate to its install mechanism ? (but this is definitely starting to be a "dirty" hack :/ ) {quote} I think that isn't possible to do it without patching MPC/Eclipse. DropTraget can be registered only once on one control. {code} target = new DropTarget(Control control, int style) {code} If some plugin registers DropTarget, we can't change or remove it. We can check if a control contains a drop target, add a transfer object(s) and a drop listener (using the API described in https://bugs.eclipse.org/bugs/show_bug.cgi?id=215388). However, the MPC plugin (or some other plugin) doesn't check that. Also, nobody can check if a drop target contains valid operations. We would be able to use MPC's drop target if it used our drop target. Since that isn't the case, MPC DND will fail if our drop target is registered before MPC's target. Can be fixed within the MPC plugin. Currently, it isn't possible (without patching Eclipse) to fix the issue that happens when a drop target is registered with invalid operations. We could ignore it. In the worst case, our DND would work only in the JBoss Central editor. > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15484) Provide support for scaled app when tailing log files

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15484?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15484: --------------------------------------- [~adietish], IIRC, I had different outputs when the application was consuming multiple gears. I used a remote load tester (BlazeMeter - with a free account) to generate activity on bit of activity the application. > Provide support for scaled app when tailing log files > ----------------------------------------------------- > > Key: JBIDE-15484 > URL: https://issues.jboss.org/browse/JBIDE-15484 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.1.1.Alpha2, 4.2.0.Alpha1 > > > Seems like it's simply a matter of adding a '--gears' parameter in the ssh command when the application is scalable. > The dialog could provide a checkbox (enabled by default) to let the user choose whether she wants to grab all logs or just those on the HA-Proxy > See [~lincolnthree]'s blog post on the subject: http://ocpsoft.org/jboss/openshift-pro-tip-scaling-tail-server-logs-on-al... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15519) Clean UI and Core dependencies

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15519: ------------------------------------- Summary: Clean UI and Core dependencies Key: JBIDE-15519 URL: https://issues.jboss.org/browse/JBIDE-15519 Project: Tools (JBoss Tools) Issue Type: Task Components: livereload Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.Alpha1 Move all *.ui.* dependencies from livereload.core to livereload.ui -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15520) Clean UI and Core dependencies

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15520: ------------------------------------- Summary: Clean UI and Core dependencies Key: JBIDE-15520 URL: https://issues.jboss.org/browse/JBIDE-15520 Project: Tools (JBoss Tools) Issue Type: Task Components: livereload Affects Versions: 4.1.0.Final Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.Alpha1 Move all *.ui.* dependencies from livereload.core to livereload.ui -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15520) Clean UI and Core dependencies

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15520?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-15520: ---------------------------------- Component/s: webservices (was: livereload) > Clean UI and Core dependencies > ------------------------------ > > Key: JBIDE-15520 > URL: https://issues.jboss.org/browse/JBIDE-15520 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Alpha1 > > > Move all *.ui.* dependencies from livereload.core to livereload.ui -- 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, 9 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 September 2013