[
http://jira.amdatu.org/jira/browse/AMDATU-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10574#comment-10574
]
Ivo Ladage - van Doorn commented on AMDATU-163:
-----------------------------------------------
Moving general project info to pom/pom/xml was covered by
http://jira.amdatu.org/jira/browse/AMDATU-117, but to resolve this Maven 3 is
required. Maven 3 upgrade is covered by
http://jira.amdatu.org/jira/browse/AMDATU-95, but will not be part of 0.1.0. As
such, we'd better wait with refactoring the maven structure until we moved to
Maven 3.
> Split of amdatu-core as separate subproject
> -------------------------------------------
>
> Key: AMDATU-163
> URL: http://jira.amdatu.org/jira/browse/AMDATU-163
> Project: Amdatu
> Issue Type: Task
> Reporter: Ivo Ladage - van Doorn
> Assignee: Ivo Ladage - van Doorn
> Fix For: 0.1.0
>
>
> The amdatu-core module needs to be split off as a separate subproject. This
> means:
> - move general project information to pom/pom.xml
> - refactor pom.xml of amdatu-core such that this new pom.xml file becomes its
> parent and the project can be build independently from the pom in the root
> - new pom.xml of amdatu-core should aggregate modules into a single osgi
> bundle 'amdatu-core-0.1.0.jar'
> - amdatu-release must be refactored such that it embeds amdatu-core as a
> whole instead of individual artifacts
> - WIKI page should be added with API documentation about the amdatu-core
> subproject
> - Refactor API to conform to standards (i.e. throwing exception instead of
> returning false on failure)
> - Improve and finalize the Javadoc of the API
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
