Presumably, you'd also have your SCM system standing watch. You shouldn't
be able to recreate tags, for instance, and any good release process should
include tagging of your released artifacts. Obviously, someone can delete
tags, but that should be frowned upon.
On Fri, Jun 23, 2017 at 1:54 PM
>
> you will be able to build another 1.0.0 locally, but you will not be able
> to release it again
I think that depends on particular Maven repository and it's configuration.
While this is probably true for Central (not sure but would assume so) a
local Nexus repo can be configured to allow
Hi Tom,
I’m very glad that you’re enjoying the baselining feature of Bndtools so much!
I think your expectations are reasonable but we just aren’t quite there with
bnd/Maven integration.
Bndtools is able to give you immediate baselining errors, but it currently only
works when bndlib is
So here's what I've just done in bndtools.
Created a project that has three bundles in it, test.api, test.command,
test.provider. All versions (package, bundle) are initialised to 1.0.0.
Set up the project so that it will release to a maven repository.
Run the "gradle release" command line
On Fri, Jun 23, 2017 at 3:23 AM Tom Quarendon <
tom.quaren...@worldprogramming.com> wrote:
> I get immutable releases. I'm not trying to redefine what 1.0.0 is with
> different source code. In fact quite the opposite. I want it to *prevent me
> from doing do*. The maven bnd plugin doesn't
>
>
>
>
> It's the difference between:
> "I'm trying to build something that the user wants to call 1.0.0. As
> part of that process I'll check whether it conflicts with what is currently
> 1.0.0, and if it does I'll fail, not actually creating the artefact at all,
> and suggest that they change the
I was having a similar problem, but I resolved it a bit differently.
I don’t use Maven, but the way I resolved this was to enforce this behaviour on
my Nexus repository. So, when I release from the CI server to the remote repo,
bnd does not care. If the artefact already exists, it just doesn’t
I get immutable releases. I'm not trying to redefine what 1.0.0 is with
different source code. In fact quite the opposite. I want it to *prevent me
from doing do*. The maven bnd plugin doesn't
It's the difference between:
"I'm trying to build something that the user wants to call 1.0.0. As
8 matches
Mail list logo
