Hi guys, I've got to say it's a good idea to keep configuration in MANIFEST.MF
I've tried to follow your instruction but didn't run well on my environment.
I'm going to describe the structure of my project and what problems I met.
root-app
| -- pom.xml
| -- core-app
| | -- src
| | ` -- main
| | ` -- java
| | ` -- Configuration.java
| ` -- pom.xml
` -- web-app
| -- src
| ` -- main
| | -- java
| ` -- resources
| ` -- META-INF
| ` -- MANIFEST.MF
` -- pom.xml
As you see, I have 2 projects : core-app and web-app.
What I want to do is quite simple:
- Set configuration(Key-Value) into web-app's MANIFEST.MF while packaging phase.
- Read configuration in core-app's Configuration class.
I'm not sure whether it's clear for you.
Willing to discuss with you, thank you.
Hi guys, I've got to say it's a good idea to keep configuration in MANIFEST.MF
I've tried to follow your instruction but didn't run well on my environment.
I'm going to describe the structure of my project and what problems I met.
As you see, I have 2 projects : core-app and web-app.
What I want to do is quite simple:
I'm not sure whether it's clear for you.
Willing to discuss with you, thank you.