If the next version requires Maven 3, then its version number should be
3.0.0
Den 3 jan 2016 12:53 skrev "Michael Osipov" :
> Am 2016-01-03 um 12:37 schrieb Hervé BOUTEMY:
>
>> the site uses old skin, because parent pom was not upgraded to 22: is this
>> intentional?
>>
>
>
Hi,
The vote has passed with the following result:
+1: Michael Osipov, Karl Heinz Marbaise, Benson Margulies, Hervé Boutemy
PMC quorum: reached
I will promote the artifacts to the central repo, the source release ZIP
file and add this release the board report.
the site uses old skin, because parent pom was not upgraded to 22: is this
intentional?
that does not cause any strong issue, just curiosity :)
so here is my +1
Regards,
Hervé
Le jeudi 31 décembre 2015 21:30:30 Michael Osipov a écrit :
> Hi,
>
> We solved 5 issues:
>
Hi,
Tested without any issue.
so +1 from me...
Kind regards
Karl Heinz Marbaise
On 12/31/15 9:30 PM, Michael Osipov wrote:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12334441
There are still a couple of issues left in JIRA:
Am 2016-01-03 um 12:37 schrieb Hervé BOUTEMY:
the site uses old skin, because parent pom was not upgraded to 22: is this
intentional?
Yes, this is intentional. Parent 22 requires Java 1.6. I did not want to
introduce that and wanted to avoid the properties again. Version 2.0
will jump on it
Am 2015-12-31 um 21:30 schrieb Michael Osipov:
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12334441
There are still a couple of issues left in JIRA:
+1
On Sat, Jan 2, 2016 at 8:42 PM, Michael Osipov wrote:
> Am 2015-12-31 um 21:30 schrieb Michael Osipov:
>>
>> Hi,
>>
>> We solved 5 issues:
>>
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12334441
>>
>>
>> There are still a couple of issues
+1 none binding. Tested with MPIR 2.8.2-SNAPSHOT which has
maven-shared-jar-1.2-SNAPSHOT, it fixes the java8/bcel issue. Sorry, I am
not able to test maven-shaded-jar-1.2 at staging repo
Thanks
-D
On Fri, Jan 1, 2016 at 3:59 AM, Michael Osipov wrote:
> Am 2016-01-01 um
Am 2016-01-01 um 05:12 schrieb Dan Tran:
Strange, I even went this far in my pluginManagement
org.apache.maven.plugins
maven-project-info-reports-plugin
${project-info-report.plugin.version}
I add this jar to my project-info-report-plugin
org.apache.maven.plugins
maven-project-info-reports-plugin
${project-info-report.plugin.version}
org.apache.maven.shared
maven-shared-jar
Am 2016-01-01 um 01:47 schrieb Dan Tran:
I add this jar to my project-info-report-plugin
org.apache.maven.plugins
maven-project-info-reports-plugin
${project-info-report.plugin.version}
org.apache.maven.shared
Hi,
We solved 5 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12334441
There are still a couple of issues left in JIRA:
I went ahead to commit MPIR to pick up maven-shared-jar-1.2-SNAPSHOT
sothat I can test with the plugin snapshot first
Thanks
-D
On Thu, Dec 31, 2015 at 8:12 PM, Dan Tran wrote:
> Strange, I even went this far in my pluginManagement
>
>
>
Strange, I even went this far in my pluginManagement
org.apache.maven.plugins
maven-project-info-reports-plugin
${project-info-report.plugin.version}
org.apache.maven.shared
maven-shared-jar
14 matches
Mail list logo