Although a version number property could be used, too, with appropriately simple build configuration instructions. I know Maven supports it for <scope>import</> at least.
On 9 January 2017 at 21:47, Matt Sicker <boa...@gmail.com> wrote: > Ok, I think it would've been annoying to match the version numbers. > However, each version of Log4j Boot will need to be released with updated > versions of Log4j anyways. > > On 9 January 2017 at 21:45, Apache <ralph.go...@dslextreme.com> wrote: > >> Please don’t try to match the Log4j version numbers. That would mean we >> would have to release them along with each Log4j release, which probably >> won’t be necessary. >> >> I would make the first release -beta, unless you think the first 1.0 >> release will be where it needs to be. >> >> Ralph >> >> On Jan 9, 2017, at 8:39 PM, Matt Sicker <boa...@gmail.com> wrote: >> >> So I'm going to go with this name as it's pretty self-explanatory what >> it's for. >> >> https://git-wip-us.apache.org/repos/asf/logging-log4j-boot.git >> >> Quick question: should these version numbers match the log4j versions? Or >> can this follow its own versioning scheme starting with 1.0? >> >> -- >> Matt Sicker <boa...@gmail.com> >> >> >> > > > -- > Matt Sicker <boa...@gmail.com> > -- Matt Sicker <boa...@gmail.com>
