I spoke too soon. It appears my java9 classes are not being found in the
multi-release jar so I still don’t know if it fixes the problem with the
scanner.
Ralph
> On Jun 15, 2017, at 8:28 PM, Ralph Goers wrote:
>
> FWIW, building the jar as a multi-release jar did
A release is always welcome ;-)
+1
Stephen Connolly wrote on 2017-06-15 04:13:
> Jesse Glick needs this release for some downstream fixes in the Jenkins
> project.
>
> If nobody objects I'll cut the release on Monday.
>
> -Stephen
>
FWIW, building the jar as a multi-release jar did fix this problem, but
building a multi-release jar with Maven is a bear to do. I have to invoke the
compiler plugin first to compile the pre-java9 classes using the java 7 or 8
compiler, call the maven-bundle-plugin, call the maven-helper-plugin
well not better as it looks not being possible
[ERROR] 'dependencyManagement.dependencies.dependency.classifier' for
org.eclipse.jetty:jetty-bom:pom:bom must be empty, imported POM cannot have
a classifier. @ line 40, column 21
WHY this restriction?
On 16 June 2017 at 11:40, Olivier Lamy
Hi Robert
Sorry for late reply.
Well this doesn't work (see source here [1]) you can attach an artifact
with his own GAV.
And it's neither possible to change GAV of an attached artifact.
Caused by: java.lang.UnsupportedOperationException: Cannot change the
groupId for an attached artifact. It is
+1
On 14 June 2017 at 05:16, Karl Heinz Marbaise wrote:
> Hi,
>
> We solved 12 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?proje
> ctId=12317922=12338026
>
> There are still a couple of issues left in JIRA:
>
I have a plugin that uses a jar that doesn’t have any Maven plugin annotations
in it but does have classes compiled for Java 9 in it that are only used when
executing on Java 9. Loading of the plugin is failing because the annotation
scanner can’t read the class. What do I need to do to prevent
+1
Regards,
Hervé
Le mardi 13 juin 2017, 21:16:12 CEST Karl Heinz Marbaise a écrit :
> Hi,
>
> We solved 12 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922
> rsion=12338026
>
> There are still a couple of issues left in JIRA:
>
Github user jglick closed the pull request at:
https://github.com/apache/maven-enforcer/pull/23
---
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
Hi,
+1 from me.
Kind regards
Karl Heinz Marbaise
On 13/06/17 21:16, Karl Heinz Marbaise wrote:
Hi,
We solved 12 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12338026
There are still a couple of issues left in JIRA:
Hi,
On 15/06/17 13:13, Stephen Connolly wrote:
Jesse Glick needs this release for some downstream fixes in the Jenkins
project.
If nobody objects I'll cut the release on Monday.
+1 from me...
Kind regards
Karl Heinz Marbaise
-Stephen
Github user jglick closed the pull request at:
https://github.com/apache/maven-enforcer/pull/22
---
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
Github user britter commented on the issue:
https://github.com/apache/maven-surefire/pull/154
@tibor17 got some time to review and merge this an #155?
---
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
Jesse Glick needs this release for some downstream fixes in the Jenkins
project.
If nobody objects I'll cut the release on Monday.
-Stephen
Github user asfgit closed the pull request at:
https://github.com/apache/maven-surefire/pull/156
---
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
15 matches
Mail list logo