Re: [DISCUSS] Maven Core Plugins versioning

Sounds good to me. /Anders (mobile) Den fre 8 mars 2024 11:19Tamás Cservenák skrev: > So, can we agree on following (maybe even vote if needed)? > > I. Core Plugin Versioning > Maven3 plugins carry 3.x as the major version number, and Maven4 plugins > will carry 4.x major versions? > > II.

Re: [VOTE] Require Java 17 for Maven 4

+1 /Anders On Wed, Feb 28, 2024 at 8:30 AM Benjamin Marwell wrote: > > Hi Maven Devs/Users/Committers and PMC members! > > After several discussions on the mailing lists, I would like to > start a vote in favour of setting the minimal Java bytecode target > of Maven-Core 4 to 17 and hence

Re: New year - new challenge - required Maven 3.6.3 as minimal for core Maven Plugins

+1 /Anders On Fri, Dec 29, 2023 at 2:43 PM Slawomir Jaranowski wrote: > Hi, > > Last year we mark all Maven versions 3.6.x and older as EOL [1] > > But we still try to support minimal API version for Core Maven Plugins as > 3.2.5 > > I would like to propose to sich it for at least to 3.6.3 >

Re: Suggestion for soft-breaking Maven Plugin 4.0 changes

Maybe bump default to at least Java 8 for source/target of maven-compiler-plugin? Or maybe switch to a default for release instead if we decide on a Java 11+ runtime requirement for mvn4. /Anders (mobile) Den tors 21 juli 2022 20:24Benjamin Marwell skrev: > Hi everyone, > > as discussed in

Re: Question - JDK Minimum of future Apache Maven 4.0.0

I'd say Java 11 if there isn't some very good feature in Java 17 that we need. So far we have supported the current and prior Java LTS version and I think that's a good aim. Lot's of users are still on Java 11 and even if you can execute Maven with a different Java version than you build for, it

Re: Maven 4 performances problems

I agree. We could even mention this known performance "issue" so there wouldn't be any surprise. /Anders On Thu, Jul 1, 2021 at 12:29 PM Enrico Olivelli wrote: > Il giorno gio 1 lug 2021 alle ore 12:27 Robert Scholte < > rfscho...@apache.org> > ha scritto: > > > Should we postpone the alpha-1

Re: [Idea] Coding Guidelines for Maven Contribution Newbies

There are settings files here: http://maven.apache.org/developers/conventions/code.html /Anders On Tue, Dec 22, 2020 at 2:47 PM Gary Gregory wrote: > It would be great if one could download Eclipse or Idea settings files, or > better yet, include them in each repo. > > Gary > > On Tue, Dec 22,

Re: [VOTE] Release Apache Maven Dependency Analyzer version 1.11.2

+1 (binding) /Anders On Mon, Jul 27, 2020 at 1:08 PM Elliotte Rusty Harold wrote: > By my count we need one more PMC member to approve this to get to > three. This is an important upgrade that enables lots of new work in > the dependency plugin. Can anyone else give us a +1? Thanks. > > On

Re: How does maven resolve cyclic dependendencies/how should the verbose depenedency:tree display them

Wrong list. Use the users list for usage questions. This list is for developing Maven. /Anders (mobile) Den lör 18 juli 2020 00:17Ian Lavallee skrev: > If I have Projects A, B, C with A depends on B, B depends on C, C depends > on A does maven still include one of each A, B, C? > > Should the

Re: Do we have a policy for minimum Maven version for plugins?

There's been some discussion regarding this lately and my take is that we've settled on that requiring Maven 3.1.0 is ok for plugins. In the same discussion I *think* we settled on that a Java 8 requirement is ok. What I don't think we all agreed on is if it's ok to bump the requirements without a

Re: Artifact installation and versions

My understanding is that it's "SNAPSHOT" when installing to the local repo but a snapshot version when deploying to a remote repo. But a rarely look in the local repo so I could be wrong. /Anders (mobile) Den tis 7 juli 2020 13:08Elliotte Rusty Harold skrev: > Let me correct that. On further

