Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 352989 - Integrate Gemini Web docs into the build
Summary: Integrate Gemini Web docs into the build
Status: CLOSED FIXED
Alias: None
Product: Gemini.Web
Classification: RT
Component: unknown (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 2.1.0.RELEASE   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-25 06:44 EDT by Glyn Normington CLA
Modified: 2012-08-27 02:23 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Glyn Normington CLA 2011-07-25 06:44:23 EDT

    
Comment 2 Chris Frost CLA 2011-08-02 10:47:17 EDT
Hi,

The build for gemini web dosn't follow the conventions for the other repos that get packaged, (Snaps, Tomcat Server, Greenpages). Doc is a part of the package target, as such the release script didn't call doc as it didn't expect to. I've changed the releasolor script to now do this but the propper solution is to make doc a part of the package target and to pull the package target into it's own file called 'package-top-level.xml'. I'm also unsure if package-ivy.xml is used at all.

I'm basing this on what was built for 2.0.0.RC1, the docs folder is there but there is nothing in it. This is because package was called for the docs projects but they were never built. This will now work but should be kept consistent with the other repos.
Comment 3 Glyn Normington CLA 2011-08-25 04:24:07 EDT
Targetting next release to standardise the doc target.
Comment 4 Chris Frost CLA 2012-06-22 11:44:57 EDT
It's working as it is and will get wrapped up in the upcomming build work