I don't need much convincing if it's easy! But I tried publishing a new release of Magnolia to Maven Central two weeks ago, and it failed, after having worked for about a year. My patience is close to zero. But if someone doesn't mind telling me what to do, I'll do it. :)
-
Ah, so no dependency except for a tool that's not yet released. That's a definition of "no dependency" I was previously unaware of :)
It's only for running the tests, so it shouldn't be published as a dependency. ;) (It had since been renamed...)
-
-
Right, but I'd have liked to run the tests before publishing anything :) The point's moot for the moment, because you do have at least one dependency that wasn't ported to 2.13: macro-compat
-
I suppose it's time to drop support for 2.11 and 2.10, if that was ever working...
- Show replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.