Switched away from jitpack, it is just not working! Started with new Major-Version for current developments and to get rid of the example stuff that I have done for jitpack.
Using JDK 21 (LTS) - managed by sdkman sdk install java 21.0.4-tem sdk use java 21.0.4-tem
Used infrastructure for development
java -Xmx32M -jar reposilite-3.5.18-all.jar inside the console you need to generate a token first token-generate --secret=admin admin m This will generate a user admin with pwd admin and the role manager
Add maven central https://repo1.maven.org/maven2/ to the mirrored repos.
one round for jitpack...
fixed jitpack.yml
updated plugins and minimum maven version to 3.9.6
skipped
Switched to the groupd ID com.github.svenruppert because custom domain names (com.svenruppert) are not working properly with Jitpack. Java Packages are still under com.svenruppert
Added the Modules:
- Logger Adapter
- Core
- Core Properties
I archived the original git repos and merged everything into this one. With this, building new versions is way easier or better - less work. :-)
updated versions
Fixed the pitest pattern com.svenruppert. junit.com.svenruppert.
removed the distribution repo definitions, because jitpack is doing it.
With version 5.x I will switch the namespace from org.rapidpm to com.svenruppert This has to do with organisational requirements on my side. I will move this repo to the Github organisation svenruppert. The license will be still the same. The change on your side, should be only the declaration of the parent pom.
- version updates
- maven plugin updates
- compile JDK will be 21 LTS
- switch from docker to podman - _tools/docker/develop
- version updates
- maven plugins updates
- version updates
- maven plugins updates
- version updates
- deploy target - via property on command line
- deploy-repo-url
- deploy-repo-snapshots-url
- V14.1 activated
- V15 alpha version update
- version updates
- Kotlin version update
- deactivate V08 dependencies
- deactivate V10 dependencies
- version update nodeJS/NPM (12.13.0/6.12.0)
- V14 update - V14.0.10
- added jCenter to repositories
- removed jitpack from repositories
- vaadin update V14 - V14.0.9
- cleared _release profiles
- update V14.0.7 to V14.0.8
- splitted the _release profile
- _release
- _release_prepare
- version updates
- version updates
- removed lic checker (flow) mix from transitive deps
- removed all indirect vaadin flow dependencies / components
- added flow minimal needed dependencies
- revert BUGFIX from 04.01.14-RPM
- BUGFIX - combobox dependency
- junit update 1.5.2
- switched VaadinXX to manual latest version compositions
- VaadinXX excludes all transitive webjars
- vaadin v14.0.3
- V10/V14/Vxx - removed the dependency to vaadin - way to heavy To get the dev cycle up to usable, add only the flow dependencies you need into your pom. example : Nano-Vaadin-Demos
- added minimal Flow dependencies, no themes, no components
- logger-adapter
- functional-reactive-lib
- pitest 1.4.10
- added junit-platform-testkit to scope test
- vaadinXX switched from V14 to V15 - 15.0.0.alpha1
- cache2k update to v1.2.4.Final
- added java-faker to scope test
- vaadin v14.0.2
- Update to V14 Final
- Update to stagemonitor 0.89.0
- junit-platform-maven-plugin.timeout - default 300 [s]
- version updates
- added Google Truth as default dependency into scope test
- excluded generated NodeJS/ NPM things from lic check
- version updates
- config changes for vaadin dependencies
- version updates
- config changes for vaadin dependencies
- version updates
- added rapidpm-vaadin-dependencies for V08/V10/V14/Vxx
- replaced reflections with reflections8
- deleted module - reflections
- changed compile cycle for AnnotationProcessing
- replaced dom4j to org.dom4j
- kotlin version update
- version updates
- externalizing version definitions
- version updates
- smaller BugFixings
- reduced maven minimum version to 3.3.9 for compatibility reasons
- added development profile for NodeJS/NPM - for Vaadin 14 projects
- externalizing required maven version
To define your maven version you could override the property maven-enforcer-plugin.version. The default is mostly the latest maven version.
- minimum-maven.version - setting required maven version, default is latest version
- activateJavaOnly - true = JDK only / false JDK plus Kotlin activated
- kotlin.compiler.jvmTarget - default latest release
- kotlin.version - default mostly latest version
- kotlin.compiler.incremental - default true
To make search/replace easier, I started with a new version format. 04.00.05-RPM ( -SNAPSHOT). The x.y.z is used in the same way, as before, but added RPM and leading zeros to make this format different from others. With this it is less possible to mix/change version numbers from other dependencies. A 4.0.3 could be used from different dependencies. ;-)
There a re a few modules deactivated and removed.
- reflection : moved as module into dynamic-dependency-injection project
- jdbc* : all deactivated and removed, code is available in the history
This will be the version based on Java8 I will create a LTD branch for this The version 4.* will be based on the JDK 10/11 (as soon as 11 is released) JDK 11 will be a LTS Version again.
With the beginning of this version the project will be compiled with the actual JDK but on source level Java 8.