marklogic-samplestack
marklogic-samplestack copied to clipboard
marklogic-community
Provide local.properties gradle mechanism
Provide mechanism for local.properties to override values in gradle.properties, for saner passwords for example
This goal was a stretch for 8.0-1 and not in scope initially. I'm setting to n/a because we should consider this for requirements of a next iteration, but probably best to cut from 8.0-1 scope at this point.
Can we use 9.0-1 vs. N/A? It helps me for planning to group things that have been pushed down the road.
Yes, absolutely -- your call. This issue/bug was Rob Rudin's idea, and a good one, but not one that was really considered for 8. It could even still be addressed in 8.0-1 timeframe probably, so you can choose where to put it and we can use time/scope to see if it goes into release.
Yes it is. Ultimately 9.0-1 is just a bucket milestone for planning - I'd like to see us separate out our milestone planning from the server and start tying to Samplestack 1.1, 1.2, etc pretty soon. Working through that.
Ok, I just didn't want us to cause a sync problem. Thanks for verifying.
This is an RFE to be sure. Rob Rudin had provided a method for doing this, and so I made this issue to follow up, but it was not part of original conception. Should not be in 8.0-2
I'm in discussion with Ganesh about BT and milestones so we can get some new ones here. Daphne is also persuing the idea of just not having BT integration for this project.
Changed the title -- it's about local.properties not local.gradle.
The idea is just to have a supplemental file, like gradle.properties that can contain sensitive info (passwords) but not be checked into git
would it be in a different directory than the rest of the Samplestack project?
I don't have any conception of implementation actually. There are a lot of ways to do this, and I've not looked at how Rob did it yet.