Re: [maven-site] branch master updated: details

A few comments: 1. I think we should separate the prerequisites for Maven core and those for our plugins. 2. Do users really care about "Maven Plugin API"? I think that an end user would like to know what version of Maven (core) that a plugin will work with. /Anders On Wed, Jun 3, 2020 at 3:01

Re: next level of compatibility (was Re: [maven-site] branch master updated: few precisions)

On Tue, May 26, 2020 at 8:37 AM Olivier Lamy wrote: > On Tue, 26 May 2020 at 08:05, Robert Scholte wrote: > > > I think it is pretty impressive that we can say that our plugins still > > support a wide range of Maven versions. > > > > So my vote will be 3.1.0 > > > > even if it doesn't happen

Re: Maven GroupID authority

In real practice it doesn't work well though, as someone already brought up. It can result in duplication of libraries on the class path (the same library under different groupId). /Anders (mobile) Den ons 19 feb. 2020 14:52Elliotte Rusty Harold skrev: > I set up some simple projects and

Re: [massembly] code question

I agree. It's strange and the debug log output is actually technically wrong. So I'd say remove it. /Anders On Thu, Dec 19, 2019 at 2:39 PM Mark Struberg wrote: > Hi! > > Feeling a bit rusty, so I thought I better ask for a 2nd opinion. > > To me it looks like the following code block is

Re: [VOTE] JDK 8 Minimum Requirement for Maven 3.7.0

+1 /Anders (mobile) Den tis 29 okt. 2019 20:11Karl Heinz Marbaise skrev: > Hi to all, > > based on the discusion this is the formal VOTE to lift the minimum of > Maven Core with version 3.7.0 to JDK 8 minimum. > > Vote open for at least 72 hours. > > [ ] +1 > [ ] +0 > [ ] -1 > > > Kind regards

Re: [DISCUSS] Maven 3.7.0

On Thu, Oct 3, 2019 at 5:47 PM Emmanuel Bourg wrote: > Le 03/10/2019 à 16:54, Karl Heinz Marbaise a écrit : > > > Hm.. first Java 7 is out for eight years now (2011) (End of live) and > > has no public updates for security/bug fixes etc. since 2015 > > RedHat still maintains OpenJDK 7 until June

Re: [VOTE] Retire Maven OSGi

+1 /Anders (mobile) Den fre 23 aug. 2019 15:17Robert Scholte skrev: > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, >

Re: [VOTE] Retire Maven Repository Builder

+1 /Anders (mobile) Den ons 7 aug. 2019 21:13Robert Scholte skrev: > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, >

Re: Push install plugin docs

, I think. > [image: image.png] > > Regards, > Tomo > > On Tue, Jul 2, 2019 at 10:23 AM Anders Hammar wrote: > >> Works for me (Sweden/Europe). >> >> /Anders >> >> On Tue, Jul 2, 2019 at 4:15 PM Elliotte Rusty Harold >> wrote: >> >>

Re: Push install plugin docs

Works for me (Sweden/Europe). /Anders On Tue, Jul 2, 2019 at 4:15 PM Elliotte Rusty Harold wrote: > Could someone push the docs for > https://maven.apache.org/plugins/maven-install-plugin/? > > I noticed a 404 from this page. When I went to fix it in Github, I > realized it had already been

Re: Anyone had an error on Eclipse IDE after upgrade maven-jar-plugin to 3.1.2?

Please read the bug report [1], which was reference in the first reply to this thread. It clearly explains that the problem is in the mavenarchiver m2e connector/plugin. The simplest solution is to just update that plugin. URL to update site is in the bug report. [1]

Re: [VOTE] Retire Maven Downloader

+1 /Anders On Fri, Jun 7, 2019 at 3:32 PM Robert Scholte wrote: > Hi, > > The Apache Maven project consist of about 90 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects,

Re: [VOTE] Retire Maven Ant Plugin

+1 /Anders On Tue, May 28, 2019 at 8:54 PM Robert Scholte wrote: > Hi, > > The Apache Maven project consist of about 100 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects,

Re: [VOTE] Release Apache Maven JAR Plugin version 3.1.2

+1 /Anders On Wed, May 8, 2019 at 10:22 PM Karl Heinz Marbaise wrote: > Hi, > > We solved 2 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317526=12344629 > > There are still a couple of issues left in JIRA: > >

Re: [VOTE] Retired Maven Artifact Resolution API (Maven2)

+1 /Anders (mobile) Den ons 8 maj 2019 20:25Robert Scholte skrev: > Hi, > > The Apache Maven project consist of about 100 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects,

Re: Regarding MJAR-259 and MSOURCES-119

lve-plugins > > (Unrelated question: Is the order of dependencies random in the above list > or is it classpath order? If it's random, it would be better if it was > sorted, so it's easy for the human eye to scan for a particular dependency) > > - Eric L > > On Tue, May 7, 2019

Re: Regarding MJAR-259 and MSOURCES-119

Checking m-jar-p, what is needed is an upgrade of plexus-archiver to version 4.0.0+ as it includes an upgraded dependency to plexus-io v3.1.1. See [1]. If you include m-jar-p in the pluginManagement section of your corporate parent-POM, you could bump this on the existing maven-jar-plugin v3.1.1

Re: Summary of meeting about Maven performance improvements

Yes, there's been reports some time ago about performance degradation in newer versions. I'm not sure if there was an actual jira ticket or just mail to the list. Iirc there was no actual end result to resolve it from that though. /Anders (mobile) Den ons 24 apr. 2019 19:09Karl Heinz Marbaise

Re: [VOTE] Retire Maven Repository Plugin

+1 /Anders (mobile) Den tis 23 apr. 2019 21:43Robert Scholte skrev: > Hi, > > The Apache Maven project consist of about 100 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects,

Re: Checkstyle plugin - bump to java 8 ?

Sounds reasonable to me. /Anders On Thu, Apr 4, 2019 at 1:47 PM Enrico Olivelli wrote: > Hi, > The Maven CheckStyle plugin currently supports Java 7 but latest > Checkstyle versions require Java 8. > For this reason we are stuck to an older version of Checkstyle and > users want to use the new

Re: Ojdbc7 dependency issue

This should have been posted to the users list, not the dev list. As adding artifact manually to an internal repo manager is a maintenance nightmare, I'd like to stress that Oracle does provide a Maven repository which can be proxied instead (with a repo manager). More info here:

Re: Release Build is Committing Artifact to Parent’s Repository

Please use the Maven User List [1] for Maven usage questions. This list is for questions related to the development of Maven. [1] https://maven.apache.org/mailing-lists.html /Anders On Tue, Jan 22, 2019 at 12:41 PM Biswa C wrote: > Hi Maven Developer Team, > > We are facing following issue

Re: Update versions of all plugins in default-bindings.xml

IMHO it shouldn't be done in a patch release, but rather a minor release (3.7.0). /Anders (mobile) Den tors 10 jan. 2019 17:09 skrev Tibor Digana : > Why we use old versions in default-bindings.xml? > Can we update all versions in 3.6.1 release? > > Here is MNG-6557 which is related to Surefire

Re: Welcome Sylwester Lachiewicz to the Apache Maven Team

Welcome Sylwester! /Anders (mobile) Den sön 2 sep. 2018 12:58Karl Heinz Marbaise skrev: > Hi to all, > > On behalf of the Apache Maven PMC I am pleased to announce that > Sylwester Lachiewicz has been voted in as a new Apache Maven committer. > > Sylwester, welcome on board and have a lot of

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.1

