Hey Ivan,
It's very possible that the Exception is being caused by thet network - we do use it to build the list of plugins.
Go ahead and send a pull request - I'll try it out locally.
~Lincoln
Hi,As promised more than a month ago, I reviewed the new site and synced all the changes done in the wiki site. I have a change prepared locally. But unfortunately I cannot start awestruct to see what I have done. I updated it to its latest version, but still my _site subdirectory remains empty so awestruct has nothing to serve:D:\projects\seamforge\forge.github.com>awestruct -dInvalid argument - https://raw.github.com/forge/plugin-repository/master/repository.yamlD:/projects/seamforge/forge.github.com/_ext/plugins.rb:13:in `initialize'D:/projects/seamforge/forge.github.com/_ext/plugins.rb:13:in `open'D:/projects/seamforge/forge.github.com/_ext/plugins.rb:13:in `execute'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/extensions/pipeline.rb:33:in `block in execute'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/extensions/pipeline.rb:32:in `each'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/extensions/pipeline.rb:32:in `execute'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/engine.rb:491:in `load_extensions'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/engine.rb:86:in `generate'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/commands/generate.rb:18:in `run'D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/bin/awestruct:165:in `<top (required)>'D:/bin/ruby-193/bin/awestruct:19:in `load'D:/bin/ruby-193/bin/awestruct:19:in `<main>'Serving site at D:/projects/seamforge/forge.github.com/_site[2012-08-23 19:05:11] INFO WEBrick 1.3.1[2012-08-23 19:05:11] INFO ruby 1.9.3 (2012-02-16) [i386-mingw32]The only problematic line here is the fact that https://raw.github.com/forge/plugin-repository/master/repository.yaml cannot be accessed. Could that be the reason why I cannot start the server?Anyway, with this I would like to state that at least the differences between our old and new sites were spotted and prepared to be transferred. Maybe I can push to my github repo and someone able to start the server can review my changes?Cheers,IvanOn Wed, May 2, 2012 at 8:00 PM, Lincoln Baxter, III <lincolnbaxter@gmail.com> wrote:
_______________________________________________Now, to deploy the website, simply checkout the 'develop' branch of https://github.com/forge.github.com, and type: "awestruct -P production --deploy"
On Wed, May 2, 2012 at 9:58 AM, Lincoln Baxter, III <lincolnbaxter@gmail.com> wrote:Sorry for the short notice. I've moved the master branch of https://github.com/forge/website into the 'develop' branch of https://github.com/forge.github.com in order to get our CI builds working.
We should be deleting the /website repository soon.
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev