Well Justin, these files are typically generated by our software. It would not be OK to force the license into all files since that wouldn't be appropriate and right since we don't force Apache copyright on the work of others. Without that possibility we're down to manually editing the files every time they are created or modified in the slightest. I don't see that as a valid option. So I guess those are good reasons why. That evaluation was made before. Now it just feels like one more rule we have to deal with that just comes out of the blue.
If you (=the wonderful people in this list) really want us to script some process on Jenkins that force-feeds the header into the .hpl/.hwf files we'll do so though. It's just a bit frustrating to be honest. On Fri, Jun 11, 2021 at 2:54 PM Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > We see integration tests as an even more important and integral part of > the > > source code compared to unit tests since they offer so much more value in > > ensuring that functionality and compatibility remain the same when we > push > > our software forward. > > So in that case they should have ASF header on them. I don’t see why > integration tests shod be excused from this and it make the release hard to > review. > > Kind Regards, > Justin -- Neo4j Chief Solutions Architect *✉ *matt.cast...@neo4j.com ☎ +32486972937
