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

Non-Default Package Directories #30

Open
dalden1981 opened this issue Mar 9, 2020 · 2 comments
Open

Non-Default Package Directories #30

dalden1981 opened this issue Mar 9, 2020 · 2 comments

Comments

@dalden1981
Copy link

My sfdx project contains one default package directory (force-app) and several non-default package directories. The command only seems to package up the default directory. Is there a way to target the non-default package directories?

@ChuckJonas
Copy link
Collaborator

ChuckJonas commented Mar 11, 2020

So you have multiple packages that your are deploying as unmanaged code?

How do you deal with name conflict (same filename in both packages)?

I think it would be possible, but maybe tricky to get right

@ChuckJonas
Copy link
Collaborator

This may provide a solution:

forcedotcom/cli#379

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