Community

Chat Logs

Monday, April 13, 2026

00:16:24* roesyyu joined #java
00:25:49* agnivn joined #java
01:23:46* roesyyu joined #java
01:30:01* Aedil joined #java
01:30:08* roesyyu joined #java
01:34:05* hwpplayer1 joined #java
02:06:31* roesyyu joined #java
02:27:53* agnivn joined #java
02:44:44* roesyyu joined #java
02:51:07* roesyyu joined #java
03:19:03* roesyyu joined #java
03:25:26* roesyyu joined #java
04:13:46* johnjay joined #java
04:20:34* Henryx joined #java
04:21:28* roesyyu joined #java
04:49:33* roesyyu joined #java
04:55:55* roesyyu joined #java
05:19:13* stfstfm joined #java
06:47:33* Ragnor joined #java
07:07:01* B_fd joined #java
07:15:23* roesyyu joined #java
07:18:21* roesyyu joined #java
07:22:00* roesyyu joined #java
07:28:22* roesyyu joined #java
07:55:31* leppard joined #java
08:01:21* roesyyu joined #java
08:02:14* leppard joined #java
08:07:44* roesyyu joined #java
08:14:22* michele joined #java
08:32:18* kmh joined #java
08:44:57* MikeBux joined #java
08:46:40* stfstfm joined #java
09:02:40* kathadris joined #java
10:01:13* agnivn joined #java
10:09:24* roesyyu joined #java
10:10:35* mwnaylor joined #java
10:12:12* mwnaylor left #java
10:15:47* roesyyu joined #java
10:34:15* roesyyu joined #java
10:37:43* roesyyu joined #java
10:44:06* roesyyu joined #java
10:49:39* Aedil joined #java
10:58:04dreamrealmorning
11:03:45CandleWith a pull-request based workflow (and a protected `main` branch), how do people handle `mvn release:prepare` via a branch & pull request?
11:05:05dreamrealwouldn't that be the CI/CD's job in that case?
11:06:42CandlePartly, let's restrict that even more, and say that CI/CD does not have write access to the repo.
11:06:52dreamrealdon't know then
11:07:09dreamrealgpt
11:07:16dreamreal~gpt With a pull-request based workflow (and a protected `main` branch), how do people handle `mvn release:prepare` via a branch & pull request?
11:07:26javabotIn a pull-request based workflow with a protected `main` branch, you'd typically handle `mvn release:prepare` via a branch & pull request by creating a separate release branch. Here's a simple process: 1. Checkout to a new branch (e.g., `release/v1.0.0`). 2. Run `mvn release:prepare` in that branch. This will update the project versions, commit, and tag the new version. 3. Push the branch and create a pull request for it. 4. Once the pull request is re
11:07:26javabotbe merged into the `main` branch. This way, `mvn release:prepare` is executed in a controlled environment and the `main` branch is updated in a clean, traceable manner through the pull request.
11:07:37* dreamreal shrugs.
11:09:58CandleIt is feels like a fast-forward merge - to get the two sequential commits into main, but then the tag still references a commit on the branch.
11:11:29deebowhat does release:prepare do?
11:12:16dreamrealI'd think you'd tag the release preparation, not the incoming
11:13:13Candle1. commits a non SNAPSHOT version (e.g. changes 1.0.5-SNAPSHOT to 1.0.5). 2. creates a tag at that commit. 3. commits the next SNAPSHOT version (e.g. 1.0.6-SNAPSHOT).
11:15:03deebodo you really need like a pom.xml with <verion>5.0.0</version> in the repo? with gradle we just rewrite the the version for the build when releasing
11:15:27dreamrealmore than one road to rome
11:15:53CandleHaving the release version in VCS That gives you something you can tag in the repo.
11:16:33deebotrue, it just seems weird (to me), main/master should produce a snapshot every time, a separate release pipeline builds a specific commit as a release
11:17:09Candle(this is a long-standing problem that stricter repository permissions are ... encouraging.. us to actually try to resolve!)
11:17:28* dreamreal shrugs. Everyone has a lot of local practices, and somehow the world manages to not end as a result
11:17:46deebowe just ./gradlew build && ./gradlew -Pversion=2026.q2 publish && git tag release/2026.q2
11:18:47deebosnapshots are satans tool against humanity, along with nodejs and xml
11:18:51dreamrealthat's just about my process, too, although I don't use gradle
11:19:03dreamrealand I have no problem with either nodejs nor XML
11:19:27dreamrealmost people who resent XML resent its verbosity and don't know it
11:19:31dreamrealnot all, but most
11:19:48Candledeebo: Depending on a SNAPSHOT in production, that is certainly satanic!
11:21:14deebowell hopefully noone does that, and no doubt the situation has improved but i just hated trying to get an actual update to a dependency as a snapshot to work
11:21:24CandleAlso, switching to use Gradle is a pretty much a non-starter due to the size of the team and quantity of code.
11:21:58deebodon't repositories require unique snapshots these days anyhow? they append like a timestamp, :1.0-SNAPSHOT ~ :1.0-SNAPSHOT-2026041309101213.999 or something
11:22:32deeboremember dealing with that when managing a nexus repo and older maven versions that tried to overwrite snapshots or something
11:22:42CandleOnly if you push that snapshot to a repo.
11:32:25* roesyyu joined #java
11:35:45* roesyyu joined #java
11:42:07* roesyyu joined #java
11:45:35* Fiji_ joined #java
12:00:38* kcomhnall joined #java
12:01:05* GreenResponse joined #java
12:01:35Parabtw, never do fast-forwarding merges
12:01:52ParaThey break actual history by removing merge points, and merge points are semantically important
12:03:05* roesyyu joined #java
12:05:24dreamrealI just don't use VCS, makes management a lot easier
12:06:16* roesyyu joined #java
12:12:39* roesyyu joined #java
12:13:11Paramanage, damage, same difference
12:30:46* roesyyu joined #java
12:37:06* roesyyu joined #java
12:44:53cheeserdeebo: they've always had timestamps on snapshots.
12:52:20* polarian joined #java
12:54:47* jamezp joined #java
13:01:40* Afroboy joined #java
13:21:50* agnivn joined #java
14:31:56* raj joined #java
14:45:57* raj joined #java
14:47:47* nb-ben joined #java
14:50:12* polarian joined #java
15:00:51* B_fd joined #java
15:33:09* magla joined #java
15:42:34* handicraftsman joined #java
15:42:55* PocketKiller joined #java
15:53:24dreamrealhttps://bytecode.news/posts/2026/04/bring-back-idiomatic-design
16:07:18* stfstfm_ joined #java
16:13:17GreenResponsenice piece, I think there’re too many people using computer technology, some only to “fit in” because of FOMO, they absorb solutions given them by AI because they are incapable of make them themselves
16:21:33Swayzeyeah but then you need to have teh right person for the rigth job
16:22:16Swayzeif its a personal project it doesnt matter what you're doing but in a professional setting there are ways to ensure you have the appropriate person in charge of architecting solutions and making decisions
16:23:02* B_fd joined #java
16:30:32* mindCrime joined #java
16:36:10* zorone joined #java
16:41:54* deepSleep joined #java
16:46:43* Zapek joined #java
16:54:18* Zapek joined #java
16:56:53* Betal joined #java
17:07:09GreenResponseI was thinking more about end-users than developers tho
17:07:48* roesyyu joined #java
18:04:20* dumptruckman joined #java
18:07:27* johnjay joined #java
18:17:04* agnivn joined #java
18:35:43* MikeBux joined #java
18:38:29* Ekho joined #java
18:46:24* stfstfm joined #java
19:09:54* polarian joined #java
19:31:57* m joined #java
20:12:24* NeXeN joined #java
20:31:33* nevet joined #java
20:31:33* CodeGeek!~codegeek@about/java/CodeGeek changed the topic to: Welcome! || Read Channel Rules at https://javachannel.org/ before participating. || Paste limit is two lines; ~pastebin lists options. || No applets, please. || Minecraft, Android, and Javascript all have their own channel. || You are being logged.
20:46:14* B_fd joined #java
21:03:25jreicherPara FF merges remove merge points???
21:23:11* kcomhnal1 joined #java
21:35:43* mindCrime joined #java
21:38:22* stfstfm_ joined #java
21:54:46* kcomhnall joined #java
22:08:11kcomhnall~jep 527
22:08:12javabot'JEP 527: Post-Quantum Hybrid Key Exchange for TLS 1.3' can be found at http://openjdk.java.net/jeps/527
22:08:13nevetJEP 527: Post-Quantum Hybrid Key Exchange for TLS 1.3
22:13:29* zorone joined #java
22:14:01* zorone joined #java
22:34:36* domicron joined #java
23:00:19* johnjay joined #java
23:02:20* B_fd joined #java
23:32:25* MikeBux joined #java