Hi, How can we configure jenkins. https://builds.apache.org/view/G-L/view/Helix/job/helix/
We need to first build(which wont run test cases) and then run the package(which will run the test cases) mvn clean install -Dmaven.test.skip.exec=true mvn package Do we need to file a jira to get permission to configure the build ? Thanks Kishore G On Thu, Oct 25, 2012 at 9:44 AM, kishore g <[email protected]> wrote: > Thanks, Roman what we want is a script that will fix the license headers > in all the files. Olivier mentioned about a maven plugin that can do it. I > dont know the details of the plugin. Olivier has created a JIRA to track > it. > > Olivier, regarding rabbitmq, it is just a sample recipe, I prefer not to > make it a part of release. But does that mean it should not be part of > documentation ? rabbitmq jars are mpl(mozilla public license), not sure if > thats allowed as part of release. > > thanks, > Kishore G > > > On Thu, Oct 25, 2012 at 5:10 AM, Olivier Lamy <[email protected]> wrote: > >> 2012/10/25 kishore g <[email protected]>: >> > - Refactored the package names, com.linkedin.helix to org.apache.helix >> > - Removed jsql parser dependency >> > Olivier, can you help me on configuring rat plugin. >> I have created the issue to track progress on that >> (https://issues.apache.org/jira/browse/HELIX-3). >> The rat plugin is configured is available in the maven profile rat (so >> use -Prat). >> I have started some cleanup. >> >> Note the jenkins is configured to add comment in jira. >> So don't miss to add the jira id in comments when committing (pattern >> is [jiraid] sample [HELIX-3] ) >> >> Question: what is the status of rabbitmq-consumer-group ? Do you want >> to release it too ? (currently that's not part of the build) >> >> >> > >> > Thanks, >> > Kishore G >> > >> > On Wed, Oct 24, 2012 at 1:45 PM, Olivier Lamy <[email protected]> wrote: >> > >> >> 2012/10/24 kishore g <[email protected]>: >> >> > I will let Santiago decide what css he wants to use. But this is very >> >> good >> >> > start. >> >> > >> >> > Doclava does look good. >> >> Done http://helix.incubator.apache.org/apidocs/reference/packages.html >> >> > >> >> > I am working on migrating the package. >> >> Great ! >> >> > >> >> > Couple of other things >> >> > >> >> > - License headers: I had added some thing to add the license header >> >> > using com.mycila.maven-license-plugin. But you mentioned something >> like >> >> > maven-rat-plugin. I had LICENSE.txt file, you added LICENSE file. >> which >> >> one >> >> > is correct one. Is the existing plugin good enough? >> >> oups my bad, usually I use LICENSE file without any extension this is >> >> as it for most of the asf projects. >> >> >> >> I would prefer rat maven plugin (always better to use asf own dogfood >> >> :-)) and we will have a very more simple configuration regarding the >> >> license format. >> >> >> >> > >> >> > - checkstyle: we have a slightly different coding convention at >> >> linkedin. I >> >> > plan to change this to something else later. The sonar generates a >> lot of >> >> > checkstyle errors. we can fix this later no hurry but is this >> something >> >> > that will stop us from making a release. >> >> Perso that won't block any release (at least for me :-) ). >> >> If you need help to change formatting let me know. >> >> maven-checkstyle-plugin has some provided style (sun, maven style). >> >> It's more a question of choose one (that can be always complicated :-) >> >> ). Perso I use the maven codestyle. >> >> > >> >> > Appreciate all the help!!! >> >> > >> >> > thanks, >> >> > Kishore G >> >> > >> >> > >> >> > On Wed, Oct 24, 2012 at 11:59 AM, Olivier Lamy <[email protected]> >> wrote: >> >> > >> >> >> 2012/10/24 kishore g <[email protected]>: >> >> >> > Amazing work Olivier. Santi will take a look at changing the look >> and >> >> >> feel >> >> >> > of the website. What is the process of changing it? >> >> >> Currently I have setup the build to use maven-fluido-skin (see >> >> >> http://maven.apache.org/skins/maven-fluido-skin/) >> >> >> For changing, it depends on what you want to change :-). >> >> >> If it's only css you can add one in src/site/resources/css//site.css >> >> >> (it will override the default bootstrap one) >> >> >> >> >> >> Any objections If I setup javadoc to use doclava ? (sample >> >> >> http://directmemory.apache.org/apidocs/reference/packages.html ) >> >> >> >> >> >> > >> >> >> > I deleted the old branches. I will make the package change to >> >> >> > org.apache.helix. Is it a convention to start the versioning from >> >> 0.0.1, >> >> >> > just to be consistent with the versions we already have, i would >> like >> >> to >> >> >> > start with 0.6.0. Is that ok ? >> >> >> yup fine. >> >> >> > >> >> >> > Thanks, >> >> >> > Kishore G >> >> >> > >> >> >> > >> >> >> > On Wed, Oct 24, 2012 at 8:16 AM, Olivier Lamy <[email protected]> >> >> wrote: >> >> >> > >> >> >> >> Update site is now live: http://helix.incubator.apache.org >> >> >> >> >> >> >> >> >> >> >> >> 2012/10/24 Olivier Lamy <[email protected]>: >> >> >> >> > Some stuff I did: >> >> >> >> > * Jenkins jobs: https://builds.apache.org/view/G-L/view/Helix/(I >> >> >> will >> >> >> >> > investigate issue on 1.7) >> >> >> >> > * Sonar analysis run daily if scm change: >> >> >> >> > >> https://analysis.apache.org/dashboard/index/org.apache.helix:helix >> >> >> >> > * configuration for web site done (still need infra change): >> >> sample of >> >> >> >> > generated site http://people.apache.org/~olamy/helix/ >> >> >> >> > * I have asked for deploying snapshots to asf repository >> (usually >> >> we >> >> >> >> > setup jenkins jobs to do that). >> >> >> >> > >> >> >> >> > So What else ? :-) >> >> >> >> > >> >> >> >> > 2012/10/23 Olivier Lamy <[email protected]>: >> >> >> >> >> 2012/10/23 kishore g <[email protected]>: >> >> >> >> >>> The code is migrated to Apache git >> >> >> >> >>> >> >> >> >> >> >> >> https://git-wip-us.apache.org/repos/asf?p=incubator-helix.git;a=summary >> >> >> . >> >> >> >> It >> >> >> >> >>> is read only at this moment but should be writable soon. >> >> >> >> >>> https://issues.apache.org/jira/browse/INFRA-5437 >> >> >> >> >>> >> >> >> >> >>> Oliver, can you help us on the website creation. Our initial >> plan >> >> >> is to >> >> >> >> >>> simply migrate the wiki pages at >> >> >> >> https://github.com/linkedin/helix/wiki to >> >> >> >> >>> http://incubator.apache.org/helix. Pat suggested us to use >> >> Apache >> >> >> CMS >> >> >> >> for >> >> >> >> >>> this and it makes sense since we already wiki in markdown >> format. >> >> >> >> >>> >> >> >> >> >>> Basically, this is what we need from you. >> >> >> >> >>> >> >> >> >> >>> Where should we put the files in helix git repo. Probably >> under >> >> site >> >> >> >> >>> Is there a maven plugin that will generate the html files >> from >> >> >> >> markdown. >> >> >> >> >>> What is command to push the generated files to apache, do we >> have >> >> >> >> >>> permission to do this? >> >> >> >> >> Yup there is a module to generate html from md files[1]. We >> only >> >> need >> >> >> >> >> to put md files under src/site/markdown >> >> >> >> >> >> >> >> >> >> What I propose is to use that to generate both doc and >> javadoc tru >> >> >> >> maven. >> >> >> >> >> Then content can be committed to the svn path >> >> >> >> >> ( >> https://svn.apache.org/repos/asf/incubator/helix/site-content ) >> >> >> >> >> Infra folks will setup svnpubsub to populate >> >> >> >> >> helix.incubator.apache.org from this svn path >> >> >> >> >> Note: there is a maven plugin to commit site content to a svn >> >> path (I >> >> >> >> >> can setup that for you) >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> Olivier >> >> >> >> >> [1] >> >> >> >> >> >> >> >> >> >> http://maven.apache.org/doxia/doxia/doxia-modules/doxia-module-markdown/index.html >> >> >> >> >>> >> >> >> >> >>> thanks, >> >> >> >> >>> Kishore G >> >> >> >> >>> >> >> >> >> >>> On Fri, Oct 19, 2012 at 3:27 PM, Olivier Lamy < >> [email protected]> >> >> >> >> wrote: >> >> >> >> >>> >> >> >> >> >>>> Hi, >> >> >> >> >>>> inline >> >> >> >> >>>> >> >> >> >> >>>> 2012/10/19 kishore g <[email protected]>: >> >> >> >> >>>> > Hi Guys, >> >> >> >> >>>> > >> >> >> >> >>>> > What are the next steps. >> >> >> >> >>>> > >> >> >> >> >>>> > From bootstrap podling >> >> >> >> >>>> > >> >> >> >> >>>> > >> >> >> >> >>>> > 1. Ensure Mentors are on the >> >> >> >> >>>> > IPMC< >> >> http://incubator.apache.org/guides/mentor.html#mentors-ipmc >> >> >> > >> >> >> >> >>>> > [Mentors] >> >> >> >> >>>> > 2. Add podling to reporting >> >> >> >> >>>> > schedule< >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> http://incubator.apache.org/guides/mentor.html#Sending+in+an+Incubation+Report >> >> >> >> >>>> > >> >> >> >> >>>> > [IPMC member < >> >> >> >> >>>> http://incubator.apache.org/guides/mentor.html#who-ipmc>] >> >> >> >> >>>> > 3. Initialize project status >> >> >> >> >>>> > page< >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> http://incubator.apache.org/guides/mentor.html#Initialize+Podling+Status+Page >> >> >> >> >>>> > >> >> >> >> >>>> > [IPMC member < >> >> >> >> >>>> http://incubator.apache.org/guides/mentor.html#who-ipmc>] >> >> >> >> >>>> > 4. Start orientation< >> >> >> >> >>>> http://incubator.apache.org/guides/mentor.html#orientation> >> >> >> >> >>>> > [Prospective >> >> >> >> >>>> > committers< >> >> >> >> http://incubator.apache.org/guides/mentor.html#who-committers >> >> >> >> >>>> > >> >> >> >> >>>> > ] >> >> >> >> >>>> > 5. Start CLA and CCLA submission [Prospective >> >> >> >> >>>> > committers< >> >> >> >> http://incubator.apache.org/guides/mentor.html#who-committers >> >> >> >> >>>> > >> >> >> >> >>>> > ] >> >> >> >> >>>> > 6. Start IP Clearance< >> >> >> >> >>>> >> >> >> http://incubator.apache.org/guides/mentor.html#initial-ip-clearance >> > >> >> >> >> >>>> > [IPMC member < >> >> >> >> >>>> http://incubator.apache.org/guides/mentor.html#who-ipmc>] >> >> >> >> >>>> > 7. Request Required Resources >> >> >> >> >>>> > 1. Mailing >> >> >> >> >>>> > Lists< >> >> >> >> >>>> >> >> >> >> http://incubator.apache.org/guides/mentor.html#request-mailing-lists> >> >> >> >> >>>> > [Infrastructure >> >> >> >> >>>> > Team< >> http://incubator.apache.org/guides/mentor.html#who-infra >> >> > >> >> >> >> >>>> > ] >> >> >> >> >>>> > - Consider and plan transition to official >> mailing >> >> >> >> >>>> > lists< >> >> >> >> >>>> >> >> >> >> >> >> >> http://incubator.apache.org/guides/mentor.html#transition-mailing-lists >> >> >> > >> >> >> >> >>>> > 2. Subversion< >> >> >> >> >>>> >> >> http://incubator.apache.org/guides/mentor.html#Set+Up+Repository> >> >> >> >> >>>> > [IPMC < >> >> >> >> http://incubator.apache.org/guides/mentor.html#who-ipmc>] >> >> >> >> >>>> > 3. Issue Tracking< >> >> >> >> >>>> >> >> >> >> http://incubator.apache.org/guides/mentor.html#request-issue-tracking >> >> >> >> > >> >> >> >> >>>> > [Infrastructure >> >> >> >> >>>> > Team< >> http://incubator.apache.org/guides/mentor.html#who-infra >> >> > >> >> >> >> >>>> > ] >> >> >> >> >>>> > - Consider and plan issue tracking >> >> >> >> >>>> > transition< >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> http://incubator.apache.org/guides/mentor.html#issue-tracking-transition> >> >> >> >> >>>> > 8. Create >> >> >> >> >>>> > website< >> >> >> >> http://incubator.apache.org/guides/mentor.html#create-website> >> >> >> >> >>>> > [Prospective >> >> >> >> >>>> > committers< >> >> >> >> http://incubator.apache.org/guides/mentor.html#who-committers >> >> >> >> >>>> > >> >> >> >> >>>> > ] >> >> >> >> >>>> > 1. Consider and plan web site >> >> >> >> >>>> > transition< >> >> >> >> >>>> >> >> http://incubator.apache.org/guides/mentor.html#web-site-transition >> >> >> > >> >> >> >> >>>> > >> >> >> >> >>>> > I think we are done with 1,5, 7.1 >> >> >> >> >>>> > >> >> >> >> >>>> > Here are the questions i have >> >> >> >> >>>> > >> >> >> >> >>>> > - How can we edit the website >> >> >> >> >>>> >> >> >> >> >>>> You mean project website ? It depends what kind of >> technology >> >> you >> >> >> want >> >> >> >> >>>> to use for building web site ? (I mean documentation >> javadoc etc >> >> >> ...) >> >> >> >> >>>> @asf website content is now committed in a svn path to have >> it >> >> >> >> deployed >> >> >> >> >>>> live. >> >> >> >> >>>> >> >> >> >> >>>> > - How to move the code to Apache, we will move to >> apache >> >> and >> >> >> then >> >> >> >> >>>> > re-factor the package >> >> >> >> >>>> >> >> >> >> >>>> How I see that but need some discussions: simply clone the >> >> current >> >> >> git >> >> >> >> >>>> repo from github and use it here @asf >> >> >> >> >>>> >> >> >> >> >>>> > - Will need help from Olivier, updating the pom files >> to >> >> >> upload >> >> >> >> to >> >> >> >> >>>> maven >> >> >> >> >>>> > repository. >> >> >> >> >>>> No problem I have a bit of knowledge on this part :-) >> >> >> >> >>>> > - Review license files >> >> >> >> >>>> There is the rat maven plugin to do that and reducing >> number of >> >> >> manual >> >> >> >> >>>> check but some are still needed. >> >> >> >> >>>> > >> >> >> >> >>>> > Anything else we need before we make the first release. I >> >> plan to >> >> >> >> get the >> >> >> >> >>>> > first release out by end of this month. Let me know if >> there >> >> are >> >> >> >> any big >> >> >> >> >>>> > unknowns >> >> >> >> >>>> >> >> >> >> >>>> Not sure we will be able to finish that for such target. But >> >> good >> >> >> to >> >> >> >> >>>> have a goal :-) >> >> >> >> >>>> >> >> >> >> >>>> > >> >> >> >> >>>> > thanks, >> >> >> >> >>>> > Kishore G >> >> >> >> >>>> >> >> >> >> >>>> >> >> >> >> >>>> >> >> >> >> >>>> -- >> >> >> >> >>>> Olivier Lamy >> >> >> >> >>>> Talend: http://coders.talend.com >> >> >> >> >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> >>>> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> >> Olivier Lamy >> >> >> >> >> Talend: http://coders.talend.com >> >> >> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> > >> >> >> >> > >> >> >> >> > >> >> >> >> > -- >> >> >> >> > Olivier Lamy >> >> >> >> > Talend: http://coders.talend.com >> >> >> >> > http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> >> Olivier Lamy >> >> >> >> Talend: http://coders.talend.com >> >> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> >> Olivier Lamy >> >> >> Talend: http://coders.talend.com >> >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> >> >> >> >> >> >> >> -- >> >> Olivier Lamy >> >> Talend: http://coders.talend.com >> >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> >> >> >> >> >> -- >> Olivier Lamy >> Talend: http://coders.talend.com >> http://twitter.com/olamy | http://linkedin.com/in/olamy >> > >
