Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330925 - The splash screen app is a WAB but is built with a .war extension
Summary: The splash screen app is a WAB but is built with a .war extension
Status: CLOSED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 3.0.0.M01   Edit
Assignee: Hristo Iliev CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-23 10:02 EST by Chris Frost CLA
Modified: 2011-02-28 10:37 EST (History)
3 users (show)

See Also:

Attachments
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 Chris Frost CLA 2010-11-23 10:02:29 EST 
Correct the build of the splash screen app to produce a .jar artifact.
Comment 1 Chris Frost CLA 2010-12-16 08:02:49 EST 
Just to give you a pointer. This is caused by the hard coded .war extension in the common.properties file in Virgo-Build. Property 'war.output.file'. This is not a trivial fix, Virgo-Build needs to support a whole new Artifact type. Just building it as a jar won't work as it will not be built as a WAB or a War file and will fail to deploy any web resources.

BTW, it has some parts of it's web module support lying around that need deleting, I spotted a load of web.module properties in the file as well, I suspect that is all that is left. Please ask if you have questions on the build system.
Comment 2 Hristo Iliev CLA 2010-12-22 07:01:43 EST 
Commit 313c9bfa8f6dddcc8c8929c84de6ac659af7bdf2
Added WAB build artifact type in virgo-build

Commit 7eb28d6e8e5f501a79b989b05d7d42f9cd971e26
Splash and admin web apps are build as WAB

virgo-build 2.09 is pushed to all project (thanks to Chris)