[GitHub] maven-plugins pull request #126: MCOMPILER-306 Fix `compilerArgs` example us...

[Stephan202]

GitHub user Stephan202 opened a pull request:

https://github.com/apache/maven-plugins/pull/126

MCOMPILER-306 Fix `compilerArgs` example usage



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

$ git pull https://github.com/PicnicSupermarket/maven-plugins 
bugfix/MCOMPILER-306

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

https://github.com/apache/maven-plugins/pull/126.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 #126


commit bb0113a07fdce8ae76b326b916c0b12924b47157
Author: Stephan Schroevers 
Date:   2017-08-19T21:34:42Z

MCOMPILER-306 Fix `compilerArgs` example usage




---
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: [VOTE] Release Apache Maven Shade Plugin version 3.1.0

[Karl Heinz Marbaise]

Hi Robert,

tested via: mvn -Prun-its clean verify
the following combinations:

jdk1.7.0_79.jdk
  apache-maven-3.0.5
  apache-maven-3.1.1
  apache-maven-3.2.5
  apache-maven-3.3.1
  apache-maven-3.3.9
  apache-maven-3.5.0
jdk1.8.0_131.jdk
  apache-maven-3.0.5
  apache-maven-3.1.1
  apache-maven-3.2.5
  apache-maven-3.3.1
  apache-maven-3.3.9
  apache-maven-3.5.0
jdk1.8.0_144.jdk
  apache-maven-3.0.5
  apache-maven-3.1.1
  apache-maven-3.2.5
  apache-maven-3.3.1
  apache-maven-3.3.9
  apache-maven-3.5.0
jdk1.9.0_ea+181.jdk
  apache-maven-3.0.5
  apache-maven-3.1.1
  apache-maven-3.2.5
  apache-maven-3.3.1
  apache-maven-3.3.9
  apache-maven-3.5.0

The only thing I found are the following related to JDK 9:

[INFO] ..SUCCESS (5.5 s)
[INFO] Building: dep-reduced-pom/pom.xml
[INFO] run script verify.groovy
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by 
org.codehaus.groovy.reflection.CachedClass$3$1 
(file:/Users/kama/.m2/repository/org/codehaus/groovy/groovy/2.0.1/groovy-2.0.1.jar) 
to method java.lang.Object.finalize()
WARNING: Please consider reporting this to the maintainers of 
org.codehaus.groovy.reflection.CachedClass$3$1
WARNING: Use --illegal-access=warn to enable warnings of further illegal 
reflective access operations

WARNING: All illegal access operations will be denied in a future release
[INFO] ..SUCCESS (4.1 s)
[INFO] Building: dep-reduced-pom-relocated-result/pom.xml
[INFO] ..SUCCESS (2.7 s)
[INFO] Building: dep-reduced-pom-unique/pom.xml

So +1 from me...

Kind regards
Karl Heinz Marbaise

On 19/08/17 16:01, 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 #157: SUREFIRE-1383 dependenciesToScan Does Not Leverag...

[owenfarrell]

Github user owenfarrell commented on the issue:

https://github.com/apache/maven-surefire/pull/157
  
@Tibor17 - thoughts?


---
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

[VOTE] Release Apache Maven Shade Plugin version 3.1.0

[Robert Scholte]

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

Re: Maven JIRA Projects - Issue Type

[Karl Heinz Marbaise]

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

Re: JDK9: Maven-JLink-Plugin, Maven-JMod-Plugin

[Karl Heinz Marbaise]

Hi,

JIRA entries for both Maven-JLink-Plugin and Maven-JMod-Plugin are now 
avaiable..Thanks to the fast work of INFRA Team. Thanks a lot to them...


https://issues.apache.org/jira/projects/MJMOD
https://issues.apache.org/jira/projects/MJLINK

Kind regards
Karl Heinz Marbaise

On 15/08/17 22:15, Karl Heinz Marbaise wrote:

Hi Robert,

I've taken a the liberaty to create INFRA[1] ticket which seemed be 
already working on...


Kind regards
Karl Heinz Marbaise

[1]: https://issues.apache.org/jira/browse/INFRA-14878

On 15/08/17 22:10, Robert Scholte wrote:

Hi Karl Heinz,

I think it makes sense to have these packaging plugins.
Haven't looked at the code yet, but you can start with the preparations.
I hope Brian is available to make this Jira projects.

thanks,
Robert

On Sun, 13 Aug 2017 21:19:55 +0200, Karl Heinz Marbaise 
 wrote:



Hi,
I would like to start a first alpha release of those two plugins to 
have something in the wild to be used and see how the feedback would 
be



What do you think?

I would request JIRA projects for them

Kind regards
Karl Heinz Marbaise

-
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





Mit freundlichem Gruß
Karl-Heinz Marbaise



Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseUSt.IdNr: DE191347579
Hauptstrasse 177
52146 Würselen   http://www.soebes.de

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

[ANN] Apache Maven Assembly EJB Version 3.0.0 Released

[Karl Heinz Marbaise]

The Apache Maven team is pleased to announce the release of the 
Apache Maven EJB Plugin Version 3.0.0

This plugin generates J2EE Enterprise Javabean (EJB) file as well as the
associated client jar.
 
