We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We'd probably want to hold off on this until 1.0 or so, but Parquet uses the maven enforcer plugin to flag API breaking changes:
<plugin> <artifactId>maven-enforcer-plugin</artifactId> <version>1.3.1</version> <dependencies> <dependency> <groupId>org.semver</groupId> <artifactId>enforcer-rule</artifactId> <version>0.9.23</version> </dependency> </dependencies> <executions> <execution> <id>check</id> <phase>verify</phase> <goals> <goal>enforce</goal> </goals> <configuration> <rules> <requireBackwardCompatibility implementation="org.semver.enforcer.RequireSemanticVersioningConformance"> <dumpDetails>true</dumpDetails> <previousVersion>${previous.version}</previousVersion> <excludes> <exclude>parquet/org/**</exclude> </excludes> </requireBackwardCompatibility> </rules> </configuration> </execution> </executions> </plugin>
The text was updated successfully, but these errors were encountered:
+1
Sorry, something went wrong.
Semantic versioning is now in place as of release version 1.0.
No branches or pull requests
We'd probably want to hold off on this until 1.0 or so, but Parquet uses the maven enforcer plugin to flag API breaking changes:
The text was updated successfully, but these errors were encountered: