From issues-return-172455-apmail-maven-issues-archive=maven.apache.org@maven.apache.org Sun Sep 6 19:06:02 2020 Return-Path: X-Original-To: apmail-maven-issues-archive@locus.apache.org Delivered-To: apmail-maven-issues-archive@locus.apache.org Received: from mxout1-ec2-va.apache.org (mxout1-ec2-va.apache.org [3.227.148.255]) by minotaur.apache.org (Postfix) with ESMTP id 9BAE91ACF6 for ; Sun, 6 Sep 2020 19:06:02 +0000 (UTC) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-ec2-va.apache.org (ASF Mail Server at mxout1-ec2-va.apache.org) with SMTP id 56AA84267D for ; Sun, 6 Sep 2020 19:06:02 +0000 (UTC) Received: (qmail 86257 invoked by uid 500); 6 Sep 2020 19:06:02 -0000 Delivered-To: apmail-maven-issues-archive@maven.apache.org Received: (qmail 86222 invoked by uid 500); 6 Sep 2020 19:06:01 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 86204 invoked by uid 99); 6 Sep 2020 19:06:01 -0000 Received: from mailrelay1-us-west.apache.org (HELO mailrelay1-us-west.apache.org) (209.188.14.139) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 06 Sep 2020 19:06:01 +0000 Received: from jira-he-de.apache.org (static.172.67.40.188.clients.your-server.de [188.40.67.172]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id BC023411E3 for ; Sun, 6 Sep 2020 19:06:00 +0000 (UTC) Received: from jira-he-de.apache.org (localhost.localdomain [127.0.0.1]) by jira-he-de.apache.org (ASF Mail Server at jira-he-de.apache.org) with ESMTP id 170057802E2 for ; Sun, 6 Sep 2020 19:06:00 +0000 (UTC) Date: Sun, 6 Sep 2020 19:06:00 +0000 (UTC) From: "Martin Kanters (Jira)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MNG-6980) Add opposite to --resume-from MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MNG-6980?page=3Dcom.atlassian.j= ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D171913= 62#comment-17191362 ]=20 Martin Kanters commented on MNG-6980: ------------------------------------- I think this could be a useful option even though there might not be many u= se cases for this. I think yours seems to be an exceptional one. Currently the reactor is almost fully configurable by the user, but your re= quested feature is indeed missing. One downside is that we should be conservative with adding CLI flags (espec= ially for unique cases like this), but in my opinion this would be a nice a= ddition.=C2=A0 If no-one objects [~mthmulders]=C2=A0and I could pick this up, since we hav= e been working a lot on the reactor lately.=C2=A0 > Add opposite to --resume-from > ----------------------------- > > Key: MNG-6980 > URL: https://issues.apache.org/jira/browse/MNG-6980 > Project: Maven > Issue Type: New Feature > Components: Command Line > Affects Versions: 3.6.3 > Reporter: Knut Wannheden > Priority: Major > > It would be very nice if the {{mvn}} command could offer an option which = basically has the opposite effect of {{\--resume-from}}. E.g. something lik= e {{\--stop-at}}, {{\--stop-after}}, {{\--build-until}} or similar. > I have often wanted an option like this. Most recently it has been when w= orking on Quarkus, where I can't simply use {{\--also-make}} because some o= f the dependencies are not known to Maven and discovered dynamically by the= Quarkus plugin at build-time. -- This message was sent by Atlassian Jira (v8.3.4#803005)