ping
Le lundi 16 décembre 2019, 19:37:00 CET Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 2 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317924
> rsion=12346480=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1545/
>
Hi,
MANTRUN-221 resolves a bug introduced by MANTRUN-178, where it incorrectly
assumes that mavenProject.getProperties() will contain all properties
present in the session. The PR is merged to master after it is approved.
Please release the new version of maven-antrun-plugin as soon as possible.
Ok, no problem.
On Fri, Dec 20, 2019 at 11:44 AM Enrico Olivelli
wrote:
> Shivaji,
> Unfortunately I don't have time these days, I hope any other committer can
> volunteer
>
> If no one volunteers I can pick this up, but in January
>
> Enrico
>
> Il ven 20 dic 2019, 17:12 Shivaji Thanneeru
>
Shivaji,
Unfortunately I don't have time these days, I hope any other committer can
volunteer
If no one volunteers I can pick this up, but in January
Enrico
Il ven 20 dic 2019, 17:12 Shivaji Thanneeru
ha scritto:
> Hi,
> MANTRUN-221 resolves a bug introduced by MANTRUN-178, where it
Approved on github
+1
Enrico
Il giorno mer 18 dic 2019 alle ore 23:53 Robert Scholte <
rfscho...@apache.org> ha scritto:
> Please review (and support) the following:
> https://issues.apache.org/jira/browse/MNG-6065
>
>
> https://github.com/apache/maven/pull/287
>
>
sorry for typo, in the backlog they should not be closed because they are
serious bugs and need to be fixed.
On Fri, Dec 20, 2019 at 1:11 PM Tibor Digana wrote:
> I want to review the closed issues as well i would like to come up with
> those which should be reopened to a certain release
I want to review the closed issues as well i would like to come up with
those which should be reopened to a certain release version.
I guess the release version should be set in such case.
We have also backlog version and that's the place where the issues should
be closed be the version has not
Please share the new query for this. It would give me fewer issues to look at.
By the way, I've chopped the original list from over four hundred to
just over two hundred, learned a lot about Maven in the process, found
one or two gems that have serious impact at my day job, and identified
one
One thing we should try going forward is be more ready to won't fix
and close bugs and RFEs we disagree with. I've seen several examples
where the comments indicate the maintainers did not agree with the
issue, but it still wasn't closed. E.g.
https://issues.apache.org/jira/browse/SUREFIRE-1227
I will exlude those. It does not makes sense to close/reopen again.
Am 2019-12-20 um 12:29 schrieb Elliotte Rusty Harold:
While working through the bugs I found this interesting bit of history:
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like
While working through the bugs I found this interesting bit of history:
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
It seems like we've been here before. Some of the bugs that were
autoclosed then were reopened and are now scheduled for autoclose
again. Any
Hi,
Since things work with plain Maven, such questions would better be directed
to the m2e-...@eclipse.org mailing-list.
On Thu, Dec 19, 2019 at 11:35 PM Elliotte Rusty Harold
wrote:
> There seems to be something I'm missing about importing projects into
> Eclipse.
How do you perform this
12 matches
Mail list logo
