Re: maven: war LICENSE file

Aaaahh … I remember … I think I had that file generated, copied it and fine-tuned the ones that needed tuning. I could remove most of them, I guess … after all it only is used for downloading the license texts for bundled artifacts. Chris Am 02.10.17, 23:09 schrieb "Dale LaBossiere"

Re: maven: war LICENSE file

Hi Chris, I see you added a bunch of comments to the wiki, thanks! I think we has a misunderstanding :-) There are many artifacts that *have* an entry in license.xml but are not bundled. e.g., junit, jetty-*. That’s what I was trying to say in the tables. Shouldn’t only bundled things be

Re: maven: war LICENSE file

I did a review and captured what I learned along with questions and/or problems in new item 21 (at the bottom of) [1] The details (table) are for only console/servlets at the moment. I’ll be doing similar for console/server shortly. [1]

Re: Jenkins Multibranch Pipeline Plugin

Nice. Seems like DEVELOPMENT.md’s Jenkins chapter should capture this sort of info? Under what conditions do these Jenkins builds run, nightly, upon new commit...? What happens when a build fails? (thinking of transient failures) What's the scoop with our “master” branch and how it's handled?

Re: maven: war LICENSE file

I’m on it! > On Oct 2, 2017, at 8:52 AM, Christofer Dutz wrote: > ... > I just committed some more changes to the java8 and jaca7 console. I hope > that now all should be in place and the modules should be ok from a legal > point of view. > ... > Please inspect my

Re: maven: war LICENSE file

Hi all, I just committed some more changes to the java8 and jaca7 console. I hope that now all should be in place and the modules should be ok from a legal point of view. Unfortunately, I had to jump though quite a lot of hoops in order to get everything working correctly. But now I think all