On 06.10.2011 18:40, Stefan Steiniger wrote: > Hi all, > > at the end its Intevations decision, which based on their company > policy.
agreed >And if we can't keep going with the builds on their > infrastructure I am thankful to Intevation, in particular Sascha and > Stephan for their support over the past years. yeah, definitely thanks, though i still hope we might find a solution, that keeps the nb alive. > If there is no more to say from Intevation after Edgars last email, then > we@OJ will have to decide what we do and get back to you then. > if intevation has a strict policy regarding proprietary code, we will have to honor it. > On the other hand - I am not seeing a need to have ecw included in the > (daily) nightly build. for bugfixing ecw/jp2 connected bugs for example? also i think streamlining snapshots and releases makes totally sense, so users do not get confused, where is this functionality gone now? in the end we could even have a build process automated which generates releases on push of a button, because a release is actually a snapshot as well ;) i see two solutions to oblige to their terms, in case intevation insists: a) have a special oss only intevation build (although ecw 3.3 is essentially oss, albeit not gpl compatible) b) externalize ecw/jp2 support into a manually to install package i'd vote for the (a) because it should be implemented quite easily. my snapshots could add them manually so we could keep one pom for the build. .. ede ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
