Hi Jim,

We have used tar for 0.1.2-incubating release.



On Fri, May 6, 2016 at 5:31 PM, Jim Jagielski <j...@jagunet.com> wrote:

> Would it make sense to consider using tar instead of zip ??
>
>
> > On May 6, 2016, at 1:49 AM, Nazeer Shaik <
> nazeer.sh...@confluxtechnologies.com> wrote:
> >
> > Hi all,
> >
> > You are seeing the mentioned issues because we have prepared the release
> on
> > windows machine. But we don't see any issues if we prepare same release
> on
> > Linux machine. Even the mentioned test case passes without any code
> change.
> >
> > *So we are withdrawing the current release from voting.*
> >
> > We will work on 0.1.2-incubating release.
> >
> > Thanks,
> > Nazeer
> >
> >
> > On Wed, May 4, 2016 at 5:26 PM, Jim Jagielski <j...@jagunet.com> wrote:
> >
> >> Same on OSX. During the unzip the EOL chars are not translated
> >> to native. According to zipinfo, text files lack the 't'
> >> flag but are, instead, 'bx'
> >>
> >> eg:
> >>
> >> -rw-a--     3.1 fat     1642 bx defN  2-May-16 18:03
> >> apache-fineract-0.1.1-incubating-src/licenses/jQuery.txt
> >> -rw-a--     3.1 fat    34388 bx defN  2-May-16 18:03
> >> apache-fineract-0.1.1-incubating-src/licenses/jszip.txt
> >> -rw-a--     3.1 fat     1065 bx defN  2-May-16 18:03
> >> apache-fineract-0.1.1-incubating-src/licenses/modernizr.txt
> >> -rw-a--     3.1 fat     1116 bx defN  2-May-16 18:03
> >> apache-fineract-0.1.1-incubating-src/licenses/normalize.txt
> >>
> >>> On May 4, 2016, at 6:02 AM, Myrle Krantz <mkra...@mifos.org> wrote:
> >>>
> >>> -1
> >>>
> >>> I checked the license and notifications.  They look good to me, so I
> >> tried
> >>> to build:
> >>>
> >>> I'm building on ubuntu, and the instruction wouldn't work for me
> because
> >>> gradlew has windows line feeds.
> >>>
> >>> Going around that by calling gradle directly I can build with "clean
> >> war",
> >>> but if I call just "gradle build" I get a build failure because of a
> unit
> >>> test failure.
> >>>
> >>> I know that unit test has been failing for a very long time.  If it's
> not
> >>> important we need to disable it, so that it doesn't distract from
> >> important
> >>> problems.  If it is important than we need to fix it before we release.
> >>>
> >>> To get my +1, we need to fix gradlew so that it can build on linux
> >> machines
> >>> and we need to have all of our unit tests green.
> >>>
> >>> Greets from the Voreifel, Germany,
> >>> Myrle
> >>>
> >>>
> >>> *Myrle Krantz*
> >>> Solutions Architect
> >>> RɅĐɅЯ, The Mifos Initiative
> >>> mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
> >>> <http://facebook.com/mifos>  <http://www.twitter.com/mifos>
> >>>
> >>>
> >>> On Wed, May 4, 2016 at 5:02 AM, Nayan Ambali <nayan.amb...@gmail.com>
> >> wrote:
> >>>
> >>>> +1
> >>>>
> >>>> On Wed, May 4, 2016, 12:43 AM Ed Cable <edca...@mifos.org> wrote:
> >>>>
> >>>>> +1
> >>>>> On May 3, 2016 4:09 AM, "Nazeer Shaik" <
> >>>>> nazeer.sh...@confluxtechnologies.com>
> >>>>> wrote:
> >>>>>
> >>>>>> Hello All
> >>>>>>
> >>>>>> We have addressed issues with Notice & License files and prepared
> >>>>>> 0.1.1-incubating release for FINERACT.
> >>>>>> The files are hosted at
> >>>>>> <goog_1854395916>
> >>>>>>
> >>>>>
> >>>>
> >>
> https://dist.apache.org/repos/dist/dev/incubator/fineract/0.1.1-incubating/
> >>>>>>
> >>>>>> This is a source only release with no binaries, with instructions on
> >>>> how
> >>>>> to
> >>>>>> build/test the application.
> >>>>>>
> >>>>>> We couldn't migrate to Open JPA to avoid dependency on
> >>>>> Hibernate(LGPLv2.1).
> >>>>>> We are referring Hibernate Entity Manager, MySQLDialect,
> >>>>>> annotations(LazyCollection, LazyCollectionOption)
> >>>>>> at run time only and it doesn't include any source or binary from
> >>>>>> Hibernate. We know that we have to get Legal VP approval on the same
> >>>> and
> >>>>> a
> >>>>>> separate mail thread will be initiated.
> >>>>>>
> >>>>>> I call for VOTING for this release and this voting closes by Friday
> >>>>>> (06-May-2015).
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Nazeer
> >>>>>>
> >>>>>
> >>>>
> >>
> >>
>
>

Reply via email to