Skip to content

Commit 02bb088

Browse files
beikovbeikov
committed
Make sure releasing works
1 parent e3b8681 commit 02bb088

File tree

2 files changed

+67
-5
lines changed

2 files changed

+67
-5
lines changed

‎core/testsuite-hibernate6/pom.xml

+62
Original file line numberDiff line numberDiff line change
@@ -470,6 +470,68 @@
470470
</profile>
471471

472472
<!-- JPA provider profiles -->
473+
<profile>
474+
<id>hibernate-5.6</id>
475+
<properties>
476+
<jpa.excludedGroups>com.blazebit.persistence.testsuite.base.jpa.category.NoHibernate60</jpa.excludedGroups>
477+
</properties>
478+
<!-- Note that we use version 6.2 here because this profile will be used during the release, which needs an ORM version for compilation -->
479+
<dependencies>
480+
<dependency>
481+
<groupId>org.hibernate</groupId>
482+
<artifactId>hibernate-core</artifactId>
483+
<version>${version.hibernate-6.2}</version>
484+
</dependency>
485+
<dependency>
486+
<groupId>org.hibernate</groupId>
487+
<artifactId>hibernate-envers</artifactId>
488+
<version>${version.hibernate-6.2}</version>
489+
</dependency>
490+
<dependency>
491+
<groupId>org.hibernate</groupId>
492+
<artifactId>hibernate-testing</artifactId>
493+
<version>${version.hibernate-6.2}</version>
494+
</dependency>
495+
<dependency>
496+
<groupId>jakarta.xml.bind</groupId>
497+
<artifactId>jakarta.xml.bind-api</artifactId>
498+
<version>${version.jakarta-jaxb-api}</version>
499+
</dependency>
500+
<dependency>
501+
<groupId>com.sun.xml.bind</groupId>
502+
<artifactId>jaxb-impl</artifactId>
503+
<version>${version.jakarta-jaxb}</version>
504+
</dependency>
505+
<dependency>
506+
<groupId>jakarta.persistence</groupId>
507+
<artifactId>jakarta.persistence-api</artifactId>
508+
<version>${version.jakarta-jpa-3.1-api}</version>
509+
<scope>provided</scope>
510+
</dependency>
511+
<dependency>
512+
<groupId>jakarta.transaction</groupId>
513+
<artifactId>jakarta.transaction-api</artifactId>
514+
<version>${version.jakarta-jta}</version>
515+
</dependency>
516+
<dependency>
517+
<groupId>jakarta.activation</groupId>
518+
<artifactId>jakarta.activation-api</artifactId>
519+
<version>${version.jakarta-activation}</version>
520+
</dependency>
521+
<dependency>
522+
<groupId>${project.groupId}</groupId>
523+
<artifactId>blaze-persistence-integration-hibernate-6.2</artifactId>
524+
<scope>test</scope>
525+
</dependency>
526+
<!-- IntelliJ apparently needs the annotation processor here -->
527+
<dependency>
528+
<groupId>org.hibernate</groupId>
529+
<artifactId>hibernate-jpamodelgen</artifactId>
530+
<version>${version.hibernate-6.2}</version>
531+
<scope>provided</scope>
532+
</dependency>
533+
</dependencies>
534+
</profile>
473535
<profile>
474536
<id>hibernate-6.2</id>
475537
<activation>

‎creating-a-release.md

