OK, I tried something new.
*Goal*: all the plugins in one Git repo (less CI jobs to set up - just one
recursive multi-module maven build).
*Constraint*: Plugins must be independently releasable.
*Test:* Take two modules from the Svn repo and check them in to master (the
rest were deleted - test
Hi Petar,
This is a clear sign that ${project} should not be used to resolve this.
Instead the pom should be analyzed again and if there's a system property
matching the parent, it should be replaced before loading the parent.
That'll require quite some new lines of code :)
The suggested
Petar Tahchiev wrote:
> Hey guys,
>
> my pull-request worked fine to not show the prompt to specify a version.
> However, it fails to update snapshot dependency versions when you resolve
> the parent to a concrete version.
> Particularly in my case:
>
>
> [BOM]
>
Hey guys,
my pull-request worked fine to not show the prompt to specify a version.
However, it fails to update snapshot dependency versions when you resolve
the parent to a concrete version.
Particularly in my case:
[BOM]
/\
