Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364988

Summary:	Migrate from Hudson Special version of JavaBeans Activation Framework
Product:	[Technology] Hudson	Reporter:	Duncan Mills <duncan.r.mills>
Component:	Core	Assignee:	Duncan Mills <duncan.r.mills>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	P3	CC:	winston.prakash
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Duncan Mills

2011-11-28 12:53:52 EST

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

Comment 1 Duncan Mills

2011-11-28 12:55:09 EST

Reached out to Glassfish team to moot this.

Comment 2 Duncan Mills

2011-11-29 03:00:04 EST

Further info - actually this was subsumed into core SE - have located the right contact at Oracle and am following up.

Comment 3 Duncan Mills

2011-11-29 07:02:15 EST

Diffs now documented:
http://wiki.eclipse.org/Hudson-ci/Planning/Library_Cleanup#JAF_Diffs

Comment 4 Duncan Mills

2011-11-29 08:38:32 EST

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

Comment 5 Winston Prakash

2011-11-29 12:09:17 EST

(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.

Comment 6 Duncan Mills

2011-12-01 07:49:49 EST

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

Comment 7 Winston Prakash

2011-12-01 17:12:21 EST

(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.

Comment 8 Winston Prakash

2013-02-04 21:17:14 EST

Done