Good point, I recall Bertrand sent something around. Maybe you could help (as long as any committer/PMC member is able to use those links?;-) The new structure would make at least these Jobs look like a good idea: DeviceMap Data 1.0: /trunk/data/1.0/device-data/ With currently these downstream builds DeviceMap Java Client 1.0: /trunk/clients/1.0/java/ DeviceMap W3C DDR Implementation: /trunk/clients/w3c-ddr/ (this POM actually builds, I'm happy to ask for Jenkins job there myself) DeviceMap C# Client 1.0 /trunk/clients/1.0/csharp/ (also happy to help, .NET Jenkins should follow what Log4Net already does at Apache.org) DeviceMap VN.NET Client 1.0 /trunk/clients/1.0/csharp/ (also happy to help, .NET Jenkins should follow what Log4Net already does at Apache.org)
Plus some more Jenkins Jobs for /trunk/examples/ as a 3rd tier behind Data and the respective Client. BrowserMap works independently. At some point similar 2.0 jobs should arise, but for now I think this is still in concept/design phase. Cheers, Werner On Wed, May 6, 2015 at 12:54 PM, Volkan Yazıcı <[email protected]> wrote: > Hello, > > Is there a way we can fix the Jenkins builds? > > Best. >
