[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix as new connector on Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13326:
-------------------------------
Release Notes Docs Status: Not Required (was: Not Yet Documented)
> include Juno SR1+ performance fix as new connector on Central
> -------------------------------------------------------------
>
> 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
> Labels: new_and_noteworthy
> Fix For: 4.0.0.Final, 4.0.1.Final
>
> Attachments: JBIDE13226-40x.patch.txt, JBIDE13326-60x.patch.txt, JBIDE13326-JBDS-central.png, JBIDE13326-JBT-central-JavaEE.png, JBIDE13326-JBT-central.png
>
>
> 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, 1 month
[JBoss JIRA] (JBIDE-13326) include Juno SR1+ performance fix as new connector on Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13326?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-13326.
------------------------------
Labels: (was: new_and_noteworthy)
Fix Version/s: (was: 4.0.1.Final)
Resolution: Done
Because of JBIDE-13335 this will not need to be documented in 4.0.1.Final.
> include Juno SR1+ performance fix as new connector on Central
> -------------------------------------------------------------
>
> 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.0.Final
>
> Attachments: JBIDE13226-40x.patch.txt, JBIDE13326-60x.patch.txt, JBIDE13326-JBDS-central.png, JBIDE13326-JBT-central-JavaEE.png, JBIDE13326-JBT-central.png
>
>
> 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, 1 month
[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13671:
------------------------------------
[~mmalina] well, the only alternative that comes to mind is to have publishing happen as a manual step performed by leads when they decide it's time for a new build to be pushed.
So we could have:
Projects build against latest PUBLISHED integration build [in a new composite site]
Aggregates build against latest PUBLISHED integration build [in a new composite site]
Projects publish by default to staging/\{JOB_NAME\} as they do today
Projects MANUALLY copy bits from staging/\{JOB_NAME\} to integration/\{project name\} when they want the downstream consumers to get something new.
Of course the problem there is that it requires that people remember to do the publish.
> parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> 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
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
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-13696) Remove test plugins form code coverage reports
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13696?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13696:
----------------------------------------
Actually, we don't think the coverage percentage is a good way to use coverage (I got this lesson by Marc Hoffman, the author of Jacoco). The interesting metrics with coverage is the number of lines missed. With such approach, there is no reason why not putting coverage on tests.
We can keep this bug open to have continue this debate from time to time ;)
> Remove test plugins form code coverage reports
> ----------------------------------------------
>
> Key: JBIDE-13696
> URL: https://issues.jboss.org/browse/JBIDE-13696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Mickael Istria
> Priority: Optional
> Fix For: 4.1.0.Alpha2
>
>
--
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-13697) Can't install Spring from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13697?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-13697:
--------------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
Nick, I'm assigning it to you because I don't understand the reason of this issue (extras refers to the right site which contains the dependency reported as missing, and I could install it locally directly from the site).
I'm clueless...
> Can't install Spring from Central
> ---------------------------------
>
> Key: JBIDE-13697
> URL: https://issues.jboss.org/browse/JBIDE-13697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.1.0.Alpha1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Installation tests are failing on Central because of Spring:
> {code}
> Contains: Cannot complete the install because one or more required items could not be found.
> Contains: Software being installed: Spring IDE Web Flow Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.webflow.feature.feature.group 3.2.0.201301251408-M2)
> Contains: Missing requirement: Spring IDE Spring Configuration Editor (Core) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.config.core 3.2.0.201301251408-M2) requires 'bundle org.springsource.ide.eclipse.commons.core 0.0.0' but it could not be found
> Contains: Cannot satisfy dependency:
> Contains: From: Spring IDE Core (required) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.feature.feature.group 3.2.0.201301251408-M2)
> Contains: To: org.springframework.ide.eclipse.config.core [3.2.0.201301251408-M2]
> Contains: Cannot satisfy dependency:
> Contains: From: Spring IDE Web Flow Extension (optional) 3.2.0.201301251408-M2 (org.springframework.ide.eclipse.webflow.feature.feature.group 3.2.0.201301251408-M2)
> Contains: To: org.springframework.ide.eclipse.feature.feature.group 0.0.0
> {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, 1 month