Ok.. now this makes more sense to me :-)
See here for how to block overwriting of artifacts.
https://stackoverflow.com/questions/6461152/how-can-i-prevent-previously-deployed-artifacts-from-being-overwritten
Christian
On 27.06.2017 09:28, Tom Quarendon wrote:
I'm not *wanting* to allow overwri
ristian Schneider
Sent: 27 June 2017 08:21
To: Tom Quarendon ; users@felix.apache.org
Subject: Re: API baselining with maven-bundle-plugin
Be very careful with overwriting a release version. It is easy to configure a
maven repository like artifactory to allow that but you will have problems in
other pl
Be very careful with overwriting a release version. It is easy to
configure a maven repository like artifactory to allow that but you will
have problems in other places.
The crucial problem is with the local maven repo. Maven updates
snapshots in a configurable way but it never updates release
ssage-
From: James Carman [mailto:ja...@carmanconsulting.com]
Sent: 23 June 2017 19:04
To: users@felix.apache.org
Subject: Re: API baselining with maven-bundle-plugin
Presumably, you'd also have your SCM system standing watch. You shouldn't be
able to recreate tags, for instance, an
> 2. If you have released version 1.0.0. (i.e. non-SNAPSHOT) of a bundle with
> Maven then you will be able to build another 1.0.0 locally, but you will not
> be able to release it again — this is a built-in feature of Maven. At this
> point you will be forced to bump your bundle version, so it
I get build failures unless I do. Perfect.
> > >
> > > This is what I'm trying to replicate, but in a project that wasn't
> > originally written with bndtools. I thought maven might be a simpler
> route
> > as it's used elsewhere, and I naively thou
might be a simpler route
> as it's used elsewhere, and I naively thought I might be able to do it
> using the bnd plugin for maven, since it exposes the baseline facility.
> >
> > Clearly I can't. Clearly my world view doesn't align with maven's.
> That&#x
ht I might be able to do it using the bnd
> plugin for maven, since it exposes the baseline facility.
>
> Clearly I can't. Clearly my world view doesn't align with maven's. That's
> fine.
>
> I will refocus my efforts on trying to do the same thing in gradl
sn't align with maven's. That's fine.
I will refocus my efforts on trying to do the same thing in gradle, where I
think I will have more success.
-Original Message-
From: Justin Edelson [mailto:jus...@justinedelson.com]
Sent: 23 June 2017 14:00
To: users@felix.apac
e maven bnd plugin appears to implement the latter.
> As far as I understand, bndtools implements the former, I *can* implement
> the former with bnd. It doesn't appear possible to implement the former
> with maven due to the way it works.
>
>
> -Original Message-
>
>
> 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
build process modify the source code, that just
>> doesn't seem right.
>>
>> I'm probably at odds with standard practice.
>>
>> -Original Message-
>> From: Justin Edelson [mailto:jus...@justinedelson.com]
>> Sent: 22 June 2017 17:40
>> T
ith maven due to
the way it works.
-Original Message-
From: Neil Bartlett [mailto:njbartl...@gmail.com]
Sent: 22 June 2017 18:52
To: users@felix.apache.org
Subject: Re: API baselining with maven-bundle-plugin
Are you sure that you’re actually *releasing* every day? Or do you only mea
Hi Justin,
> On Jun 23, 2017, at 4:11 AM, Justin Edelson wrote:
>
> So in that case, does the timestamp qualifier get automatically added on
> every build? Documentation pointers welcome :)
Warning: I am not so familiar with Maven...
The version number depends on how it is defined in the bnd
; > >> and only as necessary.
> > > >> I check out the source code, and then as I change code, it prompts
> me
> > > >> to change package and bundle versions appropriately.
> > > >> Hence after my edits, the package and version numbers of things I
;> Things that I've changed have changed version package and bundle
> > version numbers.
> > >> If I then do a "mvn deploy" (well, "gradle release") on the result,
> > >> then OK, the unchanged bundles will be re-released to the repository
> >
.
> >
> > -Original Message-
> > From: Justin Edelson [mailto:jus...@justinedelson.com]
> > Sent: 22 June 2017 17:40
> > To: users@felix.apache.org
> > Subject: Re: API baselining with maven-bundle-plugin
> >
> > The cadence of releases is irrelevant. But eac
have the build process modify the source code, that just
> doesn't seem right.
>
> I'm probably at odds with standard practice.
>
> -Original Message-
> From: Justin Edelson [mailto:jus...@justinedelson.com]
> Sent: 22 June 2017 17:40
> To: users@felix.apache.
o I want to have the build process modify the source code, that
> just doesn't seem right.
>
> I'm probably at odds with standard practice.
>
> -Original Message-
> From: Justin Edelson [mailto:jus...@justinedelson.com]
> Sent: 22 June 2017 17:40
> To: users@
ds with standard practice.
-Original Message-
From: Justin Edelson [mailto:jus...@justinedelson.com]
Sent: 22 June 2017 17:40
To: users@felix.apache.org
Subject: Re: API baselining with maven-bundle-plugin
The cadence of releases is irrelevant. But each release must have a distinct
(bundle)
erience of using maven etc, I was confused
> that it worked in an apparently different way to bndtools, which is based
> on the same thing.
>
>
>
> -Original Message-
> From: Justin Edelson [mailto:jus...@justinedelson.com]
> Sent: 22 June 2017 15:15
> To: users@felix.a
Behalf Of
Christian Schneider
Sent: 22 June 2017 17:07
To: Tom Quarendon
Subject: Re: API baselining with maven-bundle-plugin
See how we use the plugin is Aries rsa:
This is the plugin config:
https://github.com/apache/aries-rsa/blob/master/parent/pom.xml#L223-L247
The comparisonVersion is set t
See how we use the plugin is Aries rsa:
This is the plugin config:
https://github.com/apache/aries-rsa/blob/master/parent/pom.xml#L223-L247
The comparisonVersion is set to 1.9.0:
https://github.com/apache/aries-rsa/blob/master/parent/pom.xml#L28
Typically you set the baseline to the last releas
erience of using maven etc, I was confused that
it worked in an apparently different way to bndtools, which is based on the
same thing.
-Original Message-
From: Justin Edelson [mailto:jus...@justinedelson.com]
Sent: 22 June 2017 15:15
To: users@felix.apache.org
Subject: Re: API baselin
Hi,
I think you might be mixing up the bundle version (what I think you are
referring to as the "project version") with the package versions. baseline
is larger concerned with the latter, and only uses the former to find the
comparison version.
Released versions should always be considered immutab
I'm trying to set up api baselining using the maven-bundle-plugin.
I think I have it set up. I have messages coming out that say it's doing stuff.
So that's good.
Forgive my confusion though, but I don't understand how it is supposed to work.
I have published a 1.0.0 version of my bundle to the
26 matches
Mail list logo
