Re: svn commit: r630418 - /maven/plugins/trunk/maven-site-plugin/pom.xml

Yes, I know. I previously made the change in the classes copied from plexus-utils. This change is here only to track the plexus-utils version where the original modifications are. Selon Dennis Lundberg [EMAIL PROTECTED]: The site plugin still has a prerequisite of Maven 2.0.2, so this change

Re: Mevenide vs. M2Eclipse, Q for Eclipse/IAM

Since the question of choosing an Eclipse Integration is often asked, I just worked on the Eclipse Integration page from Maven Users Wiki: http://docs.codehaus.org/display/MAVENUSER/Eclipse+Integration I started a comparison matrix with basic project informations. This Wiki is public: feel free

Re: metadata schema was: [vote] Maven 2.1.0

this was added in r745216, when upgrading to Modello 1.0: see [1] for the precise modification. Selon Brett Porter br...@apache.org: Hmm, why was this added? The modello-maven-plugin is configured to generate an XML Schema, then I had to add the xml.schemaLocation configuration to avoid a

Re: svn commit: r894080 - /maven/maven-2/branches/maven-2.2.x/maven-model/src/main/mdo/maven.mdo

ok, I understand your concern: I'll revert immediately the change in 2.2.x branch, and let's discuss a little bit to decide if I revert it in 3.x too :) The good question: what is the gain by this change? I think the order we, the Maven project, chose one year ago is well thought after a long

Re: svn commit: r894080 - /maven/maven-2/branches/maven-2.2.x/maven-model/src/main/mdo/maven.mdo

+1 for a canonical POM ordering of elements we could check it as an enforcer rule (activated by people interested in it). We need a tool too to help reorder the POM. Sorry, I don't have time to work on it for the moment, but definetely +1 :) Regards, Hervé - Mail Original - De: Paul

Re: [VOTE] Release Apache Parent POM 7

+1 Hervé - Mail Original - De: Arnaud HERITIER aherit...@gmail.com À: Maven Developers List dev@maven.apache.org Envoyé: Lundi 28 Décembre 2009 10h04:58 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [VOTE] Release Apache Parent POM 7 +1 Arnaud Héritier

Re: Fail to read plugin descriptor: mvn3 regression?

Hi Baptiste, Seems like Maven 2 still has a bug in XML encoding support, incorrectly using platform encoding when it should detect the encoding from the plugin.xml file. If Maven 2 can read such a malformed XML file, the bug is in Maven 2, not Maven 3: I'll have to track and fix it. Please open

Re: [VOTE] Release Surefire version 2.6

+1 Hervé - Mail Original - De: Olivier Lamy ol...@apache.org À: Maven Developers List dev@maven.apache.org Envoyé: Jeudi 12 Août 2010 22h37:27 GMT +01:00 Amsterdam / Berlin / Berne / Rome / Stockholm / Vienne Objet: Re: [VOTE] Release Surefire version 2.6 +1 2010/8/10 Stephen Connolly

Re: Sonatype-Aether Project on github.com

maven-aether-provider is in Maven-3 in github: http://github.com/bentmann/maven-3 it contains Maven-specific code, particularly everything to read Maven's pom.xml and maven-metadata.xml from remote repository. It is an intended dependency, since aether is a repository/dependency container with

Re: [VOTE] Release Apache Parent POM 10

whoops, sorry for the wrong link for the diff, it is available from the site: that's one of the new features (even if not really built into the pom itself) Regards, Hervé - Brett Porter br...@apache.org a écrit : On 07/08/2011, at 8:14 AM, Hervé BOUTEMY wrote: Staging repo:

Re: [VOTE] Release Apache Parent POM 10

here is my +1 Hervé - Olivier Lamy ol...@apache.org a écrit : +1 2011/8/7 Hervé BOUTEMY herve.bout...@free.fr: Hi, This project consists of a POM that contains settings that are likely to be useful to any Apache project that is building and releasing code with Maven 2/3.

[RESULT][VOTE] Release Apache Parent POM 10

Hi, The vote has passed with the following result: +1 (binding): Brett Porter, Olivier Lamy, Mark Struberg, Stephen Connolly, Kristian Rosenvold, Emmanuel Venisse, Hervé Boutemy +1 (non binding): I will promote the artifacts to the central repo. Regards, Hervé

