Hi all, Replying back with defunct email addresses purged, so that any future replies don't keep receiving bounces.
-Curtis On Fri, Oct 5, 2012 at 11:09 AM, Curtis Rueden <[email protected]> wrote: > Greetings maven-nar-plugin hackers! > > I am writing to gauge interest in a unified implementation of > maven-nar-plugin. It seems there are several active (and not-so-active) > forks. It seems the original implementation (@duns) is no longer active, > but both @GregDomjan and @richardkerr have active forks (the latter forked > from the former), and merge improvements from other forks too. > > Before we were aware of this, my colleague (Johannes Schindelin) & I > started another fork (@scijava) to address some issues we had. which have > since been merged into the @GregDomjan fork (although I could not find a > cherry-picked commit... it must have been done in some non-standard way?). > > I would be happy to deprecate the @scijava fork in favor of the > @GregDomjan code, if we can agree to standardize on one officially > maintained repository. If we do go that route, it should not be too > difficult to start releasing versions to Maven Central. Can all agree to > start submitting PRs to Greg for any future patches, rather than silently > maintaining our own forks? Greg, what do you think? Others? > > Apache/Sonatype/Codehaus developers: It appears that there was once a push > for Apache to adopt maven-nar-plugin as a core plugin. Is that effort > abandoned now? Is a unified GitHub project the best way forward for > maven-nar-plugin? Or would it make more sense for one of the big Maven > umbrella groups to adopt it instead? > > Thanks, > Curtis > > > On Fri, Sep 14, 2012 at 10:34 AM, Martin Eisengardt < > [email protected]> wrote: > >> The author (@duns) seems to be not actve any more. However I failed >> contacting him for a while. >> >> https://github.com/GregDomjan/maven-nar-plugin >> And there is a second one being active: >> https://github.com/richardkerr/maven-nar-plugin (do not know how to >> contact this guy) >> >> However both try to merge the forks being around. And they like any kind >> of help. If there are some people around that want to give it a new try >> that would be nice. >> I guess the original plugin was some kind of sandbox @ sonatype. I do not >> know if we should simply group up some people that officially will maintain >> it and I do not know if even sonatype or others are interested. >> >> However for being pragmatic I would say to choose one of the active >> forks, grouping a new team and granting commit rights to the people that >> want to maintain it. >> I am able to provide both, a repository and a hudson as long as this is >> not moved to maven central. >> >> However I am personally focused on compiling php/php-extensions and using >> maven-nar-plugin to access them with maven. Multi-Platform compiles/ >> Cross-Platform compiles >> I will come back to the project as soon as our build server knows how to >> do cross compiles for various platforms. >> >> >> On Fri, Sep 14, 2012 at 5:09 PM, Curtis Rueden <[email protected]> wrote: >> >>> Hi Martin, >>> >>> >>>> There is a problem with the [maven-nar-plugin] project because there >>>> are tens of orks on github. If you have any questions about it please ask. >>>> I have contact to one of the ative authors and we try to merge all the >>>> forks. >>> >>> >>> I am guilty of one of those forks. We submitted a PR ( >>> https://github.com/duns/maven-nar-plugin/pull/5) but never heard back, >>> so we had no choice. >>> >>> It looks like the canonical version at duns/maven-nar-plugin has not >>> been updated for nearly two years. Is that going to change? It would be >>> great for this very valuable plugin to be maintained! >>> >>> Thanks, >>> Curtis >>> >> >
