Hi,
> DEBUG/INFO/WARNING/ERROR schemes I'm thinking at:
> 1. bold cyan/bold green/bold yellow/bold red (initial)
> 2. bold cyan/bold blue/bold yellow/bold red (current)
> 3. cyan/blue/bold yellow/bold red (idea to have INFO less visible)
I prefer to use the standard console color (customised by u
Sorry guys, I did this while looking at a soccer match :) , not on my main
computer, then without communicating...
This one is a little bit like the Jenkins debate on the green vs blue bullet:
this time, this was a remark on MNG-3507 that bold green on every INFO was too
much... Then I found th
Hi,
the maven-artifat-transfer shared component needed to be released first
which is used by maven-assembly-plugin...
Kind regards
Karl Heinz Marbaise
On 6/15/16 12:07 AM, Olivier Lamy wrote:
Hi Anders,
Have you finished with assembly plugin?
As said last week I'd like to release it soon.
>
> There are still some open tickets.
>
Correction: There is currently one open registered ticket for the 3.0.0
release.
However there might be something more we should do for the 3.0.0 release,
as it gives us an opportunity to do changes that break backwards
compatibility. For example I'm think
Github user barthel commented on the issue:
https://github.com/apache/maven-integration-testing/pull/14
@michael-o I changed something based on your comments.
* Duplication of version number removed in
```mng-3092/filter-extensionpom.xml```
* Version number changed in JavaDoc o
Github user barthel commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67101198
--- Diff:
core-it-suite/src/test/resources/mng-3092/filter-extension/pom.xml ---
@@ -0,0 +1,74 @@
+
+
+
+
+http://maven
Hey all,
At work we're now making use of some custom AbstractMavenLifecycleParticipant's
declared in `.mvn/extensions.xml` and whilst our command line builds all work
flawlessly ( our own minor bugs withstanding ) I'm noticing that IntelliJ IDEA
won't resolve the project dependencies anymore (
Github user barthel commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67099834
--- Diff:
core-it-suite/src/test/resources/mng-3092/filter-extension/src/main/java/org/apache/maven/its/extensions/MavenITVersionRangeResultFil
There are still some open tickets.
/Anders (mobile)
On Jun 15, 2016 00:07, "Olivier Lamy" wrote:
> Hi Anders,
> Have you finished with assembly plugin?
> As said last week I'd like to release it soon.
> Let me know
> Cheers
> Olivier
>
> On 15 June 2016 at 06:18, Karl Heinz Marbaise wrote:
>
>
Dear Committers,
I'd kindly like to ask for consideration of my PR:
http://github.com/apache/maven-shared/pull/12
Regards
-Markus
GitHub user mkarg opened a pull request:
https://github.com/apache/maven-shared/pull/12
bug fix: silently fails overwriting symlinks
When A is an existing symlink to B, then createSymbolicLink(A,C) does
neither overwrite A->B by A->C (as expected in analogy to the behavior
of
Making the colors configurable seems like a lot of overhead for what is
otherwise fairly simple.
I’d recommend leaving the colors asis for now, get this out to let users
actually make use of it, and then consider adding complexity later to make
colors configurable.
I don’t see a clean way to m
Am 2016-06-15 um 00:03 schrieb Olivier Lamy:
On 15 June 2016 at 05:25, wrote:
Repository: maven
Updated Branches:
refs/heads/master ecdb0bc2b -> e7a783db1
[MNG-3507] keep green for success: INFO in blue (DEBUG is cyan)
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: htt
Hi Anders,
Have you finished with assembly plugin?
As said last week I'd like to release it soon.
Let me know
Cheers
Olivier
On 15 June 2016 at 06:18, Karl Heinz Marbaise wrote:
> Hi Anders,
>
> On 6/14/16 10:11 PM, Anders Hammar wrote:
>
>> Hm, has nobody even tried generating the site? I'm als
On 15 June 2016 at 05:25, wrote:
> Repository: maven
> Updated Branches:
> refs/heads/master ecdb0bc2b -> e7a783db1
>
>
> [MNG-3507] keep green for success: INFO in blue (DEBUG is cyan)
>
> Project: http://git-wip-us.apache.org/repos/asf/maven/repo
> Commit: http://git-wip-us.apache.org/repos/a
Am 2016-06-14 um 23:45 schrieb Robert Scholte:
too much fun to fix this.
http://svn.apache.org/viewvc?rev=1748472&view=rev should do the trick.
Still some doc updates required
Good! We still must take great care because throughout several places in
Aether and Maven coords format with colon m
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67063784
--- Diff:
core-it-suite/src/test/resources/mng-3092/filter-extension/src/main/java/org/apache/maven/its/extensions/MavenITVersionRangeResultF
too much fun to fix this.
http://svn.apache.org/viewvc?rev=1748472&view=rev should do the trick.
Still some doc updates required
Robert
On Tue, 14 Jun 2016 22:10:30 +0200, Robert Scholte
wrote:
On Tue, 14 Jun 2016 18:59:50 +0200, Michael Osipov
wrote:
Am 2016-06-14 um 17:34 schrieb
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67059400
--- Diff:
core-it-suite/src/test/resources/mng-3092/filter-extension/src/main/java/org/apache/maven/its/extensions/MavenITVersionRangeResultF
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67059367
--- Diff:
core-it-suite/src/test/resources/mng-3092/filter-extension/pom.xml ---
@@ -0,0 +1,74 @@
+
+
+
+
+http://mav
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67059339
--- Diff:
core-it-suite/src/test/resources/mng-3092/filter-extension/pom.xml ---
@@ -0,0 +1,74 @@
+
+
+
+
+http://mav
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67059081
--- Diff:
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3092VersionRangeResultFilterExtensionTest.java
---
@@ -0,0 +1,132 @@
Github user michael-o commented on a diff in the pull request:
https://github.com/apache/maven-integration-testing/pull/14#discussion_r67058999
--- Diff:
core-it-suite/src/test/java/org/apache/maven/it/MavenITmng3092VersionRangeResultFilterExtensionTest.java
---
@@ -0,0 +1,132 @@
Am 2016-06-14 um 22:46 schrieb Uwe Barthel:
Hi,
Is there a clear roadmap for version 3.4.0?
I ask, because these PRs: https://github.com/apache/maven/pull/70 (integration
tests: https://github.com/apache/maven-integration-testing/pull/14) for Item
https://issues.apache.org/jira/browse/MNG-309
Hi Paul,
> You can find the JIRA Maven Roadmap here:
> https://issues.apache.org/jira/browse/MNG/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
Thanks for the link that I already know.
I meant a roadmap in terms of a timeline.
Is the number of items already fixed?
-- barthe
You can find the JIRA Maven Roadmap here:
https://issues.apache.org/jira/browse/MNG/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
Cheers,
Paul
On Tue, Jun 14, 2016 at 3:46 PM, Uwe Barthel wrote:
> Hi,
>
> Is there a clear roadmap for version 3.4.0?
>
> I ask, because these
Hi,
Is there a clear roadmap for version 3.4.0?
I ask, because these PRs: https://github.com/apache/maven/pull/70 (integration
tests: https://github.com/apache/maven-integration-testing/pull/14) for Item
https://issues.apache.org/jira/browse/MNG-3092.
This item lives around NINE years and thes
Github user barthel commented on the issue:
https://github.com/apache/maven/pull/70
I would like to look at ```ContextualSnapshotVersionFilter``` solution, if
the Aether code was moved back to Apache Maven.
---
If your project is set up for it, you can reply to this email and have yo
Hi Anders,
On 6/14/16 10:11 PM, Anders Hammar wrote:
Hm, has nobody even tried generating the site? I'm also seeing several
warnings among which a missing version for a reporting plugin...:-(
The warnings are a known problem in Maven 3.0.5...based on the usage
pluginManagement related to repo
Hi,
We solved 1 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12336063
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priori
Hm, has nobody even tried generating the site? I'm also seeing several
warnings among which a missing version for a reporting plugin...:-(
/grumpy
On Tue, Jun 14, 2016 at 10:06 PM, Karl Heinz Marbaise
wrote:
> Hi Anders,
>
> you need to upgrade maven-fluidoe to at least 1.5 to get it working...
On Tue, 14 Jun 2016 18:59:50 +0200, Michael Osipov
wrote:
Am 2016-06-14 um 17:34 schrieb Robert Scholte:
I think we're making it ourself very hard if we keep supporting :jar.
I would have read it as any groupId + artifactId='jar'.
Instead with 3.0 we should switch to the patterns as defined
Hi Anders,
you need to upgrade maven-fluidoe to at least 1.5 to get it working...
Kind regards
Karl Heinz
On 6/14/16 10:00 PM, Anders Hammar wrote:
I'm getting an error when building Maven site (mvn site) for
maven-assembly-plugin trunk:
[INFO] <<< maven-plugin-plugin:3.4:report @ maven-assemb
I'm getting an error when building Maven site (mvn site) for
maven-assembly-plugin trunk:
[INFO] <<< maven-plugin-plugin:3.4:report @ maven-assembly-plugin <<<
[INFO] Relativizing decoration links with respect to localized project URL:
https://maven.apache.org/plugins/maven-assembly-plugin/
[INFO]
Am 2016-06-14 um 17:34 schrieb Robert Scholte:
I think we're making it ourself very hard if we keep supporting :jar.
I would have read it as any groupId + artifactId='jar'.
Instead with 3.0 we should switch to the patterns as defined by
Aether[1]; no need to maintain assembly specific patterns, u
I think we're making it ourself very hard if we keep supporting :jar.
I would have read it as any groupId + artifactId='jar'.
Instead with 3.0 we should switch to the patterns as defined by Aether[1];
no need to maintain assembly specific patterns, use them as is with Aether.
WDYT?
Robert
[1]
>
> Therefore, it is a change in a major version.
Sure, but that's not the problem I see. I think we're moving away from
convention over configuration as there is now no default release profile
but the end user needs to configure one. Not too happy about that.
> Do you care to create an issue f
37 matches
Mail list logo
