![]() ![]() 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. 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). 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. It’s done, finally! Bidding farewell to my pet peeve ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |