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

Closed
Telokis opened this issue Jan 10, 2020 · 6 comments
Closed

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

Telokis opened this issue Jan 10, 2020 · 6 comments

Comments

@Telokis
Copy link
Contributor

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
Copy link
Contributor

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
Copy link
Contributor Author

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
Copy link
Contributor

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.

@egorpugin
Copy link
Contributor

egorpugin commented Feb 6, 2020

Ok, found possible solution.
It won't require downloading tons of stuff if you do not use external packages. It also allows you to work in offline mode in same case.

Looks good, but not sure about 100% reliability.
Maybe I'll add a fallback to current approach if new does not work.

@egorpugin
Copy link
Contributor

The solution is not very reliable and way too complex. :(
It will be used in offline mode. But it will be implemented later with better sw distribution (probably msi installer and deb/rpm packages).

@egorpugin
Copy link
Contributor

Specifically this one is fixed now.

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