February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2951) Eclipse Documentation and Context Help

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2951?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2951: -------------------------------- Summary: Eclipse Documentation and Context Help (was: What should do to provide User Documentation in eclipse format and configure context help in eclipse UI where it is possible) > Eclipse Documentation and Context Help > -------------------------------------- > > Key: JBDS-2951 > URL: https://issues.jboss.org/browse/JBDS-2951 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: documentation > Reporter: Denis Golovin > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2951) What should do to provide User Documentation in eclipse format and configure context help in eclipse UI where it is possible

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2951?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2951: -------------------------------- Epic Name: Eclipse Documentation and Context Help (was: User Documentation and Eclipse Context Help) > What should do to provide User Documentation in eclipse format and configure context help in eclipse UI where it is possible > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2951 > URL: https://issues.jboss.org/browse/JBDS-2951 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: documentation > Reporter: Denis Golovin > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2951) What should do to provide User Documentation in eclipse format and configure context help in eclipse UI where it is possible

by Denis Golovin (JIRA)

Denis Golovin created JBDS-2951: ----------------------------------- Summary: What should do to provide User Documentation in eclipse format and configure context help in eclipse UI where it is possible Key: JBDS-2951 URL: https://issues.jboss.org/browse/JBDS-2951 Project: Developer Studio (JBoss Developer Studio) Issue Type: Epic Security Level: Public (Everyone can see) Components: documentation Reporter: Denis Golovin -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15635) Null Pointer when code assumes runtime type cannot be null

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-15635: -------------------------------------- Also consider https://bugs.eclipse.org/bugs/show_bug.cgi?id=427598 for this one > Null Pointer when code assumes runtime type cannot be null > ---------------------------------------------------------- > > Key: JBIDE-15635 > URL: https://issues.jboss.org/browse/JBIDE-15635 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Mac OSX 10.8.5 > Oracle JDK 1.7.0_40 > JBoss Developer Studio > Version: 7.0.1.GA > Build id: GA-v20130930-2238-B7 > Build date: 20130930-2238 > Reporter: Cojan van Ballegooijen > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png > > > - Installed JBoss Developer 7.0.0GA using > - Upgraded to 7.0.1GA > - Starting JBoss Developer Studio shows the following error window > An internal error occurred during: "Refreshing JBoss Tutorials...". > java.lang.NullPointerException > - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet" > - Starting a new Java EE Web project results in the following error > An error has occurred. See error log for more details. > java.lang.NullPointerException > No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files. > Found .log in ~/workspace/.metadata > !SESSION 2013-10-08 16:14:47.792 ----------------------------------------------- > eclipse.buildId=unknown > java.version=1.7.0_40 > java.vendor=Oracle Corporation > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation > !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252 > !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences > !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation. > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for ALT+COMMAND+Z: > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean, > Open CDI Named Bean, > Category(org.eclipse.ui.category.navigate,Navigate,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(ALT+COMMAND+Z, > ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu, > Shows the Surround With quick menu, > Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626 > !MESSAGE A conflict occurred for COMMAND+SHIFT+F10: > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service, > Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class., > Category(org.eclipse.ui.category.file,File,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,,system) > Binding(COMMAND+SHIFT+F10, > ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu, > Show the system menu, > Category(org.eclipse.ui.category.window,Window,null,true), > org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026, > ,,true),null), > org.eclipse.ui.defaultAcceleratorConfiguration, > org.eclipse.ui.contexts.window,,cocoa,system) > !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413 > !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...". > !STACK 0 > java.lang.NullPointerException > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158) > at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:248) > at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130) > at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796) > at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16606) New Server Wizard updated for 'profiles'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16606: ------------------------------------- While your idea is absolutely awesome, there is unfortunately no way at all for us to change this page of the wizard. It is completely controlled by upstream code and the wizard is not extendable except by adding pages. > New Server Wizard updated for 'profiles' > ---------------------------------------- > > Key: JBIDE-16606 > URL: https://issues.jboss.org/browse/JBIDE-16606 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Beta1 > > Attachments: new-new-server.png, new_server.jpg, new_server_remote.jpg > > > With the additions of server profiles, servers in the rse profile (or others) do not necessarily require a local runtime. This means in a new server wizard, we don't need to force the user to create a runtime until they're in a profile that requires one. > This will make changes to the new server wizard workflow which may affect some swt bot tests and documentation -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-245) Please update JBTIS TP dependencies to Luna Alpha1

by Kevin Conner (JIRA)

