Hi,
We solved 4 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821&version=12331185
Staging repo:
https://repository.apache.org/content/repositories/maven-1206/
https://repository.apache.org/content/repositories/maven-1206/org/apache/maven/plugins/maven-project-in
Hi Michael,
On 9/7/15 10:45 AM, Michael Osipov wrote:
Hi folks,
during issue cleanup I have noticed that our category Maven contains two
other projects [1] which we do not maintain.
Namely, Archiva and Continuum.
I would open an INFRA issue to remove them. Any opinions?
Good idea...
[1] h
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138307685
Fair enough, I cannot remember that far back :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your pr
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138302328
Even if it wasn't the intended use, way back in Maven 2:
4
would give:
$ mvn2 validate
[INFO] Scanning for pro
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138297887
I'm reasonably sure it's never been used for build-time enforcement.
Anything to make it clear that the enforcer is for build-time and the
prerequisite element is for runt
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/50#issuecomment-138297741
@birkedal, does this change look okay after the switch to backticks? Or, if
you're a Solaris user, does that other idiom seem better?
---
If your project is set up for it
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138297080
@jvanzyl although the original change was unconditional deprecation, I
changed it after comments so the current language in the patch is intended to
reflect that distincti
Github user jvanzyl commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138295450
No. The enforcer plugin is for build-time enforcement. The
element is for runtime enforcement. We certainly don't want to have to inspect
the any plugin configuration ele
Github user josephw commented on the pull request:
https://github.com/apache/maven/pull/51#issuecomment-138286028
@kwin, @mosabua - is this current form acceptable as a fix?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Hi,
On Archiva side we are ok for this change.
I just hope it will not break url for bug submission.
Eric
-Message d'origine-
De : Arnaud Héritier [mailto:aherit...@gmail.com]
Envoyé : lundi 7 septembre 2015 13:31
À : Maven Developers List
Objet : Re: Category Maven in ASF JIRA
Arc
Archiva and Continuum are TLP for years. I don't know how are used Jira
categories at ASF (often they are only informative) but maybe they should
have their own categories
On Mon, Sep 7, 2015 at 10:45 AM, Michael Osipov wrote:
> Hi folks,
>
> during issue cleanup I have noticed that our categor
Hi folks,
during issue cleanup I have noticed that our category Maven contains two
other projects [1] which we do not maintain.
Namely, Archiva and Continuum.
I would open an INFRA issue to remove them. Any opinions?
[1] https://issues.apache.org/jira/secure/BrowseProjects.jspa#10510
Michael
Am 2015-08-30 um 21:31 schrieb Michael Osipov:
Hi folks,
some of you might remember that I have closed a bunch of issues some
time ago. I'd like to reperform that task because we have more than 3100
open issues at the moment [1].
Many issues (thousands) haven't been touched for years. I hardly
13 matches
Mail list logo
