[
https://issues.apache.org/jira/browse/OPENJPA-2092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Albert Lee updated OPENJPA-2092:
--------------------------------
Fix Version/s: (was: 2.2.0)
2.3.0
Move fix version to 2.3.0 in preparation for 2.2.0 release.
> check openjpa-2.2.0 for plugin and dependency updates
> -----------------------------------------------------
>
> Key: OPENJPA-2092
> URL: https://issues.apache.org/jira/browse/OPENJPA-2092
> Project: OpenJPA
> Issue Type: Task
> Components: build / infrastructure
> Affects Versions: 2.2.0
> Reporter: Mark Struberg
> Fix For: 2.3.0
>
>
> While checking the docbook, I figured that we use some pretty heavily
> outdated dependencies and plugins.
> I think it's time now to to go through those and check if they can be
> replaced with newer versions.
> Of course this would require some serious testing - but this _has_ to be done
> somewhen!
> So I would like to see this done before rather sooner than later.
> There is a neat maven plugin to report such issues, but it seems that this is
> not as widely known as it should be. If my OpenJPA fellows already use this
> already, so excuse me and treat this as just a reminder ;)
> http://mojo.codehaus.org/versions-maven-plugin/
> The most important goals.
> $> mvn versions:help
> In fact the 'help' goal exists for *all* maven plugins. So this is again just
> a reminder ...
> $> mvn versions:display-plugin-updates
> Shows all available plugin updates
> $> mvn versions:display-dependency-updates
> Shows all available dependency updates
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
