Re: [jira] [Updated] (MAHOUT-1209) DRY out maven-compiler-plugin configuration
Organizations support isn't sufficient? https://help.github.com/articles/what-s-the-difference-between-user-and-organization-accounts#organizations I guess there's need for suborganizations for each apache project on github. Not sure if that's supported or feasible with existing organizations support. On Sun, May 12, 2013 at 10:59 PM, Ted Dunning wrote: > The additional factor is that github doesn't provide sufficient control > over access to individual projects. If it were possible to ensure that > only committers had access to the github mirror, it would be plausible to > handle pull requests more directly, even with SVN as the primary repo. We > could handle the pull request using github and use git svn to push back to > SVN. > > Until github does that (and there is no motion in that direction), then > patches will rule. > > > > On Sun, May 12, 2013 at 1:50 PM, Stevo Slavić wrote: > > > I understand, thanks. This seems to be general ASF infra/policies and > > GitHub pull requests issue. > > Will continue to submit both pull requests on github and svn compatible > > patches attached to JIRA, and close pull requests by myself once patches > > get integrated/merged. > > > > Kind regards, > > Stevo Slavic. > > > > > > On Sun, May 12, 2013 at 7:43 PM, Ted Dunning > > wrote: > > > > > > > > > > > We talked about this but it is difficult to switch the user base except > > at > > > the beginning if a project. For drill, as an example, we started with > > git. > > > > > > Unfortunately that still doesn't solve the pull problem since the > apache > > > source on GitHub is just a mirror and can't push updates back to > apache. > > > > > > The only good news is that enough of use git that git formatted patches > > > are ok. > > > > > > On May 12, 2013, at 2:05, "Stevo Slavic (JIRA)" > wrote: > > > > > > > I wish Mahout used git as primary scm. > > > > > >
Re: [jira] [Updated] (MAHOUT-1209) DRY out maven-compiler-plugin configuration
The additional factor is that github doesn't provide sufficient control over access to individual projects. If it were possible to ensure that only committers had access to the github mirror, it would be plausible to handle pull requests more directly, even with SVN as the primary repo. We could handle the pull request using github and use git svn to push back to SVN. Until github does that (and there is no motion in that direction), then patches will rule. On Sun, May 12, 2013 at 1:50 PM, Stevo Slavić wrote: > I understand, thanks. This seems to be general ASF infra/policies and > GitHub pull requests issue. > Will continue to submit both pull requests on github and svn compatible > patches attached to JIRA, and close pull requests by myself once patches > get integrated/merged. > > Kind regards, > Stevo Slavic. > > > On Sun, May 12, 2013 at 7:43 PM, Ted Dunning > wrote: > > > > > > > We talked about this but it is difficult to switch the user base except > at > > the beginning if a project. For drill, as an example, we started with > git. > > > > Unfortunately that still doesn't solve the pull problem since the apache > > source on GitHub is just a mirror and can't push updates back to apache. > > > > The only good news is that enough of use git that git formatted patches > > are ok. > > > > On May 12, 2013, at 2:05, "Stevo Slavic (JIRA)" wrote: > > > > > I wish Mahout used git as primary scm. > > >
Re: [jira] [Updated] (MAHOUT-1209) DRY out maven-compiler-plugin configuration
I understand, thanks. This seems to be general ASF infra/policies and GitHub pull requests issue. Will continue to submit both pull requests on github and svn compatible patches attached to JIRA, and close pull requests by myself once patches get integrated/merged. Kind regards, Stevo Slavic. On Sun, May 12, 2013 at 7:43 PM, Ted Dunning wrote: > > > We talked about this but it is difficult to switch the user base except at > the beginning if a project. For drill, as an example, we started with git. > > Unfortunately that still doesn't solve the pull problem since the apache > source on GitHub is just a mirror and can't push updates back to apache. > > The only good news is that enough of use git that git formatted patches > are ok. > > On May 12, 2013, at 2:05, "Stevo Slavic (JIRA)" wrote: > > > I wish Mahout used git as primary scm. >
Re: [jira] [Updated] (MAHOUT-1209) DRY out maven-compiler-plugin configuration
We talked about this but it is difficult to switch the user base except at the beginning if a project. For drill, as an example, we started with git. Unfortunately that still doesn't solve the pull problem since the apache source on GitHub is just a mirror and can't push updates back to apache. The only good news is that enough of use git that git formatted patches are ok. On May 12, 2013, at 2:05, "Stevo Slavic (JIRA)" wrote: > I wish Mahout used git as primary scm.
[jira] [Updated] (MAHOUT-1209) DRY out maven-compiler-plugin configuration
[ https://issues.apache.org/jira/browse/MAHOUT-1209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic updated MAHOUT-1209: - Attachment: MAHOUT-1209.patch Attaching svn compatible [^MAHOUT-1209.patch]. I wish Mahout used git as primary scm. > DRY out maven-compiler-plugin configuration > --- > > Key: MAHOUT-1209 > URL: https://issues.apache.org/jira/browse/MAHOUT-1209 > Project: Mahout > Issue Type: Bug > Components: build >Affects Versions: 0.7 >Reporter: Stevo Slavic >Priority: Minor > Labels: maven > Attachments: MAHOUT-1209.patch > > > maven-compiler-plugin configuration is unnecessarily repeated in POMs of > several modules, even though mahout parent POM defines same > maven-compiler-plugin configuration which is inherited by all of the modules. > This unnecessarily clutters module POMs making them harder to read and > maintain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
