[compress] Last issues before 1.1

2010-05-20 Thread Christian Grobmeier
Hello in Jira are only three issues open. 2 of them seem possible to be closed, 1 seems to be minor. COMPRESS-75 ZipArchiveInputStream does not show location in file where a problem occurred Seems to be fixed COMPRESS-113 TarArchiveEntry.parseTarHeader() includes the trailing space/NUL when par

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Rahul Akolkar
2010/5/21 Xun Long Gui : > Hi Rahul, > > Thank you for your hand by hand guide. Yesterday, i add svn:eol-style > property in SVN config file for these extension files, add submited > these once more, it seems that it did not work. So, i set > svn:eol-style property for each extension file and submi

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Xun Long Gui
Hi Rahul, Thank you for your hand by hand guide. Yesterday, i add svn:eol-style property in SVN config file for these extension files, add submited these once more, it seems that it did not work. So, i set svn:eol-style property for each extension file and submit it again today, i am hoping it wor

Re: [scxml-eclipse][scxml-js] New WD and Ecore typo

2010-05-20 Thread Rahul Akolkar
On Thu, May 20, 2010 at 9:02 AM, Xun Long Gui wrote: > Hi Rahul, > I have not found a typo for the element in the model, in > fact, it is in current Ecore model, i am a little > confused. > It should not be "Translation". See lines 8, 10, 36 and 51 here: http://svn.apache.org/viewvc/common

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Rahul Akolkar
2010/5/20 Xun Long Gui : > Ok, got it > r946619 [1] did not actually add the svn:eol-style property. For each file, choose the "Set Property..." option in the "Team" menu [2] when using Subclipse. Then, for property name, use svn:eol-style and for property value, use native. Files will appear to

Re: [scxml-eclipse][scxml-js] New WD and Ecore typo

2010-05-20 Thread Xun Long Gui
Hi Rahul, I have not found a typo for the element in the model, in fact, it is in current Ecore model, i am a little confused. -Gui Xun Long On 5/19/10, Rahul Akolkar wrote: > Relevant to both GSoC projects and Commons SCXML -- a new SCXML WD > came out this week: > > http://www.w3.org/TR/20

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Xun Long Gui
Ok, got it 在 2010年5月20日 下午8:42,Rahul Akolkar 写道: > 2010/5/20 Xun Long Gui : > > I have added svn:eol-style property property to the 7 files in SVN > > config file, may be because i have not submited these 7 files again, > > so it does not work yet, when i submit these files once more, it will > >

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Rahul Akolkar
2010/5/20 Xun Long Gui : > I have added svn:eol-style property property to the 7 files in SVN > config file, may be because i have not submited these 7 files again, > so it does not work yet, when i submit these files once more, it will > work, i think. > Yes, please check in (commit) those 7 fil

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Xun Long Gui
I have added svn:eol-style property property to the 7 files in SVN config file, may be because i have not submited these 7 files again, so it does not work yet, when i submit these files once more, it will work, i think. -Gui Xun Long On 5/20/10, Rahul Akolkar wrote: > 2010/5/19 Xun Long Gui : >

Re: [scxml-eclipse] Notes on properties, headers and generated code

2010-05-20 Thread Rahul Akolkar
2010/5/19 Xun Long Gui : > Hi sebb, > > Thank you for your fervent guide here :-) Did you figure out the Subclipse way of setting properties? If so, please commit the svn:eol-style property changes to the 7 files below. If not, please let us know what didn't work. Thanks. -Rahul > 在 2010年5月19日

Re: [all] preparing initial commit

2010-05-20 Thread Rahul Akolkar
On Thu, May 20, 2010 at 1:07 AM, Jacob Beard wrote: > On Wed, May 19, 2010 at 2:29 PM, Rahul Akolkar > wrote: >> I think its best to start with what you have right now. Lets get it >> out, have people look at it -- I'd like to get a better understanding >> by looking at the setup and trying thin