Hey Ivan,<br><br>It&#39;s very possible that the Exception is being caused by thet network - we do use it to build the list of plugins.<br><br>Go ahead and send a pull request - I&#39;ll try it out locally.<br><br>~Lincoln<br>
<br><div class="gmail_quote">On Mon, Aug 27, 2012 at 3:58 PM, Ivan St. Ivanov <span dir="ltr">&lt;<a href="mailto:ivan.st.ivanov@gmail.com" target="_blank">ivan.st.ivanov@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<div><br></div><div>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:</div>

<div><br></div><div><div>D:\projects\seamforge\<a href="http://forge.github.com" target="_blank">forge.github.com</a>&gt;awestruct -d</div><div>Invalid argument - <a href="https://raw.github.com/forge/plugin-repository/master/repository.yaml" target="_blank">https://raw.github.com/forge/plugin-repository/master/repository.yaml</a></div>

<div>D:/projects/seamforge/<a href="http://forge.github.com/_ext/plugins.rb:13:in" target="_blank">forge.github.com/_ext/plugins.rb:13:in</a> `initialize&#39;</div><div>D:/projects/seamforge/<a href="http://forge.github.com/_ext/plugins.rb:13:in" target="_blank">forge.github.com/_ext/plugins.rb:13:in</a> `open&#39;</div>

<div>D:/projects/seamforge/<a href="http://forge.github.com/_ext/plugins.rb:13:in" target="_blank">forge.github.com/_ext/plugins.rb:13:in</a> `execute&#39;</div><div>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&#39;</div>

<div>D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/extensions/pipeline.rb:32:in `each&#39;</div><div>D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/extensions/pipeline.rb:32:in `execute&#39;</div>

<div>D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/engine.rb:491:in `load_extensions&#39;</div><div>D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/engine.rb:86:in `generate&#39;</div>

<div>D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/lib/awestruct/commands/generate.rb:18:in `run&#39;</div><div>D:/bin/ruby-193/lib/ruby/gems/1.9.1/gems/awestruct-0.2.14/bin/awestruct:165:in `&lt;top (required)&gt;&#39;</div>

<div>D:/bin/ruby-193/bin/awestruct:19:in `load&#39;</div><div>D:/bin/ruby-193/bin/awestruct:19:in `&lt;main&gt;&#39;</div><div>Serving site at D:/projects/seamforge/<a href="http://forge.github.com/_site" target="_blank">forge.github.com/_site</a></div>

<div>[2012-08-23 19:05:11] INFO  WEBrick 1.3.1</div><div>[2012-08-23 19:05:11] INFO  ruby 1.9.3 (2012-02-16) [i386-mingw32]</div><div><br></div><div>The only problematic line here is the fact that <a href="https://raw.github.com/forge/plugin-repository/master/repository.yaml" target="_blank">https://raw.github.com/forge/plugin-repository/master/repository.yaml</a> cannot be accessed. Could that be the reason why I cannot start the server?</div>

<div><br></div><div>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?</div>

<div><br></div><div>Cheers,</div><div>Ivan</div><br><div class="gmail_quote"><div><div class="h5">On Wed, May 2, 2012 at 8:00 PM, Lincoln Baxter, III <span dir="ltr">&lt;<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>&gt;</span> wrote:<br>

</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">Now, to deploy the website, simply checkout the &#39;develop&#39; branch of <a href="https://github.com/forge.github.com" target="_blank">https://github.com/forge.github.com</a>, and type: &quot;awestruct -P production --deploy&quot;<div>

<div><br>
<br><div class="gmail_quote">On Wed, May 2, 2012 at 9:58 AM, Lincoln Baxter, III <span dir="ltr">&lt;<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


Sorry for the short notice. I&#39;ve moved the master branch of <a href="https://github.com/forge/website" target="_blank">https://github.com/forge/website</a> into the &#39;develop&#39; branch of <a href="https://github.com/forge.github.com" target="_blank">https://github.com/forge.github.com</a> in order to get our CI builds working.<br>



<br>We should be deleting the /website repository soon.<span><font color="#888888"><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>&quot;Simpler is better.&quot;<br>



</font></span></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>&quot;Simpler is better.&quot;<br>
</div></div><br></div></div>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>&quot;Simpler is better.&quot;<br>