Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate does not support composite package #45

Open
mchip22 opened this issue Feb 16, 2017 · 2 comments
Open

Migrate does not support composite package #45

mchip22 opened this issue Feb 16, 2017 · 2 comments

Comments

@mchip22
Copy link

mchip22 commented Feb 16, 2017

Not sure we ever logged this but we have composite packages in use, and the migrate package task does not seem to work with composites. Will this be supported? With out it we cannot automate promotion of composites between XLD instances towards production deployment

@jdewinne
Copy link
Contributor

As the usage of composite packages is deprecated, I don't think we'll add this into this plugin.
Maybe you can have a look at Application Dependencies

@mchip22
Copy link
Author

mchip22 commented Feb 22, 2017

Hello @jdewinne . Thanks for the reply. We are well aware of application dependencies but we cannot adopt them with the current required naming convention (semVer 2.0) We are working with XebiaLabs on potential solutions for increases flexibility in naming of dependency versions to support other naming conventions.

If this will not be supported then we will need to look at alternative options

We have not been provided a committed timeline for deprecation as of yet as it relates to comp packages either. They are still in heavy use due to the above mentioned restriction requiring semVer use

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants