search

aardvark-platform / aardvark.build

MIT License
0 stars 0 forks source link

Changes needed for flexible RELEASE_NOTEST/version #2

Open haraldsteinlechner opened 2 years ago

haraldsteinlechner commented 2 years ago

what would be needed to aardvark.build and aardpack not depend on release_notes.md. use case: have 2 release_notes since it is used to build a product as well as packages.

in aardpack it could be a command line arg? in the msbuild target as well?

krauthaufen commented 2 years ago

You could put them in separate directories and set the <RepositoryRoot> property in msbuild to one or the other folder

haraldsteinlechner commented 2 years ago

just checked, no does not work, since native dependency injection should be separate and independent of the release_notes file. i think best way is make release_notes_path property of msbuild task and argument to the tool can give it a try if this is the way to go