Re: [VOTE] Release Maven Checkstyle Plugin version 2.7

+1 Hervé - Olivier Lamy ol...@apache.org a écrit : Hi, We solved 6 issues: https://jira.codehaus.org/secure/ReleaseNote.jspa?version=16773styleName=TextprojectId=11127Create=Create Staging repo: https://repository.apache.org/content/repositories/maven-005/ Staging site:

Re: [VOTE] Tony Chemit as Apache Maven committer

+1 Hervé - Mail original - De: Lukas Theussl ltheu...@apache.org À: Maven Developers List dev@maven.apache.org Envoyé: Samedi 7 Juillet 2012 04:34:16 Objet: Re: [VOTE] Tony Chemit as Apache Maven committer +1 -Lukas On Fri, Jul 6, 2012 at 11:28 PM, Olivier Lamy ol...@apache.org

Re: [VOTE] Release Maven Parent pom 22, Maven Plugins Parent pom 23, Maven Shared Components 18

+1 Hervé - Mail original - De: Olivier Lamy ol...@apache.org À: Maven Developers List dev@maven.apache.org Envoyé: Vendredi 10 Août 2012 15:52:05 Objet: [VOTE] Release Maven Parent pom 22, Maven Plugins Parent pom 23, Maven Shared Components 18 Hi, I'd like to release: * Maven Parent

Re: [VOTE] Maven Shared Filtering 1.1 - Maven Script Interpreter 1.1 - Maven Invoker Plugin 1.7

+1 Hervé - Mail original - De: Stephane Nicoll stephane.nic...@gmail.com À: Maven Developers List dev@maven.apache.org Envoyé: Vendredi 10 Août 2012 06:56:41 Objet: [VOTE] Maven Shared Filtering 1.1 - Maven Script Interpreter 1.1 - Maven Invoker Plugin 1.7 Hi, In order to release the

Re: [VOTE] Release Maven Reporting Exec version 1.1

see http://svn.apache.org/r1467751 for an exemple of m-site-p dependency configuration to test the component - Mail original - De: Hervé BOUTEMY herve.bout...@free.fr À: dev@maven.apache.org Envoyé: Dimanche 14 Avril 2013 10:10:41 Objet: [VOTE] Release Maven Reporting Exec version 1.1

Re: move maven core to java 7?

I created MNG-5780 to track the change I let the issue open, because I hope that we won't have to revert the commit after someone steps in with a strong reason not to upgrade But in 48h, if nobody votes -1 woth a strong issue, I'll close the issue and point to the (a little bit too quick at

Re: Maven 3.0.5 Problem

Hi, It's a known wrong and misleading message, tracked as MNG-5477 Regards, Hervé - Mail original - De: Karl Heinz Marbaise khmarba...@gmx.de À: Maven Developers List dev@maven.apache.org Envoyé: Vendredi 6 Mars 2015 09:32:01 Objet: Maven 3.0.5 Problem Hi, during the tests of maven

Re: [IMPORTANT NOTICE] Jira migration from Codehaus to Apache on April 4th

Archiva, Continuum and Groovy have only 1 Jira project each: creating groups is not useful, since adding someone to the group is equivalent to adding to the project role. Since adding someone to Jira project role can be done by project members, but adding someone to a Jira group will require

Re : ASF Jira Issues

I checked SCM configuration: permissions were ok, but not roles I fixed roles to match common configuration, ie committers = maven-developers, PMC = maven- administrators Regards, Hervé - Mail d'origine - De: Chris Graham chrisgw...@gmail.com À: Maven Developers List

Re : Problems during the Release with the Site site:stage

This one is clearly the one I was fearing last time you reported an issue parent pom still has old svnpubsub url, causing unwanted relative path Should either release parent pom or use m-site-p topParentUrl param to force relative path calculations (like multi module builds) Regards Hervé

Re: svn commit: r1695142 - /maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java

now that you told it, I'd seriously prefer change Doxia Markdown parser to use an XhtmlParser instance internally instead of extending XhtmlParser while completely replacing content parsed by the Xhtml parser: this would be a lot more clear (and would avoid adding bloat to getType()) I didn't

Re: [jira] [Commented] (MPIR-234) SCM-link in site of multimodule projects should not append module name by default (at least for git)

IMHO, what is not clear in your explanations is that scm url is not the url of the repo scm url is scm:provider:provider-specific content our git scm url is currently weak, since it does not define path in repo: then just add it, in a location perfectly disctinct from repo url inside the scm

Re: [VOTE] Maven 3.3.6

ok, so both comments were right, we need to: - add unit tests whenever makes sense - add plugins trunks built with Maven core HEAD in our Jenkins setup the more eyes, the more good enhancement ideas :) Regards, Hervé - Mail original - De: Anton Tanasenko atg.sleepl...@gmail.com À:

