Am 26.10.2016 um 21:21 schrieb Thomas Vandahl: > Am 25.10.2016 um 21:38 schrieb Oliver Heger <oliver.he...@oliver-heger.de>: >> when building on Windows 10 with Java 1.6 I get the error below. The >> build with Java 1.8 is successful. >> >> On the distributions, I found some problems: >> - Both the source and the binary distribution deflate in the same >> folder. Typically, different folders are used. > They should not overwrite anything important, though. > >> - The binary distribution does not only contain the jars but also all >> hashes and checksums. I don't think that they are required. > Yes, this happens when the assembly plugin builds from modules. I found this > a good idea, actually. Don't you? Well, not blocking, so no need to argue.
>> >> Is a site available for review? > The site is available as tar.gz in the dist area. >> >> One question regarding the beta status of the release: Are the artifacts >> going to be deployed to Maven central? > Yes. > >> Then there should be a special >> handling of breaking changes (special maven coordinates and package >> names indicating beta status). Otherwise, it would be good if the >> release notes contained a corresponding hint. > Ok. What would be required? We didn't do anything like that when releasing > beta-1. It is policy in commons to prevent binary incompatible artifacts with the same package names and maven coordinates because this leads to jar hell. So every time a release with breaking changes is made, there should be a major version bump, and maven coordinates and package names must be changed. So the question is, are there incompatible changes between JCS 1.x and the beta versions and the upcoming 2.0 final? Oliver > >> [ERROR] Failed to execute goal > > This looks like a dependency is compiled with 1.7. I'll look into it. > > Bye, Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
