[VOTE] Release Apache Trafodion JDBC T4 driver 2.2.0

[Liu, Ming (Ming)]

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.org/#stagingRepositories/orgapachetrafodion-1006/org/apache/trafodion/jdbc/t4/jdbcT4/2.2.0/jdbcT4-2.2.0.zip
Source release checksum(s):
jdbcT4-2.2.0.zip  SHA1:
028b3682fb73b92082a7a78c323f429ee6b84620
MD5:
1f5fcbe366fd37842bb6610943a1dd2f
Staging site:
https://maven.apache.org/plugins-archives/maven-XXX-plugin-LATEST/

Vote open for at least 72 hours.
[ ] +1
[ ] +0
[ ] -1

Thanks,
Ming

[GitHub] maven-plugins pull request #127: isolate and fix issue with PMD Report, incl...

[bradflood]

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 have the closing pmd element.

I've attached a failing test case, along with the small code change, 
required to fix this. 

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/bradflood/maven-plugins trunk

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-plugins/pull/127.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #127


commit acc32ae8126ff3bb358104b47e901fa7a548554c
Author: Brad Flood 
Date:   2017-08-21T01:56:48Z

isolate and fix issue with includeXmlInSite not producing a valid xml
file in the site directory




---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Maven JIRA Projects - Issue Type

[Stephen Connolly]

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 Marbaise
>
> On 18/08/17 20:52, Karl Heinz Marbaise wrote:
> > Hi to all,
> >
> > I have realized that in MASSEMBLY it is possible to define an issue Type
> > "Dependency Upgrade" which is very feasible for our projects...
> >
> > So I have asked INFRA[1] if we could have that for our other JIRA
> > projects as wellSo the now we can decide between three options:
> >
> >
> > A) switch your other schemes to match MASSEMBLY - meaning in addition to
> > getting 'Dependency Upgrade' you also get add additional 30+ others you
> > dont use.
> >
> > B) Create a Maven Issue Type Scheme, adding 'Dependency Upgrade' to the
> > default.
> >
> > C) Nothing.
> >
> >
> > So I would vote for option "B" ...The question is what do you think?
> > Which options would you like to use in JIRA ?
> >
> >
> > Kind regards
> > Karl Heinz Marbaise
> >
> > More details in the issue.
> >
> > [1]: https://issues.apache.org/jira/browse/INFRA-14898
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
Sent from my phone

Re: [VOTE] Release Apache Maven Shade Plugin version 3.1.0

[Evgeny Mandrikov]

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 charm, so +1 from me!

Regards,
Evgeny

On Sat, Aug 19, 2017 at 4:01 PM Robert Scholte  wrote:

> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317921=12339197=Text
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%2012317921%20AND%20status%20%3D%20Open%20ORDER%20BY%20key%20DESC%2C%20priority%20DESC
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1357/
>
> https://repository.apache.org/service/local/repositories/maven-1357/content/org/apache/maven/plugins/maven-shade-plugin/3.1.0/maven-shade-plugin-3.1.0-source-release.zip
>
> Source release checksum(s):
> maven-shade-plugin-3.1.0-source-release.zip sha1:
> 3d1012e380c5bb6d88f51a298aa302022a39e1ad
>
> Staging site:
> https://maven.apache.org/plugins-archives/maven-shade-plugin-LATEST/
>
> Guide to testing staged releases:
> https://maven.apache.org/guides/development/guide-testing-releases.html
>
> Note: This is a Java 9 support release. Be aware when using this on jars
> with module descriptors; it's intended strong encapsulation (i.e. not
> exported packages) will be lost. This is actually a JVM issue which is
> hopefully resolved in a future version of Java.
>
> Vote open for at least 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

[GitHub] maven-surefire issue #162: SUREFIRE-1384: ProviderInfo for JUnit Plattform (...

[Tibor17]

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 
master.
Try to delete also folders named `2.19.2-SNAPSHOT` in your local Maven 
repository additionally.


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org