You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by Ashish <pa...@gmail.com> on 2013/07/18 09:32:04 UTC
Doc patches
Flume Dev's,
Small confusion around submitting Documentation patches
We maintain docs at two places, in git and on svn pubsub.
Should we submit doc patches for both the locations?
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: Java 1.7
Posted by sainik dasgupta <ds...@gmail.com>.
We have a similar requirement where we use the new java.nio.file package.
We are working with flume 1.3.1 version and java 7 .Flume works fine with
java7.
We enforce with java 7 plugin
<
plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<executions>
*<execution>*
* *
<id>enforce-versions</id>
<goals>
<goal>enforce</goal>
</goals>
<configuration>
<rules>
<requireJavaVersion>
<version>1.7</version>
</requireJavaVersion>
</rules>
</configuration>
</execution>
</executions>
</plugin>
On Fri, Jul 19, 2013 at 10:33 AM, Phil Scala <Ph...@globalrelay.net>wrote:
> Hi everyone,
>
> I was poking around and working on creating a patch to the spool directory
> source and noticed the pom.xml is setting the java compiler/source version
> to 1.6. So I was wondering is there a historical reason to stay on 1.6?
> The patch I am working on would rely on some Java 1.7 functionality (new
> class :: java.nio.file.Files). I would love any feedback and even up the
> discussion up if needed on moving to java 1.7. BTW, a local compilation
> against 1.7 was fine with no errors.
>
> Thanks
> Phil
>
> Phil Scala
> Developer / Architect
> Global Relay
>
> phil.scala@globalrelay.net
>
> 866.484.6630 | info@globalrelay.net | globalrelay.com
>
>
>
>
Java 1.7
Posted by Phil Scala <Ph...@globalrelay.net>.
Hi everyone,
I was poking around and working on creating a patch to the spool directory source and noticed the pom.xml is setting the java compiler/source version to 1.6. So I was wondering is there a historical reason to stay on 1.6? The patch I am working on would rely on some Java 1.7 functionality (new class :: java.nio.file.Files). I would love any feedback and even up the discussion up if needed on moving to java 1.7. BTW, a local compilation against 1.7 was fine with no errors.
Thanks
Phil
Phil Scala
Developer / Architect
Global Relay
phil.scala@globalrelay.net
866.484.6630 | info@globalrelay.net | globalrelay.com
Re: Doc patches
Posted by Ashish <pa...@gmail.com>.
Thanks Hari !
Most of the bugs that we fix need updates in User Guide, so git repo
patches would be good.
thanks
ashish
On Fri, Jul 19, 2013 at 10:59 AM, Hari Shreedharan <
hshreedharan@cloudera.com> wrote:
> Hi Ashish,
>
> Depends on what you want to edit. If you want to edit stuff on the site,
> that goes through SVN pubsub, but for user guide and dev guide are kept
> with the code - so you submit a patch against the git repo. We copy over
> the guides to svn on every release.
>
>
> Thanks,
> Hari
>
>
> On Thursday, July 18, 2013 at 10:03 PM, Israel Ekpo wrote:
>
> > Ashish,
> >
> > Yes you do.
> >
> > From what I understand, the SVN repo is mainly for the website and the
> git
> > repository is where the developer and user guides are kept.
> >
> > So we need to submit patches for both repos.
> >
> >
> >
> >
> > *Author and Instructor for the Upcoming Book and Lecture Series*
> > *Massive Log Data Aggregation, Processing, Searching and Visualization
> with
> > Open Source Software*
> > *http://massivelogdata.com*
> >
> >
> > On 18 July 2013 03:32, Ashish <paliwalashish@gmail.com (mailto:
> paliwalashish@gmail.com)> wrote:
> >
> > > Flume Dev's,
> > >
> > > Small confusion around submitting Documentation patches
> > > We maintain docs at two places, in git and on svn pubsub.
> > > Should we submit doc patches for both the locations?
> > >
> > > --
> > > thanks
> > > ashish
> > >
> > > Blog: http://www.ashishpaliwal.com/blog
> > > My Photo Galleries: http://www.pbase.com/ashishpaliwal
> > >
> >
> >
> >
>
>
>
--
thanks
ashish
Blog: http://www.ashishpaliwal.com/blog
My Photo Galleries: http://www.pbase.com/ashishpaliwal
Re: Doc patches
Posted by Hari Shreedharan <hs...@cloudera.com>.
Hi Ashish,
Depends on what you want to edit. If you want to edit stuff on the site, that goes through SVN pubsub, but for user guide and dev guide are kept with the code - so you submit a patch against the git repo. We copy over the guides to svn on every release.
Thanks,
Hari
On Thursday, July 18, 2013 at 10:03 PM, Israel Ekpo wrote:
> Ashish,
>
> Yes you do.
>
> From what I understand, the SVN repo is mainly for the website and the git
> repository is where the developer and user guides are kept.
>
> So we need to submit patches for both repos.
>
>
>
>
> *Author and Instructor for the Upcoming Book and Lecture Series*
> *Massive Log Data Aggregation, Processing, Searching and Visualization with
> Open Source Software*
> *http://massivelogdata.com*
>
>
> On 18 July 2013 03:32, Ashish <paliwalashish@gmail.com (mailto:paliwalashish@gmail.com)> wrote:
>
> > Flume Dev's,
> >
> > Small confusion around submitting Documentation patches
> > We maintain docs at two places, in git and on svn pubsub.
> > Should we submit doc patches for both the locations?
> >
> > --
> > thanks
> > ashish
> >
> > Blog: http://www.ashishpaliwal.com/blog
> > My Photo Galleries: http://www.pbase.com/ashishpaliwal
> >
>
>
>
Re: Doc patches
Posted by Israel Ekpo <is...@aicer.org>.
Ashish,
Yes you do.
>From what I understand, the SVN repo is mainly for the website and the git
repository is where the developer and user guides are kept.
So we need to submit patches for both repos.
*Author and Instructor for the Upcoming Book and Lecture Series*
*Massive Log Data Aggregation, Processing, Searching and Visualization with
Open Source Software*
*http://massivelogdata.com*
On 18 July 2013 03:32, Ashish <pa...@gmail.com> wrote:
> Flume Dev's,
>
> Small confusion around submitting Documentation patches
> We maintain docs at two places, in git and on svn pubsub.
> Should we submit doc patches for both the locations?
>
> --
> thanks
> ashish
>
> Blog: http://www.ashishpaliwal.com/blog
> My Photo Galleries: http://www.pbase.com/ashishpaliwal
>