[
https://issues.apache.org/jira/browse/JENA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840034#comment-13840034
]
Andy Seaborne commented on JENA-596:
------------------------------------
Many thanks - tested locally and {{mvn verify}} works so it fixes the situation
I was using as a test case.
Patch applied and the module re-enabed in the top level POM.
(Jenkins is backed up due to (over)load at the moment so it may take a while
before it fully works through the project CI)
> Schemagen does not work with Maven 3.1.x
> ----------------------------------------
>
> Key: JENA-596
> URL: https://issues.apache.org/jira/browse/JENA-596
> Project: Apache Jena
> Issue Type: Bug
> Reporter: Ian Dickinson
> Assignee: Ian Dickinson
> Fix For: Jena 2.11.1
>
> Attachments: jena-maven-tools-it.patch, jena-maven-tools.patch
>
>
> Maven 3.1.x has changed the way that POM parameters are passed to plugin
> code, causing the schemagen Maven plugin to break.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
