Dammit! I knew something would go wrong somewhere along the lines :(
Errors: (2)
C:\builds\ccnet\server\flexwikicore-20\Working\build\FlexWikiCore.build(320,8):
External Program Failed:
C:\builds\ccnet\server\flexwikicore-20\Working\build\tools\fxcop\fxcopcmd
(return code was 5)
External Program Failed: svn.exe (return code was 1)
The first one appears in every build because we're not doing FxCop checking
at the moment, so the second seems to be the cause of the build failure, but
I have no idea what or why it's gone wrong :o(
Another hour or two and Craig should be online :o)
On 7/26/07, Derek Lakin <[EMAIL PROTECTED]> wrote:
OK, fingers crossed ...
On 7/26/07, Daren May <[EMAIL PROTECTED]> wrote:
>
> Yes - you should be presented with a list of modified files - by default
> they are all checked (unless the are new, unversioned files). To exclude
> your config file from the committed changeset, you would merely clear the
> check mark for that file and then commit.
>
> On 7/26/07, Derek Lakin <[EMAIL PROTECTED] > wrote:
> >
> > Yes, I'm using TortoiseSVN. So when I choose to perform a commit, from
> > the root level, I can choose not include certain files, even though they've
> > changed, such as the flexwiki.config?
> >
> > It certainly makes sense, I just didn't want to go ahead and try it
> > and find that my assumptions were incorrect :P
> >
> >
> > On 7/26/07, Daren May <[EMAIL PROTECTED] > wrote:
> > >
> > > If you use a SVN client such as TortoiseSVN [1] you can choose which
> > > updated files to include in a commit/patch.
> > >
> > > [1] http://tortoisesvn.tigris.org
> > >
> > >
> > > On 7/26/07, Derek Lakin <[EMAIL PROTECTED] > wrote:
> > > >
> > > > OK after a little digging into the Formatter I've found that I can
> > > > handle behaviours (things that start "@@") that start a wiki text line
on
> > > > their own, thus ensuring that the output doesn't get wrapped. Any
behaviours
> > > > that are part of a line, but not at the start will get handled as they
did
> > > > before.
> > > >
> > > > This also has the positive side effect of removing @<p>@ wrapping
> > > > for other presentations such as forms and form fields. I updated the
> > > > wiki.css file to style the <form> element in the same way as the
> > > > <p> element to give the same font sizing for text inside forms. I've
> > > > corrected the relevant unit tests and will commit when I can be sure
that
> > > > I'm doing it the right way. Unless I'm mistaken, I need to do a Commit
from
> > > > the root of the project to add the new files and commit the changes to
> > > > existing files. What I'm not sure on is how to exclude the
> > > > flexwiki.config file, which has my own settings in and doesn't
> > > > need committing. Any suggestions?
> > > >
> > > > Thanks,
> > > >
> > > > Derek.
> > > >
> > > >
> > > > On 7/26/07, Derek Lakin <[EMAIL PROTECTED] > wrote:
> > > > >
> > > > > The implementation with the horrible tag nesting is ready to go
> > > > > right now and that may be the best we can hope for at this stage.
I'll try
> > > > > to find the time today to look at the Formatter. I'm hoping to be
able to
> > > > > separately handle any wiki text that starts with "@@" and take it
outside of
> > > > > the handling that ensures that a line is wrapped in <p> and </p>.
This will
> > > > > obviously have a knock on effect to other presentations such as
forms, input
> > > > > fields, and so on, but should actually make it better, assuming I can
> > > > > actually do it :P
> > > > >
> > > > > I'll keep an eye on the other tests to make sure they work or
> > > > > are corrected.
> > > > >
> > > > > On 7/26/07, Craig Andera <[EMAIL PROTECTED] > wrote:
> > > > > >
> > > > > > > This does not appear to be a large change in terms of code
> > > > > > (< 50 lines
> > > > > > > new) but it will have a huge useability impact in positive
> > > > > > terms. It
> > > > > > > should probably go in this verson if Derek can get it
> > > > > > finished
> > > > > > > quickly.
> > > > > >
> > > > > > OK, I have no problem with that if that's the consensus. Derek
> > > > > > - where's
> > > > > > your implementation at? I ask because I'm thinking that
> > > > > > today's latest build
> > > > > > (2.0.0.68) is going to be Beta 2. So this would go in RC1, or
> > > > > > possibly a
> > > > > > Beta3 if that makes sense. Obviously, we have the build server
> > > > > > to publish
> > > > > > all interim builds, but the public pushes tend to get a bit
> > > > > > more visibility.
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
-------------------------------------------------------------------------
> > > > > > This SF.net email is sponsored by: Splunk Inc.
> > > > > > Still grepping through log files to find problems? Stop.
> > > > > > Now Search log events and configuration files using AJAX and a
> > > > > > browser.
> > > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > > > > _______________________________________________
> > > > > > Flexwiki-users mailing list
> > > > > > Flexwiki-users@lists.sourceforge.net
> > > > > > https://lists.sourceforge.net/lists/listinfo/flexwiki-users
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
-------------------------------------------------------------------------
> > > > This SF.net email is sponsored by: Splunk Inc.
> > > > Still grepping through log files to find problems? Stop.
> > > > Now Search log events and configuration files using AJAX and a
> > > > browser.
> > > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > > _______________________________________________
> > > > Flexwiki-users mailing list
> > > > Flexwiki-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/flexwiki-users
> > > >
> > > >
> > >
> > >
> > > -------------------------------------------------------------------------
> > > This SF.net email is sponsored by: Splunk Inc.
> > > Still grepping through log files to find problems? Stop.
> > > Now Search log events and configuration files using AJAX and a
> > > browser.
> > > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > > _______________________________________________
> > > Flexwiki-users mailing list
> > > Flexwiki-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/flexwiki-users
> > >
> > >
> >
> >
> > -------------------------------------------------------------------------
> > This SF.net email is sponsored by: Splunk Inc.
> > Still grepping through log files to find problems? Stop.
> > Now Search log events and configuration files using AJAX and a
> > browser.
> > Download your FREE copy of Splunk now >> http://get.splunk.com/
> > _______________________________________________
> > Flexwiki-users mailing list
> > Flexwiki-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/flexwiki-users
> >
> >
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems? Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >> http://get.splunk.com/
> _______________________________________________
> Flexwiki-users mailing list
> Flexwiki-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