Den tors 26 juli 2018 17:17Anders Hammar skrev: > -1, I agree with Robert. Looks som docs (and code) also states 1.8.0 for > this change. > Should say 3.8.0 of course. /A > /Anders (mobile) > > Den tors 26 juli 2018 14:37Robert Scholte > skrev: > >> -1, changing the default for source/

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.1

-1, I agree with Robert. Looks som docs (and code) also states 1.8.0 for this change. /Anders (mobile) Den tors 26 juli 2018 14:37Robert Scholte skrev: > -1, changing the default for source/ target should not be fixed with a > patch number. Should be 3.8.0.Probably my fault that I didn't

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

+1 /Anders (mobile) Den lör 12 maj 2018 09:28Karl Heinz Marbaise skrev: > Hi, > > I need at least two more PMC votes... > > any other support is highly appreciated.. > > Kind regards > Karl Heinz Marbaise > On 09/05/18 20:05, Karl Heinz Marbaise wrote: > > Hi, > > > > We

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

+1 Checked the site updates. /Anders On Thu, May 3, 2018 at 2:51 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12317421=12334440 > > There are still a couple of issues left in JIRA: >

Re: Spring cleanup JIRA

+1 for the same process as last time. /Anders On Wed, Mar 7, 2018 at 11:31 PM, Michael Osipov wrote: > Folks, > > I did yet another analysis on open issues. We have currently more than 400 > open issues which haven't been touched for more than three (3) years. > > The last

Re: fixing the list of artifacts in maven-metadata.xml

n, I don't see how this > can > rebuild the versions list from the real content in the repository > > Regards, > > Hervé > > Le mardi 6 mars 2018, 08:50:15 CET Anders Hammar a écrit : > > This is very often an issue. I know for sure that Nexus can fix this so > you

Re: fixing the list of artifacts in maven-metadata.xml

This is very often an issue. I know for sure that Nexus can fix this so you could ask Sonatype via Jira. That would rebuild old data. For future releases I believe this is the correct way of fixing this in m-deploy-p:

Re: eclipse java code formatter

Formatter xml for Maven and core plugins can be found here: http://maven.apache.org/developers/conventions/code.html /Anders On Mon, Feb 19, 2018 at 3:16 PM, Basin Ilya wrote: > Hi. > > Where can I download the formatter xml for maven projects? > > Aslo, I manually created

Re: What was initially intended with Mojo#threadSafe ?

mvn -T 2C ... IIRC. /Anders On Fri, Jan 12, 2018 at 12:02 AM, Tibor Digana wrote: > What was initially intended with Mojo#threadSafe ? > Was it the use case mvn -T 2C ...? > Or it was parallel processes execution from the project root? > For instance report-plugin which

Re: [FEEDBACK WANTED] edit button on a Maven site

The idea is great, but personally I don't find the icon location obvious. I was searching for a pen icon in the lower right corner of hte screen, which (to me) is the de-facto standard. If we have it where it is now, there should at least be a hoover hint saying what it does. /Anders On Mon, Dec

Re: Maven plugin developer doumentation

What you should typically do is declare dependency to the lowest version of Maven that you want to support support. So for our core Apache Maven plugins we declare dependency to version 3.0 of the (core) Maven dependencies, which is because we want the plugins to support v3.0+ of Maven. So we

Re: [VOTE] Release Apache Maven 3.5.1

>> > Damned, can't we be anonymous on Github ? > > > >> >> > I maintain it is a big word, I'm trying to fix more bugs than I > > > >> >> > add > > > >> > > > >> new > > > >> > > > >> >&g

Re: Understanding MNG-6209 (was: [VOTE] Release Apache Maven 3.5.1)

To add to the topic I think that if we fix/change the class loading, we shouldn't do that in a bug fix release. I'd rather see a 3.6.0 with it thought through, fixed and documented (could be in ITs). The arguing being that a bug fix release shouldn't cause new issues in plugins etc. /Anders On

Re: [VOTE] Release Apache Maven 3.5.1

