February 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2904: ------------------------------ CDW qa_ack: + (was: ?) > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 7.1.1.CR1 > > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2904: ------------------------------ CDW release: + (was: ?) > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 7.1.1.CR1 > > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2904: ----------------------------- CDW devel_ack: ? (was: +) CDW pm_ack: ? (was: +) CDW qa_ack: ? (was: +) CDW release: ? (was: +) > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 7.1.1.CR1 > > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2904: ------------------------------ CDW pm_ack: + (was: ?) > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 7.1.1.CR1 > > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2904: ------------------------------ Target Release: 7.1.1.GA (was: 8.0.0.GA) > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 7.1.1.CR1 > > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-16375) Allow to extend Central extensions catalog with "Beta" stuff

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16375?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16375: ---------------------------------------- According to current discovery API, the easiest way to implement that will be to have this in the *same catalog* as all modules (code can currently handle a single catalog). At the same discovery URL, there could be a file describing the list of supported or not supported *versions*. This file could only contain the list of supported stuff, with on each line the id and version of a supported item. Everything that is not in that file could be considered as "not supported". > Allow to extend Central extensions catalog with "Beta" stuff > ------------------------------------------------------------ > > Key: JBIDE-16375 > URL: https://issues.jboss.org/browse/JBIDE-16375 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, discovery > Reporter: Mickael Istria > Fix For: 4.2.0.Beta1 > > > In order to make it easier for people to consume some "Beta" extensions from JBT or JBDS release (such as installing a Beta of JBT-IS on top of a JBT release), it would make sense to have Central allow users to select some catalogs in a UI entry such as "Include Experimental stuff" to show additional catalog entries. > Either this could be a single catalog with the experimental content being annotated, or it could be 2 (or more catalogs) which have different quality levels. > The Central UI will need to give feedback on the quality level for a given entry ("supported" or "experimental" or ...). -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2904: ------------------------------ Fix Version/s: 7.1.1.CR1 > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > Fix For: 7.1.1.CR1 > > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2904) Disable m2e indexing by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2904?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBDS-2904. ------------------------------- Assignee: Fred Bricon (was: Len DiMaggio) Resolution: Done > Disable m2e indexing by default > ------------------------------- > > Key: JBDS-2904 > URL: https://issues.jboss.org/browse/JBDS-2904 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: maven, p2-product > Affects Versions: 7.1.0.GA > Reporter: Fred Bricon > Assignee: Fred Bricon > Labels: new_and_noteworthy > > By default, m2e (<= 1.4) downloads remote nexus indexes on startup. > - expanding the nexus index is very CPU intensive > - each workspace eats up at least 500MB once m2e has started. > It can be disabled in the workspace preferences but ideally, we should disable it by default for all JBDS installation on new workspaces. > Stock Eclipse Java EE Kepler has this setting turned off by default (see plugins\org.eclipse.epp.package.jee_*\plugin_customization.ini) > m2e 1.5.0 (M6+) will turn it off by default (https://bugs.eclipse.org/bugs/show_bug.cgi?id=404417), so JBDS 8.0 will get the new setting for free. > We should just add org.eclipse.m2e.core/eclipse.m2.updateIndexes=false > to com.jboss.jbds.product\plugin_customization.ini for JBDS 7.1.1. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15290) Database Connection Usability Improvements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15290?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15290: ---------------------------------------- Sprint: Sprint to 31.03.14 > Database Connection Usability Improvements > ------------------------------------------ > > Key: JBIDE-15290 > URL: https://issues.jboss.org/browse/JBIDE-15290 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Burr Sutter > > The current end-user workflow is fairly challenging and has amble opportunities for end-user error. You can see it starting around minute 4 in this video: > https://vimeo.com/39608294 > This workflow is also used with the Forge: Entities from Tables Wizard. > Here are the current steps, starting from the Forge Wizard: > http://www.screencast.com/t/mSyhEtlwfp > http://www.screencast.com/t/pNk17S4Xk9 > http://www.screencast.com/t/MssISpUZW6 > http://www.screencast.com/t/XxkzckHdi > http://www.screencast.com/t/j5pBIE0ESBM0 > http://www.screencast.com/t/GzLvpgNv8m > http://www.screencast.com/t/6KsGhlPx > http://www.screencast.com/t/yHHPnHva > http://www.screencast.com/t/v26qYQ3Cjr > http://www.screencast.com/t/NHvDtza1 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-15290) Database Connection Usability Improvements

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15290?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15290: ---------------------------------------- Sprint: (was: Sprint to 31.03.14) > Database Connection Usability Improvements > ------------------------------------------ > > Key: JBIDE-15290 > URL: https://issues.jboss.org/browse/JBIDE-15290 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Burr Sutter > > The current end-user workflow is fairly challenging and has amble opportunities for end-user error. You can see it starting around minute 4 in this video: > https://vimeo.com/39608294 > This workflow is also used with the Forge: Entities from Tables Wizard. > Here are the current steps, starting from the Forge Wizard: > http://www.screencast.com/t/mSyhEtlwfp > http://www.screencast.com/t/pNk17S4Xk9 > http://www.screencast.com/t/MssISpUZW6 > http://www.screencast.com/t/XxkzckHdi > http://www.screencast.com/t/j5pBIE0ESBM0 > http://www.screencast.com/t/GzLvpgNv8m > http://www.screencast.com/t/6KsGhlPx > http://www.screencast.com/t/yHHPnHva > http://www.screencast.com/t/v26qYQ3Cjr > http://www.screencast.com/t/NHvDtza1 -- 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, 1 month

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