Continuing from https://issues.apache.org/jira/browse/BUILDR-274
Let's suppose that version ranged dependencies don't exist.
Let's also suppose that:
* Library A depends on Library C 1.0.
* Library B depends on Library C 1.1.
* The changes from C 1.0 to C 1.1 were done according to semver (all
li
On Sun, Oct 9, 2016 at 12:16 PM, Antoine Toulme wrote:
> Thank you for taking the time to write down your thoughts.
>
> BUILDR-274 is very much something we want to get to eventually.
>
> Maven supports version ranges. How they do it might be different from the
> behavior you describe. I need to
On Wed, Oct 12, 2016 at 7:02 PM, Antoine Toulme wrote:
> Good job Michael, I look forward to using the lock_jar gem in my projects.
>
> Trejkaz, is lock_jar covering your use case?
It does appear to and will be something I'll investigate. I'll also go
digging for whether the
> I’ve seen this happen with snapshots, but not with release builds. We banned
> snapshots at $work.
I have seen it happen with release builds of external projects too.
One time we even saw a POM change where the jar file didn't, and
amazingly, *that* was enough to break someone's build. (And tha
On Thu, Oct 13, 2016 at 3:00 PM, Antoine Toulme wrote:
> Interesting. Is Buildr behaving differently, better or worse?
I haven't been using Builder heavily and in a work setting yet,
because some jackass is blocking switching to it at work. I wish we
could switch...
In a hobby context, a few of
Hi all.
I have some command-line flags I want to get passed to Javadoc, but it
isn't entirely clear how to configure it.
What I'm trying to do:
-tag some.tag:X
-tag some.other.tag:X
The documented equivalent would seem to be:
doc tag: 'some.tag:X'
doc tag: 'some.other.tag:X'
B
