Your descriptions of what pjam did sounded so wonderously buzz-wordy - thank you, I will improve documentation, (:

Also I wouldn't call svn log && svn up "scm integration" :) May be term I used not that understandable. But what I meant - pjam is intended as tool one can use in processes of continues integration, one of a part of it is a continues builds upon changes in a sources code, commonly stored in SCM system. Currently the implementation is quite primitive, but it's just a prototype, one day I may want to bring it to Jenkins or some others CI platform, but try to think about the idea behind pjam, not the current implementation.

giant if/else trees don't lend to extension very well or collaboration ... they're not plugins who said it should ? pjam is not a plugin, it's tool with command line api, plus web server api (limited api to pjam client) + some concept of directory layouts and business logic; It's not a library; It's not intended to be reused in this way; It's just intended to be used directly, as said in docs. And once again, I saw so many comments concerning code style, I'd agree with such a criticism in context of ideal code, but for end user it just works, why one should care about source code, while it works?; One day I will refactor that all, and I will, once again it *just work for me*, and it may work for others;

In reply to Re^6: Pjam - continues integration for PERL, using pinto. by melezhik
in thread Pjam - continues integration for PERL, using pinto. by melezhik

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.