| Re: [elk-dev] Checkstyle in Oomph Setup |
I just checked up on what the optional flag is supposed to mean, and it seems that it is not intended to stop the P2 director from contacting update sites. Which makes sense, since it will look through all defined update sites to check where it finds the most up-to-date version of a feature to be installed. Marking one feature as optional won't stop the P2 director from contacting the update sites. Cheers, Christoph Daniel On 08/01/17 13:54, Nis Wechselberg wrote: > Just a quick note on maybe a third option: I have seen, that some parts of the oomph setup can be marked optional. Maybe we could find a way to keep checkstyle in, but keep the setup running for cases where it breaks. > > Am 8. Januar 2017 13:17:45 MEZ schrieb Christoph Daniel Schulze <cds@xxxxxxxxxxxxxxxxxxxxxx>: >> I just received an answer from the Checkstyle developer, Lars >> Kööderitzsch, a few days ago. He knows about problems with the update >> site, but insists that most of them started appearing around December >> 13th. On that date Sourceforge apparently updated its SSL certificate, >> with the new one not supported by older JDKs. Lars says that current >> SDKs support the new certificate. >> >> He also mentions that he would love to move the project to a different >> hosting service, but lacks the time to do so. So as far as I see it, we >> have two options: >> >> 1. Upgrade to the most recent JDKs (which everyone should do from time >> to time anyway) and hope for the best. >> >> 2. Kick Checkstyle out of our setup permanently. >> >> I don't like the second solution very much since Checkstyle plays a >> part >> in unifying the style of everyone's code. >> >> Cheers, >> Christoph Daniel >> >> On 20/12/16 11:28, Miro Spönemann wrote: >>> I needed to reinstall the whole ELK setup because my previous Eclipse >>> launcher refused to launch (no idea why). So my intermediate solution >>> was to create a copy of the Oomph setup and remove all references to >>> Checkstyle. >>> >>> Miro >>> >>>> On 16 Dec 2016, at 13:49, Christoph Daniel Schulze >>>> <cds@xxxxxxxxxxxxxxxxxxxxxx <mailto:cds@xxxxxxxxxxxxxxxxxxxxxx>> >> wrote: >>>> >>>> Greetings, >>>> >>>> I just sent an e-mail to the Eclipse-CS developer. This is a problem >>>> that occurs quite frequently, it would be good to have a proper >> solution. >>>> >>>> I'll keep you posted. >>>> >>>> Cheers, >>>> Christoph Daniel >>>> >>>> On 15/12/16 17:32, Miro Spönemann wrote: >>>>> Hi, >>>>> the Oomph setup is currently broken because the Checkstyle update >> site >>>>> does not work. Is there an alternative update site we could use? >>>>> >>>>> Miro >>>>> >>>>> >>>>> Adding repository http://eclipse-cs.sf.net/update >>>>> Fetching compositeContent.xml from http://eclipse-cs.sf.net/update/ >>>>> (705B) >>>>> Calculating requirements and dependencies. >>>>> Cannot complete the request. Generating details. >>>>> ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete >> the >>>>> install because one or more required items could not be found. >>>>> at >>>>> >> org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:280) >>>>> at >>>>> >> org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.resolve(ProfileTransactionImpl.java:425) >>>>> at >>>>> >> org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.commit(ProfileTransactionImpl.java:337) >>>>> at >>>>> >> org.eclipse.oomph.setup.p2.impl.P2TaskImpl.perform(P2TaskImpl.java:729) >>>>> at >>>>> >> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3305) >>>>> at >>>>> >> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3233) >>>>> at >>>>> >> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3214) >>>>> at >>>>> >> org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3114) >>>>> at >>>>> >> org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:556) >>>>> at >>>>> >> org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:682) >>>>> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) >>>>> ERROR: org.eclipse.equinox.p2.director code=0 Software being >>>>> installed: artificial_root 1.0.0.v1481819418030 >>>>> ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: >>>>> artificial_root 1.0.0.v1481819418030 requires >>>>> 'net.sf.eclipsecs.feature.group 0.0.0' but it could not be found >>> >>> -- >>> Dr. Miro Spönemann >>> Software engineer and consultant >>> >>> TypeFox GmbH >>> Am Germaniahafen 1, 24143 Kiel >>> >>> http://typefox.io >>> Tel.: +49 151 42679459 >>> >>> Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 >>> Geschäftsführer: Sven Efftinge, Dr. Jan Köhnlein, Moritz Eysholdt >>> >>> >>> >>> _______________________________________________ >>> elk-dev mailing list >>> elk-dev@xxxxxxxxxxx >>> To change your delivery options, retrieve your password, or >> unsubscribe from this list, visit >>> https://dev.eclipse.org/mailman/listinfo/elk-dev >>> > _______________________________________________ > elk-dev mailing list > elk-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/elk-dev >
Attachment:
signature.asc
Description: OpenPGP digital signature