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

Packages: no entry point for org.sw.demo.jbeder.yaml_cpp-master #20

Open
Telokis opened this issue Jan 10, 2020 · 3 comments
Open

Packages: no entry point for org.sw.demo.jbeder.yaml_cpp-master #20

Telokis opened this issue Jan 10, 2020 · 3 comments

Comments

@Telokis
Copy link
Contributor

@Telokis Telokis commented Jan 10, 2020

Running sw build --output-dir bin triggers an error

Exception in file D:\dev\cppan2\client2\src\sw\core\build.cpp:314, function loadPackages: no entry point for org.sw.demo.jbeder.yaml_cpp-master

Even after self-upgrading and cleaning the storage.

@egorpugin

This comment has been minimized.

Copy link
Contributor

@egorpugin egorpugin commented Jan 10, 2020

Try to update the client and try again.
I updated yaml library, so new client must be deployed.
(I'm investigating the stability issues on such cases.)

@Telokis

This comment has been minimized.

Copy link
Contributor Author

@Telokis Telokis commented Jan 10, 2020

Ok, that did the trick, thank you!
Do you think there is anything we could do to prevent this kind of issues? The fact that updating completely prevents the usage of SW is quite a strong constraint since nothing can be done until you fix it manually

@egorpugin

This comment has been minimized.

Copy link
Contributor

@egorpugin egorpugin commented Jan 11, 2020

Do you think there is anything we could do to prevent this kind of issues?

Not yet. This issue is postponed, until I implement some other architecture improvements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.