Hi,
On 9/3/14 9:39 AM, Anders Hammar wrote:
One problem is that the JIRA URL is on the produced mojo site, so
creating the JIRA project after the release requires a new release to
update the site.
/Anders
I have the same opinion as Anders....
so i would vote against this kind of relaxing...
I have gone that way as well...for the JDEPEND plugin...which is not
really a big deal...
Kind regards
Karl-Heinz Marbaise
On Wed, Sep 3, 2014 at 9:31 AM, Dan Tran <dant...@gmail.com
<mailto:dant...@gmail.com>> wrote:
Correct
-Dan
On Tuesday, September 2, 2014, Anders Hammar <and...@hammar.net
<mailto:and...@hammar.net>> wrote:
Not sure what you mean. Do you want to make a 1.0 release
without a mojo specific JIRA project?
/Anders
On Wed, Sep 3, 2014 at 8:29 AM, Dan Tran <dant...@gmail.com> wrote:
Currently in order for a component to become 1.0, it just
have a Jira project. So far we have a hard time getting
depot to manage this procedure.
Could we just mangen it like the way Jenkins does with
plugin? a component id is just good enough
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