ve we can compensate > for the change from m2e end. In the worst case we'll bundle hacked > version of DefaultClassRealmManager with m2e, not ideal, but not the end > of the world either. > > -- > Regards, > Igor > > On Fri, Sep 15, 2017, at 07:21 AM, Anders Hammar wrote:

Re: [VOTE] Release Apache Maven 3.5.1

On Fri, Sep 15, 2017 at 8:29 AM, Anders Hammar <and...@hammar.net> wrote: > Reporting back from tests of m2e with embedded Maven 3.5.1, we see problem > with the jaxws-maven-plugin mojo. We're two people seeing the issue > independently, but unfortunately Fred Bricon hasn't been ab

Re: [VOTE] Release Apache Maven 3.5.1

On Wed, Sep 13, 2017 at 9:26 AM, Anders Hammar <and...@hammar.net> wrote: > > > On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> Have we got any feedback from the embedder integrations yet? >> > > I haven't

Re: [VOTE] Release Apache Maven 3.5.1

On Tue, Sep 12, 2017 at 8:54 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Have we got any feedback from the embedder integrations yet? > I haven't heard anything from the m2e people. Maybe we need to ping them directly. I can contact Fred Bricon. /Anders > > On Mon 11 Sep

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.2

+1 Tested with Maven 3.3.9 and IBM JDK 7.1 on Windows 7. /Anders On Sat, Sep 9, 2017 at 2:34 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12317227=12341254 > > There are still a couple of

Re: Users can assign Fix Version/s in Jira

I agree, it's for us as committers to decide. /Anders On Fri, Sep 8, 2017 at 8:51 AM, Michael Osipov wrote: > Am 2017-09-08 um 00:42 schrieb Tibor Digana: > >> I found out that users create an issue in Jira and *assign version* [1]. >> I remember this did not happen in old

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.7.0

+1 Tested with Maven 3.3.3 and IBM JDK 7.1 on Windows 7. /Anders On Fri, Sep 1, 2017 at 3:50 PM, Robert Scholte wrote: > Hi, > > We solved 6 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12317225=12341266=Text > > There are still a couple

Re: Maven JIRA Projects - Issue Type

B would be great. /Anders (mobile) Den 18 aug. 2017 20:53 skrev "Karl Heinz Marbaise" : > Hi to all, > > I have realized that in MASSEMBLY it is possible to define an issue Type > "Dependency Upgrade" which is very feasible for our projects... > > So I have asked INFRA[1] if

Re: [VOTE] Release Apache Maven EJB Plugin version 3.0.0

+1 (binding) Tested with Maven 3.3.3 and IBM JDK 7.1. I did find some minor text bugs on the site which I filed tickets for [1] [2] [3]. [1] https://issues.apache.org/jira/browse/MEJB-115 [2] https://issues.apache.org/jira/browse/MEJB-116 [3] https://issues.apache.org/jira/browse/MEJB-117

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

+1 Tested with Maven 3.3.3 and IBM JDK 7.1 on Windows 7. /Anders On Mon, Jul 17, 2017 at 10:05 PM, Robert Scholte wrote: > Hi, > > We solved 18 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12317529=12330875=Text > > There are still a

Fwd: [JENKINS] [IMPORTANT] - Jenkins Migration and Upgrade (And JDK7 deprecation)

See info below. It looks as we're on the Maven project build type for some builds so that this will affect us wrt JDK7 deprecation. /Anders -- Forwarded message -- From: Gavin McDonald Date: Tue, Jun 27, 2017 at 9:03 AM Subject: [JENKINS] [IMPORTANT] -

Re: [VOTE] Release Apache Maven Enforcer version 1.4.2

v2.0.0? /Anders On Tue, Jun 20, 2017 at 12:53 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Hmmm in reviewing the code provenance I notice that > https://svn.apache.org/viewvc?view=revision=1791757 was merged > without bumping the pom version to 3.0.0. > > Should we drop and

Re: The maven-archetype-plugin paradox

