Bug 272403 - Support running headless JUnit tests from Update zip
Summary: Support running headless JUnit tests from Update zip
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Dash Athena (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: Common Build Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 271549 (view as bug list)
Depends on:
Blocks: 237588
  Show dependency tree
 
Reported: 2009-04-15 18:10 EDT by Nick Boldt CLA
Modified: 2012-01-30 11:32 EST (History)
1 user (show)

See Also:

Attachments
Patch to support using update/master instead of sdk when running tests (25.79 KB, patch)
2009-04-20 18:27 EDT, Nick Boldt CLA 		no flags Details | Diff
mylyn/context/zip (25.13 KB, application/octet-stream)
2009-04-20 18:27 EDT, Nick Boldt CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Boldt CLA 2009-04-15 18:10:09 EDT 
For builds which only need to produce an update site (zipped or not), the JUnit tests should be able to run from that zip, rather than needing the exploded/installed format of an SDK or runtime zip. 

This would mean that builds such as Linux Tools, VE, and Nebula need not produce SDKs at all, as they have no historical need to create those when a packed, archived update site + unpacked one published provides both online and offline installation.
Comment 1 Nick Boldt CLA 2009-04-20 18:27:40 EDT 
Created attachment 132517 [details]
Patch to support using update/master instead of sdk when running tests
Comment 2 Nick Boldt CLA 2009-04-20 18:27:45 EDT 
Created attachment 132518 [details]
mylyn/context/zip
Comment 3 Nick Boldt CLA 2009-04-21 15:04:31 EDT 
You can now run a build w/o the buildZips build.step, as tests can be run from the output of the buildUpdate step.

Closing.
Comment 4 Nick Boldt CLA 2009-04-21 20:10:45 EDT 
*** Bug 271549 has been marked as a duplicate of this bug. ***