[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[viatra-dev] Recent changes
|
Hi all,
in the last few days I have cleaned up a few things in the project I want to share.
1. Automated Javadoc generation was set up. For each CI build there are some Javadoc generated: https://hudson.eclipse.org/viatra/job/viatra-master/lastSuccessfulBuild/artifact/releng/org.eclipse.viatra.docs/target/reference/api/index.html
Not all projects are included in the Javadoc; I tried to only add projects that I imagined to be used as an API. If somebody thinks something should not be here, or is missing, it could be modified easily.
2. Removal of old, deprecated code: I have opened bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=489340 to track this task. The primary candidates to remove are present in the generated Javadoc of EMF-IncQuery 1.1: https://www.eclipse.org/viatra/javadoc/releases/incquery-1.1.0/deprecated-list.html
Generally, everything that is in that list is planned to be removed (in some case it is possible that the call will remain, but its visibility will be reduced). If somebody wants something to remain; or remove some additional old API, please report it in the bug.
3. New bugzilla component setup is now active. We have a set of generic bugzilla addresses that are assigned to tickets by default. We should subscribe to these component owners to follow newly created issues. For the list of generic inboxes and link to subscribe to them is listed in https://wiki.eclipse.org/VIATRA/DeveloperDocumentation/IssueTracking
Existing issues are not yet assigned to development milestones; if somebody fixes an existing ticket, assign them to the current milestone (1.2 M2 for now).
4. Integration builds are up and running for the new VIATRA. During the setup, I have changed the update site urls not to include the ‘emf’ prefix; old urls redirect using the composite update site mechanism (so should be available transparently to end users). The current pages are listed in https://www.eclipse.org/viatra/downloads.php
The main difference between the new and the old structure is that there will be separate update sites for separate builds (e.g. each weeks integration build will go to a separate folder, and they are aggregated using a composite update site). The main goal of this is to allow the removal of old integration/migration builds without changing the infrastructure.
Everything should work as before; if anyone notices any issue, please report it to make sure everything is fixed.
Cheers,
Zoli
-- Zoltán Ujhelyi
Eclipse Technologies Expert
IncQueryLabs Ltd.