[ https://issues.jboss.org/browse/JBTIS-245?page=com.atlassian.jira.plugin.... ] Kevin Conner commented on JBTIS-245: ------------------------------------ It is very unlikely that FSW would have committed last year to update our plugins for the Alpha build as any work would have to be agreed within the context of expected deliverables. The work for upcoming platform releases will invariably take precedence over work for new JBDS releases as we have a small team. > Please update JBTIS TP dependencies to Luna Alpha1 > -------------------------------------------------- > > Key: JBTIS-245 > URL: https://issues.jboss.org/browse/JBTIS-245 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: BPEL, drools/ jBPM, ESB, Fuse IDE, modeshape, savara, switchyard, teiid > Affects Versions: 4.2.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > > Greetings - welcome to Luna! > An Alpha1 version of the Eclipse Luna based JBTIS TP is now available in nexus [1]. It's also available here [2] and an integration build of the current Luna JBTIS is available here [3]. > I'm still working on dates but if we could get a first cut at the scope involved with upgrading that would help planning this thing immensely. There is SpringIDE and graphiti changes among others. > Thanks! > [1] https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... > [2] http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.0.Al... > [3] http://download.jboss.org/jbosstools/updates/integration/luna/integration... -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16659) Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure

by Vineet Reynolds (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16659?page=com.atlassian.jira.plugi... ] Vineet Reynolds commented on JBIDE-16659: ----------------------------------------- I agree with what you've said in principle - having the generated ADT/XCode projects in the platforms subdirectory makes it somewhat redundant, but the underlying rationale for this request was not so clear. It was to support deployment of HMT projects in a CI build; Cordova CLI is an easy and known way to make these deployments. We might able to get rid of the requirement on the 'platforms' sub-directory if this location is customizable, but it does not appear to be currently: https://github.com/apache/cordova-cli/blob/master/src/platform.js#L243. Also, if it can be done via other means from the command-line (and hence also from a CI server job), we might be able to offer an alternative. I'll defer to [~kpiwko] to emphasize whether we should/must support Cordova CLI for CI jobs, or whether an alternative could be found. I suspect it's going to be the former. > Create 'platforms' and 'merges' sub-directories in the Hybrid Mobile project structure > -------------------------------------------------------------------------------------- > > Key: JBIDE-16659 > URL: https://issues.jboss.org/browse/JBIDE-16659 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid > Affects Versions: 4.1.1.Final > Reporter: Vineet Reynolds > Fix For: 4.2.x > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Currently the Hybrid Mobile project structure is very nearly similar to the project structure created by the Cordova CLI. It simply lacks the {{platforms}} and {{merges}} sub-directories. > When attempting to use the Cordova CLI, the {{platforms}} directory needs to be created at the very least, followed by execution of the {{cordova platform add android}} or {{cordova platform add ios}} CLI commands. This eventually sets up the native SDK projects that can be built with ADT or XCode. > We should attempt to create a {{platforms}} sub-dir so that the hybrid mobile project is compatible with Cordova CLI. Additionally, if possible (due to the presence of a nested ADT sub-project), we should try and use the {{platforms}} directory as the default export location of the created native projects. This would ensure that exporting of the project in Eclipse is more or less equivalent to the {{cordova platform add android}} + {{cordova prepare android}} or {{cordova platform add ios}} + {{cordova prepare ios}} group of commands that create the native SDK projects and update their contents. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-2913: ----------------------------------- [~rob.stryker], can you check that one and see if we can cram into 7.1.1? > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2913) Console log when running EAP 6.2.x not formatted correctly

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2913?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2913: ------------------------------ Assignee: Rob Stryker (was: Max Rydahl Andersen) > Console log when running EAP 6.2.x not formatted correctly > ---------------------------------------------------------- > > Key: JBDS-2913 > URL: https://issues.jboss.org/browse/JBDS-2913 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: server > Affects Versions: 7.1.0.GA > Reporter: Mustafa Musaji > Assignee: Rob Stryker > Attachments: EAP-6.1.0.png, EAP-6.2.1.png > > > When running EAP from JBDS the console logging shows strange characters from the logging. See screen shots comparing EAP 6.1.0 to EAP 6.2.1 (this also happens on EAP 6.2.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16583) Disable Apply button when incorrect avd is selected in Run Configurations

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16583?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-16583: --------------------------------- Original Estimate: 0 minutes Remaining Estimate: 0 minutes Issue Type: Bug (was: Feature Request) > Disable Apply button when incorrect avd is selected in Run Configurations > ------------------------------------------------------------------------- > > Key: JBIDE-16583 > URL: https://issues.jboss.org/browse/JBIDE-16583 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.2.0.Alpha2 > Environment: JBT 4.2.0.Alpha2-v20140212-1651-B82 > Reporter: Vlado Pakan > Priority: Minor > Fix For: 4.2.0.Beta1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > 1. Create Hybrid Mobile project. > 2. Define AVD with API level lower than 17 > 3. Define another AVD with API level 17+ > 4. Run Project on Android Emulator > 5. Open Run Configurations of this project > 6. Select AVD with level lower than 17 > ASSERT: Warning is displayed "Selected AVD does not satisfy the minimum required API level. Please select a different one" > ERROR: Button Apply is enabled I think would be nice to have it disabled -- 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, 3 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