Re: [mylyn-docs-dev] exploring changes to Mylyn Docs build

[David Green <david.green@xxxxxxxxxxx>]

All,

I've opened the following bug to track this effort:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=511120

You can see the results of what I've done so far, with this review being the tip of the chain: https://git.eclipse.org/r/#/c/89651/

Note that some of the changes don't build - only from the last review does the whole chain build properly.

Some things left to do:

* iterate as needed to improve the changes until we're ready to merge

* update sites - do we want WikiText in the Mylyn Docs site or separate?

* determine where and how to publish the Maven artifacts from the core part of the build

* update build jobs accordingly (Gerrit review verification, snapshot and release builds)

* determine if or how this affects EPP contributions

I'd appreciate your feedback on the bug or on the reviews.

Thanks,

David

On Fri, Dec 2, 2016 at 9:47 AM David Green <david.green@xxxxxxxxxxx> wrote:

Devs,

I've been experimenting with restructuring the Mylyn Docs build to achieve a few things:

* easier to build/release Mylyn Docs (or at least Mylyn WikiText) separately from Mylyn

* easier to consume Mylyn WikiText core bundles (e.g. as plain jars, with normal poms)

* easier to contribute (e.g. without knowledge of OSGi or PDE)

* better structured code/tests (e.g. using normal Maven project layout)

* faster cycle time (e.g. easier to verify code changes, faster builds)

To achieve these things I've been looking at building the "core" wikitext bundles as normal Maven artifacts, using a Maven plug-in to generate OSGi manifests.

You can see the results of my experiment here: https://github.com/greensopinion/mylyn.docs

The build is split into two parts: a "core" part which is Tycho-less, and a UI/OSGi part which uses Tycho.

I'd love to get your thoughts and feedback on the goals and the approach.

David

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx