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

ls fails to detect "sbt" in the project #48

Closed
alaz opened this issue Jan 28, 2012 · 3 comments
Closed

ls fails to detect "sbt" in the project #48

alaz opened this issue Jan 28, 2012 · 3 comments

Comments

@alaz
Copy link

alaz commented Jan 28, 2012

The generated JSON is here. As you may see sbt is equal to false.

That's pretty ridiculous actually: since the JSON is generated from SBT plugin, sbt is supposed to be true :)

@softprops
Copy link
Owner

Um... I'll leave this issue unless I am misunderstanding you.

The project you want to publish is actually not a plugin. See the "Creating a Plugin" section of the sbt wiki.

The first thing you have to do is to tell sbt your project is an sbt plugin with

sbtPlugin := true

There not one line in your project that references that setting in your project so actually, the sbt property of your project is supposed to be false :) I can give you a quick tip and add it here if you want sbt to treat your project as a plugin.

For a short description of the json properties listed in the :version.json file, check my own documentation

I hope you don't think everything is ridiculous before you understand the tool :)

fwiw, I'm not even sure you meant for this to be a plugin but instead a library which works fine through ls - https://gist.github.com/1694858

Please clarify your question.

@alaz
Copy link
Author

alaz commented Jan 28, 2012

Uh-oh, my bad! I've just been inattentive to the documentation at ls.implicit.ly and simply didn't read that sbt in JSON means plugin vs. not a plugin. Since my project is not a plugin, everything works as expected, so I'm closing the issue. Really sorry for wasting your time and many thanks for the detailed answer!

Regards,
Alexander

@alaz alaz closed this as completed Jan 28, 2012
@softprops
Copy link
Owner

no worries. I wouldn't disagree that I could always to a better job with my own documentation :)

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