uess you should > add --offline. > > WDYT? > > Robert > > [1] https://issues.apache.org/jira/browse/ARCHETYPE-520 > > On Tue, 16 May 2017 13:02:11 +0200, Anders Hammar <and...@hammar.net> > wrote: > > I would expect "remote" not be the central repo bu

Re: The maven-archetype-plugin paradox

l be a way to have it configured via Maven > settings.xml. > > Do you think my concern is valid? > > Amélie > > [1] http://maven.apache.org/archetype/maven-archetype-plugin/ > examples/generate-alternative-catalog.html > > On 05/16/2017 08:56 AM, Anders Hammar wrote: &g

Re: The maven-archetype-plugin paradox

Amélie, Thanks for describing your use case here on the list! As I am one of the reporters for the tickets behind the change in question I'd like to describe my reasoning: First off, your use case is actually (if I understand it correctly) standard for Maven usage. For a company environment I

Re: The maven-archetype-plugin paradox

As one of the reporters of the breaking change tickets I also rather not see this reverted as I think that our plugins should follow The Maven Way and help people do the right thing. I've seen some voices raises in some of the tickets (after the fact). But how many is it really that has a

Re: Re: Re: Heads up, Plexus IO/Archiver is going Java 7

On Fri, May 5, 2017 at 10:22 AM, Michael Osipov <1983-01...@gmx.net> wrote: > This will also ultimately mean that these plugins will run with Maven 3.3 > only > if someone still uses an older version and Java 6 to build their projects. > I don't follow. Not to confuse anyone we should separate

Re: Heads up, Plexus IO/Archiver is going Java 7

On Fri, May 5, 2017 at 9:01 AM, Olivier Lamy <ol...@apache.org> wrote: > well IMHO we can definitely have everything 7 mandatory... > I'm fine with that, but I think we should at least bump minor version of a plugin when this happens. /Anders > > On 5 May 2017 at 16

Re: Heads up, Plexus IO/Archiver is going Java 7

How would we handle this wrt versions of our plugins when the requirements for those are bumped from Java 6 to Java 7? For example, maven-jar-plugin has plexus-archiver as a dependency. m-jar-p v3.0.2 requires Java 6. Is a bump to v3.1.0 enough for going to Java 7? /Anders On Thu, May 4, 2017

Re: [VOTE] Release Apache Maven 3.5.0

+1, non-binding Tested on Windows 7 with IBM JDK 7.1. One minor regression found [1]. [1] https://issues.apache.org/jira/browse/MNG-6205 /Anders On Tue, Apr 4, 2017 at 12:14 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Hi, > > We solved 86 issues: >

Re: [DISCUSS] Retrospective on Maven 3.5.0-alpha-1

