felix uses maven-bundle-plugin. Not sure why plugin name is important here.
-D On Tue, Oct 9, 2012 at 2:38 PM, Stephen Connolly <stephen.alan.conno...@gmail.com> wrote: > On 9 October 2012 21:12, Mark Donszelmann <mark.donszelm...@cern.ch> wrote: > >> Hi >> >> On Oct 9, 2012, at 7:18 PM, Stephen Connolly < >> stephen.alan.conno...@gmail.com> >> wrote: >> >> Don't forget to change the artifactId to nar-maven-plugin or such as >> maven-___-plugin is reserved for maven.apache.org owned plugins >> >> >> I guess that is correct, however Jason (van Zyl) at the time told me to >> use maven-nar-plugin... >> >> > That guidance has changed. > > >> Regards >> Duns >> >> >> On Tuesday, 9 October 2012, Curtis Rueden wrote: >> >>> Hi all, >>> >>> > Feel free to create it an invite the people :) >>> >>> Done: >>> https://groups.google.com/forum/?fromgroups#!forum/maven-nar >>> >>> Let's continue this thread there! >>> >>> Regards, >>> Curtis >>> >>> >>> On Mon, Oct 8, 2012 at 5:40 PM, Martin Eisengardt < >>> martin.eisenga...@gmail.com> wrote: >>> >>> > >>> >> >>> > Also, rather than migrating a fork directly, perhaps (if Mark agrees) we >>> >> could migrate the @duns repo, then push all of Greg's changes back on >>> top? >>> >> That way, existing GitHub forks will all state "forked from >>> >> maven-nar/maven-nar-plugin" afterward, which would be ideal. And to >>> >> preserve old links Mark could fork it back into @duns again and update >>> the >>> >> README to state what happened. Thoughts? >>> >> >>> >> >>> > >>> > Sounds like a good plan. However I did not compare the forks so I do not >>> > have an idea how many work has to be done. But I will have a look in the >>> > next days. >>> > >>> > >>> >> Presumably we would also want to similarly migrate cpptasks-parallel? >>> >> >>> >> >>> > >>> > I think so. It isn't maintained too (correct me if I am wrong). >>> > >>> > >>> >> >>> >> > Technical features can be discussed in the github wiki at the moment. >>> >> >>> >> Martin, shall we create a mailing list for the project? Perhaps a >>> Google >>> >> group? Then we can migrate this discussion there instead. >>> >> >>> >> >>> > >>> > Feel free to create it an invite the people :) >>> > >>> > >>> >> >>> >> Regarding cross-compilation: I know it is of interest (wouldn't it be >>> >> great to build for multiple target platforms all from the CloudBees >>> Jenkins >>> >> on Linux?). My colleague has done quite a lot of work in that area, but >>> >> there are some substantial obstacles. Shall we discuss further on our >>> shiny >>> >> new maven-nar-plugin mailing list, once it exists? >>> >> >>> >> >>> > >>> > Yeah, we should discuss it in a working group with experience on this >>> > topic. Setting up cross compilation and having a maven-nar-plugin >>> > supporting it is not that easy. >>> > >>> > >>> >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