https://maven.apache.org/plugins/maven-ejb-plugin/

Important Note since 3.0.0:

 * Maven 3.X only
 * JDK 7 minimum requirement

You should specify the version in your project's plugin configuration:
 

  org.apache.maven.plugins
  maven-ejb-plugin
  3.0.0


You can download the appropriate sources etc. from the download page:
 
https://maven.apache.org/plugins/maven-ejb-plugin/download.cgi
 
Release Notes Maven EJB Plugin 3.0.0

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317421=12330676

Bugs:

 * [MEJB-109] - JDK 9 - EA compatibility Issue

Improvements:

 * [MEJB-72] - Add LifecycleMapping and ArtifactHandler from maven-core to 
target packaging plugin
 * [MEJB-81] - Upgrade to Maven 3.X only compatiblity
 * [MEJB-86] - Make naming of properties consistent
 * [MEJB-87] - Upgrade EJB Version default to 3.1 in accordance with Java EE 6
 * [MEJB-88] - Change package to org.apache.maven.plugins to prevent conflict 
with Maven Core
 * [MEJB-92] - Make separate classifier for client and main aritfact
 * [MEJB-93] - Prevent re-adding of main artifact twice
 * [MEJB-94] - Make integration tests more reliable
 * [MEJB-97] - Remove param properties that doesn't make sense for CLI usage
 * [MEJB-101] - Upgrade maven-shared-components parent to version 30
 * [MEJB-108] - Upgrade bound plugins to life cycle
 * [MEJB-113] - Move component.xml to correct location.

Dependency Upgrades:

 * [MEJB-114] - Upgrade plexus-utils to version 3.1.0
 * [MEJB-111] - Upgrade plexus-archiver to 3.5.
 * [MEJB-110] - Updated maven-archiver to 3.2.0
 * [MEJB-107] - Upgrade of plexus-interpolation to 1.24.
 * [MEJB-106] - Upgrade of maven-archiver to 3.1.1.
 * [MEJB-105] - Upgrade of maven-archiver to 3.1.0.
 * [MEJB-104] - Upgrade of maven-filtering to 3.1.1.
 * [MEJB-103] - Upgrade of plexus-interpolation to 1.22.
 * [MEJB-102] - Upgrade of plexus-archiver to 3.4.
 * [MEJB-100] - Upgrade plexus-archiver from 3.2 to 3.3
 * [MEJB-99] - Upgrade maven-filtering to 3.1.0
 * [MEJB-98] - Upgrade maven-archiver to 3.0.2
 * [MEJB-96] - Upgrade plexus-archiver to 3.1.1
 * [MEJB-95] - Upgrade plexus-archiver from 3.0.1 to 3.0.3
 * [MEJB-91] - Upgrade plexus-archiver from 2.10.2 to 3.0.1
 * [MEJB-90] - Upgrade commons-io to 2.4

Enjoy,
 
-The Apache Maven team

-
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 (...

[britter]

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/162
  
@Tibor17 when I run `mvn compile` I get:

```
Restricted to JDK 1.5 yet 
org.apache.maven.surefire:surefire-api:jar:2.19.2-SNAPSHOT:compile contains 
org/apache/maven/plugin/surefire/runorder/PrioritizedTest.class targeted to JDK 
1.6
[WARNING] Rule 0: org.apache.maven.plugins.enforcer.EnforceBytecodeVersion 
failed with message:
Found Banned Dependency: 
org.apache.maven.surefire:surefire-api:jar:2.19.2-SNAPSHOT
```

Jenkins Build is also red. I don't know how to fix this. Can you help?


---
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

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

[britter]

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/153
  
See #162 


---
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

[GitHub] maven-surefire pull request #162: SUREFIRE-1384: ProviderInfo for JUnit Plat...

[britter]

GitHub user britter opened a pull request:

https://github.com/apache/maven-surefire/pull/162

SUREFIRE-1384: ProviderInfo for JUnit Plattform (WIP)

Followup for #153 

This is Work in Progress! First take on a JUnitPlattform ProviderInfo, to 
enable automatic provider lookup.

Need help to get things working :)

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

$ git pull https://github.com/britter/maven-surefire SUREFIRE-1384

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

https://github.com/apache/maven-surefire/pull/162.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 #162


commit 1a7dd9b84f8462fa841e015826b44c553ff64b5e
Author: Benedikt Ritter 
Date:   2017-06-08T12:46:04Z

SUREFIRE-1384: Start implemeting JUnit Plattform ProviderInfo for automatic
provider lookup




---
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

[GitHub] maven-surefire pull request #153: SUREFIRE-1384: ProviderInfo for JUnit Plat...

[britter]

Github user britter closed the pull request at:

https://github.com/apache/maven-surefire/pull/153


---
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

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

[britter]

Github user britter commented on the issue:

https://github.com/apache/maven-surefire/pull/153
  
Opening a new PR against junit5 branch!


---
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

Release of jar signer suite next week

[Olivier Lamy]

Hi
All is in the subject :-)

Cheers
-- 
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy

Re: Maven JIRA Projects - Issue Type

[Anders Hammar]

B would be great.

/Anders (mobile)

Den 18 aug. 2017 20:53 skrev "Karl Heinz Marbaise" :

> 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
>
>