+5-5
Original file line numberDiff line numberDiff line change
@@ -17,14 +17,14 @@ A release involves various steps which are outlined here and should be kept up-t
1717
. Open `website/src/main/jbake/jbake.properties` and update `stable.version` to the latest released version
1818
. Open `website/pom.xml` and update the property `stable.version` to the latest released version, `snapshot.version` to the latest snapshot version and `series.version` to the current version series
1919
. Open `documentation/pom.xml` and update the property `stable.version` to the latest released version and `series.version` to the current version series
20-
. Prepare a local Maven release via `mvn -P "blazebit-release,h2,hibernate-5.6,deltaspike-1.9,spring-data-2.7.x" release:clean release:prepare "-Darguments=-DskipTests -DskipITs '-Djdk8.home=C:\Program Files\Java\jdk1.8.0_181'"`
21-
. Actually deploy the release with `mvn -P "blazebit-release,h2,hibernate-5.6,deltaspike-1.9,spring-data-2.7.x" release:perform "-Darguments=-DskipTests -DskipITs '-Djdk8.home=C:\Program Files\Java\jdk1.8.0_181'"`
20+
. Prepare a local Maven release via `mvnw -P "blazebit-release,h2,hibernate-5.6,deltaspike-1.9,spring-data-2.7.x" release:clean release:prepare "-Darguments=-DskipTests -DskipITs '-Djdk8.home=C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot'"`
21+
. Actually deploy the release with `mvnw -P "blazebit-release,h2,hibernate-5.6,deltaspike-1.9,spring-data-2.7.x" release:perform "-Darguments=-DskipTests -DskipITs '-Djdk8.home=C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot'"`
2222
. Goto https://oss.sonatype.org and login. In *Build Promotion* click on *Staging Repositories* then scroll down and find a repository named *comblazebit-...*
2323
. Click on the repository, then click *Close* and *Confirm*. Wait a few seconds, click *Refresh* and finally click *Release* and *Confirm*
2424
. Commit the changes and push the branch `git push origin`, as well as the created tag `git push origin TAG`
2525
. Create a GitHub release from the tag and use the same content as in `website/src/main/jbake/content/news/CURRENT_YEAR/blaze-persistence-VERSION-release.adoc` and add the _tar.gz_ and _zip_ artifacts of `blaze-persistence-distribution` as binaries to the release
26-
. Push the new website changes only if you are working on the latest version series and first to the staging server by invoking `./build-deploy-website.sh staging '-Djdk8.home=C:\Program Files\Java\jdk1.8.0_181'` and if everything is alright push to production with `./build-deploy-website.sh prod '-Djdk8.home=C:\Program Files\Java\jdk1.8.0_181'`
27-
. If you want to push just the documentation changes use `./build-deploy-documentation.sh staging '-Djdk8.home=C:\Program Files\Java\jdk1.8.0_181'` and if everything is alright also push to production with `./build-deploy-documentation.sh prod '-Djdk8.home=C:\Program Files\Java\jdk1.8.0_181'`
26+
. Push the new website changes only if you are working on the latest version series and first to the staging server by invoking `./build-deploy-website.sh staging '-Djdk8.home=C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot'` and if everything is alright push to production with `./build-deploy-website.sh prod '-Djdk8.home=C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot'`
27+
. If you want to push just the documentation changes use `./build-deploy-documentation.sh staging '-Djdk8.home=C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot'` and if everything is alright also push to production with `./build-deploy-documentation.sh prod '-Djdk8.home=C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot'`
2828
. Create tweet about new version
2929
. Update version in Quarkus ecosystem ci poms
3030

@@ -37,7 +37,7 @@ A private release involves the following steps
3737
. Make sure you have GPG installed and the executable is available on PATH
3838
. Make sure your Maven settings.xml has credentials for the server `blazebit` configured
3939
. Make sure your Maven settings.xml has a profile called `blazebit-release` with the property `gpg.passphrase`
40-
. Make sure you have `C:\Program Files\Java\jdk-14` and `C:\Program Files\Java\jdk1.8.0_181` installed or update the `deploy-project-release.bat` script
40+
. Make sure you have `C:\Program Files\Java\jdk-14` and `C:\Program Files\Eclipse Adoptium\jdk-8.0.332.9-hotspot` installed or update the `deploy-project-release.bat` script
4141
. Checkout the commercial branch for the minor version e.g. `1.5-commercial`
4242
. Invoke `mvn org.codehaus.mojo:versions-maven-plugin:2.1:set "-DnewVersion=1.5.X"`
4343
. Invoke `deploy-project-release.bat`

0 commit comments

Comments
 (0)