Re: [VOTE] Maven 3.3.6

yes, currently we consider only core ITs as core ITs [1]: but plugins trunks are good core ITs candidates too :) Regards, Hervé [1] https://builds.apache.org/view/M-R/view/Maven%20Core%20ITs/ - Mail original - De: Jason van Zyl ja...@takari.io À: Maven Developers List

Re: svn commit: r1695142 - /maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java

wow, I don't like this in XML, encoding is self provided with such feature, an XML-invalid document can be read by Maven (and Maven only, since it is XML-invalid) I'm -1 on this: we can't help people make Maven-specific pseudo XML Regards, Hervé - Mail original - De:

Re: Working on MJAVADOC-400

Hi, AFAIK, there is currently a severe problem with aggregate reports, causing multiple executions: I couldn't find issues references at the moment, but I can provide Then when working on this, please check that the multiple execution problem doesn't get worse Regards, Hervé - Mail

Re: [VOTE] Release Apache Maven Archetype version 2.4 - TAKE 2

+1 notice that the / is important for the staging site URL: this avoids a redirection to /components see http://maven.apache.org/archetype-archives/archetype-LATEST/ (vs wrong http://maven.apache.org/archetype-archives/archetype-LATEST ) but no problem for the release: great work, thanks for

Re: svn commit: r1695142 - /maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java

Hi Lukas: nice to se that it has catched your interest :) Yes, DOXIA-436 is the ideal, where we completely remove any Xhtml intermediate The idea here is less ambitious: just avoid extending XhtmlParser, since the source is not Xhtml/Xml But of course, don't hesitate to help! Regards, Hervé

Re: Jira Permissions

Since Brian can't do the job for now (ie adding you to the maven-dev Jira group, that gives you proper karma to every Maven Jira project), I added your login to ARCHETYPE Jira project to avoid you loosing time waiting: now you can work immediately! :) (FYI, Brian is the only one who has karma

maven-archetype git commits not sent to commits@m.a.o?

Hi, I just found Petar git commits, but didn't see them in commits@m.a.o (then reported little issues somewhat late as I didn't notice them earlier) Is there some missing configuration on this repo? Are there other Maven git repos with such missing configuration? PLease some git expert at ASF

Re: maven-archetype git commits not sent to commits@m.a.o?

ok, created INFRA-10093 Regards, Hervé - Mail original - De: Benson Margulies bimargul...@gmail.com À: Maven Developers List dev@maven.apache.org Envoyé: Dimanche 9 Août 2015 17:41:51 Objet: Re: maven-archetype git commits not sent to commits@m.a.o? I'd suggest an INFRA ticket. On

Re: maven-archetype git commits not sent to commits@m.a.o?

no, nothing that deserve stopping the release: just the Jira issues that don't get a link to code fix in SCM I found the issue and its cause in https://issues.apache.org/jira/browse/ARCHETYPE-483 The fix for now is in Jira issues (manually adding links) And for future commits, it's in the

Re: svn commit: r1695142 - /maven/doxia/doxia-sitetools/trunk/doxia-site-renderer/src/main/java/org/apache/maven/doxia/siterenderer/DefaultSiteRenderer.java

IIUC, your concerns are about Mardown: if Markdown parser has a bug, don't hesitate to fix it but do not break content for normal XML parsers, like fml or xdoc since your change did not make unit tests fail, this proves unit tests are too weak: I just improved them in r1695408 to fail (and show

Re: Working on MJAVADOC-400

ok, I took time to find back Jira issues related to what I'm fearing: MJAVADOC-171 and related issues I'll need some time to carefully review your patch, since it's quite big and the plugin is already quite complex if others could have a look at it too, that would probably help Regards, Hervé

