Command not available; unresolved specs about jekyll-compose HOT 16 CLOSED

Did you try Jekyll 3?

from jekyll-compose.

Ah, I thought github-pages 39 was already Jekyll 3.

from jekyll-compose.

Hi, stumbled upon the same error, did an upgrade to 3.0.pre.beta8 and now i still have this error

>> bundle exec jekyll draft
Invalid command. Use --help for more information 

>> jekyll draft "IoT Compass with IndianaJS"
WARN: Unresolved specs during Gem::Specification.reset:
      listen (~> 2.7)
WARN: Clearing out unresolved specs.
Please report a bug if this causes problems.
Invalid command. Use --help for more information

Gemfile:

gem 'github-pages', versions['github-pages']
gem 'jekyll-compose'

group :jekyll_plugins do
  gem 'jekyll-compose'
end

from jekyll-compose.

Sorry, my mistake.

I had both 2.4.0 and 2.5.3 installed and was using the gh-pages gem.
It seems that version 39 of gh-pages still uses 2.4.0 so that was installed as my main version.

from jekyll-compose.

I was trying to get this working as well. What's the final verdict here? GitHub pages does indeed run jekyll 2.4.0, but why is that even an issue with this plugin I don't understand.

Feedback kindly requested. 😉

from jekyll-compose.

@exalted The feature to add automatic plugin loading for plugins with commands wasn't added until 2.5.0: jekyll/jekyll#2865.

from jekyll-compose.

@parkr Oh, that makes sense!

What was the old way of doind things back then please? 🍷

from jekyll-compose.

What was the old way of doind things back then please?

The old way was to generate your own command, like jekyll-compose or jekyll-draft and calling it directly. This plugin doesn't support that, sadly.

from jekyll-compose.

@parkr thanks for the feedback. I guess I will cross my fingers for GitHub to update to at least 2.5.0

from jekyll-compose.

@parkr thanks for the feedback. I guess I will cross my fingers for GitHub to update to at least 2.5.0

We're releasing 3.0 this week and they should be able to upgrade sometime soon. I have heard that they are taking a look at it as we speak. I'll work with any contacts I have there to try to make 3.0 a reality on Pages as soon as we can.

In the meantime, you can use 2.5.3 locally as it's very similar to 2.4.0.

from jekyll-compose.

@parkr great! 👏

from jekyll-compose.

I just got caught out by this 😞

@parkr Do you think we could add this to the readme so that newcomers know that they need Jekyll >=2.5.0 for this gem to actually do anything?

from jekyll-compose.

👍

Ali

On Sun, Nov 1, 2015 at 5:36 AM -0800, "Joe Nyland" [email protected] wrote:

I just got caught out by this

@parkr Do you think we could add this to the readme so that newcomers know that they need Jekyll >=2.5.0 for this gem to actually do anything?

—
Reply to this email directly or view it on GitHub.

from jekyll-compose.

@parkr Do you think we could add this to the readme so that newcomers know that they need Jekyll >=2.5.0 for this gem to actually do anything?

Great idea, sorry that's so confusing.

from jekyll-compose.

More on this: would it be too crazy to specify this gem to depend on jekyll at least >= 2.5.0 rather than current >= 2.0?

from jekyll-compose.

@exalted great idea!

from jekyll-compose.