Agree with Srikanth. -1 (Binding)
Seems the zip created has node and node-modules folders. Raju, try regenerating from same tag and check. If it still includes those folders, some build changes might be required to skip those folders. Thanks Amareshwari On Thu, Nov 19, 2015 at 10:02 AM, Puneet Gupta <[email protected]> wrote: > Was able to build and run all test cases from source distribution. > > Thanks, > Puneet Gupta > > On Thu, Nov 19, 2015 at 9:46 AM, Srikanth Sundarrajan <[email protected] > > > wrote: > > > Looks like compiled node modules are included in the source tar ball > > (under lens-ui). I think this has to be respun. > > > > -1 binding > > > > Regards > > Srikanth Sundarrajan > > > > > From: [email protected] > > > To: [email protected] > > > Subject: RE: [VOTE] Release of Apache Lens 2.4.0-beta > > > Date: Thu, 19 Nov 2015 08:42:27 +0530 > > > > > > Checked Signatures & checksums and found them to be ok. > > > > > > There seems to be licensing issues around lens-ui module. On cursory > rat > > check, there seemed many violations. Will do a more thorough check and > > record my vote. > > > > > > Regards > > > Srikanth Sundarrajan > > > > > > > From: [email protected] > > > > Date: Wed, 18 Nov 2015 22:33:51 +0800 > > > > Subject: [VOTE] Release of Apache Lens 2.4.0-beta > > > > To: [email protected] > > > > > > > > Hi everyone, > > > > > > > > I propose the following RC to be released as official Apache Lens > > > > 2.4.0-beta release. > > > > > > > > The commit id is 03e1697535970b4deb75eed13a7a98b939c281d6 > > > > :http://git-wip-us.apache.org/repos/asf/lens/commit/03e16975 > > > > This corresponds to the tag: apache-lens-2.4.0-beta > > > > : > > > https://git-wip-us.apache.org/repos/asf?p=lens.git;a=tag;h=refs/tags/apache-lens-2.4.0-beta > > > > Release archives (tar.gz/.zip), signature, and checksums are > > > > here:* > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.4.0-beta-rc0/ > > > > < > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.4.0-beta-rc0/ > >* > > > > > > > > You can find the KEYS file > > > > here:https://dist.apache.org/repos/dist/release/lens/KEYS > > > > > > > > > > > > The release candidate consists of the following source distribution > > > > archive:apache-lens-2.4.0-beta-source-release.zip > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.4.0-beta-rc0/apache-lens-2.4.0-beta-source-release.zip > > > > < > > > https://mail.google.com/mail/u/0/%3Chttps://dist.apache.org/repos/dist/dev/lens/apache-lens-2.4.0-beta-rc0/apache-lens-2.4.0-beta-source-release.zip%3E > > > > > > > > > > > In addition, the following supplementary binary distributions are > > > > provided for user convenience at the same > > > > location:apache-lens-2.4.0-beta-bin.tar.gz > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.4.0-beta-rc0/apache-lens-2.4.0-beta-bin.tar.gz > > > > << > > > https://dist.apache.org/repos/dist/dev/lens/apache-lens-2.4.0-beta-rc0/apache-lens-2.4.0-beta-bin.tar.gz > > >>The > > > > licensing of bundled bits in the archives are documented > > > > athttps:// > > cwiki.apache.org/confluence/display/LENS/Licensing+in+Apache+Lens > > > > > > > > Nexus staging url: > > > > > > > > > https://repository.apache.org/content/repositories/orgapachelens-1007/ > > > > > > > > Release notes available > > > > athttps:// > > > issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315923&version=12333087 > > > > > > > > > > > > Vote will be open for at least 72 hours > > > > > > > > [ ] +1 approve > > > > [ ] 0 no opinion > > > > [ ] -1 disapprove (and reason why) > > > > > > > > +1 from my side for the release. > > > > > > > > For folks not familiar with vetting a release, please refer to > > > > > > > > http://incubator.apache.org/guides/releasemanagement.html#check-list > > > > > > > > > > > > -- > > > > Thanks > > > > Raju Bairishetti, > > > > > > > > www.lazada.com <http://www.inmobi.com/> > > > > > > > > > -- > _____________________________________________________________ > The information contained in this communication is intended solely for the > use of the individual or entity to whom it is addressed and others > authorized to receive it. It may contain confidential or legally privileged > information. If you are not the intended recipient you are hereby notified > that any disclosure, copying, distribution or taking any action in reliance > on the contents of this information is strictly prohibited and may be > unlawful. If you have received this communication in error, please notify > us immediately by responding to this email and then delete it from your > system. The firm is neither liable for the proper and complete transmission > of the information contained in this communication nor for any delay in its > receipt. >
