[ 
https://issues.apache.org/jira/browse/JENA-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shane StClair updated JENA-596:
-------------------------------

    Attachment: jena-maven-tools-it.patch

Ok, replicated and fixed with the attached patch (jena-maven-tools-it.patch). 
Integration test projects needed to be cloned to the target directory in order 
for proper version filtering (thus the previous warning), and IT test verify 
scripts needed to be adjusted to the new location. Also, it looks like some 
changes to SchemagenMojo were missed in the first patch, so they're included 
here.

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

Reply via email to