Bugzilla – Full Text Bug Listing
| Summary: | create a Maven plug-in for generating Eclipse Help from wikitext | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | David Green <greensopinion> |
| Component: | Mylyn | Assignee: | David Green <greensopinion> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | john.arthorne, steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | 2.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Bug Depends on: | 419621, 420104 | ||
| Bug Blocks: | |||
|
Description
David Green
CQ approved for Maven API usage: 7658: maven-plugin-api Version: 3.0 (PB CQ4591) https://dev.eclipse.org/ipzilla/show_bug.cgi?id=7658 pushed reviews: https://git.eclipse.org/r/17653 https://git.eclipse.org/r/17654 https://git.eclipse.org/r/17655 https://git.eclipse.org/r/17656 https://git.eclipse.org/r/17657 Steffen, according to bug 420104 and http://wiki.eclipse.org/Services/Nexus we would need to add the following to our POM to publish to the Eclipse.org Nexus repository. I looked into adding that to the Mylyn parent POM, but it looks like distributionManagement is already defined there. Would it make sense to add this to a separate pom in the docs Git repossitory? bc.. <distributionManagement> <repository> <id>repo.eclipse.org</id> <name>Mylyn Repository - Releases</name> <url>https://repo.eclipse.org/content/repositories/mylyn-releases/</url> </repository> <snapshotRepository> <id>repo.eclipse.org</id> <name>Mylyn Repository - Snapshots</name> <url>https://repo.eclipse.org/content/repositories/mylyn-snapshots/</url> </snapshotRepository> </distributionManagement> It makes sense to me that we would use the new Maven repository for all of Mylyn from now on and updated the parent pom. For now feel free to override the distributionManagement in the Mylyn Docs pom. We only publish poms from the org.eclipse.mylyn repository at the moment so it won't do any harm. Thanks Steffen. Pushed https://git.eclipse.org/r/17665 TODO: user guide with example John, this might be of interest to you. The goal is to create a WikiText Maven plug-in to generate documentation as part of the build. (In reply to Steffen Pingel from comment #13) > John, this might be of interest to you. The goal is to create a WikiText > Maven plug-in to generate documentation as part of the build. Thanks for the pointer. Since just about anyone can edit the wiki I actually like the manual step of comparing the latest wiki contents against what is committed before I push changes into real documentation. I can see this being useful in nightly builds for example though. |