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

Add MacOS (Darwin) Support #96

Open
11 of 19 tasks
dblock opened this issue Oct 27, 2021 · 8 comments
Open
11 of 19 tasks

Add MacOS (Darwin) Support #96

dblock opened this issue Oct 27, 2021 · 8 comments
Labels
enhancement New feature or request macos

Comments

@ylwu-amzn
Copy link

Should we finish this in 1.2 release?

@dblock
Copy link
Member Author

dblock commented Oct 30, 2021

Should we finish this in 1.2 release?

It's in the roadmap under 1.3 currently, but don't wait on other plugins to add MacOS CI :)

@dbbaughe
Copy link

dbbaughe commented Nov 2, 2021

@dblock I'm assuming plugins are blocked from moving forward on this until core publishes the min mac distribution?

@dblock
Copy link
Member Author

dblock commented Nov 4, 2021

@dblock I'm assuming plugins are blocked from moving forward on this until core publishes the min mac distribution?

Plugins should be able to build and CI on MacOS without core. Maven dependencies aren't platform-specific.

@dbbaughe
Copy link

dbbaughe commented Nov 4, 2021

@dblock I'm assuming plugins are blocked from moving forward on this until core publishes the min mac distribution?

Plugins should be able to build and CI on MacOS without core. Maven dependencies aren't platform-specific.

Wouldn't that mean macos development is solved then and all plugin developers should be able to develop on their local macos? Has that been fixed? I know we have a hacky workaround to switch from ARCHIVE to INTEG_TEST for the distribution, but that does not include any of the extra modules which means a lot of plugin functionality is broken.

@dblock
Copy link
Member Author

dblock commented Nov 4, 2021

@dblock I'm assuming plugins are blocked from moving forward on this until core publishes the min mac distribution?

Plugins should be able to build and CI on MacOS without core. Maven dependencies aren't platform-specific.

Wouldn't that mean macos development is solved then and all plugin developers should be able to develop on their local macos? Has that been fixed? I know we have a hacky workaround to switch from ARCHIVE to INTEG_TEST for the distribution, but that does not include any of the extra modules which means a lot of plugin functionality is broken.

Yes, that too. I don't know anything about ARCHIVE vs. INTEG_TEST, point to an issue? We should fix it.

@derek-ho
Copy link

@dblock is this still planned, or should we close this out?

@dblock
Copy link
Member Author

dblock commented Jun 19, 2024

This is still valid.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request macos
Projects
None yet
Development

No branches or pull requests

4 participants