Re: Maven Web Site

Hi Jon, always intrested in improvements... can you make a JIRA issue and attach the patch to the issue ...so i can take a look within the next days... Kind regards Karl Heinz On 7/7/16 5:23 PM, Jon Harper wrote: Hello, is anyone interested in this very small change for fluido and doing an

Re: Is there a reason extensions in ".mvn/extensions.xml" don't seem to support configuration?

Oh, well I would have a use case for it. I am currently working on bringing more and more parts of Apache Flex from Ant to Maven. Here in a lot of places I have dependencies that are not yet available as Maven artifacts. While I managed to get in contact with quite some of the people

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Actually, for me the ideal would be a command line switch that could re-enable the feature that was deprecated. Then you don’t really have to wait a release, so long as it is documented. This makes sure user’s are aware since they have to take a minor action to continue to make things work.

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

On Thu, Jul 7, 2016 at 8:49 AM, Paul Benedict wrote: > If there is a change that will prevent a build from working, asking for > users@ testing is not the way to do this. The way to do this is to > introduce emit a "warning" first in the next version of Maven, and then >

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Christian, you are right that introducing a warning does delay delivering the fix. Thanks for pointing that out. With that said, it's not all that bad because there are some choices... 1) If 3.4-SNAPSHOT has a warning, make sure 3.5-SNAPSHOT has the fix enabled, and ask users@ to concurrently

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

Am 07/07/16 um 17:49 schrieb Paul Benedict: > If there is a change that will prevent a build from working, asking for > users@ testing is not the way to do this. The way to do this is to > introduce emit a "warning" first in the next version of Maven, and then > convert it to an "error" in the

Re: [jira] [Created] (MNG-6059) Important use cases not covered, as child.inherit.append.path affects all children

Wouldn't it be better to re-open MNG-5951? Does not make much sense to release 3.4 introducing this when there already is a ticket telling us it does not fit the needs. Regards, Am 07/07/16 um 12:14 schrieb Andreas Sewe (JIRA): > Andreas Sewe created MNG-6059: > -

Re: Preleminary Maven 3.4.0-SNAPSHOT Testing (Take 3)

If there is a change that will prevent a build from working, asking for users@ testing is not the way to do this. The way to do this is to introduce emit a "warning" first in the next version of Maven, and then convert it to an "error" in the next version after that. We can't just say to users

Re: Maven Web Site

Hello, is anyone interested in this very small change for fluido and doing an 1.6 release ? Jon Jon On Wed, Apr 27, 2016 at 7:05 PM, Jon Harper wrote: > Hi Karl, > congratulations on improving fluido and releasing fluido 1.5 in february. > > I tried enabling Bootstrap's

Re: 3.4.0-SNAPSHOT failure with findbugs Re: colorized Maven output

FYI Garvin just released the findbugs plugin 3.0.4 which solves this issue. Thanks Garvin On Fri, Jun 10, 2016 at 11:01 PM, Arnaud Héritier wrote: > yes it is exactly this one Stuart > > Thanks > > On Fri, Jun 10, 2016 at 10:46 PM, Stuart McCulloch >

[GitHub] maven-plugins pull request #87: Reintroduce verbose support for dependency:t...

Github user retomerz closed the pull request at: https://github.com/apache/maven-plugins/pull/87 --- 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-scm pull request #51: fix SCM-835 collision

GitHub user shvar opened a pull request: https://github.com/apache/maven-scm/pull/51 fix SCM-835 collision Please, see: https://issues.apache.org/jira/browse/SCM-835 You can merge this pull request into a Git repository by running: $ git pull https://github.com/shvar/maven-scm