Thank you Olivier !
So I think I should vote in Apache Trafodion mail list :-)
thanks,
Ming
-Original Message-
From: Olivier Lamy [mailto:ol...@apache.org]
Sent: Monday, August 21, 2017 2:46 PM
To: Liu, Ming (Ming)
Cc: Maven Developers List ; Xu, Kai-Hua (Kevin)
; Peng, Huai-Tao (Alex
This is the page to release Maven component. (ie. artifacts generated by
the Maven project itself)
The Maven project cannot vote for your release!
Please refer to http://www.apache.org/dev/publishing-maven-artifacts.html
On 21 August 2017 at 16:40, Liu, Ming (Ming) wrote:
> sorry, we want to p
sorry, we want to publish our JDBC driver into Maven central repository and I
refer to this page :
http://maven.apache.org/developers/release/maven-project-release-procedure.html
to call for a vote.
If this is the wrong list, could someone help to point me the correct list? Or
any other referen
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/162
Sorry my bad, yes master has enforcer with JDK8 (due to javadoc checks
within compile time) however maven.compoler.source/target is 1.6.
I will have a look in to junit5 branch.
---
If yo
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/162
@Tibor17 for the JUnit Plattform Provider we even need JDK 8! Can you merge
Master to junit5 Branch so we have the enforcer fixes? Than I can rebase this
PR.
Thank you!
---
If your
I guess it's the wrong list :-)
On 21 August 2017 at 15:43, Liu, Ming (Ming) wrote:
> Hi,
> We solved N issues:
> https://issues.apache.org/jira/browse/TRAFODION-2554
> https://issues.apache.org/jira/browse/TRAFODION-2544
> https://issues.apache.org/jira/browse/TRAFODION-2513
>
> Staging repo:
>
Hi,
We solved N issues:
https://issues.apache.org/jira/browse/TRAFODION-2554
https://issues.apache.org/jira/browse/TRAFODION-2544
https://issues.apache.org/jira/browse/TRAFODION-2513
Staging repo:
https://repository.apache.org/#stagingRepositories/orgapachetrafodion-1006
https://repository.apache.
GitHub user bradflood opened a pull request:
https://github.com/apache/maven-plugins/pull/127
isolate and fix issue with PMD Report, includeXmlInSite - invalid xml file
for PMD reports with format XML and includeXmlInSite=true, the pmd.xml file
copied to the site directory does not
B please,
On Sat 19 Aug 2017 at 06:54, Karl Heinz Marbaise wrote:
> Hi,
>
> so based on the feedback I will go back to INFRA and let them configure
> a separate Configuration type "Maven Issue Type Scheme" which contains
> the issue type "Dependency Upgrade"...
>
> Kind regards
> Karl Heinz Marb
Hi Robert,
In JaCoCo project tested shading of ASM 6.0_BETA that contains module-info
(relocation+minimization)
jdk1.6.0_45 , apache-maven-3.2.5
jdk1.7.0_80 , apache-maven-3.5.0
jdk1.8.0_144 , apache-maven-3.5.0
jdk-8u152-ea-b05 , apache-maven-3.5.0
jdk-9+181 , apache-maven-3.5.0
Works like char
Github user Tibor17 commented on the issue:
https://github.com/apache/maven-surefire/pull/162
@britter
Actually the master is on JDK6 and the branch junit5 could be on JDK5 that
time we created it.
Maybe you should fix the enforcer configuration to similar to the one in
maste
11 matches
Mail list logo
