For the current case, maven-release-plugin correctly pick up
plexus-utils-3.0.10 since it is locked by maven-release's
dependencyManagement. This is the correct behavior
To fix this issue at project/consumer level, one must have pluginManagement
to pick up the correct plexus-util (3.0.15)
-Dan
+1
On 12 October 2015 at 05:20, Karl Heinz Marbaise wrote:
> Hi,
>
> +1 ...
>
> Kind regards
> Karl Heinz Marbaise
>
> On 10/11/15 2:56 AM, Benson Margulies wrote:
>
>> Hi,
>>
>> 2 changes in JIRA. Many other commits.
>>
>>
>> ** Bug
>> * [MPOM-88] - yyy-LATEST deployment URL breaks site pa
On Oct 11, 2015 6:59 PM, "Dan Tran" wrote:
> Hi all, according to my understanding, maven uses depManagement to lock
> down and version.
>
>
just sets defaults for version, scope, optional, and
exclusions. It doesn't 'lock' any more than writing the same things in the
regular dependency element
My solution would be to upgrade
maven-parent Version in maven-release POM if you want to release the fix in
maven-release-plugin:3.0 as marked in MRELEASE-907.
Or if you want to release 2.5.3 then yes the dependencyManagement would be
the way to go and the target version in MRELEASE-907 change from
Hi all, according to my understanding, maven uses depManagement to lock
down and version.
If it not so, it is a very serious miss understanding for lots of users
Can someone confirm?
-Dan
On Sun, Oct 11, 2015 at 1:07 PM, Benson Margulies
wrote:
> Tibor, I don't understand. Normally, the mave
On Sun, Oct 11, 2015 at 6:54 PM, Karl Heinz Marbaise wrote:
> Hi Benson,
>
> sorry...oversight this..my fault...
I don't know why you are apologizing; the JIRA needed fixing, I fixed it.
>
> (It is too late)..
>
> Kind regards
> Karl Heinz Marbaise
> On 10/12/15 12:38 AM, Benson Margulies wrote:
Hi Benson,
sorry...oversight this..my fault...
(It is too late)..
Kind regards
Karl Heinz Marbaise
On 10/12/15 12:38 AM, Benson Margulies wrote:
As far as I knew, JIRA would only include resolved issues in a
release. it used to complain if an unresolved issue was tagged with a
release that one
As far as I knew, JIRA would only include resolved issues in a
release. it used to complain if an unresolved issue was tagged with a
release that one was releasing.
The log shows that Robert did this. So I marked it resolved in JIRA.
---
Question of homogeneity only.
Thx for explanation, Herve.
On Sun, Oct 11, 2015 at 11:02 PM, Hervé BOUTEMY
wrote:
> this was done when reporting-api went out from Maven 3.0 core: before, it
> was
> a core API [1]
>
> but the API, which is really basic and only an API, did not change year
> after
I am confused and away from my computer. I will try to clarify later
On Oct 11, 2015 5:57 PM, "Karl Heinz Marbaise" wrote:
> Hi Benson,
>
> On 10/11/15 11:39 PM, Benson Margulies wrote:
>
>> Hey, I just assume that the JIRAs are correct. What component do you
>> think it should be?
>>
>
> sorry i
Hi Benson,
On 10/11/15 11:39 PM, Benson Margulies wrote:
Hey, I just assume that the JIRAs are correct. What component do you
think it should be?
sorry i couldn't read...So the question is: Is this completely done or
not? Based on the jira it is not and neither based on the svn history...
S
Hey, I just assume that the JIRAs are correct. What component do you
think it should be?
On Sun, Oct 11, 2015 at 4:51 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> If i take a look into JIRA there are 4 issues in 3.0 release...
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=123179
this was done when reporting-api went out from Maven 3.0 core: before, it was
a core API [1]
but the API, which is really basic and only an API, did not change year after
year.
Do you see some precise issues to solve (fear of loss of compatibility with
newer JREs, for example), or is it just a
sorry, I won't be at this one :(
I hope you'll have fun together
Regards,
Hervé
Le dimanche 11 octobre 2015 20:00:33 Robert Scholte a écrit :
> Hi,
>
> this I will be visiting Java One. Based on my experiences with other
> events this year I know that it is always good to meet other teammember
Hi,
If i take a look into JIRA there are 4 issues in 3.0 release...
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12331490
is MSHARED-420 wrongly assigned to maven-dependency-tree 3.0, cause it
is not part of the release nor it is it ready ?
Kind regards
Hi,
Note: This is a Maven 3.0 / JDK 6 release
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12333677
There are several issue open:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20ORDER%20BY%
Tibor, I don't understand. Normally, the maven core 'rounds up' to the
highest dependency called for by all the things in the dependency
tree. Specifying a version does not 'lock it down'. If release depends
on 3.0.10, and also depends on SCM that depends on 3.0.15, I'd expect
15 to be used. Is the
maven-reporting-api already has Version 3.0 which was built with JDK 1.4
5 years ago.
Does not fit to current movement to Maven 3.0.
How we will upgrade this artifact?
Hi,
based on a discussion with Hervé and a mistake of mine i have to cancel
the VOTE...i will respin a new one ...
Kind regards
Karl Heinz Marbaise
On 10/11/15 9:32 PM, Karl Heinz Marbaise wrote:
Hi,
I need one more binding VOTE...for the release...
Kind regards
Karl Heinz Marbaise
On 10/8
Hi,
I need one more binding VOTE...for the release...
Kind regards
Karl Heinz Marbaise
On 10/8/15 11:55 AM, Karl Heinz Marbaise wrote:
Hi,
Note: This is a Maven 3.0 / JDK 6 release
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12333677
If you fix it in maven-release's dependencyManagement then overriding
parent deps may introduce a new issue in the future on missing upgrades on
the parent.
Maybe worse for POM clarity.
On Sun, Oct 11, 2015 at 9:23 PM, Dan Tran [via Maven] <
ml-node+s40175n5848418...@n5.nabble.com> wrote:
> Dont
Dont think it is maven core issue, maven-release parent's
dependencyManagment locks plexus-utils to 3.0.10.
May as well fix up maven-release's dependencyManagement to cover all other
dependencies
-D
On Sun, Oct 11, 2015 at 12:07 PM, Tibor Digana
wrote:
> The problem is that plexus-utils:3
The problem is that plexus-utils:3.0.10 does not have
org/codehaus/plexus/util/xml/
pull/EntityReplacementMap
It starts since 3.0.13. Maybe 3.0.12 which is missing in my repo.
On Sun, Oct 11, 2015 at 9:02 PM, Benson Margulies [via Maven] <
ml-node+s40175n5848412...@n5.nabble.com> wrote:
> The ful
The fully-document JIRA is MRELEASE-925.
On Sun, Oct 11, 2015 at 3:00 PM, Benson Margulies wrote:
> This is presumably a core issue, won't someone comment who delves into
> that part of the salt mine?
>
>
> On Sun, Oct 11, 2015 at 2:57 PM, Dan Tran wrote:
>> I encounter the same issue and filed
This is presumably a core issue, won't someone comment who delves into
that part of the salt mine?
On Sun, Oct 11, 2015 at 2:57 PM, Dan Tran wrote:
> I encounter the same issue and filed at
> https://issues.apache.org/jira/browse/MRELEASE-907
>
> -D
>
> On Sat, Oct 10, 2015 at 5:43 PM, Benson Ma
I encounter the same issue and filed at
https://issues.apache.org/jira/browse/MRELEASE-907
-D
On Sat, Oct 10, 2015 at 5:43 PM, Benson Margulies
wrote:
> I see that the bad version of plexus-utils is called out in the
> maven-release parent pom. I patched it in place in my local repo, and
> now
On Sun, Oct 11, 2015 at 2:36 PM, Tibor Digana wrote:
> @Benson, what about to join together with Robert and help him. I guess he
> is going to make a lot of work on our plugins in SNAPSHOT Versions and
> testing them all over again. Then you may utilize your time in Maven one
> way or another as y
@Benson, what about to join together with Robert and help him. I guess he
is going to make a lot of work on our plugins in SNAPSHOT Versions and
testing them all over again. Then you may utilize your time in Maven one
way or another as you always wanted.
Other activity i.e. development than your am
Hi,
+1 ...
Kind regards
Karl Heinz Marbaise
On 10/11/15 2:56 AM, Benson Margulies wrote:
Hi,
2 changes in JIRA. Many other commits.
** Bug
* [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference menu
* [MPOM-89] - Unbalanced versions of Maven Invoker Plugin
There are
-1 (non-binding): I have to require maven-shared-utils:3.0 in dependency
tree. Sorry!
On Sun, Oct 11, 2015 at 12:58 PM, Benson Margulies [via Maven] <
ml-node+s40175n5848358...@n5.nabble.com> wrote:
> I was clearly up too late.
>
> On Sun, Oct 11, 2015 at 6:46 AM, Karl Heinz Marbaise <[hidden em
Hi,
this I will be visiting Java One. Based on my experiences with other
events this year I know that it is always good to meet other teammembers
and users of Maven.
Who else is going and wants to meet somewhere during the event?
cheers,
Robert
-
+1
Regards,
Hervé
Le samedi 10 octobre 2015 20:56:10 Benson Margulies a écrit :
> Hi,
>
> 2 changes in JIRA. Many other commits.
>
>
> ** Bug
> * [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference
> menu * [MPOM-89] - Unbalanced versions of Maven Invoker Plugin
>
> There
Just writing for myself, I want to explain why I am pushing just a bit.
I can justify spending time on Maven because I can, amongst other
things, solve some practical problems for my colleagues. If we hit a
plugin issue, I can (usually) fix it, fix whatever other low-hanging
items are in the JIRA
I was clearly up too late.
On Sun, Oct 11, 2015 at 6:46 AM, Karl Heinz Marbaise wrote:
> Hi Benson,
>
> as i already mentioned
>
> -0 from me based on the missing upgrade to maven-shared-utils-3.0.0 ...which
> can only be a few days in worst case...so i don't see a reason for that rush
> at the
Hi Benson,
as i already mentioned
-0 from me based on the missing upgrade to maven-shared-utils-3.0.0
...which can only be a few days in worst case...so i don't see a reason
for that rush at the moment...
On 10/11/15 2:12 AM, Benson Margulies wrote:
Hi,
We solved 5 issues:
https://issues
I guess I swapped two of them in reading the email. I will unwind.
On Oct 11, 2015 1:53 AM, "Tibor Digana" wrote:
> @Benson
> That's good that you take this responsibility but I guess you rush too much
> with this artifact since we still use the old maven-shared-utils:0.7 in it.
> Normally I am t
+1 (non-binding) Here is mine.
contains maven-parent:27
On Sun, Oct 11, 2015 at 2:56 AM, Benson Margulies
wrote:
> Hi,
>
> 2 changes in JIRA. Many other commits.
>
>
> ** Bug
> * [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference
> menu
> * [MPOM-89] - Unbalanced versions
+1
11. okt. 2015 2.56 a.m. skrev "Benson Margulies" :
> Hi,
>
> 2 changes in JIRA. Many other commits.
>
>
> ** Bug
> * [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference
> menu
> * [MPOM-89] - Unbalanced versions of Maven Invoker Plugin
>
> There are no pending issues I ca
I keep changing the method signatures from time to time if I discover
there's a better way.
Once released we shouldn't touch method signatures anymore.
It's a matter of rewriting plugins and testing to confirm that all works
as intended.
Robert
Op Sat, 10 Oct 2015 23:58:58 +0200 schreef Tib
Am 2015-10-11 um 02:56 schrieb Benson Margulies:
Hi,
2 changes in JIRA. Many other commits.
** Bug
* [MPOM-88] - yyy-LATEST deployment URL breaks site parent reference menu
* [MPOM-89] - Unbalanced versions of Maven Invoker Plugin
There are no pending issues I can find in JIRA for t
I will call a new Vote later - maybe tomorrow or tonight.
Meanwhile we have a chance to get TestNG 6.9.7 with a fix we need in
Surefire.
After a discussion with Cedric Beust he is decided to cut the TestNG
Version 6.9.7 soon.
Meanwhile I will wait and prepare an update of Surefire documentation
ref
41 matches
Mail list logo