Thanks for the reminder. :-) Working well: 1. Strong release lead 2. CI in better shape 3. Good momentum (right now) Not working well: 1. Scope slipping. "Just one more small thing..." 2. Not a shared view on version meaning (e.g. what's a bug fix release?) 3. Hard to keep up on ML discussions

Fwd: [jira] [Resolved] (MNG-5971) Imported dependencies should be available to inheritance processing

I don't understand. Why is this marked as fixed (with no commit reference) if it's on the 3.6.0-candidate list? There have been several similar cases just recently; has there been some incorrect jira update? /Anders -- Forwarded message -- From: Christian Schulte (JIRA)

Re: MNG-5868 for 3.5.0

Didn't we agree on v3.5.0 to be a drop-in replacement for v3.3.9? IMO fixing MNG-5868 wouldn't fit in that. I'm sorry to say, but I think we're heading back to where we were before the reset. /Anders On Wed, Feb 1, 2017 at 8:42 AM, Hervé BOUTEMY wrote: >

Re: [DISCUSS] How do we want to handle false positives in the integration tests

I favor B. /Anders On Tue, Jan 31, 2017 at 12:42 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > We have kind of established a consensus on how to handle the case where we > want to change the specification of how Maven works going forward. > Specifically, if we decide that the

Re: [VOTE] Reset Maven Core, Integration Tests and Resolver repository master branches

+1 /Anders On Wed, Jan 4, 2017 at 1:16 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Hi, > > We have collectively managed to mess up our ability to follow the original > release plan for 3.4.0 which was originally supposed to consist of an > effective no-op change of

Re: [VOTE] Release Apache Maven Dependency Plugin version 3.0.0

+1 Verified analyze mojo with Maven 3.3.3, IBM JDK 1.7 on Windows 7. Also checked staged doc site. One small issue with 404 link found (MDEP-547); not a blocker. /Anders On Mon, Dec 12, 2016 at 11:20 PM, Robert Scholte wrote: > Hi, > > We solved 25 issues: >

Re: Documenting Maven 3.4.0

Stating any differences campared to older versions would be good as well. /Anders (mobile) Den 14 dec. 2016 01:41 skrev "Manfred Moser" : > I would suggest latest publically available version (so 3.3.9). > > Manfred > > Christian Schulte wrote on 2016-12-13 16:22: > >

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

+1 /Anders On Mon, Dec 5, 2016 at 9:23 PM, Robert Scholte wrote: > +1 > > > On Mon, 05 Dec 2016 13:20:25 +0100, Christian Schulte > wrote: > > Hi, >> >> We solved 3 issues: >> >

Re: Taking Security Seriously

My view is that the artifact checksums deployed have nothing to do with security, but just a way for Maven to verify that the download was ok. It's not verifying that it's the *correct* (valid) artifact that was downloaded. The apache link you're refering to talks about release signatures, not

Re: [VOTE] Maven Assembly Plugin 3.0.0

Currently, the assembly plugin has compilation issues due to the downgrade to plexus-interpolation 1.21. :-( /Anders On Mon, Nov 7, 2016 at 12:42 AM, Olivier Lamy wrote: > Well it's not a big problem and not too long to fix. > I will fix that and do an other vote on

Re: [VOTE] Release Apache Maven Compiler Plugin version 3.6.0

+1 Tested with Maven 3.3.3 and IBM JDK 7.1 on Windows. /Anderfs On Wed, Oct 26, 2016 at 10:29 PM, Robert Scholte wrote: > Hi, > > We solved 7 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12317225=12334708=Text > > There are still a couple

Re: POM Model version 4.1.0 in 3.4.0-SNAPSHOTs

On Wed, Aug 24, 2016 at 11:08 AM, Martijn Dashorst < martijn.dasho...@gmail.com> wrote: > On Wed, Aug 24, 2016 at 8:41 AM, Fred Cooke wrote: > > Fair call re embedded pom, however it's quite convenient to just browse > to > > it and read. > I'd like to vent another opinion:

Re: [VOTE] Release Apache Maven WAR Plugin version 3.0.0

Personally I think a change of default value should go in into 3.0.0 rather than 3.0.1. We have a great oportunity here with v3.0.0 to fix these types of changes. /Anders On Tue, Aug 23, 2016 at 10:22 AM, Romain Manni-Bucau wrote: > +1, created another thread about this

Re: [VOTE] Release Apache Maven WAR Plugin version 3.0.0

+1 non-binding /Anders On Mon, Aug 22, 2016 at 10:01 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 32 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje > ctId=12318121=12331760 > > There are still a couple of issues left in JIRA: >

Re: Building Maven from scratch

I doubt this is possible. We used to support building Maven core with Ant, but IIRC a fairly recent discussion resulted in a decision to stop supporting that. So you need Maven installed to build Maven core. More info here: http://maven.apache.org/guides/development/guide-building-maven.html

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

> > Tycho does not use Aether to resolve p2 artifacts. > I'll shut up then. :-) /Anders > > -- > Regards, > Igor > > On Thu, Jul 28, 2016, at 10:07 AM, Anders Hammar wrote: > > This might be a language thing. "Maven Artifact Resolver API" makes me

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

al purpose tool. It is clear that this never happened > and probably never will. Does it matter? > > > On Jul 28, 2016, at 6:12 AM, Anders Hammar <and...@hammar.net> wrote: > > > > Are we making the non-Maven-specific Aether library/code Maven-specific > >

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

Are we making the non-Maven-specific Aether library/code Maven-specific during this move? If not, then I don't think we should have the Maven part in the name. /Anders On Thu, Jul 28, 2016 at 10:40 AM, Michael Osipov wrote: > I fully agree with you Stephen! > > > Am

Re: [VOTE] Release Apache Maven SCM version 1.9.5

Shouldn't this rather be v1.10.0 as there are new features? /Anders On Fri, Jul 1, 2016 at 1:24 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 24 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828=12331366 > > There are still a couple

Re: Plugin resolution for Maven 3.5

Not sure I completely understand the question, but we've always said that you shouldn't use another plugin as a dependency. Re-usable logic should be kept in a library instead. /Anders On Fri, Jul 1, 2016 at 9:16 AM, Christian Schulte wrote: > Hi, > > I am currently stumbling

Re: VOTE] Release Apache Maven Source Plugin version 3.0.1

Shouldn't this rather be v3.1.0 due to the change of finalName parameter. It's not a bugfix IMO. /Anders (mobile) On Jun 18, 2016 16:49, "Karl Heinz Marbaise" wrote: > Hi, > > We solved 8 issues: > >

Re: Can't build Maven site for m-assembly-p trunk

n? >> 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 <khmarba...@gmx.de> wrote: >> >> > Hi Anders, >> > >> > On 6/14/16 10:11 PM, Ander

Re: Can't build Maven site for m-assembly-p trunk

gt; On 15 June 2016 at 06:18, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > > > 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

Re: Can't build Maven site for m-assembly-p trunk

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-pl

Can't build Maven site for m-assembly-p trunk

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/

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

> > 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

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

On Sat, Jun 11, 2016 at 5:46 PM, Michael Osipov <micha...@apache.org> wrote: > Am 2016-06-11 um 15:25 schrieb Anders Hammar: > >> Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing >> some clear docs about how it is supposed to work from now on. Specif

Re: svn commit: r1747802 - in /maven/release/trunk/maven-release-plugin/src: it/projects/perform/MRELEASE-459/pom.xml main/java/org/apache/maven/plugins/release/PerformReleaseMojo.java

Even if this (breaking) change is for v3.0.0 of the plugin, I'm missing some clear docs about how it is supposed to work from now on. Specifically for the plugin I assume that the idea is that the release profile to use should be specified explicitly? Also, if the releaseProfile in the super-POM

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

> > Some findings: > * pom.properties doesn't include time stamp row (exists in v3.0.0) > * MANIFEST.MF does not include Archiver-Version element (exists in v3.0.0) > - seems to be an intentional change in plexus-archiver 3.3 > > Is the change to pom.properties intentional? > I'll answer this

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

Some findings: * pom.properties doesn't include time stamp row (exists in v3.0.0) * MANIFEST.MF does not include Archiver-Version element (exists in v3.0.0) - seems to be an intentional change in plexus-archiver 3.3 Is the change to pom.properties intentional? I vote 0. /Anders On Mon, Jun 6,

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

+1 /Anders On Fri, Jun 3, 2016 at 11:36 PM, Karl Heinz Marbaise wrote: > Hi, > > We solved 4 issues: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317827=12335752 > > There are still a couple of issues left in JIRA: > >

Re: [VOTE] Release Apache Maven Shared Component: Maven Filtering 3.1.1 (Take 2)

+1 /Anders On Mon, May 30, 2016 at 10:37 PM, Karl Heinz Marbaise wrote: > Hi, > > We have solved 6 issues: > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSHARED%20AND%20fixVersion%20%3D%20maven-filtering-3.1.1 > > There are still a couple of issues left in

  1   2   3   4   5   6   >