[
https://jira.nuxeo.com/browse/NXP-8013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bogdan Stefanescu resolved NXP-8013.
------------------------------------
Resolution: Fixed
A registry.xml file is generated in packages dir to describe the versions of
all the JARs installed using the "update" command.
Also a backup directory is created at runtime to keep track of backups for all
registered JAR versions.
The command to use is "update" with 2 required arguments:
file - the file path in the package (must contain a version)
todir - the directory where to copy. (tofile is not supported - you must
specify a directory since target jar names are managed by the update registry)
Also you have 3 optional attributes:
removeOnExit - default to false (to force a deleteOnExit)
allowDowngrade - default to true (to allow installing versions inferior to the
one currently installed on the server)
upgradeOnly - default to false - to perform the update only if the target jar
exists and the new jar has a greater version.
> Add a registry for Marketplace packages
> ---------------------------------------
>
> Key: NXP-8013
> URL: https://jira.nuxeo.com/browse/NXP-8013
> Project: Nuxeo Enterprise Platform
> Issue Type: Bug
> Components: Packaging
> Affects Versions: 5.4.2
> Reporter: Julien Carsique
> Assignee: Bogdan Stefanescu
> Priority: Critical
> Fix For: 5.5
>
>
> For instance, install DM, then DAM, then uninstall DM, DAM must still work.
> But when DAM was installed, it did not install the stuff it needs which was
> already install by DM.
> So, at least Copy and Delete commands must register and check their target
> usage in a registry.
> It may be required to also manage versions in that registry.
> Also, check how it works with hotfixes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
