I didn't want to hijack Asger's REST thread, but the conversation
about JSON serializations caught my attention. I've been
experimenting with a localized version of Trippi on our test servers
that has baked-in JSON support for tuple (and tuple count) outputs,
and have been pretty compelled by the
I’m mostly just following the discussion (which I’m very happy to be seeing,
by the way), but I wanted to clarify this one minor offhanded suggestion:
Quoth Asger Askov Blekinge on Fri, Oct 30, 2009 at 08:16:49AM -0400:
> Allowing people to post RDF directly sounds like a good idea, but it has
> i
I believe this warning happened when the Axis dependency was moved to
1.3. We don't use attachments but it is on the Jira tracker for future
incorporation using some SOAP library (TBD). If this passes regression
testing it would be nice to have a clean Axis 1.3 with no warnings even
though we
Hi Steve,
Good to know, thanks for adding it to the tracker. As far as my Mac
OS X error is concerned, I did a fresh checkout and clean build and am
now unable to reproduce it. It looked like it had to do with "mvn
clean" not really cleaning up everything that the tests expected not
to exist, bu
I agree with setting UTF-8 in the pom as Kai suggests. I was getting
a similar warning and had the same concern about non-reproducible
builds.
If the coding guidelines don't already mention it, I think we need to
standardize on UTF-8 for any text files in the source tree. Thus,
Eclipse (or any I
Hi
On Thu, 2009-10-29 at 15:39 +0100, Lodewijk Bogaards wrote:
> Hi Asger,
>
> On 10/26/09 12:46 PM, "Asger Askov Blekinge"
> wrote:
>
> > I think I can follow the design you propose, even though I am not really
> > into the database code part of Fedora.
> > To retell it, so you can check my un
On Thu, 2009-10-29 at 18:26 +0100, Matt Zumwalt wrote:
> Asger, Thanks for taking this on, and thanks for writing up this
> proposal. It's really important to keep refining this API and it
> helps to have a document to work from. Here are a few thoughts based
> on the proposal and the comments so
Should we set a uniform encoding in Eclipse (and other editors)? Also
line termination?
-- Dan
Steve Bayliss wrote:
> Hi Kai
>
> Thanks for that - yes it does sound like a good idea to specify the encoding
> in the pom.xml.
>
> Regards
> Steve
>
> -Original Message-
> From: Kai Strnad
Hi Kai
Thanks for that - yes it does sound like a good idea to specify the encoding
in the pom.xml.
Regards
Steve
-Original Message-
From: Kai Strnad [mailto:kai.str...@googlemail.com]
Sent: 30 October 2009 10:48
To: Steve Bayliss
Cc: 'Chris Wilper'; fedora-commons-developers@lists.sour
Hi Steve,
the encoding can be changed by adding the following property to
section of the pom.xml:
UTF-8
Perhaps we should generally set this property in order to avoid
potentially irreproducable builds due to the usage of default platform
encodings (MacRoman, Cp1252, etc).
Regarding the
Hi Chris, Andrew
Think I may have got to the bottom of this. I tried esing an Eclipse
workspace "C:\workspace", and it seems to build fine. Then tried another -
"C:\work space" - and it failed. So it looks like there's a problem
building if there are spaces in the path. I've added FCREPO-566 f
11 matches
Mail list logo
