You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Kevin Menard <km...@servprise.com> on 2007/04/05 14:05:03 UTC
Sandbox question
Hi all,
I have an immature jython plugin I've been working on that has largely
been used internally. It looks like something that the sandbox could be
useful for, but I'm debating the merits of just hosting it myself. I
guess what would help me is understand what the sandbox provides. Is it
just an SVN area? Where would plugin docs, site, etc. be hosted? Is
there some sort of graduation path up to a fully supported plugin?
Thanks,
Kevin
Kevin Menard
Servprise International, Inc.
800.832.3823 x308
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Sandbox question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
I forgot to mention that if your plugin should be run by the command
line, maven by default only looks for org.apache.maven or
org.codehaus.mojo plugins without the user having to add some settings.
This can be a barrier to use as well (this is less troublesome if your
plugin is supposed to be run by binding to a pom)
-----Original Message-----
From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Thursday, April 05, 2007 9:47 AM
To: Maven Developers List
Subject: RE: Sandbox question
Hi Kevin,
The sandbox was created to give existing Apache committers a place to
create plugins that may potentially be brought up to full released
plugins. The benefits to putting them here are that the infrastructure
with all the other plugins will be shared (Jira, Svn,Site etc) and it's
the first place people look for plugins. If you aren't already an Apache
committer, then an option would be to try the mojo project on codehaus
(http://mojo.codehaus.org). This is where we host plugins that don't
meet Apache licenses, or are developed by non-apache committers (or they
choose to put it there for other reasons). The barriers to entry are
lower in mojo, but you still need to be active for a while and submit
plugins and patches via jira until you get voted in with full commit
rights.
Hosting a plugin yourself can certainly be easier in the short term, but
you will get more exposure and potential users and developers on either
of the 2 communities I mentioned. It's also easier to get your builds
onto the central repository so people can easily use them.
Hope that helps.
--Brian
-----Original Message-----
From: Kevin Menard [mailto:kmenard@servprise.com]
Sent: Thursday, April 05, 2007 8:05 AM
To: dev@maven.apache.org
Subject: Sandbox question
Hi all,
I have an immature jython plugin I've been working on that has largely
been used internally. It looks like something that the sandbox could be
useful for, but I'm debating the merits of just hosting it myself. I
guess what would help me is understand what the sandbox provides. Is it
just an SVN area? Where would plugin docs, site, etc. be hosted? Is
there some sort of graduation path up to a fully supported plugin?
Thanks,
Kevin
Kevin Menard
Servprise International, Inc.
800.832.3823 x308
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Sandbox question
Posted by Eric Redmond <er...@gmail.com>.
Groovy, JRuby and Jelly language extensions are in the Mojo project... for
consistency I'd say put the Jython plugin in Mojo as well. Just FYI, there
already exists a Jython factory in Plexus, and it would be optimal to use
that as your plugin's base (see the other language extensions for examples).
Eric
On 4/5/07, Kevin Menard <km...@servprise.com> wrote:
>
> Hi Brian,
>
> Thanks for the info. I am already an ASF committer (Cayenne project),
> but other than the initial message sent to the committers list regarding
> the sandbox, I couldn't find much more on it.
>
> I take it I can can just add my contribution to
> https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/ ?
>
> Is there a standard place to put the site & docs or just my p.a.o
> account? Re: JIRA, how is that handled? It looks like all the maven
> JIRA items are hosted by codehaus . . .
>
> Thanks again,
> Kevin
>
> > -----Original Message-----
> > From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> > Sent: Thursday, April 05, 2007 9:47 AM
> > To: Maven Developers List
> > Subject: RE: Sandbox question
> >
> > Hi Kevin,
> > The sandbox was created to give existing Apache committers a
> > place to create plugins that may potentially be brought up to
> > full released plugins. The benefits to putting them here are
> > that the infrastructure with all the other plugins will be
> > shared (Jira, Svn,Site etc) and it's the first place people
> > look for plugins. If you aren't already an Apache committer,
> > then an option would be to try the mojo project on codehaus
> > (http://mojo.codehaus.org). This is where we host plugins
> > that don't meet Apache licenses, or are developed by
> > non-apache committers (or they choose to put it there for
> > other reasons). The barriers to entry are lower in mojo, but
> > you still need to be active for a while and submit plugins
> > and patches via jira until you get voted in with full commit rights.
> >
> > Hosting a plugin yourself can certainly be easier in the
> > short term, but you will get more exposure and potential
> > users and developers on either of the 2 communities I
> > mentioned. It's also easier to get your builds onto the
> > central repository so people can easily use them.
> >
> > Hope that helps.
> >
> > --Brian
> >
> > -----Original Message-----
> > From: Kevin Menard [mailto:kmenard@servprise.com]
> > Sent: Thursday, April 05, 2007 8:05 AM
> > To: dev@maven.apache.org
> > Subject: Sandbox question
> >
> > Hi all,
> >
> > I have an immature jython plugin I've been working on that
> > has largely been used internally. It looks like something
> > that the sandbox could be useful for, but I'm debating the
> > merits of just hosting it myself. I guess what would help me
> > is understand what the sandbox provides. Is it just an SVN
> > area? Where would plugin docs, site, etc. be hosted? Is
> > there some sort of graduation path up to a fully supported plugin?
> >
> > Thanks,
> > Kevin
> >
> > Kevin Menard
> > Servprise International, Inc.
> > 800.832.3823 x308
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> > additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Eric Redmond
http://codehaus.org/~eredmond
RE: Sandbox question
Posted by Kevin Menard <km...@servprise.com>.
Hi Brian,
Thanks for the info. I am already an ASF committer (Cayenne project),
but other than the initial message sent to the committers list regarding
the sandbox, I couldn't find much more on it.
I take it I can can just add my contribution to
https://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/ ?
Is there a standard place to put the site & docs or just my p.a.o
account? Re: JIRA, how is that handled? It looks like all the maven
JIRA items are hosted by codehaus . . .
Thanks again,
Kevin
> -----Original Message-----
> From: Brian E. Fox [mailto:brianf@reply.infinity.nu]
> Sent: Thursday, April 05, 2007 9:47 AM
> To: Maven Developers List
> Subject: RE: Sandbox question
>
> Hi Kevin,
> The sandbox was created to give existing Apache committers a
> place to create plugins that may potentially be brought up to
> full released plugins. The benefits to putting them here are
> that the infrastructure with all the other plugins will be
> shared (Jira, Svn,Site etc) and it's the first place people
> look for plugins. If you aren't already an Apache committer,
> then an option would be to try the mojo project on codehaus
> (http://mojo.codehaus.org). This is where we host plugins
> that don't meet Apache licenses, or are developed by
> non-apache committers (or they choose to put it there for
> other reasons). The barriers to entry are lower in mojo, but
> you still need to be active for a while and submit plugins
> and patches via jira until you get voted in with full commit rights.
>
> Hosting a plugin yourself can certainly be easier in the
> short term, but you will get more exposure and potential
> users and developers on either of the 2 communities I
> mentioned. It's also easier to get your builds onto the
> central repository so people can easily use them.
>
> Hope that helps.
>
> --Brian
>
> -----Original Message-----
> From: Kevin Menard [mailto:kmenard@servprise.com]
> Sent: Thursday, April 05, 2007 8:05 AM
> To: dev@maven.apache.org
> Subject: Sandbox question
>
> Hi all,
>
> I have an immature jython plugin I've been working on that
> has largely been used internally. It looks like something
> that the sandbox could be useful for, but I'm debating the
> merits of just hosting it myself. I guess what would help me
> is understand what the sandbox provides. Is it just an SVN
> area? Where would plugin docs, site, etc. be hosted? Is
> there some sort of graduation path up to a fully supported plugin?
>
> Thanks,
> Kevin
>
> Kevin Menard
> Servprise International, Inc.
> 800.832.3823 x308
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: Sandbox question
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
Hi Kevin,
The sandbox was created to give existing Apache committers a place to
create plugins that may potentially be brought up to full released
plugins. The benefits to putting them here are that the infrastructure
with all the other plugins will be shared (Jira, Svn,Site etc) and it's
the first place people look for plugins. If you aren't already an Apache
committer, then an option would be to try the mojo project on codehaus
(http://mojo.codehaus.org). This is where we host plugins that don't
meet Apache licenses, or are developed by non-apache committers (or they
choose to put it there for other reasons). The barriers to entry are
lower in mojo, but you still need to be active for a while and submit
plugins and patches via jira until you get voted in with full commit
rights.
Hosting a plugin yourself can certainly be easier in the short term, but
you will get more exposure and potential users and developers on either
of the 2 communities I mentioned. It's also easier to get your builds
onto the central repository so people can easily use them.
Hope that helps.
--Brian
-----Original Message-----
From: Kevin Menard [mailto:kmenard@servprise.com]
Sent: Thursday, April 05, 2007 8:05 AM
To: dev@maven.apache.org
Subject: Sandbox question
Hi all,
I have an immature jython plugin I've been working on that has largely
been used internally. It looks like something that the sandbox could be
useful for, but I'm debating the merits of just hosting it myself. I
guess what would help me is understand what the sandbox provides. Is it
just an SVN area? Where would plugin docs, site, etc. be hosted? Is
there some sort of graduation path up to a fully supported plugin?
Thanks,
Kevin
Kevin Menard
Servprise International, Inc.
800.832.3823 x308
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional
commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org