[JBoss JIRA] (JBIDE-18005) Disable automatic Portlet configuration via pom property
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18005?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18005:
--------------------------------
Description:
add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
an xml template should be made available for ctrl+space in the properties section. See
was:add support for <m2e.cdi.activation>false</m2e.cdi.activation> to prevent automatic CDI configuration (Or force it if workspace preference has it disabled)
> Disable automatic Portlet configuration via pom property
> --------------------------------------------------------
>
> Key: JBIDE-18005
> URL: https://issues.jboss.org/browse/JBIDE-18005
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.CR1
>
>
> add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
> an xml template should be made available for ctrl+space in the properties section. See
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18005) Disable automatic Portlet configuration via pom property
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18005?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18005:
--------------------------------
Description:
add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
an xml template should be made available for ctrl+space in the properties section. See JBIDE-17885
was:
add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
an xml template should be made available for ctrl+space in the properties section. See
> Disable automatic Portlet configuration via pom property
> --------------------------------------------------------
>
> Key: JBIDE-18005
> URL: https://issues.jboss.org/browse/JBIDE-18005
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.CR1
>
>
> add support for <m2e.portlet.activation>false</m2e.portlet.activation> to prevent automatic Portlet configuration (Or force it if workspace preference has it disabled)
> an xml template should be made available for ctrl+space in the properties section. See JBIDE-17885
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18005) Disable automatic Portlet configuration via pom property
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18005?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18005:
--------------------------------
Release Notes Text: (was: The CDI project configurator for m2e now supports the <m2e.cdi.activation> property in the <properties> section of pom.xml. Expected values are true/false and override the workspace-wide preference found under Preferences > JBoss Tools > JBoss Maven Integration > CDI Facet
The pom.xml editor also provides a <m2e.cdi.activation>false</m2e.cdi.activation> template when doing ctrl+space in the <properties> section)
> Disable automatic Portlet configuration via pom property
> --------------------------------------------------------
>
> Key: JBIDE-18005
> URL: https://issues.jboss.org/browse/JBIDE-18005
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.2.0.CR1
>
>
> add support for <m2e.cdi.activation>false</m2e.cdi.activation> to prevent automatic CDI configuration (Or force it if workspace preference has it disabled)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18005) Disable automatic Portlet configuration via pom property
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-18005:
-----------------------------------
Summary: Disable automatic Portlet configuration via pom property
Key: JBIDE-18005
URL: https://issues.jboss.org/browse/JBIDE-18005
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: maven
Affects Versions: 4.2.0.Beta3
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.2.0.Beta3
add support for <m2e.cdi.activation>false</m2e.cdi.activation> to prevent automatic CDI configuration (Or force it if workspace preference has it disabled)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-17990:
-----------------------------------
Assignee: Snjezana Peco (was: Fred Bricon)
assigning to [~snjeza] for investigation, while I'm away
> Organize imports does not work for Maven dependencies
> -----------------------------------------------------
>
> Key: JBIDE-17990
> URL: https://issues.jboss.org/browse/JBIDE-17990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Environment: Oracle JDK 1.8.0_05, Eclipse Luna
> Reporter: Harald Wellmann
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
>
> After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN.
> The corresponding Quick Fix is also broken.
> It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository.
> This is even worse than JBIDE-17724, I'll have to revert to Beta2.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-18001) Consider using a more pale shade of yellow to identify Early Access content in JBoss Central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18001?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18001:
--------------------------------
Assignee: Mickael Istria
> Consider using a more pale shade of yellow to identify Early Access content in JBoss Central
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-18001
> URL: https://issues.jboss.org/browse/JBIDE-18001
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central, discovery
> Affects Versions: 4.2.0.Beta3
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.2.0.CR1
>
>
> From [~maxandersen] (sic):
> {quote}
> (2014-07-30 09:43:42) maxandersen: nickboldt1: yes but having a paler yellow actually sounds like better than what is there now
> (2014-07-30 09:47:42) maxandersen: nickboldt1: suggestions to make the bigy ellow we got now very welcome. thus yes if we dont have a jira for better suggestion for this alrady
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-17990:
-------------------------------------
have you tried maven > update project?
> Organize imports does not work for Maven dependencies
> -----------------------------------------------------
>
> Key: JBIDE-17990
> URL: https://issues.jboss.org/browse/JBIDE-17990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.2.0.Beta3
> Environment: Oracle JDK 1.8.0_05, Eclipse Luna
> Reporter: Harald Wellmann
> Assignee: Fred Bricon
> Fix For: 4.2.0.CR1
>
>
> After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN.
> The corresponding Quick Fix is also broken.
> It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository.
> This is even worse than JBIDE-17724, I'll have to revert to Beta2.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months