#Eclipse neon 2 generator#
#Eclipse neon 2 software#

Still a few things had to be settled, either by improving the tool, by fine tuning the input to the tool, or by some steps of post-processing the resulting Maven repo. That tool does a great job of extracting meta data from the p2 repo in order to create вЂњmeaningfulвЂќ pom files, the key feature being: it copies all dependency information, which is originally authored in MANIFEST.MF, into corresponding declarations in the pom file. One of its capabilities is to create a Maven repository (a dual use repo actually, but the p2 side of this is immaterial to this story). The main tool in this endeavour is the CBI aggregator, a model based tool for transforming p2 repositories in various ways.

I should like to report some details of how our artifacts are mapped into the Maven world: The resulting вЂњdiversityвЂќ was one of my pet peeves in my job.ДЄt this point I decided to be the next volunteer who would screw up other peopleвЂ™s builds who would collaborate with the powers that be at to produce the official uploads to Maven Central.ДЄs of today, I can report that this dream has become reality, all relevant artifacts of Neon.2 that are produced by the Eclipse Project, are now вЂњofficiallyвЂќ available from Maven Central. Anybody who has ever studied the differences between Maven and OSGi (wrt dependencies and building that is) will immediately see that there are many possible ways to represent Eclipse artifacts (OSGi bundles) in a Maven pom. More stories like this and I realized that relying on Eclipse artifacts in Maven builds was always at the mercy of some volunteers, who typically donвЂ™t have a long-term relationship to Eclipse, who filled in a major gap by uploading individual Eclipse artifacts to Maven Central (thanks to you volunteers, please donвЂ™t take it personally: IвЂ™m happy that your work is no longer needed). Bottom line, with both almost-identical versions available, Maven couldnвЂ™t figure out what to do, maybe each was considered as worse than the other, to the effect that Maven simply failed to use either. Yes take a close look, there is a difference. Well, if itвЂ™s the same, whatвЂ™s the buzz? It turned out it had a one-char difference in its version: instead of 1.2.3.v20140815 its version was 1.2.3-v20140815.

So what? Well, that artifact was the same that we also had on our internal servers. Quite to the contrary somewhere on the wide internet (Maven Central to be precise) a new artifact had appeared. Followed long nights of searching why that artifact may have disappeared, but we reassured ourselves, nothing had disappeared. One Eclipse artifact could no longer be resolved.

#Eclipse neon 2 generator#

It doesnвЂ™t make a big difference if they are just invoking a code generator built using Xtext etc or whether some Eclipse technology should actually be included in their application runtime.ДЄmong many troubles, I recall one situation that really opened my eyes: one particular build had been running successfully for some time, until one day it was fubar. So whenever their build touches my technology we are facing a вЂњchallengeвЂќ. Their build technology of choice is Maven (without tycho that is).

#Eclipse neon 2 software#

But those colleagues consuming my technology work on software that has no direct connection to Eclipse nor OSGi. In my job at GK Software I have the pleasure of developing technology based on Eclipse. Represents a request for enhancement (also for 'major' features that would be really nice to have).ItвЂ™s done, finally! Bidding farewell to my pet peeve This describes a cosmetic problem like misspelled words or misaligned text, but doesnвЂ™t affect function. Something is wrong, but doesnвЂ™t affect function significantly or other problem where easy workaround is present. Implies some loss of functionality under specific circumstances, typically the correct setting unless one of the other levels fit. This is the default value for new bug reports. Implies 'loss of data' or frequent crashes or a severe memory leak. The bug blocks development or testing of the build and no workaround is known. The following rules can be used as guideline. The Eclipse Bugzilla system allows you and the Eclipse committer to enter the bug priority.Д«ut overall, it is up to each project do decide how they handle bugs so some variation from project to project will occur.