On 01/04/2014 16:30, Amend, Christian wrote:
Hi,
1. yes. I will close this.
Fine.
2. Seems like an issue with infrastructure that they haven't set up this
feature for the new Repository. I will look into this.
Thanks.
3. Yes but I would like to merge my Olingo168 branch first. To do that I would
need OLINGO-227 completed. Otherwise I can`t verify that my changes don`t break
anything.
You are right: Fabio is working on this and should be out with a fix
very soon.
Regards.
-----Original Message-----
From: Francesco Chicchiriccò [mailto:[email protected]]
Sent: Dienstag, 1. April 2014 16:22
To: [email protected]
Subject: Re: xml issue in
On 01/04/2014 16:09, Francesco Chicchiriccò wrote:
On 01/04/2014 16:05, Klevenz, Stephan wrote:
Hi,
There is a small issue with these xml files below. Some XML editors
expect to to have this processing instruction
<?xml version="1.0" encoding="utf-8"?>
in the very first line. Otherwise they report an error. I have just
fixed that and added also some excludes for rat check and .gitignore
for generated files with my latest commits to master.
I hope that's ok.
Hi Stephan,
I have just tested such changes and everything went out fine.
I am about to merge the olingo-200 branch back into master and to
delete olingo-200 (more or less 40 commits, including some local stuff
I haven't pushed yet).
Merge to master completed.
Questions:
1. Can you take a look at OLINGO-65 to see if it can be resolved? (I
think so).
2. Do you have idea of why git commits don't generate any more
comments to related JIRA issues?
3. Shall we remove the "-incubating" suffix from artifact ids (and
directory names)?
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PMC
http://people.apache.org/~ilgrosso/