Re: How to access $project.build.sourceEncoding?

true, no method we documented it in the notice at the end of model building reference documentation [1] But for sure, once Maven 4 is out with an improved model and compatibility layer for Maven 3, these 2 encoding parameters are the first candidates to go into the enhanced model :) Regards,

Re: Another yearly bug squash

this is a *bug report* squash, not a bug squash And looking at the list, I see not only bug reports but a good number of enhancements notes (TODO list): perhaps limiting the search to bugs only would avoid dropping our TODO list And this notice IMHO should go to maven-users too Regards,

Re: Automating upload(commit) to "dist" area ?

I'd like it, but I have no idea how to do it because of: - the time it has to happen (ie after vote success) - the credentials required - need not only to add new release but also remove older (this one is the simple one to fix, a wildcard for version may do the job) something that can be done

Re: Retiring Maven Skins

yes, that's a good cleanup Regards, Hervé - Mail original - De: "Michael Osipov" <1983-01...@gmx.net> À: dev@maven.apache.org Envoyé: Mercredi 23 Décembre 2015 21:30:28 Objet: Retiring Maven Skins Hi folks, Hervé is quite busy right now preparing Doxia (Sitetools) 1.7 along with Maven

Re: [VOTE] Release Apache Maven Shared Component: Maven Archiver Version 3.1.0

+1 Regards, Hervé - Mail original - De: "Robert Scholte" À: "Maven Developers List" Envoyé: Dimanche 5 Juin 2016 21:15:26 Objet: Re: [VOTE] Release Apache Maven Shared Component: Maven Archiver Version 3.1.0 +1 On Fri, 03 Jun 2016

Re: [VOTE] Release Apache Maven Resources Plugin version 3.0.1

+1 Regards, Hervé - Mail original - De: "Robert Scholte" À: "Maven Developers List" Envoyé: Dimanche 5 Juin 2016 21:48:38 Objet: Re: [VOTE] Release Apache Maven Resources Plugin version 3.0.1 +1 On Fri, 03 Jun 2016 23:36:36 +0200, Karl

Re: MNG-5799

+1 good idea there are so many cases that I don't think any algorithm can give really meaningfull result, unless we add more fields to describe precisely how to keep a meaningfull order on each merge trying to summarize the current situation is a good first step Regards, Hervé - Mail

Re: [DISCUSSION] finishing Aether import: help find a new name

true: I know it sounded familiar... :) this artifact seems used by maven-remote-resources-plugin only And if you look at the content, it contains a little helper to resolve dependencies: we should probably deprecate it at the end If there is no objection, I'll update code in a few days to

Re: [DISCUSSION] finishing Aether import: help find a new name

sorry, I find it somewhat abstract: it does not tell anything about the interactions Even if I agree that resolver does not tell everything, just the majority and most complex Regards, Hervé (sorry, on holidays with unusual email access: tracking such thread is not easy...) - Mail

Re: PR Inquiry

Hi, Please have a look at answers from Robert and myself on https://issues.apache.org/jira/browse/MDEP-519 (for the second PR) Regards, Hervé - Mail original - De: "Rajiv Jain" À: "Maven Developers List" Envoyé: Jeudi 4 Août 2016 22:45:40

Re: [DISCUSSION] finishing Aether import: help find a new name

the whole functionality of the lib is visible in one interface: RepositorySystem http://maven.apache.org/aether-archives/aether-LATEST/apidocs/org/eclipse/aether/RepositorySystem.html in this interface, 6 methods are about resolution + 1 about collection (a special "sort of" resolution) + 1 to

Re: [DISCUSSION] finishing Aether import: help find a new name

if I let apart the confusion with java jars... it's not a specification: the specification of the repository is in maven-aether-provider dependencies Regards, Hervé - Mail original - De: "Christian Schulte" À: "Maven Developers List" Envoyé:

Re: [DISCUSSION] finishing Aether import: help find a new name

yes, in the current case, this is an internal component name we're looking for: end-users will not notice Regards, Hervé - Mail original - De: "Gary Gregory" À: "Maven Developers List" Envoyé: Vendredi 5 Août 2016 00:15:24 Objet: Re:

Re: Can we disable emails to commits@ for branches?

