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

[Jeremie Bresson <dev@xxxxxxxx>]

I am trying to work on the Oomph setup for the new structure with Change 90138
https://git.eclipse.org/r/90138

All the projects are now materialized into the workspace, but most of the "ui" plugins now complain that they cannot find the "core" bundles. Those bundles are located in "wikitext/repository/target/repository" after a maven build was executed on "wikitext/core" and on "wikitext/repository".

How do you bring them in the IDE to make the "ui" bundles aware of this additional P2 Update Site. This is a problem independent from the Oomph setup. I am the only one experiencing difficulties?

Le 01.02.2017 01:10, David Green a écrit :

All,

 

The changes are merged, and the nightly has completed successfully: https://hudson.eclipse.org/mylyn/view/Nightlies/job/mylyn-docs-nightly/

 

In order to get that build working, I had to change the goal from deploy to verify.  This means that the nightly build is no longer deploying to the snapshot repository, something that we'll have to figure out.

 

I'll keep the bug open https://bugs.eclipse.org/bugs/show_bug.cgi?id=511120 since there is still some work to do.

 

David

On Tue, Jan 31, 2017 at 3:36 PM David Green <david.green@xxxxxxxxxxx> wrote:

All,

I plan to merge the review chain ending with https://git.eclipse.org/r/90016 today.  I will also make the corresponding changes to the Mylyn Docs nightly build here: https://hudson.eclipse.org/mylyn/view/Nightlies/job/mylyn-docs-nightly/

 

There is a chance that other builds could break, we should find out quickly.

 

The folder structure in the Mylyn Docs git repository will be different after merging.  As a result anyone with Mylyn Docs checked out into their Eclipse workspace will want to delete all Mylyn Docs projects from their workspace before pulling the changes, and then reimport those projects.  Gerrit reviews will also need rebasing.

 

I just discussed these changes with Sam and Steffen and it looks like these changes will cause the Mylyn release build to fail, since the Mylyn release build relies on having a single Maven reactor.

 

To overcome this problem Sam's suggestion is to switch the Mylyn Git submodule to point to Mylyn Docs at a specific commit until such time as the Mylyn release build has been decoupled.  A Mylyn committer will have to do this.

 

Apologies in advance for any trouble this causes, hopefully we can get through this change quickly.

 

David

On Thu, Jan 26, 2017 at 2:40 PM David Green <david.green@xxxxxxxxxxx> wrote:

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

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

--

David Green | VP of Architecture | Tasktop

email: david.green@xxxxxxxxxxx

_______________________________________________
mylyn-docs-dev mailing list
mylyn-docs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-docs-dev