standard approach were to be agreed upon and then it would be
implemented in the main plugins thats a different story (and potentially
a LOT of work).
So for Calum - you would have to specify more what you want to achieve,
figure out a plan and then work on implementation.
Manfred
On 2025-07-10 3
There is significantly less backing (nearly none) from any commercial
entities. There is no product management team or PR team or ... we just
get by with anyone chipping in as they can .. and that varies a LOT.
Manfred
On 2025-05-24 12:26 p.m., John Neffenger wrote:
I'm genuinely curiou
and I am still baffled by some thinking it
should work with an old, outdated JDK.
Manfred
On 2025-05-24 10:52 a.m., Karl Heinz Marbaise wrote:
Hi,
greatly summarized.
Thank you for that.
Kind regards
Karl Heinz Marbaise
On 24.05.25 19:21, Michael Bien wrote:
On 5/24/25 15:33, Elliotte
Personally I am opposed to changing the default to a worse format and
introduce a breaking change.
The `v` is redundant. If users want to use that we should enable a
configuration to do so (I think that exists already) but the default
should stay as is and use the project version.
On 2025-05
or Maven 4
before we release a final version.
Manfred
On 2025-05-03 11:57 p.m., Matthias Bünger wrote:
Morning everyone,
first I would like to thank everybody who participated in the vote
[*1] about lifting the required Java version to 21 for Maven 4.0.0.
The vote has ended with the follo
I assume you are also aware of the yaml support in Polyglot Maven
https://github.com/takari/polyglot-maven
Feel free to check that out and pull relevant bits for it all to go
upstream.
Manfred
On 2025-03-05 8:16 a.m., Guillaume Nodet wrote:
Hey !
A while ago, I created a Hocon based POM
I used to use this plugin quite a bit but things have definitely moved
on .. so
+1
Manfred
On 2025-02-13 1:22 p.m., Slawomir Jaranowski wrote:
+1 for retirement.
On Wed, 12 Feb 2025 at 20:00, Matthias Bünger
wrote:
Hi all,
some months ago, we noticed that the regular build of the Maven
I agree with idea of keeping comments. In fact I think it might be best
to somehow select for each comment section to be part of the consumer
pom or not.
Not sure how to achieve that cleanly though
Manfred
On 2025-02-09 11:28 a.m., Anders Hammar wrote:
Hi,
I and Robert did a Maven 4
Maybe it would be good to prefix all branches the the github names of
owners.. at least it is easier to find the person then to figure out
next steps..
For existing branches.. maybe check who the last committer was..
Manfred
On 2025-01-24 4:37 a.m., Elliotte Rusty Harold wrote:
Just trying
mited for each contributor and committer. Honestly .. I can not
imagine working without my personal forks of projects I contribute to.
Manfred
use the main repo nothing stops
other committers to push changes into the branches.. or even delete them.
Manfred
On 2025-01-06 8:51 a.m., Elliotte Rusty Harold wrote:
Well, it's not like abandoned branches cost anything significant, but
as someone else suggested if there's no activi
o all our benefit. The core Maven repos
for the project should be as slim and simple as possible and not contain
any personal branches or features or tags or whatever.
Manfred
On 2025-01-06 8:02 a.m., Tamás Cservenák wrote:
Howdy,
This is all nice and dandy with you explaining how things are
Fair enough .. that would be good as well. If we have no clear way for a
reasonable default value .. the default can be a warning with advice.
manfred
On 2024-09-24 2:06 p.m., Tamás Cservenák wrote:
Just to tie to the previous message:
we also discussed making ".mvn" directory _
Without looking at the details in the PR or issue..
I strongly support this on principle. Maven was always about doing the
right thing out of the box. I think this falls very much in that category.
+1
Manfred
On 2024-09-24 12:03 a.m., Hervé Boutemy wrote:
everything is in the title
Jira
+1 .. works flawlessly with Trino Gateway and a few other smaller projects
manfred
mmo...@apache.org
On 2024-06-14 7:28 a.m., Sylwester Lachiewicz wrote:
+1
pt., 14 cze 2024, 08:33 użytkownik Karl Heinz Marbaise
napisał:
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 13.06.24 10:49
Looks good!
+1
On 2024-05-21 8:17 a.m., Tamás Cservenák wrote:
Howdy,
We solved 6 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721&version=12354608
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/projects/MWRAPPER/issues
Stagin
Awesome work everyone. It is great to see all the progress Maven and
related tooling is making.
Manfred
On 2024-04-23 2:12 p.m., Tamás Cservenák wrote:
Howdy,
This is just a short newsflash about upcoming planned releases related to
Maven.
Recently we got a huge spike in plugin releases
+100 (committer)
For build and runtime and source code level.
Also +100 for later upgrade to 21 ;-)
On 2024-02-27 23:30, 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 th
experience with the upgrade in the Trino project the
leap from 17 to 21 is relatively small.
Manfred
On 2024-02-22 14:40, Brian Fox wrote:
That feels right to me based on the data and all the discussion so far.
On Thu, Feb 22, 2024 at 3:49 PM Tamás Cservenák wrote:
I think this starts to
next LTS.
Manfred
On 2024-01-22 4:33 a.m., Benjamin Marwell wrote:
To add some more information, I have seen some extreme reduction in
build times after switching from Java 11 to 17 or even 21 (just for
build, not the runtime).
We can still verify it runs on 11/17 by using the integration tests
against staying with an outdated version that
reached EOL years ago.
Manfred
On 2023-06-05 15:31, Hunter C Payne wrote:
Other projects have tried to do that (given they are different types of
projects) and it turned out that keeping JVM8 support going when not compiling
on JDK8 proved difficult
painful.
Manfred
On 2023-05-31 03:00, Tamás Cservenák wrote:
+1 for the move to Java 17 with Maven 4 (am actually for "move to latest
current Java LTS")
As anyone can see, all the major (OSS) projects did or are in the middle of
pushing for Java 17.
In September we have Java 21. The Ja
Massive congratulations! I am so glad we got beyond the milestones finally.
Manfred
On 2023-03-14 03:11, Slawomir Jaranowski wrote:
Hi
The Apache Maven team is pleased to announce the availability of Maven
Surefire 3.0.0
Release Notes - Maven Surefire - Version 3.0.0
** Bug
* [SUREFIRE
as well.
Manfred
On 2022-11-18 9:55 a.m., Tamás Cservenák wrote:
Howdy,
My pet peeve these days is our release process. IMHO, we should be able to
release ("move") much faster than today.
My proposal would be:
* vote is "done done" the moment quorum is reached
* change the
itself and various plugins use
this stuff a lot.. and various apache projects use it as well
manfred
On 2022-11-17 04:24, Tamás Cservenák wrote:
Howdy,
It's not about losing at all, on the contrary: my "proposal" would be to
keep reporting, but make them write in "interm
then send a pull request ;-)
Manfred
Graham Leggett wrote on 2022-06-17 10:14 (GMT -04:00):
> Hi all,
>
> I find myself with a large project, not knowing which dependency(ies) is
> transitively providing a given class.
>
> Is there a plugin that will allow a search within a
Awesome work everyone. I am glad this made it to the users from Apache now.
Manfred
Hervé Boutemy wrote on 2022-05-14 07:06 (GMT -07:00):
> The Apache Maven team is pleased to announce the release of the Apache Maven
> Wrapper, version 3.1.1.
>
> The Maven Wrapper is an easy way
I could not agree more. It is extremely important for users to understand that
we
are NOT a commercial entity providing support. And contrary to other open source
products there is large, well known commercial entity either.
I also second all the other points from Tamas.
Manfred
Tamás
You can build locally and test that way as well. I used to do that with local
repository as well as a locally running repository manager (Sonatype Nexus).
Manfred
Dan Tran wrote on 2021-12-13 22:53 (GMT -08:00):
> Hi
>
> Could you deploy a snapshot? my company repository manager
Awesome. Thank you Herve.
+ 100
Hervé BOUTEMY wrote on 2021-12-13 13:09 (GMT -08:00):
> Hi,
>
> We solved 18 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12323721&version=12350068&styleName=Text
>
> Staging repo:
> https://repository.apache.org/content/repositorie
improve however
desired.
Manfred
Robert Scholte wrote on 2021-12-11 04:43 (GMT -08:00):
> It was marked for Maven 4, and part of the improvements was test
> automation, which was now possible because it became part of Maven Core.
> Even thought the code still exists in Maven Core, i
. Let's not wait nay more and let perfection get into our way. It surely
is good enough for a release.
The beauty is that if you find an issue.. you just ship again ... no reason to
wait.
manfred
Hervé BOUTEMY wrote on 2021-12-10 04:13 (GMT -08:00):
> the current 3.1.0-SNAPSHOT wo
large effort that is much better invested in the
user facing improvements and new features.
Manfred
Robert Scholte wrote on 2021-06-02 11:54 (GMT -07:00):
> The title suggest it should me moved completely from the Maven codebase, but I
> think there's no alternative for Maven Core,
You can use polyglot-maven for a compatible approach for your own pom files
right now..
https://github.com/takari/polyglot-maven/tree/master/polyglot-xml
Manfred
Will Iverson wrote on 2020-12-11 14:40 (GMT -08:00):
> One of the biggest complaints about Maven has long been the verbosity
Mickael Istria wrote on 2020-08-25 14:17 (GMT -07:00):
> I
>
> On Tuesday, August 25, 2020, Manfred Moser wrote:
>> And the VS code integration from Red Hat might also do something along
> those lines.
>
> It embeds and uses m2eclipse.
>
Haha.. thanks for confi
.
Manfred
John Patrick wrote on 2020-08-25 13:29 (GMT -07:00):
> Are you planning to create a baseline project or selecting a range of
> projects to be used as a baseline, so that perceived improvements can
> be monitored? So that anyone wanting to help out or give feedback can
> subm
I guess we just need confirmation that the fact that CMS goes away does not
include svnpubsub/subversion...
Manfred
Hervé BOUTEMY wrote on 2020-08-20 12:21 (GMT -07:00):
> (forgot to cc infra)
>
> sorry, I completely overlooked the discussion during PTO...
>
> I worked with
?
Manfred
Olivier Lamy wrote on 2020-08-19 18:33 (GMT -07:00):
> Hi Andrew & Infra
> We (maven-dev) wonder what does it mean with using Apache CMS?
> As far as we can see, we only generate content and commit it to a svn
> directory.
> Maybe not for the root part of the websit
I am not sure but I think that SVN commit is a backend for the CMS ..
Olivier Lamy wrote on 2020-08-19 00:06 (GMT -07:00):
> Hi
> I'm not sure if we use CMS.
> I don't think so AFAIK to publish website content we only commit to a svn
> repo.
> Am I missing something?
>
> cheers
> Olivier
>
> -
Awesome! +1
Robert Scholte wrote on 2020-05-22 13:36 (GMT -07:00):
> I've reached the point where apache-maven-wrapper is ready to be merged into
> master.
> The code contains all original commits and a few from me to get them step by
> step into core.
>
> Related tickets:
> https://issues.apac
Elliotte Rusty Harold wrote on 2020-05-04 07:02 (GMT -07:00):
> 2. Is it possible to boostrap the resolver without using the internal
> class MavenRepositorySystemUtils?
>
> https://issues.apache.org/jira/browse/MNG-6579
>
I am using the resolver in my Maven Repository Provisioner and boots
We nearly never backport fixes. Support just means that there is a chance it
still works.. realistically we only support latest release..
Manfred
Tibor Digana wrote on 2020-04-16 13:30 (GMT -07:00):
> I want to ask a question regarding the maintenance of old minor
> versions becaus
All features are already in Maven Resolver ..
We should deprecate everything before 3.5.0 imho
Or if really necessary everything before 3.2.5
Gabriel Belingueres wrote on 2020-04-16 17:35 (GMT -07:00):
> +1 to deprecate 3.0.x to get rid of Sonatype Aether, which would
> considerably simplify
+100
I would deprecate everything before the maven-resolver import back to the
project while you are at it. Not sure exact version but 3.1x would definitely
on that list as well. Maybe also 3.2x
Manfred
Tibor Digana wrote on 2020-04-15 13:39 (GMT -07:00):
> Some users still use Maven 3.
I agree with adding it to .gitignore
Elliotte Rusty Harold wrote on 2020-03-03 04:07 (GMT -08:00):
> There's content in it but it's autogenerated as a consequence of
> building the project. It's not hand edited.
>
> On Tue, Mar 3, 2020 at 3:24 AM Maarten Mulders wrote:
>>
>> It depends a bit...
not seen it in
practice.
Overall its important that you use Central and othter trusted repos first and
foremost..
Manfred
Elliotte Rusty Harold wrote on 2020-02-28 11:01 (GMT -08:00):
> Folks,
>
> A colleague is preparing a presentation on general dependency security
> issues. I
Anything that goes to Central is immutable .. so no edits or updates or
whatever. Make sure you keep that in mind
Manfred
Jonathan Valliere wrote on 2020-02-20 09:50 (GMT -08:00):
> Just indicate a date in the pom at which point the relocation warning turns
> into a relocation error
/dists/
apache-maven-3.6.1
apache-maven-3.6.3
apache-maven-3.7.0
and so on..
Manfred
Bernd Eckenfels wrote on 2020-02-19 13:43 (GMT -08:00):
> How about adding a system property or environment variable stating the type of
> starter script and it's version, so this can be logged by
That sounds good.
Robert Scholte wrote on 2020-02-19 12:50 (GMT -08:00):
> I will write several integration tests matching these use cases.
> Based on that we can decide what to do.
>
> Robert
>
> On 19-2-2020 21:04:51, Manfred Moser wrote:
> There are kinda three main u
you are already largely redoing things so a
reimplementation seems okay. I would just try to maintain the user facing
config and behavior.
Manfred
Robert Scholte wrote on 2020-02-19 11:40 (GMT -08:00):
> Manfred, I don't understand the need for the org.apache.maven.wrapper.cli
> p
All done. All note with pointers to both project readme files, closed all
issues and closed all PRs. Hopefully further input and help will show up here
now.
Manfred
Robert Scholte wrote on 2020-02-18 10:56 (GMT -08:00):
> sure, go ahead
> On 18-2-2020 19:47:29, Manfred Moser wrote:
Okay .. so then I think I should update the Takari repos with a note about that
and send any contributors to the Maven dev list NOW. I think this has the
potential to drive some more help in this effort.
If you agree I can do that tonight ..
manfred
Robert Scholte wrote on 2020-02-18 10:40
that is.
And in terms of getting the scripts in a separate repo or Maven core ... I see
good reasons for both and dont really have a preference. I just would love to
get it moved and into main Maven as soon as possible.
Would we cut 3.6.4 when the wrapper is done in core?
Manfred
Robert
>From what I know it is no taken into account by the resolver.
Elliotte Rusty Harold wrote on 2020-02-14 14:25 (GMT -08:00):
> On Fri, Feb 14, 2020 at 5:12 PM Hervé BOUTEMY wrote:
>>
>> Le vendredi 14 février 2020, 14:11:07 CET Elliotte Rusty Harold a écrit :
>> > Changing group IDs of existing
ave
very little to no guidance or enforcement ...
The burden lies with the user not to be cheated.
Manfred
PS: and the cynic in me says that there are plenty of "open source security"
companies out there that want to "help" you and provide tooling to organize the
mess, so they
mpliance
> - Provide symlinks for backwards compatibility for a limited period of
> time (1 year)
> - Update Maven clients to provide warnings for symlinks during
> builds/tests/etc
>
>
> On Thu, Feb 13, 2020 at 10:23 PM Manfred Moser
> <mailto:manf...@simplig
.. fyi there is a feature in Maven that allows migration and such but it is
barely used.
Manfred
Jonathan Valliere wrote on 2020-02-13 19:28 (GMT -08:00):
> Is there any kind of planned timeline to force compliance against old
> projects?
>
> For example:
>
> - Force
videos linked on the site in which I explain more as well.
Manfred
Jonathan Valliere wrote on 2020-02-13 17:06 (GMT -08:00):
> I have been growing concerned about the process of allowing the creation of
> GroupIDs, within the Maven Central repository, which do not adhere to the
> naming g
Chris,
IANAL but I dont think we can make such a claim ... even though there is not
much to the code and scripts ... its still an Apache project and code of it..
Manfred
Christofer Dutz wrote on 2020-02-12 22:29 (GMT -08:00):
> Hi all,
>
> would it also be possible for some sort of
frozen until we continue at ASF.
Manfred
James Gao wrote on 2020-02-12 21:12 (GMT -08:00):
> With maven wrapper, most maven project could be build out of box iff jdk is
> installed, and the maven version used for build is locked by the project
> owner. So in run time, each version o
benefit - so in the interest of making it more user friendly and explicit I
advocate for just being explicit and using 2.1.0
Manfred
Matt Foley wrote on 2020-01-08 12:36 (GMT -08:00):
>>> So do NOT use a version like 2.1 .. instead use 2.1.0.
>
> The fact that 2.1 is identical to 2.1.0
Elliotte Rusty Harold wrote on 2020-01-07 13:38 (GMT -08:00):
> On Tue, Jan 7, 2020 at 4:00 PM Clemens Quoss wrote:
>>
>> artifactId-version-classifier.jar
>>
>> How do i separate the classifier?
>>
>
> If all you have is the name of the jar, I don't think you can. You
> need the repo metadata o
.g. latest release by date for example could be a patch release of an lower
version...
manfred
Elliotte Rusty Harold wrote on 2020-01-07 04:16 (GMT -08:00):
> I've been looking at Maven 's version comparison algorithm: what it
> does, what it's documented to do, and what it
really
where it ends.
Manfred
Karl Heinz Marbaise wrote on 2019-12-16 12:57 (GMT -08:00):
> On 15.12.19 12:14, Elliotte Rusty Harold wrote:
>> Tentative +1.
>>
>> Is there any reason we would ever backport a fix to 3.0 or 3.2? E.g.
>> this was the last release to support J
I just release a new version which now default to use Maven 3.6.3.
Update your projects with
mvn -N io.takari:maven:0.7.7:wrapper
and enjoy.
More info at https://github.com/takari/maven-wrapper
Manfred
-
To unsubscribe, e
+1
works for polyglot-maven, maven-wrapper and a whole bunch of other projects of
various sizes and complexity.
Manfred
Robert Scholte wrote on 2019-11-21 12:06 (GMT -08:00):
> Hi,
>
> This will be a regression release based on some critical issues discovered in
> Maven 3.6.2
&g
Why? jsoup is MIT licensed which is compatible with Apache V2.
Manfred
Vladimir Sitnikov wrote on 2019-11-05 11:10 (GMT -08:00):
>> Staging repo:
>> https://repository.apache.org/content/repositories/maven-1535/
>
> -1 since
> https://repository.apache.org/content/reposi
+1
or more ... haha
Manfred
Stephen Connolly wrote on 2019-10-29 16:23 (GMT -07:00):
> +1
>
> On Tue 29 Oct 2019 at 20:11, Karl Heinz Marbaise wrote:
>
>> Hi to all,
>>
>> based on the discusion this is the formal VOTE to lift the minimum of
>> Maven Core
The polyglot support is implemented as a project extension as you can see from
the docs.
So if your project has the extension configured and a pom.kts .. nothing
changes for you on the command line..
mvn install
will do the job just fine. No need for -f and so on..
Manfred
Tibor Digana
Shipped 0.4.1 of polyglot-maven with more kotlin goodness ;-)
https://www.simpligility.com/2019/06/kotlin-improvements-for-polyglot-maven/
Enjoy
Manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
Somewhere between +5 and +10 ;-)
Robert Scholte wrote on 2019-05-28 11:54:
> 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 projec
+1 .. definitely about time ;-)
Robert Scholte wrote on 2019-05-15 13:33:
> 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 proje
+1
Robert Scholte wrote on 2019-04-23 12:43:
> 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, including
> our ambitious
I just cut a new release of maven wrapper and the plugin for installing it. It
now defaults to the shiny new 3.6.1
Enjoy
manfred
Karl Heinz Marbaise wrote on 2019-04-13 03:03:
> The Apache Maven team is pleased to announce the release of the Apache
> Maven 3.6.1.
>
> Apach
Specifically look at
https://github.com/simpligility/maven-repository-tools/blob/master/maven-repository-provisioner/src/main/java/com/simpligility/maven/provisioner/ArtifactRetriever.java
Manfred
simpligility.com
Michael Lipp wrote on 2019-04-06 06:07:
> Hi,
>
> I've spent consid
...
https://www.simpligility.com/2019/03/kotlin-for-polyglot-maven/
https://github.com/takari/polyglot-maven
Manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
Hi all,
Just wanted to give you a heads up about the recent Maven wrapper and plugin
releases.
https://www.simpligility.com/2019/03/recent-maven-wrapper-updates/
Some pretty nice features worth checking out imho.
Go update your projects to this latest version!
Manfred
Fair enough. If its just for outside contributor PRs I am agree with not owning
the risk ;-)
Stephen Connolly wrote on 2019-01-04 16:06:
> On Fri 4 Jan 2019 at 22:00, Tibor Digana wrote:
>
>> @Stephen Connolly
>> After such a big investment, especially made on your side, in Jenkins
>> plugi
I agree with Tibor. I would rather not have to deal with two different CI
systems...
Manfred
Tibor Digana wrote on 2019-01-04 14:00:
> @Stephen Connolly
> After such a big investment, especially made on your side, in Jenkins
> plugin you developed you do not want to support the GitHu
Used it every day since this email for a bunch of different projects of varying
complexity and everything is working fine.
+1
Manfred
Karl Heinz Marbaise wrote on 2018-10-24 12:50:
> Hi,
>
> We have solved 26 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projec
Tried on a bunch of small to largish projects. All good
+1
Stephen Connolly wrote on 2018-06-17 13:44:
> 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 co
Great to have you on the team Christian. Looking forward to see your
contributions.
Manfred
Robert Scholte wrote on 2018-05-07 15:01:
> Hi,
>
> On behalf of the Apache Maven PMC I am pleased to announce that Christian
> Stein (sor) has been voted in as a new Apache Mav
agreed
+1 again ;-)
Olivier Lamy wrote on 2018-03-02 18:14:
> +1 to release as is
>
> On 3 March 2018 at 05:55, wrote:
>
>> 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 rel
Used on a bunch of project for a couple of days now without problems.
+1
Manfred
Stephen Connolly wrote on 2018-02-24 16:00:
> Hi,
>
> We solved 22 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12341428&styleName=Text&projectId=12316922
>
Seconding with
+2
;-)
Olivier Lamy wrote on 2018-02-07 17:18:
> +1
>
> On 8 February 2018 at 00:09, Hervé BOUTEMY wrote:
>
>> Hi,
>>
>> I need seconders for:
>>
>> http://git-wip-us.apache.org/repos/asf/maven/commit/7fed4792
>> [MNG-5992] Upgrade default version of maven-release-plugin t
As a team we are not actively maintaining a presence on Facebook or G+ as far
as I know so I vote for removing them...
Manfred
Hervé BOUTEMY wrote on 2018-01-31 09:40:
> I must confess that I don't understand G+ nor Facebook buttons result
>
> any reason not to remove them
Robert
>
> On Sat, 27 Jan 2018 19:56:49 +0100, Manfred Moser
> wrote:
>
>> Awesome. On the resolver release can we make sure we release the ant
>> task as well (maybe even the current version first since that has never
>> been released yet..)
>>
>> Man
Awesome. On the resolver release can we make sure we release the ant task as
well (maybe even the current version first since that has never been released
yet..)
Manfred
Stephen Connolly wrote on 2018-01-27 09:52:
> Robert and I discussed on IRC...
>
> Our plan is as follows:
&g
All done on the ant-tasks migration now as well.
Next would be a release of the ant-tasks for which I filed
https://issues.apache.org/jira/browse/MRESOLVER-37
Imho we should do that but I don't know what is involved and wont be able to
work on it until some time in January.
ma
Awesome! +1
Tamás Cservenák wrote on 2017-11-28 02:20:
> [VOTE] Release Maven Indexer 6.0.0
>
> Hi,
>
> We solved 25 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317523&version=12330802
>
> There are still a couple of issues left in JIRA:
> https://issues.apach
t control compared
to Maven..
Manfred
Romain Manni-Bucau wrote on 2017-11-27 13:43:
> Doesnt change anything significative - this is my setup.
>
> Le 27 nov. 2017 22:01, "Igor Fedorenko" a écrit :
>
>> I wouldn't bother with Takari local repository, it's br
tasks. Not sure what it
takes to do that.. the codebase seems ready from my point of view..
Manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Awesome ... setting up my github account and such now. In terms of pom.xml ..
should the scm info just point to github then?
Manfred
Hervé BOUTEMY wrote on 2017-11-25 14:00:
> ok, done: https://github.com/apache/maven-resolver-ant-tasks
>
> Regards,
>
> Hervé
>
> Le sa
So .. I tried this now. Seems like something on gitbox is not configured
correctly for me because the Your PMCs drop down contains no entries apart from
Your PMCs.
Can someone either fix this for me or create maven-resolver-ant-tasks
repository? Then I can do the rest.
thx
manfred
Hervé
So how do I make this repo copy happen? An infra ticket or something like that?
Stephen Connolly wrote on 2017-11-22 23:53:
> On Thu 23 Nov 2017 at 04:20, Manfred Moser wrote:
>
>> Status update and questions:
>>
>> - demos are all now in master and part of the mu
do
that in terms of the branches and so on but how do I go about getting the repo
copied into a new repo named maven-resolver-ant-tasks?
Thanks
Manfred
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional
Hahah ... what a pain. Since so at this stage I think I will move the demos
into the master and leave the ant tasks as they stand and
close the relevant tickets with remarks that details this situation.
Manfred
Robert Scholte wrote on 2017-11-17 03:10:
> "We can solve any pr
with demo branch merge first. I just have to redo the work I did without
the ant tasks in the tree. Stay tuned on that..
Manfred
Hervé BOUTEMY wrote on 2017-11-16 05:49:
> feasible, but I really don't like it: separation is good.
>
> seriously, just merge demos and let ant-tasks
Sorry herve. For some reason I totally missed those. I commented on the issues.
In summary I would like to get the ant-tasks merged as well since that makes a
lot more sense to me than keeping it separate.
Manfred
Hervé BOUTEMY wrote on 2017-11-14 15:50:
> I answered on the mailing list
Any feedback or should I just go ahead with the cleanup?
Manfred
Manfred Moser wrote on 2017-11-08 21:35:
> Hi all,
>
> I have started and made good progress on getting Maven resolver all into the
> master branch instead of having master, demos and ant-tasks in separat
1 - 100 of 349 matches
Mail list logo
