Hi Stephen everyone,
Don't forget to change the artifactId to nar-maven-plugin or such as
maven-___-plugin is reserved for maven.apache.org owned plugins
Thanks, I filed an issue for it on GitHub:
https://github.com/maven-nar/maven-nar-plugin/issues/9
Regards,
Curtis
On Tue, Oct 9, 2012
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
Don't forget to change the artifactId to nar-maven-plugin or such as
maven-___-plugin is reserved for maven.apache.org owned plugins
On Tuesday, 9 October 2012, Curtis Rueden wrote:
Hi all,
Feel free to create it an invite the people :)
Done:
; Mark
Donszelmann; Mark Donszelmann; Elliot Metsger; sthelen; Peter Janes; Claudio
Bantaloukas; Mirko Jahn; sugree
Subject: Re: Unifying maven-nar-plugin implementations
Also, rather than migrating a fork directly, perhaps (if Mark agrees) we could
migrate the @duns repo, then push all
What I understood was that Marks aim in loading to github, and what I think our
aim now is to have it available for general use and progress to it being an
apache.org plugin.
Would that mean we should change the name until it is ready, or is having the
apache naming part of being ready.
Hi
On Oct 9, 2012, at 7:18 PM, Stephen Connolly
stephen.alan.conno...@gmail.commailto: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.orghttp://maven.apache.org/
owned plugins
I guess
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
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
Newer versions of the plugin-plugin enforce the standard so you have to
switch to nar-maven-plugin or whatever unless you use the org.apache.maven
groupId...
imho I would just change and keep the momentum going on github and not
really worry about moving it to apache..
manfred
On Tue, October
felix will have to change
On 9 October 2012 23:11, Dan Tran dant...@gmail.com wrote:
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
On 7 October 2012 16:36, Martin Eisengardt martin.eisenga...@gmail.comwrote:
OK. Thanks four your responses, Mark and Jason.
Lets sum up. We have the agreement of the authors to build up a new
working group.
I recently created a new organization at github:
https://github.com/maven-nar (just
@maven.apache.org
Cc: joerg.schai...@gmx.de; Donszelmann Mark d...@cern.ch
Sent: Monday, October 8, 2012 10:06 AM
Subject: Re: Unifying maven-nar-plugin implementations
On 7 October 2012 16:36, Martin Eisengardt martin.eisenga...@gmail.comwrote:
OK. Thanks four your responses, Mark and Jason.
Lets sum up
My employers (CloudBees) will give free jenkins instance to any Open Source
project that asks for one.
Thanks for your support. Is your jenkins aware of native builds for win,
linux, sunosx, macosx and aware of doing cross-compiles? However please let
us talk directly. Maybe we need more
On 8 October 2012 13:30, Martin Eisengardt martin.eisenga...@gmail.comwrote:
My employers (CloudBees) will give free jenkins instance to any Open
Source
project that asks for one.
Thanks for your support. Is your jenkins aware of native builds for win,
linux, sunosx, macosx and
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
Hi,
Benson Margulies wrote:
Adding plugins to the core is not so much a matter of 'strategy'.
The nar plugin is a non-trivial amount of code. So, for it to come to
Apache, it would have to pass IP clearance. That means understanding
the provenance of all of the code and that the people
Do we actually need the agreement of all authors to become a maven core
project?
The sources are already licensed under terms of ASF.
The original authors seem not respond for months or the email addresses are
no longer valid.
Would it be fine if there is a new (active) project group filling up
Hi
I am the author of the maven-nar-plugin. Let me start by apologizing that I
have not kept track of, neither have worked on
it in recent years. I moved on to other things, but may come back using /
working on it later on.
The nar plugin was created by me when I was working at Stanford
I was waiting for you to respond as its your baby :-)
While Sonatype helped pay for some of the work in the last stage of NARs
development, our focus has really been on Java so we really haven't had much
time in the last few years. That said with all the work Sonatype has been doing
with
Jason will, I'm sure, correct me if I'm wrong, but I believe the IP
provenance issues to be comparable at Eclipse and Apache.
The Apache Foundation only accepts code that is *voluntarily*
contributed. That amounts to two tests:
a) is there clear provenance?
b) is there clear evidence of the
OK. Thanks four your responses, Mark and Jason.
Lets sum up. We have the agreement of the authors to build up a new
working group.
I recently created a new organization at github:
https://github.com/maven-nar (just to give this a kickstart)
Please tell me who wants to become a project owner. I
I think the github organization is a great start.
On Oct 7, 2012, at 11:36 AM, Martin Eisengardt martin.eisenga...@gmail.com
wrote:
OK. Thanks four your responses, Mark and Jason.
Lets sum up. We have the agreement of the authors to build up a new
working group.
I recently created a new
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
Great news for the project, it looks very promising, especially for working
on jni libs.
I have no personal interest in the project anymore as it has served its
purpose for me (building a legacy jni lib on windows AIX and linux)
I had only made two commits
Adding plugins to the core is not so much a matter of 'strategy'.
The nar plugin is a non-trivial amount of code. So, for it to come to
Apache, it would have to pass IP clearance. That means understanding
the provenance of all of the code and that the people contributing it
have sufficient rights
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
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 ctrue...@wisc.edu wrote:
Greetings maven-nar-plugin hackers!
I am writing to gauge interest in a unified implementation
Hi.
However the first topic is to group a team that will be well active and
that will be adoting all forks. I suggest to choose one github project and
declare it to be the new main project.
One fork by one should be merged and than deleted. Maybe we should choose
richards or gregs project (that
28 matches
Mail list logo