sure: isn't git supposed to solve everything? :) Regards, Hervé - Mail original - De: "Stephen Connolly" À: "Maven Developers List" , i...@soebes.de Envoyé: Vendredi 3 Février 2017 13:07:50 Objet: Re: Can we disable emails to

Re: MNG-5961 for 3.5.0 ?

seconded for 3.5.0 yes, basic bug fix Regards, Hervé - Mail original - De: "Arnaud Héritier" À: "Maven Developers List" Envoyé: Mardi 31 Janvier 2017 21:44:09 Objet: MNG-5961 for 3.5.0 ? Hi, This is a so easy one I fixed a long time ago in

Re: [CANCELLED] [VOTE] Release Apache Maven Site Plugin version 3.6

will do when removing support for Maven 2 Regards, Hervé - Mail original - De: "Robert Scholte" À: "Maven Developers List" Envoyé: Samedi 12 Novembre 2016 18:33:22 Objet: Re: [CANCELLED] [VOTE] Release Apache Maven Site Plugin version 3.6

Re: svn commit: r1769704 - /maven/site/trunk/content/apt/guides/introduction/introduction-to-dependency-mechanism.apt

I like the new description What I still don't understand is "Since they are replaced, dependencies with a scope of <<>> do not actually participate in limiting the transitivity of a dependency.": what's the intent with this? Regards, Hervé - Mail original - De: schu...@apache.org À:

Re: [VOTE] Release Apache Maven Site Plugin version 3.6

here is my +1 Regards, Hervé - Mail original - De: "herve boutemy" <herve.bout...@free.fr> À: "Maven Developers List" <dev@maven.apache.org> Envoyé: Dimanche 13 Novembre 2016 00:23:50 Objet: [VOTE] Release Apache Maven Site Plugin version 3.6

[RESULT] [VOTE] Release Apache Maven Site Plugin version 3.6

Hi, The vote has passed with the following result: +1 : Olivier Lamy, Michael Osipov, Hervé Boutemy PMC quorum: reached I will promote the artifacts to the central repo. - Mail original - De: "herve boutemy" <herve.bout...@free.fr> À: "Maven Developers List&q

Re: How to disable colours?

