Closed opalfroot closed 7 years ago
How is this different from the BuildPath
?
The BuildPath is where the binary goes and the BuildTargetPath is where the source resides - ie look here for buildable code.
The idea behind this is you can specify a specific package to rebuild on change and you dont need to rely on having a main somewhere at the top level. This is a likely scenario for people building cli's and web services in the same codebase using shared middle code.
In that case, couldn't we use the AppRoot
config setting instead of adding a new one?
That wouldn't really work. That setting is used by the walker which needs to know about all the code you have in your project - not just the build target directory.
Merged! Thanks!
Thank you!
From: Mark Bates notifications@github.com Sent: 29 June 2017 21:55 To: markbates/refresh Cc: opalfroot; Author Subject: Re: [markbates/refresh] Allow users to specify a build target directory - useful if for examp… (#12)
Merged! Thanks!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/markbates/refresh/pull/12#issuecomment-312106046, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ACG7VByohT39qoQ9WAdA60FYww7sXxPqks5sJA8_gaJpZM4OIEJ_.
This small changes allows users to specify a build target path. I find this useful in cases where my project has many modules and I'd like to be able to specify the path of say a REST service to be rebuild and run.