You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Uwe Schindler (JIRA)" <ji...@apache.org> on 2015/09/30 23:03:05 UTC

[jira] [Created] (TIKA-1756) Update forbiddenapis to v2.0

Uwe Schindler created TIKA-1756:
-----------------------------------

             Summary: Update forbiddenapis to v2.0
                 Key: TIKA-1756
                 URL: https://issues.apache.org/jira/browse/TIKA-1756
             Project: Tika
          Issue Type: Improvement
            Reporter: Uwe Schindler


Forbiddenapis 2.0 was released a few hours ago. Apache POI and Lucene already updated, Tika should do this, too.

Attached is a patch.

{quote}
The main new feature is native support for the Gradle build system (minimum requirement is Gradle 2.3). But also Apache Ant and Apache Maven build systems got improved support: Ant can now load signatures from arbitrary resources by using a new XML element <signatures></signatures> that may contain any valid ANT resource, e.g., ivy's cache-filesets or plain URLs. Apache Maven now supports to load signatures files as artifacts from your repository or Maven Central (new signaturesArtifacts Mojo property).

Breaking changes:
- Update to Java 6 as minimum requirement.
- Switch default Maven lifecycle phase to verify.

Bug fixes:
- Add automatic plugin execution override for M2E. It is no longer needed to add a lifecycle mapping to exclude forbiddenapis to execute inside Eclipse's M2E 
{quote}

The M2E change is nice, because you no longer need the M2E workaround to disable running the plugin in Eclipse manually.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)