[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 12/21/12 1:55 AM:
--------------------------------------------------------------
Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless.
We could, however, branch the jbosstools-build repo every time there's a new TP definition created, and put that new definition into a separate branch.
BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix.
Still waiting on a +1 to proceed.
was (Author: nickboldt):
Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless.
BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix.
Still waiting on a +1 to proceed.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 7 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 12/21/12 1:56 AM:
--------------------------------------------------------------
Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless.
We could, however, BRANCH the jbosstools-build repo every time there's a new TP definition created, and put that new definition into a separate branch. Or we could simply TAG after each TP is defined, built, and deployed to nexus.
BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix.
Still waiting on a +1 to proceed.
was (Author: nickboldt):
Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless.
We could, however, branch the jbosstools-build repo every time there's a new TP definition created, and put that new definition into a separate branch.
BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix.
Still waiting on a +1 to proceed.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 7 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13232:
------------------------------------
Multiple git repos was never suggested. [~mickael_istria] suggested we move target-platforms/ to its own github repo, but if we did that then jbosstools-build would only have 2 files in it - parent/pom.xml and the checkout.sh script. So... that seems pointless.
BTW, [~maxandersen] when you edited my proposal to cut down the Maven/POM Path lines, you omitted the fact that we moved from snapshots/ to public-jboss/, since the goal here is also to drop the -SNAPSHOT suffix.
Still waiting on a +1 to proceed.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 7 months
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen edited comment on JBIDE-13232 at 12/21/12 1:44 AM:
-----------------------------------------------------------------------
(Edited by Max to have the repo path only show the relevant parts)
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml, multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml, jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml, jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Maven/POM Path:*
*JBT 4.0 (current):*
{code}
<repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.0.c-SNAPSHOT/
<repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.0.c-SNAPSHOT/
<repo>/org/jboss/tools/target-platforms/jbosstools/multiple/4.2.1.a-SNAPSHOT/
<repo>/org/jboss/tools/target-platforms/jbosstools/unified/4.2.1.a-SNAPSHOT/
{code}
*JBT 4.1 (proposed):*
{code}
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.430.0
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.430.0
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-with-sources/1.431.0
<repo>/org/jboss/tools/target-platforms/jbosstools-tp-no-sources/1.431.0
{code}
{quote}
was (Author: nickboldt):
Here's my proposal:
{quote}
* *Path:*
*JBT 4.0 (current):*
{code}
jbosstools-build/target-platforms/
jbdevstudio-{4.2.0.c,4.2.1.a}/
jbosstools-{4.2.0.c,4.2.1.a}/
pom.xml
multiple/pom.xml, multiple.target
unified/pom.xml
{code}
*JBT 4.1 (proposed):*
{code}
jbosstools-build/target-platforms/
{minimum,maximum}/
pom.xml
jbosstools-tp-with-sources/pom.xml, jbosstools-tp-with-sources.target
jbosstools-tp-no-sources/pom.xml
jbdevstudio-tp-with-sources/pom.xml, jbdevstudio-tp-with-sources.target
jbdevstudio-tp-no-sources/pom.xml
{code}
* *Pom version:*
*JBT 4.0 (current):*
{code}
root: 4.1.0.Alpha1-SNAPSHOT (used to be tied to parent pom version, then later just the same version)
minimums: 4.2.0-SNAPSHOT, 4.2.0.a-SNAPSHOT, 4.2.0.b-SNAPSHOT, 4.2.0.c-SNAPSHOT
maximums: 4.2.1.a-SNAPSHOT, 4.2.1-SNAPSHOT
{code}
*JBT 4.1 (proposed):*
{code}
root: 4.1.0-SNAPSHOT (not published, shouldn't have to increment it unless testing new version of Tycho or adding new profiles?)
minimum: 1.430.0, 1.430.1, ... (note that SNAPSHOT is dropped)
maximum (after July release): 1.431.0, 1.431.1, ... (note that SNAPSHOT is dropped)
{code}
* *Pom Params:*
*JBT 4.0 (current):*
{code}
<name>jbosstools Multiple (Composite) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>multiple</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
<name>jbosstools Unified (Aggregate) Target Platform 4.2.1.a</name>
<groupId>org.jboss.tools.target-platforms.jbosstools</groupId>
<artifactId>unified</artifactId>
<version>4.2.1.a-SNAPSHOT</version>
{code}
*JBT 4.1 (proposed):*
{code}
<name>JBoss Tools Target Platform - Multiple URLs With Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-with-sources</artifactId>
<version>1.430.0</version>
<name>JBoss Tools Target Platform - Unified URL Without Sources</name>
<groupId>org.jboss.tools.target-platforms</groupId> (drops the ".jbosstools" segment)
<artifactId>jbosstools-tp-no-sources</artifactId>
<version>1.430.0</version>
{code}
* *.target file name attribute:*
*JBT 4.0 (current):*
{code}
<target name="jbosstools-4.2.1.a">
<target name="jbdevstudio-4.2.1.a">
{code}
*JBT 4.1 (proposed):*
{code}
<target name="jbosstools-tp-with-sources-1.430.0">
<target name="jbdevstudio-tp-with-sources-1.430.0">
{code}
* *Nexus Path:*
*JBT 4.0 (current):*
{code}
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
{code}
*JBT 4.1 (proposed):*
{code}
https://repository.jboss.org/nexus/content/repositories/public-jboss/org/...
https://repository.jboss.org/nexus/content/repositories/public-jboss/org/...
https://repository.jboss.org/nexus/content/repositories/public-jboss/org/...
https://repository.jboss.org/nexus/content/repositories/public-jboss/org/...
{code}
{quote}
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 7 months
[JBoss JIRA] (JBDS-2365) ESB projects cannot be deployed using Server Add/Remove
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2365:
-------------------------------------------
Nick, this issue was fixed in JBDS 6.0 for ESB 4.11 - why do you want to reopen it ?
> ESB projects cannot be deployed using Server Add/Remove
> -------------------------------------------------------
>
> Key: JBDS-2365
> URL: https://issues.jboss.org/browse/JBDS-2365
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Jeremy Davis
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 6.0.0.CR1, 6.0.1.GA
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years, 7 months
[JBoss JIRA] (JBDS-2394) CLONE - ESB projects cannot be deployed using Server Add/Remove
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2394?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2394:
-------------------------------------------
nick - adding 4.12 to the end of this list solves nothing does it ? The one that need to recognize it is the esb tooling.
> CLONE - ESB projects cannot be deployed using Server Add/Remove
> ---------------------------------------------------------------
>
> Key: JBDS-2394
> URL: https://issues.jboss.org/browse/JBDS-2394
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: SOA Tooling / Platform
> Affects Versions: 5.0.0.GA-SOA
> Environment: Fedora, jdk7
> Reporter: Rob Stryker
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 5.0.2.GA
>
> Attachments: JBDS2394-add-4.12.patch.txt, JBDS2394.patch-with-5-lines-changed-in-plugin.xml-and-all-feature-and-plugin-manifests-and-poms-upversioned-to-2.3.2.txt, JBDS2394.patch.txt
>
>
> * Create a new server runtime for SOA-P 5.3
> -- Preferences -> Server -> Runtime Environments
> * Create a new ESB project with the defaults
> * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification.
> The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove."
--
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
13 years, 7 months
[JBoss JIRA] (JBIDE-13209) Need to add ESB 4.12 option with constraints
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13209?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen reassigned JBIDE-13209:
-------------------------------------------
Assignee: Brian Fitzpatrick (was: Rob Stryker)
Nick - "fixing" it in AS tools has little to zero value since when ESB 4.13 comes out we got the same problem and the whole current need for knowing the diff between 4.10 and 4.11 is about xsd name differences.
Brian - can't we fix ESB detection to not complain about the version number match *exactly* and as long as it is 4.x we just take the highest known version ? Yes - this won't make the wizard put in the latest greatest XSD but at least it will work for new version (assuming XSD are backwards compatible which I assume they are) and users can easily (just like they do today when updating) set the proper XSD if need be.
Tom - do you see any problems of making the ESB tooling just assume ESB 4.11 schema/names are ok for any future ESB 4.x+ releases so we avoid this need for constant adding specific version numbers for every minor release ?
(p.s. we can of course still go and add additional versions support when we are doing an esb tooling release but just trying to avoid *forcing* a release of esb tooling just to support a minor update)
> Need to add ESB 4.12 option with constraints
> --------------------------------------------
>
> Key: JBIDE-13209
> URL: https://issues.jboss.org/browse/JBIDE-13209
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: esb
> Reporter: Tom Cunningham
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.0.Alpha1
>
>
> SOA-P 5.3.1 is coming out soon and will require an ESB "4.12" option to be added to the ESB versions.
> Additionally, it may or may not have a new jUDDI version, which would require a different constraint to verify the AS has ESB 4.12 - or a removal of the constraints altogether.
--
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
13 years, 7 months
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13326:
------------------------------------
Mirror created: http://download.jboss.org/jbosstools/updates/requirements/eclipse/4.2.1.v...
[~maxandersen], [~dgolovin], [~mickael_istria]... should we add the org.eclipse.ui.juno.feature to Central as a new connector / optional installable into JBT and JBDS?
If so, no respin for 6.0.1 will be needed.
If we also want to tweak the eclipse.ini / jbdevstudio.ini files as noted above (via p2.inf instructions) we will need to rebuild Central (1.1.1), JBT (4.0.1), and JBDS (6.0.1).
If we also want to tweak the installer to include these patches OOTB, we will need to rebuild JBDS (6.0.1).
---
What would you like to see done here?
> include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.0.1.Final
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {code}
--
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
13 years, 7 months
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13326 at 12/21/12 12:44 AM:
---------------------------------------------------------------
Mirror created: http://download.jboss.org/jbosstools/updates/requirements/eclipse/4.2.1.v...
[~maxandersen], [~dgolovin], [~mickael_istria]... should we add the org.eclipse.ui.juno.feature to Central as a new connector / optional installable into JBT and JBDS?
If so, *no respin for 6.0.1 will be needed*.
---
If we also want to tweak the eclipse.ini / jbdevstudio.ini files as noted above (via p2.inf instructions) we will need to rebuild Central (1.1.1), JBT (4.0.1), and JBDS (6.0.1).
If we also want to tweak the installer to include these patches OOTB, we will need to rebuild JBDS (6.0.1).
---
What would you like to see done here?
was (Author: nickboldt):
Mirror created: http://download.jboss.org/jbosstools/updates/requirements/eclipse/4.2.1.v...
[~maxandersen], [~dgolovin], [~mickael_istria]... should we add the org.eclipse.ui.juno.feature to Central as a new connector / optional installable into JBT and JBDS?
If so, no respin for 6.0.1 will be needed.
If we also want to tweak the eclipse.ini / jbdevstudio.ini files as noted above (via p2.inf instructions) we will need to rebuild Central (1.1.1), JBT (4.0.1), and JBDS (6.0.1).
If we also want to tweak the installer to include these patches OOTB, we will need to rebuild JBDS (6.0.1).
---
What would you like to see done here?
> include Juno SR1+ performance fix in target platform? new connector on Central? In Installer?
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-13326
> URL: https://issues.jboss.org/browse/JBIDE-13326
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, target-platform, updatesite
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.0.1.Final
>
>
> Info: https://bugs.eclipse.org/bugs/show_bug.cgi?id=385272, http://wiki.eclipse.org/Platform_UI/Juno_Performance_Investigation
> Update Site: http://download.eclipse.org/eclipse/updates/4.2 --> Eclipse UI Juno SR1 Optimizations should be installed
> For Juno SR2 maintenance builds >= Nov 21, patch feature not needed.
> We could also consider setting these vmargs when installing JBT (community cental feature?) and/or JBDS BYOE:
> {code}
> -Xmn128m
> -Xms1024m
> -Xmx1024m
> -Xss2m
> -XX:PermSize=256m
> -XX:MaxPermSize=384m
> {code}
--
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
13 years, 7 months