without using SNAPSHOT
> >> > dependencies you will need to find a solution for this. You could use
> >> > version ranges, but then you are not much different then using
> SNAPSHOT
> >> > builds. This is one of the main reasons why we are doing manual
> &g
t; version ranges, but then you are not much different then using SNAPSHOT
>> > builds. This is one of the main reasons why we are doing manual
>> releases -
>> > and managing the dependency versions by hand.
>> >
>> > Gruss
>> > Bernd
>> >
uss
> > Bernd
> > --
> > http://bernd.eckenfels.net
> >
> > From: Eric Benzacar
> > Sent: Thursday, November 16, 2017 5:05:45 AM
> > To: Maven Users List
> > Cc: i...@soebes.de
> > Subject: Re: Special parame
fels.net
>
> From: Eric Benzacar
> Sent: Thursday, November 16, 2017 5:05:45 AM
> To: Maven Users List
> Cc: i...@soebes.de
> Subject: Re: Special parameters - sha1
>
> I'm not sure what you mean when you say:
>
> "How ar
From: Eric Benzacar
Sent: Thursday, November 16, 2017 5:05:45 AM
To: Maven Users List
Cc: i...@soebes.de
Subject: Re: Special parameters - sha1
I'm not sure what you mean when you say:
"How are you planning to deal with the changed version numbers of
dependencies?"
At whic
s.net
>
> From: Eric B
> Sent: Wednesday, November 15, 2017 4:30:06 AM
> To: i...@soebes.de; Maven Users List
> Subject: Re: Special parameters - sha1
>
> Hi,
>
> Thanks for the additional insight. I think I understand better now how
>
, November 15, 2017 4:30:06 AM
To: i...@soebes.de; Maven Users List
Subject: Re: Special parameters - sha1
Hi,
Thanks for the additional insight. I think I understand better now how
this works. I'll try to explain my use case, and perhaps someone can
provide some ideas for best practices.
I star
Hi,
Thanks for the additional insight. I think I understand better now how
this works. I'll try to explain my use case, and perhaps someone can
provide some ideas for best practices.
I started a pom refactoring because I wanted to add the enforcer-plugin for
a release candidate to ensure there
Hi,
I will give some more details cause I have created the docs /
implementation and you mentioned my blog ;-)..
On 14/11/17 03:12, Eric B wrote:
Following a long thread on this list, and a blog by khmarbaise (
http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
.2.3${revision}${changelist}
Gruss
Bernd
--
http://bernd.eckenfels.net
From: Eric B
Sent: Tuesday, November 14, 2017 4:16:08 AM
To: Maven Users List
Subject: Re: Special parameters - sha1
Bernd,
Is my understanding correct though? These three properties cannot con
gt; else)
>
> Gruss
> Bernd
> --
> http://bernd.eckenfels.net
>
> From: Eric B
> Sent: Tuesday, November 14, 2017 3:12:21 AM
> To: Maven Users List
> Subject: Special parameters - sha1
>
> Following a long thread on this list, and
:21 AM
To: Maven Users List
Subject: Special parameters - sha1
Following a long thread on this list, and a blog by khmarbaise (
http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
I'm still a little confused as to exactly what is allowed in the special
version tags
Following a long thread on this list, and a blog by khmarbaise (
http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
I'm still a little confused as to exactly what is allowed in the special
version tags for a maven pom.
I know and realize that the 3 allowable tags are:
13 matches
Mail list logo
