Re: releasing maven-shared-utils 3.1.0 with styled message API

ok, you convinced me: done styled content should be small, then the overhead to create some Strings should be really small... Regards, Hervé Le dimanche 17 juillet 2016 21:11:09 Robert Scholte a écrit : > On Sun, 17 Jul 2016 20:49:52 +0200, Christian Schulte > > wrote: > >

Re: svn commit: r1753099 - in /maven/plugins/trunk/maven-assembly-plugin/src/it/projects/basic-features: simple-dir-format/ this & that/

Hi Robert, I see, I will try to debug why the test is failing for spaces and special characters. How about naming the folder "space & special char" instead? It would make it clearer that this is the purpose of the test. Regards, Guillaume 2016-07-17 22:39 GMT+02:00 Robert Scholte

Re: svn commit: r1753099 - in /maven/plugins/trunk/maven-assembly-plugin/src/it/projects/basic-features: simple-dir-format/ this & that/

Hi, or those folders should be generated with a setup script during the invoker run... Kind regards Karl Heinz On 7/17/16 10:39 PM, Robert Scholte wrote: Hi Guillaume, there's a reason why this directory was called like this (spaces + special character). It is failing on my Windows machine

Re: svn commit: r1753099 - in /maven/plugins/trunk/maven-assembly-plugin/src/it/projects/basic-features: simple-dir-format/ this & that/

Hi Guillaume, there's a reason why this directory was called like this (spaces + special character). It is failing on my Windows machine too, but haven't investigated why it is failing, I think the Plexus Commandline doesn't like it... This should be reverted and fixed or excluded for

Re: releasing maven-shared-utils 3.1.0 with styled message API

On Sun, 17 Jul 2016 20:49:52 +0200, Christian Schulte wrote: Am 07/17/16 um 12:04 schrieb Robert Scholte: On Sun, 17 Jul 2016 09:49:39 +0200, Hervé BOUTEMY wrote: I worked on documentation to finish from my pov my work on this API:

Re: releasing maven-shared-utils 3.1.0 with styled message API

Am 07/17/16 um 12:04 schrieb Robert Scholte: > On Sun, 17 Jul 2016 09:49:39 +0200, Hervé BOUTEMY > wrote: > >> I worked on documentation to finish from my pov my work on this API: >> http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ >> >> I'd like to

Re: releasing maven-shared-utils 3.1.0 with styled message API

On Sun, 17 Jul 2016 19:12:35 +0200, Hervé BOUTEMY wrote: just keeping the option with Object will meaen that you must create a String to append it to the buffer: that's less memory-efficient What do you mean: you must create a String? Because in the end

Re: releasing maven-shared-utils 3.1.0 with styled message API

just keeping the option with Object will meaen that you must create a String to append it to the buffer: that's less memory-efficient if we stay with only one concept, let's remove the methods with Object that were suppose just to ease simple use cases Do you really want that? Regards, Hervé

Re: releasing maven-shared-utils 3.1.0 with styled message API

fixed thanks for the feedback Regards, Hervé Le dimanche 17 juillet 2016 11:19:44 Michael Osipov a écrit : > Am 2016-07-17 um 09:49 schrieb Hervé BOUTEMY: > > I worked on documentation to finish from my pov my work on this API: > >

[GitHub] maven-archetype pull request #10: Fix import order in ArchetypeConfiuration

Github user mryan43 closed the pull request at: https://github.com/apache/maven-archetype/pull/10 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

[GitHub] maven-archetype issue #10: Fix import order in ArchetypeConfiuration

Github user michael-o commented on the issue: https://github.com/apache/maven-archetype/pull/10 @mryan43 Please close the PR. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

Re: MNG-4800

On Sat, 16 Jul 2016 20:15:16 +0200, Christian Schulte wrote: Am 16.07.2016 um 15:40 schrieb Robert Scholte: I understand that every element has an original scope, but I wonder if it is useful in the tree. I'd say based on the scope(s) you get a certain tree, where scopes

[GitHub] maven-archetype issue #10: Fix import order in ArchetypeConfiuration

Github user michael-o commented on the issue: https://github.com/apache/maven-archetype/pull/10 Agreed. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or

[GitHub] maven-archetype issue #10: Fix import order in ArchetypeConfiuration

Github user mryan43 commented on the issue: https://github.com/apache/maven-archetype/pull/10 I just want to make it coherent with other source files in this project so that contributors can configure their IDE to order the imports properly and avoid unrelated changes due to

Re: releasing maven-shared-utils 3.1.0 with styled message API

On Sun, 17 Jul 2016 09:49:39 +0200, Hervé BOUTEMY wrote: I worked on documentation to finish from my pov my work on this API: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ I'd like to release maven-shared-utils 3.1.0 to start releasing plugins

[GitHub] maven-archetype issue #10: Fix import order in ArchetypeConfiuration

Github user michael-o commented on the issue: https://github.com/apache/maven-archetype/pull/10 Where is the need for this fix? `O` comes after `J`. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does

https://issues.apache.org/jira/browse/MNG-5895

Hi, so after I found the issue related to reactor order (MNG-6057) (Thanks Robert for the tip which brought me to right direction) now I'm diving more into the problem related to the resolution of the artifacts which I have described related to maven-assembly-plugin after more testing I have

[GitHub] maven-archetype pull request #11: Fix for ARCHETYPE-504

Github user AlesRybak closed the pull request at: https://github.com/apache/maven-archetype/pull/11 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the

Re: releasing maven-shared-utils 3.1.0 with styled message API

Am 2016-07-17 um 09:49 schrieb Hervé BOUTEMY: I worked on documentation to finish from my pov my work on this API: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ I'd like to release maven-shared-utils 3.1.0 to start releasing plugins with styled messages, and of course work

Re: releasing maven-shared-utils 3.1.0 with styled message API

Hi Hervé, I was to fast pushing on the send button ;-(. On 7/17/16 9:49 AM, Hervé BOUTEMY wrote: I worked on documentation to finish from my pov my work on this API: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ I'd like to release maven-shared-utils 3.1.0 to start

Re: releasing maven-shared-utils 3.1.0 with styled message API

Hi Hervé, On 7/17/16 9:49 AM, Hervé BOUTEMY wrote: I worked on documentation to finish from my pov my work on this API: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ I'd like to release maven-shared-utils 3.1.0 to start releasing plugins with styled messages, and of course

releasing maven-shared-utils 3.1.0 with styled message API

I worked on documentation to finish from my pov my work on this API: http://maven.apache.org/shared-archives/maven-shared-utils-LATEST/ I'd like to release maven-shared-utils 3.1.0 to start releasing plugins with styled messages, and of course work on releasing Maven 3.4.0-SNAPSHOT any