https://github.com/codehaus-plexus/plexus-compiler/blob/master/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavaxToolsCompiler.java
So this file needs to be rewritten, since it is using javax.tools, right?
Robert
Op Wed, 09 Sep 2015 23:47:46 +0200
+1 from me. None binding
Verify the staging with WAGON-440, build and run unit test with the
source bundle at staging as well
Thanks
-Dan
On Wed, Sep 9, 2015 at 12:24 PM, Dan Tran wrote:
> Hi,
>
> We have fixed 2 issues:
>
Hi,
The vote has passed with the following result:
+1 (binding): Robert Scholte, Olivier Lamy, Hervé Boutemy
+1 (non binding): jieryn
I will promote the artifacts to the central repo.
-
To unsubscribe, e-mail:
here is my +1
Le lundi 7 septembre 2015 22:30:05 Hervé BOUTEMY a écrit :
> Hi,
>
> We solved 4 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317821
> rsion=12331185
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1206/
>
this is currently onoly seen as a scm migration task: ok, that's one part of
the job
But remember that there is Jenkins & Sonar questions also
and usability to work on whole Maven codebase
and everything is written on our Wiki
I don’t think there is any technical issue of mirroring a repository whether in
SVN or Git.
But it’s not a very nice situation where an SVN repository is mirrored to Git
and then you have to fiddle around making a patch and getting it back into SVN.
I think it would just be nicer for users
The Maven team is pleased to announce the release of the Apache Maven Project
Info Reports Plugin, version 2.8.1
The Maven Project Info Reports Plugin is a plugin that generates standard
reports
for the specified project.
http://maven.apache.org/plugins/maven-project-info-reports-plugin/