[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Assignee: Denis Golovin (was: Fred Bricon)
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Denis Golovin
> Fix For: 4.1.2.CR1
>
>
> -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
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
10 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Description:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
was:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint (the p2 remediation wizard doesn't work as I expected) to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
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
10 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Description:
-Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
-The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
was:
Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.
The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.
The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> -Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.-
> -The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.-
> Change of plans : it's way better, from a user standpoint to allow both managers to coexist, while hiding the JBoss one when there's a conflict
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
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
10 years, 3 months
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Daniel Azarov edited comment on JBIDE-16636 at 2/27/14 5:03 PM:
----------------------------------------------------------------
[~maxandersen], I faced some troubles when I tried to read Alt key:
There are two ways which I tried:
UBUNTU:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Shift keys. It does not work with Alt key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press Alt and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
WINDOWS:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Alt keys. It does not work with Shift key at all.
My suggestion is to use Ctrl.
I will investigate how Mac works with keys.
WDYT?
was (Author: dazarov):
[~maxandersen], I faced some troubles when I tried to read Alt key:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Shift keys. It does not work with Alt key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press Alt and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
My suggestion is to use Shift instead.
WDYT?
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
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
10 years, 3 months
[JBoss JIRA] (JBIDE-16649) Deactivate the Maven Profile Management if m2e 1.5 is installed
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16649?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-16649:
--------------------------------
Summary: Deactivate the Maven Profile Management if m2e 1.5 is installed (was: Restrict Maven Profile Management to m2e < 1.5)
> Deactivate the Maven Profile Management if m2e 1.5 is installed
> ---------------------------------------------------------------
>
> Key: JBIDE-16649
> URL: https://issues.jboss.org/browse/JBIDE-16649
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> Given we're going to contribute the Maven Profile Mgmt UI to m2e 1.5 (JBIDE-15836), which will be effective in JBT 4.2/JBDS 8, and given the plugins will be added to the main m2e feature, we need to prevent the current, soon-to-be-deprecated Profile UI to be installed with m2e 1.5 to prevent shortkeys/menu conflicts.
> The plan is to just add version constraints to JBoss Maven Profile Mgmt UI, so that m2e 1.5 can't be installed over it.
> The JBDS 8 installer will simply not embed the JBoss Maven Profile Mgmt UI, as the functionnality will be brought by m2e 1.5 directly.
--
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
10 years, 3 months
[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
10 years, 3 months
[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
10 years, 3 months