[
http://jira.amdatu.org/jira/browse/AMDATU-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bram de Kruijff updated AMDATU-465:
-----------------------------------
Affects Version/s: Sprint 6
(was: 0.3.0)
> Support artifact uploads to AMS Ace OBR from the build
> ------------------------------------------------------
>
> Key: AMDATU-465
> URL: http://jira.amdatu.org/jira/browse/AMDATU-465
> Project: Amdatu
> Issue Type: Improvement
> Components: Amdatu Ace Client, Amdatu Maven Plugin, Build & Release
> management
> Affects Versions: Sprint 6
> Reporter: Bram de Kruijff
> Fix For: Backlog
>
>
> In the current version of the deploybundle mojo an "ACE artifact" is deployed
> to Ace by using a url reference to the local (or remote) file. This means
> that at present this only works when the AMS is running locally and has
> access to the filesystem.
> The real world solution is to upload the artifact to a maven repository / OBR
> first and register the "Ace artifact"with a reference to the uploaded
> artifact. However this is at the very least not very convenient in a
> development setting. Therefore I suggest we extend the ace client and mavn
> plugin functionality to support artifact upload to the AMS Ace OBR prior to
> deploying the "ACE artifact".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://jira.amdatu.org/jira/secure/ContactAdministrators!default.jspa
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
