+1 (non binding)
On Wed, Feb 28, 2024 at 8:31 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
; >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> | Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <
> > https://github.com/rmannibucau> |
> > Li
20 à 18:52, Christian Stein a écrit :
>
> > On Mon, May 4, 2020 at 6:45 PM Romain Manni-Bucau >
> > wrote:
> >
> > > Le lun. 4 mai 2020 à 18:30, Stephane Nicoll >
> > a
> > > écrit :
> > >
> > > ...
> >
> > > OK. Wh
On Mon, May 4, 2020 at 5:55 PM Romain Manni-Bucau
wrote:
> Le lun. 4 mai 2020 à 17:23, Stephane Nicoll a
> écrit :
>
> > On Mon, May 4, 2020 at 5:17 PM Romain Manni-Bucau >
> > wrote:
> >
> > > Le lun. 4 mai 2020 à 17:06, Stephane Nicoll >
> &g
On Mon, May 4, 2020 at 5:17 PM Romain Manni-Bucau
wrote:
> Le lun. 4 mai 2020 à 17:06, Stephane Nicoll a
> écrit :
>
> > Thanks but that doesn't really answer my question. That version is picked
> > up by dependency management of the project as far as I can tell. If
b.com/application-development/java-ee-8-high-performance
> >
>
>
> Le lun. 4 mai 2020 à 16:35, Stephane Nicoll a
> écrit :
>
> > An update. This may be the other fixed issue in that release actually
> > (SUREFIRE-1764). Is JUnit engine 1.6.1 now mandatory? What
An update. This may be the other fixed issue in that release actually
(SUREFIRE-1764). Is JUnit engine 1.6.1 now mandatory? What happens for
projects that are using an older JUnit version?
On Mon, May 4, 2020 at 3:59 PM Stephane Nicoll
wrote:
> I am not sure that SUREFIRE-1679 is fixed. I
I am not sure that SUREFIRE-1679 is fixed. I've ran the Spring Boot build
with 2.22.2 and reproduced the error there. Upgrading to this candidate
release and I got this error.
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.22.3:test (default-test)
on project spring
+1 (non-binding anymore).
Cheers,
S.
On Tue, Feb 11, 2020 at 1:47 PM Enrico Olivelli wrote:
> Thank you Hervé
>
> I need two more binding +1 please
>
> Enrico
>
> Il Sab 8 Feb 2020, 21:43 Hervé BOUTEMY ha scritto:
>
> > +1
> >
> > I was able to rebuild (with JDK 8) .jar, -sources.jar and
> > -
+1
On Tue, Oct 29, 2019 at 10:11 PM Karl Heinz Marbaise
wrote:
> 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
> Karl Hei
I second that though I've seen some activity today, including a fix that
allows the Spring Boot project to upgrade to Maven 3.6[1]. Looking forward
to a release of the plugin!
Thanks,
S.
[1] https://github.com/mojohaus/flatten-maven-plugin/issues/89
On Sun, Oct 6, 2019 at 11:52 AM Falko Modler
+1
On Fri, Aug 23, 2019 at 3:17 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,
> including our
+1
Thanks a lot for your help Enrico!
On Sat, Apr 27, 2019 at 6:04 PM Enrico Olivelli wrote:
> Hi,
>
> We solved 1 issue:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12345433&styleName=Text&projectId=12317927&Create=Create&atl_token=A5KQ-2QAV-T4JA-FDED%7C568123541489d6320
t;
> but I have to do some burocratic steps in JIRA before sending the
> official [VOTE] email
> I have sent other emails on this mailing list in order to complete my task
>
> @Stephane Nicoll if you want to try out the artifacts you are welcome.
> Anyway I will expect an offici
; >>> > > > > unfortunately rework internal code in Surefire project which
> >>> takes
> >>> > > > really a
> >>> > > > > lots of time and spends private energy, and thus 2.22.2 is less
> >>> > > important
>
ble, we'll
> probably
> need a grace period with warnings for people setting such read-only
> parameters
> before really breaking such abnormal builds
>
> Regards,
>
> Hervé
>
> Le jeudi 4 avril 2019, 13:22:17 CEST Stephane Nicoll a écrit :
> > Hey,
> >
>
Hey,
I have a weird case trying to deprecate a "finalName" property where said
property can still be set by the user.
Here is the definition:
/**
* Name of the generated archive.
* @since 1.0
*/
@Parameter(defaultValue = "${project.build.finalName}", readonly = true)
private String finalName;
vious developers on the board as well and grow the team, i.e.
> Andreas and Kristian.
>
> Cheers
> Tibor
>
>
> On Mon, Mar 25, 2019 at 5:11 PM Stephane Nicoll >
> wrote:
>
> > Thanks for having a look Tibor!
> >
> > On Mon, Mar 25, 2019 at 4:37 PM Tib
gt; But the benefit in this concept is that we define it once and we won't have
> any reason to change this concept again in another version.
> Makes sense?
>
> Cheers
> Tibor
>
> On Mon, Mar 25, 2019 at 3:38 PM Stephane Nicoll >
> wrote:
>
> > Hey,
>
Hey,
Can someone working on surefire confirm the interest of creating that
branch in the main repo and kick-off a release if a review is satisfactory?
Thanks!
S.
On Wed, Mar 13, 2019 at 4:09 PM Stephane Nicoll
wrote:
> Hey,
>
> I've created a `2.22.x` branch based on the 2.22.
75b8db7861aaefb5af4c256d919a9b2e7a
>
> [2]:
>
> https://github.com/apache/maven-surefire/commit/19006aa70f36705f399b8c105a16f636904f00f3
>
> Cheers
> Tibor
>
> On Mon, Feb 25, 2019 at 8:54 AM Stephane Nicoll >
> wrote:
>
> > Hi everyone,
> >
> &
BOM with
> > dependencyManagement but not the pluginManagement.
> > We did not break current users and so we split the entire work into
> > multiple stages. The naming convention really is not a problem as you can
> > see and Stephane confirmed it.
> > So we made welcom
;t. The name is not the problem by the way as I've hopefully
indicated above.
Thanks,
S.
>
> Cheers
> Tibor
>
>
> On Mon, Feb 25, 2019 at 8:54 AM Stephane Nicoll >
> wrote:
>
> > Hi everyone,
> >
> > It's great to see the progress on Surefi
Hi everyone,
It's great to see the progress on Surefire 3.0 and I wanted to reach out to
discuss a practicable problem with the 2.x line. There are a number of
fixes for JUnit 5 that are only available in the 3.x line that isn't GA
yet. [1][2]
Putting my Spring Boot hat for a min, this actually p
au> | Book
> <
> https://www.packtpub.com/application-development/java-ee-8-high-performance
> >
>
>
> Le mer. 5 sept. 2018 à 10:07, Stephane Nicoll
> a
> écrit :
>
> > How do I reproduce this problem concretely? Having to specify a
> dependency
&g
How do I reproduce this problem concretely? Having to specify a dependency
in surefire is not an option for us as we want the JUnit5 provider to be
detected automatically.
I've upgraded a Spring Boot project to use 5.3.0 and I don't see any
problem.
Thanks,
S.
On Tue, Sep 4, 2018 at 10:46 PM Ro
Welcome Sylwester!
On Sun, Sep 2, 2018 at 12:58 PM Karl Heinz Marbaise
wrote:
> 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 fun!
>
> Than
+1
Thanks,
S.
On Thu, 26 Jul 2018 at 19:28, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 18 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341563
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jq
Good point about the release number there though. I'd be +1 for 3.8.0 as
well.
On Thu, Jul 26, 2018 at 1:37 PM Robert Scholte
wrote:
> -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 update the
> version, but
+1
Thanks,
S.
On Wed, Jul 25, 2018 at 10:18 PM Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 18 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317225&version=12341563
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/
+1
Thanks,
S.
On Sun, Jun 17, 2018 at 10:45 PM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 16 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12342826&styleName=Text&projectId=12316922
>
> There are 356 issues left in JIRA for Maven c
+1
Thanks,
S.
On Tue, Jun 12, 2018 at 8:45 PM Robert Scholte wrote:
> Hi,
>
> We solved 28 issues (including those for M1):
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520&version=12343432&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> http
+1
On Tue, Jun 12, 2018 at 3:31 AM Tibor Digana wrote:
> Hi,
>
> We solved 15 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12343247
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/i#issues/?jql=project+%
> 3D+
+1
On Sat, 9 Jun 2018 at 15:46, Karl Heinz Marbaise wrote:
> Hi,
>
> I need at least one more PMC Vote...someone there?
>
> Kind regards
> Karl Heinz Marbaise
>
> On 08/06/18 19:06, Karl Heinz Marbaise wrote:
> > Hi,
> >
> > I need at least one more PMC Vote...
> >
> > Kind regards
> > Karl Hein
+1
S.
On Fri, Mar 9, 2018 at 9:47 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 41 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317422&version=12330696
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=proje
>
>
> > Regards,
> > Sylwester
> >
> > czw., 1 mar 2018 o 19:45 użytkownik Dan Tran
> napisał:
> >
> > > Hi all
> > >
> > > Sylwester Lachiewicz provided a fix for jansi 1.18-SNAPSHOT which
> > resolves
> > >
+1 (also tested on JDK10)
Thanks,
S.
On Sat, Mar 3, 2018 at 12:42 PM, Tibor Digana
wrote:
> Hi,
>
> We solved 33 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317927&version=12341630
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.o
+1
Thanks,
S.
On Sat, Feb 24, 2018 at 11:01 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> On 24 February 2018 at 22:00, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > Hi,
> >
> > We solved 22 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jsp
+1
Thanks,
S.
On Sun, Jan 7, 2018 at 8:20 AM, Hervé BOUTEMY wrote:
> +1
>
> Regards,
>
> Hervé
>
> Le jeudi 4 janvier 2018, 11:27:02 CET Robert Scholte a écrit :
> > Hi,
> >
> > We solved 13 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317223&ve
> > rsion=1
+1
S.
On Sun, Sep 10, 2017 at 5:39 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> version=12338964&styleName=Text&projectId=12316922
>
> There are 350 issues left in JIRA for Maven core:
>
+1
Thanks!
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&version=12341254
>
> There are still a couple of issues left in JIRA:
> https://issues.apache.org/jira/issues/?jql=p
+1
On Sat, 19 Aug 2017 at 16:01, Robert Scholte wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921&version=12339197&styleName=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql
+1 tested with various projects (including the regression that was
affecting Spring Boot).
Thanks!
On Sun, Aug 13, 2017 at 2:18 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317220&version=12338667
>
> There
+1 the spring boot project is waiting for a new release as well.
On Fri, 11 Aug 2017 at 12:47, Mat Booth wrote:
> Hi all,
>
> Are there any plans for a maven-assembly-plugin release?
>
> At Eclipse project we are keen to use the xz tarball compression support
> :-)
>
> Thanks!
>
--
Sent from my
+1
> On 27 July 2017 at 06:58, Robert Scholte wrote:
>
> > Hi,
> >
> > We solved 14 issues:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> > ctId=12317520&version=12330768&styleName=Text
> >
> > There are still a couple of issues left in JIRA:
> > https://issues.apache.org/ji
+1
Thanks Olivier!
S.
On Wed, Jul 26, 2017 at 1:44 AM, Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven Compiler Plugin version 3.6.2.
>
> We fixed 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?
> projectId=12317225&version=12339154
>
> Staging repo: https://re
Hey,
There are only 3 issues fixed and the last release was in January this
year. Any objection to release 3.6.2?
Cheers,
S.
+1
S.
On Tue, 4 Apr 2017 at 00:14, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> Hi,
>
> We solved 86 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12336084&styleName=Text
>
> In there are 324 issues left in JIRA for Maven core:
>
>
I might come on Sunday.
On Thu, 5 Jan 2017 at 14:20, Robert Scholte wrote:
> Hi,
>
>
>
> Just like the last couple of years FOSDEM has been a great opportunity to
>
> meet several Maven developers.
>
> Some of the new features and improvements started here when the Maven
>
> committers shared t
+1
On Wed, 4 Jan 2017 at 17:39, Manfred Moser wrote:
> +1 (committer)
>
>
>
> Stephen Connolly wrote on 2017-01-04 04:16:
>
>
>
> > 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
Isn't that postponing the discussion we're having here on those
controversial changes? I'd rather give it an extra effort rather than
pushing it back and loosing all the context once we have to tackle 3.5.
On Sun, Dec 18, 2016 at 10:02 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
Awesome Christian, it's much better now.
Thank you!
On Wed, Sep 14, 2016 at 3:48 PM, Christian Schulte wrote:
> Am 09/14/16 um 13:50 schrieb Stephane Nicoll:
> > Dependency 'org.springframework.cloud:spring-cloud-commons:jar' has
> > conflict
On Wed, Sep 14, 2016 at 1:32 PM, Christian Schulte wrote:
> Am 09/14/16 um 08:42 schrieb Stephane Nicoll:
> > First of all, I'd like the error message to change. I still don't know to
> > this day what it means. Second, if Maven is able to find out that two
>
s this
warning is an excellent move IMO. But just change the damn error message ;-)
Cheers,
S.
>
> On Tue, Sep 13, 2016 at 10:47 AM, Stephane Nicoll
> wrote:
> > On Tue, Sep 13, 2016 at 2:50 PM, jieryn wrote:
> >
> >> I reported this for Arquillian, earlier...
&
he
causing imports in the inheritance hierarchy to apply standard override
logic based on artifact coordinates."
Thanks!
S.
>
> I don't think I've seen a more clear piece of evidence for Maven
> pom.xml technical debt. :-)
>
> On Tue, Sep 13, 2016 at 4:30 AM, Stepha
Hi,
This command creates a vanilla project using Spring Cloud that has a
hierarchy of BOMs
curl https://start.spring.io/starter.zip -d
dependencies=cloud-config-client -o demo.zip
extract and run and you'll get plenty of warnings[1]
I am trying to make sense of this message:
To resolve this co
Welcome Benedikt!
On Sat, Aug 27, 2016 at 11:14 AM, Benedikt Ritter
wrote:
> Hello maven community,
>
> I'm Benedikt Ritter, 30 years old from Neuss (Germany). I'm committer and
> member of the project management committee of the Apache Commons project. I
> just wanted to introduce myself, since
Sorry to be a party pooper but is there any way we could include MWAR-262
still?
Thanks,
S.
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&version=12331760
>
> There are s
Hey,
I am curious, are we involved in any way with the Maven central download
statistics thing? I am asking because I think I've found a major problem[1]
and I am happy to investigate. I just don't know where the code is.
Cheers,
S.
[1] https://issues.sonatype.org/browse/MVNCENTRAL-1159
I disagree. Changing system requirements in a minor release is kind of
weird so I'd rather say that the current practice is problematic. I
actually don't know the rationale to require Java8 in the codebase but if
we do it please let's label that as a major release.
S.
On Tue, Dec 1, 2015 at 8:10
+1
S.
On Wed, May 13, 2015 at 8:55 AM, Hervé BOUTEMY
wrote:
> Hi,
>
> I'd like to introduce Manfred Moser as committer for the Apache Maven
> project.
>
> He's working on Android Maven plugin for years, has great discussions both
> on
> users and dev MLs, has a great attitude.
> And he's just
I clearly overlooked this one, sorry.
+1
On Wed, Dec 31, 2014 at 1:02 PM, Karl Heinz Marbaise
wrote:
> Hi,
>
> just one VOTE is missing ;-)...
>
> Kind regards
> Karl Heinz Marbaise
> On 12/28/14 3:30 PM, Karl Heinz Marbaise wrote:
>
>> Hi,
>>
>> We solved 19 issues:
>> http://jira.codehaus.org
On Mon, Dec 15, 2014 at 2:15 PM, Gary Gregory
wrote:
> As "cute" as "Shutgun" might seem, for some unspecified definition of
> "cute", I am sick of hearing about any kind of gun...
>
> http://www.chicagotribune.com/news/nationworld/chi-school-shootings-sandy-hook-20141211-story.html
Same here.
B E
On Tue Dec 09 2014 at 11:52:59 AM Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> H, E, K
>
> On 9 December 2014 at 10:52, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > This is a run-off vote to select the top two options for our new mascot's
> > name.
> >
>
+1
On Tuesday, November 25, 2014, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> For anyone who has been living under a rock, here is the background
>
> Background
> =
>
> I think everyone can agree that the site needs a reorganisation and a
> rewrite. Users cannot find what
Congrats Karl!
On Tue, Aug 26, 2014 at 7:41 AM, Barrie Treloar wrote:
> I'm pleased to announce that the Maven PMC has voted to add Karl to the
> Maven PMC.
>
> Welcome, Karl.
>
+1
Thanks,
S.
On Mon, Jun 16, 2014 at 9:33 PM, Robert Scholte
wrote:
> +1
>
> * maven-ear-plugin-2.9.1-source-release.zip results in BUILD SUCCESS
> * [INFO] Rat check: Summary of files. Unapproved: 0 unknown: 0 generated:
> 0 approved: 330 licence.
> * SHA1 correct
> * Site is ok
>
> Robert
>
+1
S.
On Sat, Mar 22, 2014 at 10:52 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> based on the decision we have made on the 18. february 2014 to define End
> Of Life of Maven 2 http://maven.apache.org/maven-2.x-eol.html
>
> I would suggest to retire the Maven Reactor Plugin.
> The last release has b
Welcome!
S.
On Mon, Mar 17, 2014 at 8:53 PM, Robert Scholte wrote:
> Hi,
>
> On behalf of the Apache Maven PMC I am pleased to announce that Mirko
> Friedenhagen (mfriedenhagen) has been voted in as a new Apache Maven
> committer.
>
> Mirko, welcome on board and have a lot of fun!
>
> thanks,
>
Probably because not a lot of folks are using it. It's a mistake, go ahead
and add it.
Thanks,
S.
On Thursday, February 20, 2014, Karl Heinz Marbaise
wrote:
> Hi,
>
> so after taken a look into SVN it looks a little bit strange to me.
>
> The entry for the maven-acr-plugin has been added in r10
+1
On Thu, Feb 13, 2014 at 4:14 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
> We have not made a release of Maven 2.x since 2.2.1 which was August 2009.
>
> During that period no release manager has stepped up to cut a release.
>
> I would argue that we should just therefore
Hi,
Has anybody thought (or worked on) the ability to exclude dependencies from
the import of a pom for a given project.
Let's say that project S uses commons-logging and we use that project in
our project. We have something like
the-s-project
...
pom
import
Now I'd like to exc
+1, thanks!
S.
On Tue, Nov 26, 2013 at 9:45 PM, Robert Scholte wrote:
> Hi,
>
> We solved 11 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?
> projectId=11132&version=18770&styleName=Html
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNav
Honestly, I don't really see the problem. Looking at the latest release[1],
there are 4 required parameters indeed but the default value is defined (in
bold). I don't think this is specific to the EAR plugin actually: the jar
plugin has exactly the same kind of doc! [2]
Maybe the required paramete
Welcome on board!
On Wed, Oct 16, 2013 at 4:57 AM, Olivier Lamy wrote:
> Hi all,
>
> Please welcome Bartholdi Dominik as a new committer of the Apache
> Maven project. The Apache Maven PMC has voted to grant committership
> to him.
>
> The account have already been set up and he can begin worki
Yep, +1 for 3.2 and onward.
S.
On Sat, Oct 5, 2013 at 5:03 AM, Jason van Zyl wrote:
> Given the vote we had about releases after September does anyone mind if I
> update the source/target levels to 1.6 for the core?
>
> Thanks,
>
> Jason
>
>
Hi,
On Mon, Aug 19, 2013 at 1:38 PM, Jason van Zyl wrote:
> I hope to release the next version in pretty short order, integrating
> Aether 0.9.0.M3 and fixing a few more bugs. So if you can't do the things
> you want by tomorrow I think we'll have another release in a couple weeks.
>
This certa
On Sun, Jul 28, 2013 at 6:48 PM, Robert Scholte wrote:
> Hi,
>
> Personally I'm not a huge fan of the release-model as done by Jenkins,
> meaning releasing once or twice a week with only a few fixes.
> As a user I'm not going to update for every new release, it most have real
> value before I upgr
+1
On Tue, Jul 23, 2013 at 8:23 PM, Dennis Lundberg
wrote:
> Hi,
>
> This is the final release of this plugin. After this release it will
> be retired, see separate vote thread for more info on that.
>
> We solved 1 issue:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11135&styl
Same here.
On Sunday, March 3, 2013, Benson Margulies wrote:
> As I see it, you are using the version number to communicate with the
> tiny number of people who have made plugins that depend on Aether.
>
> I would rather see us use the version number to communicate with the
> vast number of peopl
+1
S.
On Saturday, March 2, 2013, Benson Margulies wrote:
> Based on the sentiment on the discussion thread, I call a formal vote
> to end support for Maven 1.x. This is a vote to:
>
> 1: Remove maven 1 release materials from the primary distribution
> area, leaving them only on the archive.
>
>
+1
S.
On Tue, Feb 19, 2013 at 4:28 PM, Olivier Lamy wrote:
> Hi,
> We fixed 1 issue:
>
> https://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=19088
>
> Staging repository:
> https://repository.apache.org/content/repositories/maven-270/
>
> Staging distribution:
> https://d
I was testing this on one of our projects that has "good" use of forkmode
for all kinds of reasons and I have one test that is consistently stuck
with this but it's stuck with 2.12.4 too so I am not going to -1 but I
can't vote +1 either...
I'll investigate a bit more and report the issue later.
I would go for 2.2. Releasing something and then include it as the default
version the same day seems a bit too much for me.
On Thursday, November 29, 2012, Jason van Zyl wrote:
> I'm going to re-spin it. Shall I just use 2.2 or wait for you guys to spin
> 2.4?
>
> On Nov 28, 2012, at 12:54 PM, D
+1
S.
On Fri, Nov 16, 2012 at 12:36 AM, Olivier Lamy wrote:
> Hi,
> I'd like to release Maven Compiler 3.0
> We fixed 9 issues.
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=18537&styleName=Text&projectId=11130&Create=Create
>
> Staging repository:
> https://repository.apache.or
+1
On Tue, Oct 9, 2012 at 1:02 PM, Olivier Lamy wrote:
> Hi,
> I'd like to release Maven Sources Plugin 2.2.1.
> We fix 1 blocking issue which prevent some users to upgrade:
> http://jira.codehaus.org/browse/MSOURCES-62
>
> Staging repository:
> https://repository.apache.org/content/repositories
+1
Thanks,
S.
On Fri, Sep 28, 2012 at 8:08 AM, Dennis Lundberg wrote:
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11150&styleName=Html&version=18298
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigato
+0
S.
On Wed, Sep 5, 2012 at 1:04 PM, Olivier Lamy wrote:
> Hi,
> This vote is to decide moving our source tree currently located in one
> svn repository to git (multiple git repositories).
> First, we need to have at least 3 volunteers to help on Apache infra
> for this move and more generally
The Maven team is pleased to announce the release of the Maven EAR
Plugin, version 2.8
The plugin generates a JavaEE Enterprise Archive (EAR) file.
http://maven.apache.org/plugins/maven-ear-plugin/
You should specify the version in your project's plugin configuration:
org.apache.maven.plugin
Hi,
The vote has passed with the following result :
+1 (binding): Hervé Boutemy, Mark Struberg, Olivier Lamy and Stéphane Nicoll
+1 (non binding): Tony Chemit
I will promote the artifacts to the central repo.
Best,
S.
-
To uns
Before I forget, my +1
S.
On Wed, Aug 29, 2012 at 7:18 PM, Stephane Nicoll
wrote:
> Hi,
>
> We solved 7 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&styleName=Html&version=18269
>
> There are still around 15 issues left in JIRA:
> ht
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11132&styleName=Html&version=18269
There are still around 15 issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11132&status=1
Staging repo:
https://repository.apache.org/conte
+1
S.
On Sun, Aug 26, 2012 at 10:11 PM, Hervé BOUTEMY wrote:
> Hi,
>
> We solved 5 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11142&version=18715&styleName=Html
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?re
+1
S.
On Fri, Aug 24, 2012 at 10:49 AM, Olivier Lamy wrote:
> Hi,
> I'd like to release Maven Dependency Plugin 2.5.1.
> This release contains a regression issue fix and a perf improvement
> (https://jira.codehaus.org/browse/MDEP/fixforversion/18718)
>
> Staging repository:
> https://repository.
The Maven team is pleased to announce the release of the Maven Resources
Plugin, version 2.6
The Resources Plugin handles the copying of project resources to the
output directory.
http://maven.apache.org/plugins/maven-resources-plugin/
You should specify the version in your project's plugin conf
Hi,
The vote has passed with the following result :
+1 (binding): Stephen Connolly, Robert Scholte, Hervé Boutemy, Olivier
Lamy and Stéphane Nicoll
+1 (non binding): Tony Chemit
I will promote the artifacts to the central repo.
Best,
S.
--
ugin:
> "scp://people.apache.org/www/maven.apache.org/scm/maven-scm-plugin"
>
> Regards,
>
> Hervé
>
> [1] http://maven.apache.org/plugins/maven-resources-plugin-2.6/maven-
> resources-plugin/plugin-management.html
>
> Le mercredi 15 août 2012 12:45:31 Stephane Nicoll a
+1
S.
On Wed, Aug 15, 2012 at 12:45 PM, Stephane Nicoll
wrote:
> Hi,
>
> We solved 9 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&styleName=Html&version=17177
>
> There are still around 30 issues left in JIRA:
> http://jira.codehaus.o
Hi,
We solved 9 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11145&styleName=Html&version=17177
There are still around 30 issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11145&status=1
Staging repo:
https://repository.apache.org/conte
Hi guys,
Per Stephen comment, I am going to cancel this one and fix the IT.
Thanks,
S.
-- Forwarded message --
From: Stephane Nicoll
Date: Wed, Aug 15, 2012 at 8:50 AM
Subject: [VOTE] Release Maven Resources Plugin version 2.6
To: Maven Developers List
Hi,
We solved 9
1 - 100 of 1039 matches
Mail list logo
