You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@empire-db.apache.org by "Francis De Brabandere (JIRA)" <em...@incubator.apache.org> on 2014/07/04 16:32:34 UTC

[jira] [Resolved] (EMPIREDB-127) Switch to apache maven 3.0.x

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

Francis De Brabandere resolved EMPIREDB-127.
--------------------------------------------

    Resolution: Fixed

Switched to maven 3.x
Had to fix some javadocs along the way
Had to update the maven plugin

> Switch to apache maven 3.0.x
> ----------------------------
>
>                 Key: EMPIREDB-127
>                 URL: https://issues.apache.org/jira/browse/EMPIREDB-127
>             Project: Empire-DB
>          Issue Type: Task
>          Components: Core
>    Affects Versions: empire-db-2.2.0-incubating
>            Reporter: Francis De Brabandere
>            Assignee: Francis De Brabandere
>            Priority: Minor
>              Labels: maven
>             Fix For: empire-db-2.4.3
>
>
> Apache maven 3.0.4 is out and should be stable enough to start using
> Check if it works correctly with the apache parent pom and switch.
> Any objections?



--
This message was sent by Atlassian JIRA
(v6.2#6252)