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

Bug 345043

Summary:	Add a source bundle to javax.activation 1.1.0
Product:	[Tools] Orbit	Reporter:	Hugues Malphettes <hmalphettes>
Component:	bundles	Assignee:	Hugues Malphettes <hmalphettes>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	david_williams
Version:	unspecified
Target Milestone:	Indigo RC1
Hardware:	All
OS:	All
Whiteboard:

Description Hugues Malphettes

2011-05-06 20:07:19 EDT

javax.activation 1.1.0 was packaged ages ago and there is no source bundle for it.

I have found myself manually making a source bundle, loosing it and making it again more than once.
I would like to provide it from orbit once and for all.

The original CQ is CQ-260 and it is tagged with sourceandbinary.
The PB CQ is no different than the other CQs so I think we are clear IP wise to package the source bundle.

I volunteer to do this if I get a green light from the PMC.

Comment 1 Hugues Malphettes

2011-05-06 20:08:25 EDT

The original CQ is in fact CQ-2060.

Comment 2 David Williams

2011-05-06 23:50:21 EDT

I agree, the original CQ covers 'source'. And, yes, you can take that as your PMC approval. :) 

And as original "committer" for javax.activation, you have my approval to add the source-bundle. (I'm sure you've noticed it is the Geronimo version, specifically). 

Now ... as Project Lead ... it's always something :) ... I'd question if this was an "RC level issue". I guess if you get it in by RC1 deadline (that's today, Saturday, 5/7) no one would complain ... but, I think after that, it'd start to be questionable. Not really a "bug", more an enhancement. And, as I've said in other cases, you could check into cvs anytime, but ... imagine if there was no other contributions to, say, RC2 ... then would this one thing be worth asking everyone to update their build scripts/URLs? 

I'm know you understand and are sensitive to these stability/rampdown issues, so I'm fine leaving final decision up to you -- but you might ask others if you have any doubts about right direction for any particular RC. 

Thanks,

Comment 3 Hugues Malphettes

2011-05-07 00:15:57 EDT

Thanks David for the fast reply.

I am doing this at the very last acceptable minute regarding the release train.
I am giving it a shot now then.

Comment 4 Hugues Malphettes

2011-05-07 00:40:57 EDT

Edited as an enhancement: certainly not a bug indeed.
Watching the cruisecontrol dashboard and hopefully this will be marked as fixed in 90 minutes.

Comment 5 Hugues Malphettes

2011-05-07 02:24:44 EDT

I believe it is fixed:
The build is green and I can download it:
http://download.eclipse.org/tools/orbit/committers/drops/I20110507043747/repository/plugins/javax.activation.source_1.1.0.v201105071233.jar

However at the moment when I browse to http://download.eclipse.org/tools/orbit/committers/drops/I20110507043747 I get an HTTP 500.

Comment 6 David Williams

2011-05-07 10:38:56 EDT

> However at the moment when I browse to
> http://download.eclipse.org/tools/orbit/committers/drops/I20110507043747 I get
> an HTTP 500.

Kind of strange, I tried to debug this, on download and build server, everything seemed ok ... but in the course of all that I effectively "touched" the index.php file ... and then it seemed to display just fine! So ... there might still be something amiss with infrastructure (or, our "upload" scripts?) ... but, I'd say if you proof read that download page now, and if it looks ok, then I'd say you are good to go. And we'll just see if it happens again (next build) before doing more about scripts or infrastructure.

Comment 7 David Williams

2011-05-07 13:17:16 EDT

The next build did go fine (that is, its download page displayed just fine) ... we we'll write off the glitch as due to sunspots or something ... maybe some dates/time "crossed midnight" or something? 

Thanks so much Hughes.