Hi, I was going to reply earlier but it slipped.
I'd also like to hear more on "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?" In the meantime I'm in favour of merging the branches, though for the moment I'm not sure how much time I will have to progress the work mostly it seemed done for all the smaller changes, haven't kept up recently with other 2 active branches. Using my branch or another I'll continue to contribute. I'll merge in changes or grant others access to commit directly on the branch I started to allow this to get moving forward. What I would really need help with is getting the meta setup - I haven't setup a location for the site info before, or worked on publishing to maven central or the other major stores - I'm certainly open to using Martin's offered locations for this. Also the issue log at sonatype is sort of locked up right now, we can add to it, but nobody seems to be able to take on being a developer or own a task assign next milestone etc. --- Sorry about missing cherry pick notes, there where a few changes that overlapped and git got the best of me. --- I actually have another currently private branch that is a mangled mess that does multi builds libtype x linker x arch. I'm going to upload it as another fork for reference, but in the end I think it is a dead end. --- Thoughts on changes that might break with maven 2? The changes I'd really like to make now are in line with making NAR a first class group of plugins for maven3 that would even integrate with other tools such as eclipse or msvc. Thats things like separating the packaging/lifecycle, dependency, compilation into separate plugins, adding a nar-plugin api for plugins to share nar info like sources, layout etc. - having a vague hand wavy idea, but no concrete statement to guide others with yet. I have plugins but then I found need to make special config to share info * xsd-mapping-maven that generates source from an xsd code generator, but have to make config changes currently to tell nar where to get the source. * signing that zips up items to sign and sends them to a web service to sign - at the moment it just grabs all the dll, exe, jar and sends, it needs instruction from nar config on what was built. richardkerr work on additonal compile / post processing seems like a candidate for a seperate plugin 1spatial work on NuGet seems like a candidate for a seperate plugin as alternate archiving Greg >>> Curtis Rueden <[email protected]> 10/05/12 12:14 PM >>> 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
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
