[
http://jira.amdatu.org/jira/browse/AMDATU-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff resolved AMDATU-394.
------------------------------------
Assignee: Marcel Offermans (was: Bram de Kruijff)
Resolution: Fixed
Initial server implemented based on platform release overlay (no pax yet).
Moved release artifact to trunk under module amdatu-release-ams and added to
bamboo (see comment above).
Please review and test. I propose to resolve this issue as it is there, runs
and is generaly usable in terms of ACE functions. New bugs, features and
extensions can be managed through new issues once the server is moved to a
seperate project.
> Create initial Amdatu AMS with ACE server
> -----------------------------------------
>
> Key: AMDATU-394
> URL: http://jira.amdatu.org/jira/browse/AMDATU-394
> Project: Amdatu
> Issue Type: Task
> Components: Amdatu Provisioning
> Affects Versions: 0.3.0-M0
> Reporter: Marcel Offermans
> Assignee: Marcel Offermans
> Fix For: 0.3.0-M1
>
>
> Based on the Apache ACE server, create an Amdatu AMS that can be used to
> provision Amdatu AMA targets.
> Proposed approach:
> 1) Create new Amdatu AMS module that creates an assembly like the release
> module does (could become a subproject at a later stage)
> 2) Investigate maven inheritance, overlayt and pax runner scan options to
> avoid redundancy (not highest priority but would be nice)
> 3) Assemble minimal set of ACE artifacts required to provide provisioning
> capabilities and webui
> 4) Look into simple ways to brand the UI a little (low prio as it may be just
> a tmp solution)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Amdatu-developers mailing list
[email protected]
http://lists.amdatu.org/mailman/listinfo/amdatu-developers
