Community
Participate
Working Groups
At the moment we use a custom version of the javax.activation.* classes sourced from: git://github.com/kohsuke/javax.activation.git Need to investigate how we can contribute Hudson Specific changes back to GlassFish and then revert the dependency
Reached out to Glassfish team to moot this.
Further info - actually this was subsumed into core SE - have located the right contact at Oracle and am following up.
Diffs now documented: http://wiki.eclipse.org/Hudson-ci/Planning/Library_Cleanup#JAF_Diffs
Note it appears that this is a loosly coupled dependency - i.e. No Hudson code directly imports the com.sun.activation or javax.activation packages. Therefore the probably hook point is through Hudson's use of the javax.mail package
(In reply to comment #4) > Note it appears that this is a loosly coupled dependency - i.e. No Hudson code > directly imports the com.sun.activation or javax.activation packages. > Therefore the probably hook point is through Hudson's use of the javax.mail > package I think that is correct.
OK Got to the bottom of this. Upon diffing with the latest version of JAF (1.1.1) from Java SE, there are no differences. So what we have here is essentially a backport of JAF 1.1.1 into a standalone JAR that can be used in versions of Java SE that do not include JAF. So we will only need to ship this if we want masters to be able to run on versions of Java < SE6
(In reply to comment #6) > OK Got to the bottom of this. Upon diffing with the latest version of JAF > (1.1.1) from Java SE, there are no differences. > So what we have here is essentially a backport of JAF 1.1.1 into a standalone > JAR that can be used in versions of Java SE that do not include JAF. > So we will only need to ship this if we want masters to be able to run on > versions of Java < SE6 We support only SE6 or later, so I guess we can safely remove this jar.
Done
