Re: POM license guidance (and need for documentation/FAQ)
Alexander Kriegisch wrote: > I think what Nils says applies internationally, not just in the NL. A > copyright claim for any project which sports at least one easily > discoverable licence file in its SCM and in each major artifact should > be easy to defend against any licence violations. Legally, redundant > copies are totally unnecessary. My point was that even when there is no copyright notice anywhere, legally means that nobody except the author is allowed to use the code. At least in The Netherlands. Other countries may require an explicit copyright notice. Of course having an explicit copyright notice may help when there is a copyright dispute. When there is no license, there can also be no license violation, but default copyright rules apply when there is no license. You only need to license something when you want to deviate from standard copyright rules. Nils. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: POM license guidance (and need for documentation/FAQ)
I think what Nils says applies internationally, not just in the NL. A copyright claim for any project which sports at least one easily discoverable licence file in its SCM and in each major artifact should be easy to defend against any licence violations. Legally, redundant copies are totally unnecessary. This whole licence copying mania only serves the purpose to increase the probability of licence discovery from 99% to 99.5%. Whoever uses OSS source code accidentally, will be glad to remove it or acknowledge the licence if you tell him to. Whoever steals it on purpose is probably smart enough to remove licence headers from source code and config files anyway. This whole practice, however many years established and followed like cargo cult, is simply a waste of time and resources that does not increase or decrease any party's chances of winning or losing in court by one iota. I think, we should let it go. Apologies to the person starting the thread, asking a different question, for straying somewhat off topic. -- Alexander Kriegisch https://scrum-master.de Nils Breunese schrieb am 30.03.2024 14:26 (GMT +01:00): > Timothy Stone wrote: > >> Organizationally, we lack a policy and much of our code lacks even a >> "copyright." > > Where I live (The Netherlands) there is no need to explicitly add a copyright > notice to the work you create, you automatically have the copyright on > anything > you create (not just software). But laws are not the same all over the world, > which I guess is why many organizations add an explicit copyright notice in > each individual source file. > > Nils. > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: POM license guidance (and need for documentation/FAQ)
Timothy Stone wrote: > Organizationally, we lack a policy and much of our code lacks even a > "copyright." Where I live (The Netherlands) there is no need to explicitly add a copyright notice to the work you create, you automatically have the copyright on anything you create (not just software). But laws are not the same all over the world, which I guess is why many organizations add an explicit copyright notice in each individual source file. Nils. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to include only certain test packages in a maven test-jar & all non test code in a non test jar?
Sat, 30 Mar 2024, /Debraj Manna/: As suggested by Stanimir if I remove the test-jar type and also the includes like below then mvn package --projects=:agent -T 2 --also-make works [...] But if I add back the below inclusion it again starts throwing the NoClassDefFoundError [...] At least for me, it is already hard to follow. Without accessible full example setup I can only suggest you follow Gary's and the official documentation advice to factor the necessary classes into their own module, declaring their dependencies explicitly: * https://maven.apache.org/plugins/maven-jar-plugin/examples/create-test-jar.html#the-preferred-way *The preferred way* In order to let Maven resolve all |test|-scoped transitive dependencies you should create a separate project. * Move the sources files from |src/test/java| you want to share from the original project to the |src/main/java| of this project... -- Stanimir - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