wow, removing jansi jar file is expeditive, but for sure gives guaranteed result :) Currently, there are 2 ways to disable color: - -B option: batch mode - -l option: log file (if you search for "setColorEnabled" in MavenCli, you'll see) For the moment, after discussions we had on the ML, the

Re: maven git commit: MNG-5889 - adding logic that looks for the file argument and starts the search for the .mvn directory at the location of the specified POM when present

I completely overlooked the failing IT on Windows: thanks for fixing On ASF Jenkins, MavenITmng3599useHttpProxyForWebDAVTest.testitUseHttpProxyForWebDAV looks flaky: sometimes it passes, but fails in general. Any idea? regarding MavenITmng4625SettingsXmlInterpolationWithXmlMarkupTest, it was

Re: Build failed in Jenkins: maven-plugins-ITs-m3-windows #1762

perhaps there are issue in how Maven sees some Windows OS: I don't have such machines at hand to clearly tell how each precise OS version is displayed Perhaps a Wiki page to have people fill cases could be useful At least now, I see there are 2 versions that require precise tests: Windows 10 Pro

Re: [VOTE] Release Apache Maven Site Plugin version 3.6

no MSITE issue was created AFAIK this is classical issue with dependencies: how to clearly show what is fixed by dependencies and what is fixed directly by the released code if you have ideas on how to better show this without giving too much work (abolutely requiring to create one MSITE issue

Re: Releasing maven-resources-plugin 3.0.2

seems you missed https://www.apache.org/dev/publishing-maven-artifacts.html#dev-env Regards, Hervé - Mail original - De: "Christian Schulte" À: "Maven Developers List" Envoyé: Dimanche 13 Novembre 2016 17:56:30 Objet: Releasing

Re: maven-3.x Jigsaw - Build # 10 - Fixed

yay! - Mail original - De: "Apache Jenkins Server" À: schu...@apache.org, micha...@apache.org, rfscho...@apache.org, notificati...@maven.apache.org Envoyé: Samedi 12 Novembre 2016 21:43:19 Objet: maven-3.x Jigsaw - Build # 10 - Fixed The Apache Jenkins build

[VOTE] Release Apache Maven Site Plugin version 3.6

Hi, We solved 14 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317923=12335570=Text There are still a couple of issues left in JIRA:

Re: Gitbox pull requests

On 2017-12-12 07:11, Chas Honton wrote: > Pull requests for new project are not sent to the dev mailing list (e.g. > https://github.com/apache/maven-deploy-plugin/pull/1). Are these PRs > supposed to be forwarded to some mailing list? they are sent to iss...@maven.apache.org,

Re: [IMPORTANT] Re: Git migration next steps

I'd suggest to try the process to a personal personal repo on GitHub to see if you're able to get a better result before involving manual work from INFRA (on more than 60 repos...) (it's sad to see nobody try to explain what's happenning or improve the documented commands, just get to a

Re: MPOM-205 creating source release checksums in target for Apache dist area

squashed and kept only SHA-512 Maven core plugins don't cover everything even quite generic like creating checksums, that's why there are many Maven plugins out there... Regards, Hervé - Mail original - De: "Michael Osipov" À: "Maven Developers List" , "her

MPOM-205 creating source release checksums in target for Apache dist area

Hi, Recently, Apache distribution policy changed regarding checksums [1]: now, SHA-256 or SHA-512 checksums are required. This lead to discussion about changing checksums used on Maven repository and/or Apache Nexus repository. But Maven repository requirements and Apache source distribution

Re: archetype-descriptor-1.0.0.xsd outdated

ARCHETYPE-554 created https://issues.apache.org/jira/browse/ARCHETYPE-554 I'll update the version and publish it Regards, Hervé - Mail original - De: "Robert Scholte" À: "Maven Developers List" Envoyé: Samedi 11 Août 2018 11:39:59 Objet: Re: archetype-descriptor-1.0.0.xsd outdated

Re: MPOM-205 creating source release checksums in target for Apache dist area

rent demand from ASF we should consider writing a maven-checksum-plugin. Robert > > Regards, > > Hervé > > - Mail original - > De: "Michael Osipov" > À: "Maven Developers List" , "herve boutemy" > > Cc: release-disc...@apache.org

Re: [VOTE] Release Apache Maven 3.5.3

+1 both for immediate vote and for the plan to release as is then releasing ASAP 3.5.4 Regards, Hervé - Mail original - De: "Mirko Friedenhagen" À: "Maven Developers List" Envoyé: Samedi 3 Mars 2018 13:42:43 Objet: Re: [VOTE] Release

Re: [VOTE] Release Apache Maven 3.5.3

the issue is a multi-threading issue on Windows Jansi, then this affects people on Windows who try to use parallel build. I can commit on Jansi but not do a release: I can see this if a quick 1.17.1 is feasible... Regards, Hervé - Mail original - De: "Stephen Connolly"

Re: Packaging from Aether

a dependency has a type, but not really a packaging: a packaging is a recipe to build a project that will produce multiple artifacts, each with its own type see the comparison [1] and default artifact handlers [2] gives you informations about default types. The only misleading field IMHO is

Re: [VOTE] Release Apache Maven Source Plugin version 3.2.0

uh, strange, the test for maven-assembly-plugin is even more aggressive than maven-source-plugin: the issue should not only happen here yes, I'm interested in the archive, with details on the OS used Regards, Hervé - Mail original - De: "Tibor Digana" À: "Maven Developers List" ,

Re: last review of Reproducible Builds proposal

ok, Reproducible Builds are not so easy to get: each plugin that you use can cause an issue I really recommend you diffoscope to investigate differences, it really helps a lot by easily giving you precise differences Good luck for the investigations :) Regards, Hervé - Mail original

Re: Apache Wagon vs maven-shade vs embedded licenses

issue created: https://issues.apache.org/jira/browse/WAGON-574 Regards, Hervé - Mail original - De: "Enrico Olivelli" À: "Maven Developers List" Cc: "Hervé BOUTEMY" Envoyé: Mercredi 6 Novembre 2019 09:53:29 Objet: Re: Apache Wagon vs maven-shade vs embedded licenses Il giorno

Re: Apache Wagon vs maven-shade vs embedded licenses

sure, if you know how to fix, yes, I can drop this release and start the next one quickly particularly if it helps us later to improve Maven handling of the case This case of -shaded.jar published to Central [1] is really a completely different scenario than Maven -bin.zip/tar,gz binary

Re: Apache Wagon vs maven-shade vs embedded licenses

I agree on all points, perfect match :) Regards, Hervé - Mail original - De: "Enrico Olivelli" À: "Maven Developers List" Envoyé: Jeudi 7 Novembre 2019 12:08:11 Objet: Re: Apache Wagon vs maven-shade vs embedded licenses Il giorno gio 7 nov 2019 alle ore 10:38 ha scritto: > sure,

Re: Regression in model interpolation coming from using JSR-330?

MNG-6799 issue created [1] proposed fix added to the reproducible branch [2] by simply removing the @Named annotation for the deprecated StringSearchModelInterpolator: CI seems ok ok for merge? Regards, Hervé [1] https://issues.apache.org/jira/browse/MNG-6799 [2]

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

nobody interested? Or I was too hard on testing reproducibility with JDK 7? This reproducibility test is just an option, don't hesitate to not test On next vote, I'll do the release with JDK 8, which will be easier for everyone to have on his computer... Regards, Hervé On 2019/12/08 23:35:03,

Re: [VOTE] Release Apache Maven Release Plugin version 3.0.0-M1

BUILD SUCCESS [INFO] [INFO] Total time: 06:27 min [INFO] Finished at: 2019-12-11T17:58:08+01:00 All its run without problems. Enrico Il giorno mer 11 dic 2019 alle ore 17:35 Herve Boutemy ha scritto: > nobody interested? Or I was too hard on testing reproducibility with JDK 7? >

Re: [VOTE] Release Apache Maven Archiver version 3.5.0

here is my +1 On 2019/10/19 17:40:46, Hervé BOUTEMY wrote: > Hi, > > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12345174=Text > > Staging repo: > https://repository.apache.org/content/repositories/maven-1531/ >

[RESULT} [VOTE] Release Apache Maven Archiver version 3.5.0

Hi, the vote passed with the following resuts: +1: Tibor Digana, Olivier Lamy, Karl Heinz Marbaise, Romain Manni-Bucau, Sylwester Lachiewicz, Hervé Boutemy PMC Quorum: reached I will promote the artifacts to the central repo and complete the procedure

Re: [VOTE] Release Apache Maven Parent POMs version 34

good news: finally, the build is reproducible there is just a subtle task to do if you build from source-release.zip archive: start with "rm DEPENDENCIES LICENSE NOTICE" still need one vote, please - Mail original - De: "herve boutemy" À: "Maven Developer

Re: Maven Runtime Metrics

maven-studies looks like the right location: https://github.com/apache/maven-studies Regards, Hervé - Mail original - De: "Enrico Olivelli" À: "Maven Developers List" Envoyé: Jeudi 30 Janvier 2020 04:31:14 Objet: Re: Maven Runtime Metrics I sound like to draft a prototype. Any

[RESULT] [VOTE] Release Maven Parent POMs version 34

Hi, The vote has passed with the following result: +1 : Enrico Olivelli, Sylwester Lachiewicz, Karl Heinz Marbaise, Robert Scholte, Hervé Boutemy PMC quorum: reached I will promote the artifacts to the central repo. - To

Re: [VOTE] Release Apache Maven PMD Plugin version 3.13.0

+1 Regards, Hervé - Mail original - De: "Karl Heinz Marbaise" À: "Maven Developers List" , "Andreas Dangel" Envoyé: Lundi 27 Janvier 2020 10:49:32 Objet: Re: [VOTE] Release Apache Maven PMD Plugin version 3.13.0 Hi, +1 from me. Kind regards Karl Heinz Marbaise On 25.01.20 12:04,

Re: [VOTE] Release Apache Maven Parent POMs version 34

here is my +1 sadly, the build is not fully reproducible, I'll need to investigate why... I need more votes, please Regards, Hervé - Mail original - De: "Hervé BOUTEMY" À: "Maven Developers List" Envoyé: Dimanche 26 Janvier 2020 01:16:20 Objet: [VOTE] Release Apache Maven Parent

Re: Maven GroupID authority

see: - http://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_relocation - https://maven.apache.org/guides/mini/guide-relocation.html Everything is there. I confess I never tried it myself, but there are POMs in central using it. - Mail original - De: "Elliotte Rusty Harold" À:

Re: Doxia test flakiness

nothing really went wrong: there are a few cases I did not migrate because I was convinced that classical migration to 1 git repo each was not appropriate, but I did not know really what to do better (and was tired doing the migration on the many "easy" cases) correponding repositories are

Re: [DISCUSS] checking reproducible builds

please "git pull": you're one commit behind HEAD https://github.com/apache/maven-studies/commits/maven-buildinfo-plugin - Mail original - De: "Karl Heinz Marbaise" À: "Maven Developers List" , "Hervé BOUTEMY" Envoyé: Samedi 7 Mars 2020 12:12:08 Objet: Re: [DISCUSS] checking

Reproducible Builds for war files and Tomcat expectations

Reproducible Builds is now implemented in many plugins: it's time to work on reproducible war files. I created MWAR-432 issue and implemented classical Reproducible jar output in corresponding branch. But in our discussion in november [1], an issue was reported for unchanged timestamp in

Re: [VOTE] Apache Maven Javadoc Plugin 3.2.0

+1 reproducibility verified: little issue found on source-release.zip, with strange generated file added, but nothing serious mvn -Papache-release clean verify buildinfo:save -Dgpg.skip -Dreference.repo=https://repository.apache.org/content/repositories/maven-1557 Regards, Hervé - Mail

Re: Maven in python

"pip install maven" will apparently install https://pypi.org/project/maven/ which is https://github.com/john-sandall/maven nothing related to the well known Apache Maven build tool https://maven.apache.org/ Regards, Hervé - Mail original - De: "Vikas Mishra" À: "Maven Developers

[VOTE] Release Apache Maven WAR Plugin version 3.3.1

Hi, We solved 4 issues: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318121=12348374=Text Staging repo: https://repository.apache.org/content/repositories/maven-1593/

Re: [VOTE] Release Maven Wagon version 3.5.1

+1 Reproducible Build checked: reference build was done with JDK 8 on Windows Regards, Hervé On 2021/12/22 23:07:27 Michael Osipov wrote: > Hi, > > We solved 5 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318122=12351145 > > There are still a couple of issues

Re: [VOTE] Release Apache Maven Archiver version 3.5.2

+1 Reproducible Build checked: reference build was done with JDK 8 on Windows Regards, Hervé On 2022/01/02 12:48:58 Michael Osipov wrote: > Hi, > > We solved 2 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12349631 > > There are still a couple of issues

Re: [VOTE] Release Maven Release version 3.0.0-M5

+1 Reproducible Build checked: reference build was done with JDK 8 on Windows Regards, Hervé - Mail original - De: "Michael Osipov" À: "Maven Developers List" Envoyé: Dimanche 2 Janvier 2022 11:41:24 Objet: [VOTE] Release Maven Release version 3.0.0-M5 Hi, We solved 9 issues:

Re: [DISCUSS] Move maven caching to an external repository

done: https://github.com/apache/maven-build-cache-extension On 2022/01/04 07:30:40 Guillaume Nodet wrote: > I'd go for #2 ... > > Le mar. 4 janv. 2022 à 00:14, Hervé BOUTEMY a > écrit : > > > yes, I was happy to learn about that shallow + filter approach :) > > > > now, we have one choice to

Re: [VOTE] Release Maven SCM version 2.0.0-M1

+1 Reproducible Build checked: reference build was done with JDK 8 on Windows Regards, Hervé On 2022/01/08 20:24:01 Michael Osipov wrote: > Hi, > > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12350622 > > There are still a couple of issues

Re: [VOTE] Release Maven Plugin Tools version 3.6.3

having worked on this for the whole WE, please review my last comment in https://issues.apache.org/jira/browse/MPLUGIN-384 and associated PR in short: given Maven classloading, Sonatype plugin cannot be fixed by our breaking move done in our own plugin in MPLUGIN-377 : in up to us to restore

Re: [VOTE] Release Maven Compiler Plugin version 3.9.0

I rebuilt from current Git HEAD and got same result looking at ASF Jenkins, it seems 1 configuration has exactly the same issue than me: https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-compiler-plugin/job/master/92/execution/node/249/log/ it's JDK 8 with Maven 3.2 on ASF Jenkins,

  1   2   3   >