[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13335:
----------------------------------
Assignee: Nick Boldt (was: Denis Golovin)
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-patched-sr2.png, JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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, 1 month
[JBoss JIRA] (JBIDE-13773) Clean-Up New Context Menu
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13773?page=com.atlassian.jira.plugi... ]
Burr Sutter updated JBIDE-13773:
--------------------------------
Description:
The New context-menu in the JBoss Perspective has too many options, several of which are not valuable to the average end-user.
Possible Removals:
- Project
- SQL File
- Annotation
- Enum
- Dynamic Web Project
- Enterprise Application Project
- JSP File
- Filter
- Listener
- Servlet
- Decorator
- Interceptor
- Example...
was:
The New context-menu in the JBoss Perspective has too many options, several of which are not valuable to the average end-user.
> Clean-Up New Context Menu
> -------------------------
>
> Key: JBIDE-13773
> URL: https://issues.jboss.org/browse/JBIDE-13773
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Burr Sutter
> Attachments: Screen Shot 2013-03-12 at 11.52.38 AM.png
>
>
> The New context-menu in the JBoss Perspective has too many options, several of which are not valuable to the average end-user.
> Possible Removals:
> - Project
> - SQL File
> - Annotation
> - Enum
> - Dynamic Web Project
> - Enterprise Application Project
> - JSP File
> - Filter
> - Listener
> - Servlet
> - Decorator
> - Interceptor
> - Example...
--
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, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13335 at 3/12/13 11:47 AM:
--------------------------------------------------------------
1. Install Eclipse Juno SR1 JEE
2. Install JBT (or just the Community Cental feature)
3. Restart, then open Central's Software/Update tab
4a. User can install the optimization patch...
*OR*
4b. Help > Check for updates and update to Juno SR2
!JBIDE13335-sr1-can-update-to-sr2.png!
(Curiously, you can then install the optimization patch onto SR2, too.)
So... putting the patch back on Central won't break anyone. But it's also no longer needed.
was (Author: nickboldt):
1. Install Eclipse Juno SR1 JEE
2. Install JBT (or just the Community Cental feature)
3. Restart, then open Central's Software/Update tab
4. User can install the optimization patch...
OR
5. Help > Check for updates and update to Juno SR2
!JBIDE13335-sr1-can-update-to-sr2.png!
(Curiously, you can then install the optimization patch onto SR2, too.)
So... putting the patch back on Central won't break anyone. But it's also no longer needed.
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-patched-sr2.png, JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13335:
-------------------------------
Attachment: JBIDE13335-patched-sr2.png
Resulting install includes both feature patches and the rcp features (with newer date stamps than the patches):
!JBIDE13335-patched-sr2.png!
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-patched-sr2.png, JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13335:
-------------------------------
Attachment: JBIDE13335-sr1-can-update-to-sr2.png
1. Install Eclipse Juno SR1 JEE
2. Install JBT (or just the Community Cental feature)
3. Restart, then open Central's Software/Update tab
4. User can install the optimization patch...
OR
5. Help > Check for updates and update to Juno SR2
!JBIDE13335-sr1-can-update-to-sr2.png!
(Curiously, you can then install the optimization patch onto SR2, too.)
So... putting the patch back on Central won't break anyone.
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13335 at 3/12/13 11:44 AM:
--------------------------------------------------------------
1. Install Eclipse Juno SR1 JEE
2. Install JBT (or just the Community Cental feature)
3. Restart, then open Central's Software/Update tab
4. User can install the optimization patch...
OR
5. Help > Check for updates and update to Juno SR2
!JBIDE13335-sr1-can-update-to-sr2.png!
(Curiously, you can then install the optimization patch onto SR2, too.)
So... putting the patch back on Central won't break anyone. But it's also no longer needed.
was (Author: nickboldt):
1. Install Eclipse Juno SR1 JEE
2. Install JBT (or just the Community Cental feature)
3. Restart, then open Central's Software/Update tab
4. User can install the optimization patch...
OR
5. Help > Check for updates and update to Juno SR2
!JBIDE13335-sr1-can-update-to-sr2.png!
(Curiously, you can then install the optimization patch onto SR2, too.)
So... putting the patch back on Central won't break anyone.
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335-sr1-can-update-to-sr2.png, JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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, 1 month
[JBoss JIRA] (JBIDE-13673) jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13673?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13673 at 3/12/13 11:37 AM:
--------------------------------------------------------------
Not sure what you mean by "in the Maven executors".
Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :)
for 40x:
{code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code}
for 41x/trunk/master:
{code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code}
was (Author: nickboldt):
Not sure what you mean by "in the Maven executors".
Anyway, I've updated the jobs in the 40x, 41x and trunk/master branches adding these to the invocation of maven. Could have added these into the MAVEN_FLAGS variable, but this is a change that happens globally anyway, not per-job, so making it harder to see in the job's configure page doesn't bother me. And not all the affected jobs use that, so this is better. :)
for 40x:
{code}-DTARGET_PLATFORM_VERSION=4.20.6.Final-SNAPSHOT -DTARGET_PLATFORM_VERSION-maximum=4.22.1.Final-SNAPSHOT{code
for 41x/trunk/master:
{code}-DTARGET_PLATFORM_VERSION=4.30.5.Alpha -DTARGET_PLATFORM_VERSION-maximum=4.30.5.Alpha{code}
> jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13673
> URL: https://issues.jboss.org/browse/JBIDE-13673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha2
>
>
> jenkins jobs for components and aggregates should set overrides for TARGET_PLATFORM_VERSION and TARGET_PLATFORM_VERSION-maximum so we ensure that builds use the correct TP regardless of their root pom's included parent pom version
--
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, 1 month