Bugzilla – Full Text Bug Listing
| Summary: | Integrate Gemini Web docs into the build | ||
|---|---|---|---|
| Product: | [RT] Gemini.Web | Reporter: | Glyn Normington <glyn.normington> |
| Component: | unknown | Assignee: | Project Inbox <gemini.web-inbox> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | eclipse, milesg78 |
| Version: | unspecified | ||
| Target Milestone: | 2.1.0.RELEASE | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Glyn Normington
Wasn't it integrated already? https://hudson.eclipse.org/hudson/view/Virgo/job/virgo.gemini-web-container.snapshot/ws/build-web-container/target/package-expanded/gemini-web-2.0.0.CI-2011-07-28_21-54-13/docs/ 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. Targetting next release to standardise the doc target. It's working as it is and will get wrapped up in the upcomming build work |