[JBoss JIRA] (JBIDE-15366) Create target platform from Kepler SR1 (RC) dependencies
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15366?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-15366:
----------------------------------------
Target platform branch 4.31.x created with TP 4.31.0.Alpha1-SNAPSHOT (so far, it's the same content as 4.30.6.Alpha1-SNAPSHOT but it will get changed as soon as newer dependencies for Kepler SR1 are mirrored).
Job jbosstoolstargetplatforms-matrix was updated to build 4.31.0.Alpha-SNAPSHOT.
> Create target platform from Kepler SR1 (RC) dependencies
> --------------------------------------------------------
>
> Key: JBIDE-15366
> URL: https://issues.jboss.org/browse/JBIDE-15366
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.1.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.1.Final
>
>
> Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0.
> [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1
> There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items.
> For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS.
--
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
11 years, 1 month
[JBoss JIRA] (JBDS-2707) Unexpected plugin changes between two builds of JBDS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBDS-2707?page=com.atlassian.jira.plugin.... ]
Mickael Istria resolved JBDS-2707.
----------------------------------
Resolution: Cannot Reproduce Bug
The jars seems to come from different build (they are produced by m2e project). This is probably related to a change in Target Platform.
This has no impact on usability/features. So I close this report as Cannot Reproduce.
However, let's keep an eye on such changes for next stream, in case it happens more often than expected. They are actually quite useful reports as they can hide severe changes.
> Unexpected plugin changes between two builds of JBDS
> ----------------------------------------------------
>
> Key: JBDS-2707
> URL: https://issues.jboss.org/browse/JBDS-2707
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Build
> Affects Versions: 7.0.0.CR1
> Reporter: Martin Malina
> Assignee: Mickael Istria
> Fix For: 7.1.0.Alpha1
>
>
> I was trying to compare the contents of these two installers:
> jbdevstudio-product-universal-7.0.0.GA-v20130717-1700-B362.jar
> jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar
> The only expected difference was in central. But in fact there were many differences in these two plugins:
> org.jboss.netty_3.2.5.Final-20130531-2315.jar
> com.ning.async-http-client_1.6.5.20130531-2315.jar
> I could provide instructions on how to run the comparison using the dist-diff tool that is able to spot differences in classes. But for now let's start with the probable cause.
> In build B364, both of these plugins had this additional file in them:
> eclipse.inf
> with this content:
> #Processed using Jarprocessor
> pack200.conditioned = true
> Now the question is: Why was the option used in B364, but not B362?
> And what are the consequences, if any?
--
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
11 years, 1 month