[
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