Hi,
The vote has passed with the following result:
+1 (binding): Jason van Zyl, Hervé Boutemy, Dennis Lundberg
-0 (binding): Robert Scholte
I will promote the artifacts to the central repo.
On Fri, Jul 3, 2015 at 8:46 AM, Dennis Lundberg wrote:
> Hi,
>
> We solved 6 issues:
> https://issues.a
Hi,
No objection: in fact, I already updated the site before.
One thing I think could improve the front page (without changing everything)
would be to have some text on 3 or 4 columns, like http://bigtop.apache.org/
(I still didn't have time to make tests)
Regards,
Hervé
Le dimanche 5 juillet
Hi,
The vote has passed with the following result:
+1 (binding): Jason Van Zyl, Tamas Cservenak, Hervé Boutemy
+1 (non binding): Tibor Digana
I will promote the artifacts to the central repo.
Regards,
Hervé
-
To unsubscrib
+1 from me as well
Thank you Robert for finding that bug, I'll go ahead and file an issue
in JIRA for it. I agree with Hervé's evaluation though that it can be
fixed at a later point, as it is not something that was introduced
with the changes for the new version, but rather an old bug.
On Mon, J
+1
the bug reported by Robert should be fixed later
Regards,
Hervé
Le vendredi 3 juillet 2015 08:46:25 Dennis Lundberg a écrit :
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317621&ve
> rsion=12330969
>
> There are still a couple of issues
yes, that's a known limitation of Maven 3: read-only parameters are not read
only...
see MNG-5001 [1]
the question is: should this parameter be read-only? Why is the IT requiring
changing the default value (ie property =
"project.artifact.artifactHandler.language")?
Regards,
Hervé
[1] https:
here is my +1
Regards,
Hervé
Le vendredi 3 juillet 2015 00:15:18 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 5 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&ve
> rsion=12331430
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-11
GitHub user andrewgaul opened a pull request:
https://github.com/apache/maven-plugins/pull/56
Suggest using verify phase for Checkstyle
The Maven lifecycle[1] reference suggests using validate to:
> validate the project is correct and all necessary information is
available.
Github user barthel closed the pull request at:
https://github.com/apache/maven/pull/55
---
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 project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user barthel opened a pull request:
https://github.com/apache/maven/pull/55
Merge from barthel/maven
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/barthel/maven MNG-3092
Alternatively you can review and apply these cha
Github user barthel closed the pull request at:
https://github.com/apache/maven/pull/54
---
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 project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user barthel opened a pull request:
https://github.com/apache/maven/pull/54
Merge pull request #1 from apache/master
Merge all commits from apache/master into barthel/master.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
Hi,
currently there had been done many (realy good) changes by Manfred and i
would like to bring them life as soon as possible...
Any objections ?
Kind regards
Karl Heinz Marbaise
-
To unsubscribe, e-mail: dev-unsubscr...@ma
-0
The buildserver fails and I can reproduce it on my system:
mvn clean verify -Prun-its -Dinvoker.mavenHome=d:\apache-maven-2.2.1
[ERROR] The following builds failed:
[ERROR] * MPMD-205-pmd-js-check\pom.xml
[ERROR] BUILD ERROR
[INFO]
---
14 matches
Mail list logo