-
Notifications
You must be signed in to change notification settings - Fork 2
Expand file tree
/
Copy pathnotes.txt
More file actions
89 lines (62 loc) · 2.43 KB
/
notes.txt
File metadata and controls
89 lines (62 loc) · 2.43 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
https://search.maven.org/solrsearch/select?q=g:org.postgresql+AND+a:postgresql&rows=200&core=gav&wt=json' "&start=" is offset
https://repo1.maven.org/maven2/org/postgresql/postgresql/42.7.7/postgresql-42.7.7.pom (also swap ".pom" with ".jar")
in POM only consider "compile" and "rutime" ignore others
javac -d out -cp "lib/*" $(find src/main/java -name "*.java")
Manifest.txt
Main-Class: com.example.Main
Class-Path: lib/gson-2.10.1.jar lib/foo.jar etc
jar cfm app.jar manifest.txt -C out .
# Version Manager
(https://api.adoptium.net/q/swagger-ui)
list of versions:
curl -X 'GET' \
'https://api.adoptium.net/v3/info/available_releases' \
-H 'accept: application/json'
get link of download
curl -X 'GET' \
'https://api.adoptium.net/v3/assets/latest/25/hotspot?architecture=x64&image_type=jdk&os=linux&vendor=eclipse' \
-H 'accept: application/json'
download all versions into some folder and then have a "current" symlink pointing to the path of the version
we want to run
e.g
/jdks
- current (symlink) -> v1
- v1/
- v2/
- v3/
Then PREFIX the $PATH e.g `export PATH="/jdkds/current:$PATH", prefixing should "over ride" any system installed version.
if the prefix is removed then it will revert back to the system installed version
https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
---
Parent Resolution:
* walk "up" the parent until we reach the "super" POM
* walk down collecting all the <dependencyManagement> into a map (+ along with any potential Dependency? unlikely but could happen)
- if we have a "BOM" with import scope, then that needs to be "merged" into the <dependencyManagement>
* child values override parent values of the same item
* finally apply property find/replace
* finally use this "collated" <dependencyManagement> Map to fill out any depedency that doesn't have a version
USE Maven Meta Data in order to get latest version NOT solr!
https://repo1.maven.org/maven2/org/springframework/boot/spring-boot-autoconfigure/maven-metadata.xml
```yaml
profiles:
dev:
flags:
- debug
- hot_reload
envs:
RUST_LOG: "debug"
DATABASE_URL: "postgres://localhost/dev_db"
stage:
flags:
- optimize
envs:
RUST_LOG: "info"
DATABASE_URL: "postgres://staging.server/stage_db"
prod:
flags:
- optimize
- telemetry
envs:
RUST_LOG: "warn"
DATABASE_URL: "postgres://prod.server/prod_db"
```