Hi,
We solved 2 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522=12345382=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1498/
ght that this simple fix fixes the error, but if there is some other
> reason I think you will be able to fix it better :)
> Sylwester
>
> pt., 12 kwi 2019 o 19:23 Hervé BOUTEMY napisał(a):
> > this avoid the NPE but does not fix the root cause = missing input
> > location
> &g
this avoid the NPE but does not fix the root cause = missing input location
tracking
see first comment of https://issues.apache.org/jira/browse/MNG-6636
Do you want to try to fix the root cause?
Regards,
Hervé
Le jeudi 11 avril 2019, 22:06:00 CEST slachiew...@apache.org a écrit :
> This is an
Hi,
Yes, I can reproduce and confirm that it is caused by MNG-6601.
The impact is minimal: it's caused by the fact that there is no "" in the Maven site's pom.xml for the default reportset (the one that
adds skip=true)
This is a construct that is really unusual, then should really not impact
the solution is better explained in MNG-6059:
https://issues.apache.org/jira/browse/MNG-6059
And in reference documentation for model inheritance:
https://maven.apache.org/ref/3-LATEST/maven-model-builder/index.html#Inheritance_Assembly
Regards,
Hervé
Le jeudi 11 avril 2019, 19:16:40 CEST Karl
+1
On binary reproducibility, the convenience binaries were built with JDK 8 on
Windows. I was able to rebuild equivalent binaries, with explained differences
documented on our Wiki [1] plus one very specific to maven-core artifact (org/
apache/maven/messages/build.properties content). Animal
with corresponding site published at
https://maven.apache.org/resolver/maven-resolver-demos/
and don't hesitate to provide PRs to improve Maven Resolver introduction or
documentation
https://maven.apache.org/resolver/index.html
Regards,
Hervé
Le dimanche 7 avril 2019, 11:23:39 CEST Olivier
+1
I updated MRESOLVER-71 [1] title to better explain the key update: "Upgrade
Maven Resolver from 1.1.1 (used by Maven 3.5.3) to 1.3.3 (used by Maven
3.6.1)"
on version choice: IMHO, we should either align the Maven Resolver Ant Tasks
version with Maven Resolver, either with Maven
And the
sadly nothing: this is a known limitation in Maven 3 (that did not exist in
Maven 2)
https://issues.apache.org/jira/browse/MNG-5001
I never had time to dig precisely into source code to see how hard the fix
would be. What I know is that when the fix will be available, we'll probably
need a
+1
notice that the fix in Maven core should be marked with MNG-6506 like the IT:
MNG-6543 is just a duplicate Jira entry
Regards,
Hervé
Le mardi 26 mars 2019, 21:08:24 CET Sylwester Lachiewicz a écrit :
> I'd like to merge MNG-6543 Upgrade Plexus Classwords to 2.6.0 to fix the
> problem with
> On 22.03.19 09:25, Michael Osipov wrote:
> > > Am 2019-03-22 um 08:37 schrieb Mickael Istria:
> > >> Hi,
> > >>
> > >> On Sat, Mar 9, 2019 at 6:34 PM Hervé BOUTEMY
> > >>
> > >> wrote:
> > >>> We're working on
looking quickly at PRs and open Jira issue, it seems MCOMPILER-366 could be
merged
Perhaps there are other low hanging fruits for this release
Regards,
Hervé
Le samedi 23 mars 2019, 12:20:36 CET Tibor Digana a écrit :
> Hi,
>
> All the issues for maven-compiler-plugin:3.8.1 is fixed.
>
"use int or long instead of BigIntegers for little numbers in
ComparableVersion"
https://issues.apache.org/jira/browse/MNG-6572
implementation:
https://github.com/apache/maven/commits/MNG-6572
there is just a question: keep the second commit (use regexp) or not? I'm not
convinced it is an
+1
checked also the binary against my local build: same bytecode found (built
with JDK 7 compiler)
regards,
Hervé
Le dimanche 17 mars 2019, 09:34:25 CET Michael Osipov a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317828
>
+1
as usual now, checked binaries for reproducibility:
- this time, they were built with JDK 8
- not found any difference in compiled .class files
- found expected differences in MANIFEST.MF, that will be resolved when
plugins upgrade to maven-archiver 3.4.0
- found expected differences in file
Hi Alex,
We're working on it, it should happen quite soon, but no date is really
guaranteed: as you can see from Jira issues to be resolved [1], we're near...
Regards,
Hervé
[1] https://issues.apache.org/jira/projects/MNG/versions/12344378
Le lundi 4 mars 2019, 17:48:57 CET Alexander
if nobody has any objection, I'll commit to plexus-utils and Modello and do a
new release of each tonight then update MNG and MPH branches to use the
releases (then not fail any more)
Regards,
Hervé
Le samedi 23 février 2019, 23:00:27 CET Hervé BOUTEMY a écrit :
> Hi,
>
> work on M
+1
on *.jar binaries check, I was able to rebuild the jars: they were built with
javac compiler from JDK 11 on a unix family OS, and I get the exact same
bytecode (even if I built with JDK 11.0 when Karl Heinz built with JDK 11.0.1)
There were the usual not Reproducible Build little
CET Enrico Olivelli a écrit :
> Great work.
> What about creating pull requests on github? It is only a matter of pushing
> the 'compare' button.
> I am very used to that kind of reviews and I find it very productive
>
> Enrico
>
> Il sab 23 feb 2019, 23:00 Hervé BOU
+1
FYI, using a JDK 8 and simulating Windows end of line during build on my Linux
box (running "mvn -Dline.separator=$'\r\n' clean verify"), I was able to
reproduce a binary archive with expected little differences
once this component will be integrated into plugins, we'll have less little
Hi,
work on MPH-160 [1] = add source location in comments to effective pom.xml, is
now ready: I did prepare changes in branches for plexus-utils, modello, Maven
core and maven-help-plugin
I need your review before merging and releasing plexus-utils 3.2.0 and Modello
1.10.0, then merging into
while working on MPH-160 = add source location in comments to effective
pom.xml, I found that source location tracking is not done for super-pom content
any seconders to merge associated commit?
https://github.com/apache/maven/commit/f1f9ffc06fbf8b11f0fca0b697e03e6d235477fd
Le samedi 16 février 2019, 11:38:59 CET Emmanuel Bourg a écrit :
> Le 15/02/2019 à 17:34, Hervé BOUTEMY a écrit :
> > IIUC you don't use the same versions of dependencies (because of
> > uniqueness of each lib in Debian [1]) as those used in a "normal
> > unconstra
not sure we're on the same understanding.
I'll try to focus on 2 specific topics
Le jeudi 14 février 2019, 22:57:26 CET Emmanuel Bourg a écrit :
> > - Are you making clear that you're not using the official Maven
> > distribution, e.g. by adjust the info from 'mvn --version'?
>
> No we aren't,
e added to refs/heads/master by this push:
> > new 6bd8bb9 [MNG-6571] forgot to put new instance in cache
> >
> > 6bd8bb9 is described below
> >
> > commit 6bd8bb9ba6515446e3699202104f01f98fea1e63
> > Author: Hervé Boutemy
> > AuthorDate: Tue Feb 5
configuration
that was not really leaking, but at least was visible
This idea is implemented in MPOM-215 branch of Maven core.
The only issue I found is how to publish the documentation site: I suppose
we'll find a solution.
WDYT?
Regards,
Hervé
Le mardi 15 janvier 2019, 17:04:27 CET Hervé BOUTEMY
as discusses in the Jira issue, the cache on Version Range is simple and very
efficient
can someone review and second for merge to master?
Regards,
Hervé
Le mercredi 23 janvier 2019, 11:07:43 CET Hervé BOUTEMY a écrit :
> Hi,
>
> Interesting.
> I created MNG-6571 to track this i
Hi,
Interesting.
I created MNG-6571 to track this issue: please move the memory dump on this
issue.
Then I created MNG-6571 branch [2] with a cache on VersionRange: this class is
currently immutable, then caching it is trivial. I don't know if it's the best
location, or if there are not other
+1
Regards,
Hervé
Le vendredi 18 janvier 2019, 16:01:25 CET Robert Scholte a écrit :
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317525
> rsion=12343368=Text
>
> There are still a couple of issues left in JIRA:
>
need to see what to do with still opened issues:
https://issues.apache.org/jira/projects/MENFORCER/versions/12330768
Regards,
Hervé
Le mercredi 16 janvier 2019, 13:56:30 CET Enrico Olivelli a écrit :
> An user is asking for a release of the enforcer plugin
>
>
ok ok, stupid me :)
Le mardi 15 janvier 2019, 17:16:57 CET Stephen Connolly a écrit :
> false in the executions?
>
> On Tue, 15 Jan 2019 at 16:04, Hervé BOUTEMY wrote:
> > initial content published, as a branch in maven-studies [1]
> >
> > I have a few issues th
to document how plugins are controlled.
> These are probably all variants I can think of
> - pom.xml
> - via packaging-plugin
> - parent (custom or new maven-defaults-plugins)
> - super pom
> - maven core
>
> thanks,
> Robert
>
> On Mon, 14 Jan 2019 12:01:00 +0
sorry, I forgot to do it while merging
done: I hope the result will be as good as expected
Regards,
Hervé
Le mardi 15 janvier 2019, 16:09:22 CET Mickael Istria a écrit :
> Hi again,
>
> The (hopefully) final patch to make save GBs of RAM in m2e was merged in
> Maven earlier today.
> I'd like
> versions is compatibility with some specific Java version?
> > >
> > > How about developing a plugin that "recommends" specific plugin versions
> > > based on the source/target java version? recommendation can be based on
> > > a
> > > downl
Hi,
I worked with Mickael on his PR and we came to MNG-6533-2 branch:
https://github.com/apache/maven/tree/MNG-6533-2
for MNG-6533 https://issues.apache.org/jira/browse/MNG-6533
Seconders to merge to master?
Regards,
Hervé
PR also created :)
https://github.com/apache/maven/pull/233
Le lundi 14 janvier 2019, 12:06:40 CET Hervé BOUTEMY a écrit :
> MNG-6562 Jira issue [1] and Git branch [2] created: please review and
> comment
>
> I'll start to work on the new parent POM that locks down versions of pl
really matters where the default lifecycle bindings are comings from:
> maven-core or packaging plugin.
>
> All this is an interesting feature worth for 3.7.0
>
> thanks,
> Robert
>
> On Sun, 13 Jan 2019 04:39:15 +0100, Hervé BOUTEMY
>
> wrote:
> > we have 2 op
Le dimanche 13 janvier 2019, 21:18:28 CET Robert Scholte a écrit :
> On Sun, 13 Jan 2019 21:03:20 +0100, Hervé BOUTEMY
>
> wrote:
> > Le dimanche 13 janvier 2019, 20:22:15 CET Robert Scholte a écrit :
> >> On Sun, 13 Jan 2019 18:48:29 +0100, Hervé BOUTEMY
> >
Le dimanche 13 janvier 2019, 20:22:15 CET Robert Scholte a écrit :
> On Sun, 13 Jan 2019 18:48:29 +0100, Hervé BOUTEMY
>
> wrote:
> > Le dimanche 13 janvier 2019, 11:37:43 CET Robert Scholte a écrit :
> >> This is indeed a good approach.
> >> The first grou
e where the "magic" currently happens, and imagine how you could
inject more complex algorithm than the current LifeCyclePluginAnalyzer, and
eventually if this will remain as dreams...
Regards,
Hervé
>
> On Sun, Jan 13, 2019 at 6:48 PM Hervé BOUTEMY wrote:
> > Le diman
bindings.xml in core
I'll prepare a Jira issue and a branch for review
Regards,
Hervé
>
> All this is an interesting feature worth for 3.7.0
>
> thanks,
> Robert
>
> On Sun, 13 Jan 2019 04:39:15 +0100, Hervé BOUTEMY
>
> wrote:
> > we have 2 opposite objectiv
t;
> Thanks
> David Jencks
> Sent from my iPhone
>
> > On Jan 12, 2019, at 7:39 PM, Hervé BOUTEMY wrote:
> >
> > we have 2 opposite objectives:
> > - make default near-empty pom work at best,
> > - but force people to have defined plugins versions (then
> > > When starting with Maven and create your first hello world, it should
> >
> > work
> >
> > > out of the box.
> > > Right now if you are using Java 11, you'll probably hit issues because
> > > some defaults won't work anymore.
&
t;
> Hervé and I already discovered that current focus is mainly on plugins
> right now. We should also work on extensions.
>
> Robert
>
> On Sat, 12 Jan 2019 15:37:23 +0100, Hervé BOUTEMY
>
> wrote:
> > Le vendredi 11 janvier 2019, 12:55:03 CET Tibor Digana a écri
o changing Maven
version
WDYT?
Regards,
Hervé
[1] https://issues.apache.org/jira/browse/MARCHETYPES-54
> How can we be on safe side with these updates? What is mandatory to do for
> such upgrade?
>
> On Fri, Jan 11, 2019 at 7:41 AM Hervé BOUTEMY wrote:
> > As I wrote in many Ji
As I wrote in many Jira issues over years on this topic, I'm not in favor of
that
To me, staying with the same default plugins versions from Maven version to
Maven version is a feature: nobody should expect to change his Maven version
to change the plugins versions
The best practice is to
n case of disaster
>
>
> Enrico
>
> Il dom 6 gen 2019, 10:32 Hervé BOUTEMY ha scritto:
> > interesting
> >
> > I suppose this is enabled by the content of .test-infra/jenkins directory
> > [1]
> > even if I don't really understand the cont
I didn't know about these special "pull/1234/head" refs, that are not real
branches: if these pseudo-branches were synchronized to Gitbox like any
branch, the Gitpubsub mechanism could happen at Apache
of course, the security implications of running code from these PR branches
would still have
of the .travis.yml on any git repository?
Regards,
Hervé
>
> Il giorno sab 5 gen 2019 alle ore 10:35 Enrico Olivelli
>
> ha scritto:
> > Il sab 5 gen 2019, 08:48 Hervé BOUTEMY ha scritto:
> >> Le samedi 5 janvier 2019, 08:10:51 CET Olivier Lamy a écrit :
> >>
samedi 5 janvier 2019, 10:35:11 CET Enrico Olivelli a écrit :
> Il sab 5 gen 2019, 08:48 Hervé BOUTEMY ha scritto:
> > Le samedi 5 janvier 2019, 08:10:51 CET Olivier Lamy a écrit :
> > > On Sat, 5 Jan 2019 at 12:39, Tibor Digana
> >
> > wrote:
> > > >
Le samedi 5 janvier 2019, 08:10:51 CET Olivier Lamy a écrit :
> On Sat, 5 Jan 2019 at 12:39, Tibor Digana wrote:
> > Manfred, did you see my comment on Slack?
> > Shortly, let's have dedicated machines just only for Maven project with
> > Infra support and one person from our team with Infra
I think we need to have a sample project to be able to see the full tree, and
not only the part on phoenix-core dependency
but I already have one fact to share: the issue happens not only on httpclient
but also on junit:
[INFO] | +- junit:junit:jar:4.12:compile
[INFO] | | \-
yes, on our 100 Git repos [1], 90% should be easy to run on any CI with
minimum configuration and resources
then there is Maven core and complex plugins (like Surefire) which are not the
same story
if someone wants to test other toolings to show some useful feature we don't
get in our current
here is the status on the Maven core side:
- MNG-6059 was implemented, which means the attributes were renamed: see
MNG-6059 issue description [1] to get the new child.(x).
(y).inherit.append.path names ((x) and (y) were missing in 3.6.0, forgotten by
inadvertance...)
- MNG-6505 was implemented
Le samedi 29 décembre 2018, 12:40:20 CET Enrico Olivelli a écrit :
> Il sab 29 dic 2018, 12:37 Mickael Istria ha scritto:
> > On Sat, Dec 29, 2018 at 12:01 PM Hervé BOUTEMY
> >
> > wrote:
> > > But in both cases, currently, there is no automatic GitHub PR
>
Le samedi 29 décembre 2018, 12:37:36 CET Mickael Istria a écrit :
> On Sat, Dec 29, 2018 at 12:01 PM Hervé BOUTEMY
>
> wrote:
> > But in both cases, currently, there is no automatic GitHub PR integration:
> > Maven committers need to create a branch in the official repo
Le samedi 29 décembre 2018, 11:29:53 CET Robert Scholte a écrit :
> I've already introduces the concept of "plans"[1][2], which also include
> 'site' for documentation and 'release' to verify if the project is
> releasable (should probably change that name to prevent confusion).
+1 to change the
Le samedi 29 décembre 2018, 09:57:30 CET Mickael Istria a écrit :
> On Mon, Dec 24, 2018 at 5:21 PM Karl Heinz Marbaise
>
> wrote:
> > Hi Mickael,
>
> Hi,
>
> I have to summarize this simply.
>
> > This is no lack of interest in any kind. It is simply a lack of time of
> > the
+1
notice: working on reproducible builds for the JVM to avoid such issue in the
future (= published binary that has an issue)
stay tuned...
Regards,
Hervé
Le mardi 25 décembre 2018, 23:28:15 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 1 issues:
>
+1
Regards,
Hervé
Le dimanche 16 décembre 2018, 13:13:50 CET Robert Scholte a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12343568=Text
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le samedi 15 décembre 2018, 12:43:59 CET Robert Scholte a écrit :
> Hi,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12338638=Text
>
> There are NO MORE issues left in JIRA (the only one left is doing this
>
aiting for the improvement, you can do the job by hand:
mvn verify -Dinvoker.test=it-project-parent,projects/bugs/massembly-201
-Prun-its
Regards,
Hervé
Le samedi 15 décembre 2018, 20:31:50 CET Enrico Olivelli a écrit :
> Il sab 15 dic 2018, 18:56 Hervé BOUTEMY ha scritto:
> > Hi Enric
The Apache Maven team is pleased to announce the release of the Apache Maven
Archetype Bundles, version 1.4
Apache Maven Archetype Bundles is a collection of archetypes.
https://maven.apache.org/archetypes/
You can download the appropriate sources etc. from the download page:
Hi Enrico,
you need the path relative to the basedir of it, not just the last
subdirectory name
in this case, this is:
mvn verify -Dinvoker.test=projects/bugs/massembly-201 -Prun-its
Welcome to the team :)
Regards,
Hervé
Le samedi 15 décembre 2018, 16:24:10 CET Enrico Olivelli a écrit :
>
here is my +1
Regards,
Hervé
Le dimanche 9 décembre 2018, 16:41:48 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 3 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317123
> rsion=12343035=Text
>
> There are still a couple of issues
Hi,
The vote has passed with the following result:
+1 : Olivier Lamy, Karl Heinz Marbaise, Tibor Digana, Hervé Boutemy
PMC quorum reached
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev
+1
Regards,
Hervé
Le samedi 8 décembre 2018, 13:40:43 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/projects/MSHARED/versions/12344434
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le samedi 8 décembre 2018, 13:24:44 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317522
> rsion=12343422=text
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le samedi 8 décembre 2018, 13:02:26 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 7 issues:
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317526%20AND%20
> fixVersion%20%3D%2012343046%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC
>
> There are still
its) from the src zip but the
> build failed:
> Archetype IT 'it-basic' failed: Some content are not equals
>
> Can you check it in the logs attached?
>
> Thx
>
> On Sun, Dec 9, 2018 at 4:48 PM Hervé BOUTEMY wrote:
> > Hi,
> >
> > We solved 3 iss
+1 for MNG-6529
we'll just have to see how we merge changes done in the Maven branch with
updates to the PR...
for MNG-6533, I'm less clear: what is in the Maven branch does not correspond
to the PR
what should we really check?
Regards,
Hervé
Le dimanche 9 décembre 2018, 16:24:22 CET Robert
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317123=12343035=Text
There are still a couple of issues left in JIRA:
wow, nice idea
I noticed the issue for a long time, but never figured out the link with Java
7 nor this idea of fix that is so "magic"...
thank you for the help
Regards,
Hervé
Le vendredi 30 novembre 2018, 05:11:56 CET Gabriel Belingueres a écrit :
> Indeed, that seems to be the case. It
+1
Regards,
Hervé
Le samedi 17 novembre 2018, 14:45:17 CET Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 10 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12341347
>
> There are still a couple of issues left in JIRA:
>
what you describe looks like MPIR-373
AFAIK, this does not fail the build
I tried to run the maven-site-plugin build on my computer and got the 2 failing
ITs, and for fullreporting it displays:
[INFO] Building: full-reporting/pom.xml
[INFO] run post-build script verify.groovy
[INFO]
oh, subtle issue
can you provide a unit test, please?
regards,
Hervé
Le mercredi 14 novembre 2018, 16:34:30 CET Romain Manni-Bucau a écrit :
> assume i have a standard package-info.json with @XmlSchema, nothing crazy
> in jaxb land.
>
> jaxb will do a loadClass(module,
to branch master
> in repository https://gitbox.apache.org/repos/asf/maven-parent.git
>
> commit 9782eabad3cc07473924723d9ecfdc8b821b01a9
> Author: Hervé Boutemy
> AuthorDate: Sun Nov 11 20:36:40 2018 +0100
>
> [maven-release-plugin] rollback the release of maven-
+1
Regards,
Hervé
Le jeudi 8 novembre 2018, 06:25:21 CET Olivier Lamy a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12344059
> eName=Text=12317921
>
> There are still a couple of issues left in JIRA:
>
/asf?p=maven.git;a=commit;h=11312d5b275260fbd2b3ed3294da3ccff5413d42
Le mercredi 7 novembre 2018, 00:03:19 CET Hervé BOUTEMY a écrit :
> Le mardi 6 novembre 2018, 10:35:25 CET Mark Raynsford a écrit :
> > 'Ello.
> >
> > On 2018-11-06T00:03:53 +0100
> >
> > He
Le mardi 6 novembre 2018, 10:35:25 CET Mark Raynsford a écrit :
> 'Ello.
>
> On 2018-11-06T00:03:53 +0100
>
> Hervé BOUTEMY wrote:
> > Hi Mark,
> >
> > even if this is somewhat a corner case (while overriding everything in b,
> > you can override the att
+1
Regards,
Hervé
Le samedi 3 novembre 2018, 11:32:23 CET Robert Scholte a écrit :
> Hi,
>
> We solved 8 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317528
> rsion=12330856=Text
>
> There are still a couple of issues left in JIRA:
>
that merge for other fields does not work
I'll investigate later, it's late here now :)
Regards,
Hervé
Le lundi 5 novembre 2018, 13:19:43 CET Mark Raynsford a écrit :
> On 2018-11-04T15:05:19 +
>
> Mark Raynsford wrote:
> > On 2018-11-04T15:34:11 +0100
> >
> >
you can build https://github.com/apache/maven/tree/MNG-6059 with quick build
instruction at the end of README
Regards,
Hervé
Le dimanche 4 novembre 2018, 13:48:51 CET Mark Raynsford a écrit :
> On 2018-11-04T13:34:39 +0100
>
> Hervé BOUTEMY wrote:
> > Hi Mark,
> >
&g
Hi Mark,
Seems you found one more thing that I forgot when merging MNG-6059:
inheritance of these child.inherit.append.path configurations...
I created MNG-6505 [1] and added the fix to MNG-6059 branch.
Can you check that it works as you expect? (notice: with the new
The Apache Maven team is pleased to announce the release of the Apache Maven
Remote Resources Plugin, version 1.6.0
This plugin is used to retrieve JARs of resources from remote repositories,
process those resources, and incorporate them into JARs you build with Maven.
Hi,
The vote has passed with the following result:
+1 : Tibor Digana, Olivier Lamy, Karl Heinz Marbaise, Hervé Boutemy
PMC quorum: reached
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail: dev
+1
Regards,
Hervé
Le lundi 29 octobre 2018, 05:34:12 CET Olivier Lamy a écrit :
> Hi
> I'd like to release Maven plugin Tools 3.6.0
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12343309
> eName=Text=12317820
>
> There are still a couple of issues left
here is my +1
Regards,
Hervé
Le dimanche 28 octobre 2018, 17:35:13 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 30 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317825
> rsion=12331230=Text
>
> There are still a couple of issues
I personnally don't :)
Regards,
Hervé
Le lundi 29 octobre 2018, 01:00:45 CET Tibor Digana a écrit :
> +1
> We plan also version 3.0?
>
> On Sun, Oct 28, 2018 at 5:35 PM Hervé BOUTEMY wrote:
> > Hi,
> >
> > We solved 30 issues:
> >
> > https://issu
+1
Regards,
Hervé
Le vendredi 26 octobre 2018, 15:23:46 CET Robert Scholte a écrit :
> Hi,
>
> We solved 12 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12335540=Text
>
> There are still a couple of issues left in JIRA:
>
Hi,
We solved 30 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317825=12331230=Text
There are still a couple of issues left in JIRA:
works well from CLI, as secured with our Core ITs
Notice that there are some risks for IDE integrations:
- Eclipse, as reported in MNG-6311 [1]
- Intellij, as reported in IDEA-201282 [2] caused by MRESOLVER-36 [3]
AFAIK, these are not really blockers, but we should probably find a way to be
more
+1
this time, I tested the Core ITs and they don't fail with this version
And I updated MRESOLVER-60 and MNG-6489 issues description to ease
understanding of the issue encountered during Core ITs build with resolver
1.3.0...
Regards,
Hervé
Le jeudi 11 octobre 2018, 23:06:26 CEST Karl Heinz
+1
Regards,
Hervé
Le lundi 8 octobre 2018, 10:22:38 CEST Tibor Digana a écrit :
> Hi,
>
> We solved 17 issues:
> https://issues.apache.org/jira/projects/SUREFIRE/versions/12343425
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le dimanche 7 octobre 2018, 00:01:55 CEST Michael Osipov a écrit :
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320628
> rsion=12342803
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le dimanche 23 septembre 2018, 19:49:47 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 31 issues:
> https://issues.apache.org/jira/projects/MDEPLOY/versions/12330476
>
> There are still a couple of issues left in JIRA:
>
+1
Regards,
Hervé
Le dimanche 23 septembre 2018, 19:44:03 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 32 issues:
> https://issues.apache.org/jira/projects/MINSTALL/versions/12334343
>
> There are still a couple of issues left in JIRA:
>
notice that the script will have to be updated for sha512 (that is not
published to staging repo)
most of the release procedure for core is exactly the same as for any
component:
https://maven.apache.org/developers/release/maven-core-release.html
Regards,
Hervé
Le lundi 24 septembre 2018,
+1
Regards,
Hervé
Le samedi 22 septembre 2018, 13:29:51 CEST Robert Scholte a écrit :
> Hi,
>
> We solved 18 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317527
> rsion=12330848=Text
>
> There is still 1 issues left in JIRA:
>
Hi Elliotte,
In Maven, this workspace is mapped to the Maven reactor: see
MavenWorkspaceReader interface [1] in maven-resolver-provider and ReactorReader
implementation [2] in maven-core, which is package private then not visible in
javadoc...
In other tools, this workspace feature could be
801 - 900 of 3649 matches
Mail list logo
