Quantcast

FAO Plugin Authors - Important changes to plugin publication

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

FAO Plugin Authors - Important changes to plugin publication

pledbrook
Hi everyone,

As part of our continued efforts to improve the Grails plugin
infrastructure, we will be moving all existing plugins to our
Artifactory repository and making the existing Subversion repository
read-only. This move will be transparent for end users, but it will
have a significant impact on plugin authors.

First, let me explain what that effect will be. Since the Subversion
repository will be made read-only, you will not be able to store
plugin source code in svn.codehaus.org/grails-plugins. We recommend
you move all plugins to alternative code repositories such as GitHub
or Google Code. This will also mean you can't publish direct to the
Subversion Repository. In other words:

    the release-plugin command and all existing versions of the
Release plugin will cease to work!

Unfortunately, even configuration changes won't get previous versions
of the Release plugin working because the publication mechanism has
changed completely. There are very good reasons for this, but it does
mean some disruption for plugin authors.

Once the transition has happened, you will have to upgrade to the
latest Release plugin and publish all future versions of your plugins
using that. Don't worry though, the publish-plugin command remains the
same and all your existing configuration settings will work as before.
As an added bonus, you will only require your grails.org credentials
for publishing plugins.

You will also have to request permission to publish plugins that you
own or that you're a team member for. Simply send an email to the
developer mailing list ( [hidden email] ) quoting the name(s)
of the plugin(s) and your grails.org username. You can do this at any
time - even now if you want! The earlier the better. You will also
have to change your current 'grailsCentral' username and password to
the ones for grails.org (since publishing will happen via
http://grails.org/ ).

Now for the why. The Subversion repository has served us well for some
time, but it is limiting what we can now do. For a start, it's not
possible to restrict who can publish what plugins. In addition, the
time taken to publish a plugin has become too long. Finally, far more
of the Java ecosystem works with Maven-compatible repositories than it
does with Grails ones. Simply by switching to an Artifactory
repository, Maven users gain access to all published plugins. In
addition, because we publish via grails.org now, we have a lot of
potential to do clever things and integrate publishing more closely
with the plugin portal.

We apologise for the inevitable disruption this will cause, but we
hope you'll understand how important this change is. To summarise, the
only actions that you need to take are:

(before the transition)
1. send your grails.org username and a list of the plugins you wish to
publish in an email to the Grails dev mailing list;

(after the transition)
2. move your source code out of svn.codehaus.org if you haven't
already done that;
3. upgrade to the new version of the Release plugin (2.0.0); and
4. change your grailsCentral repo credentials to your grails.org ones.

Thanks for your patience and we welcome any questions or feedback you have.

Regards,

The Grails Team

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

Graeme Rocher-4
Administrator
Following up on this. The migrated repository is now live:

http://repo.grails.org/grails/plugins-releases-local/org/grails/plugins/

We will have to re-publish plugins published between now and the time
when SVN goes read-only (probably next week)

We are still testing things out. If you want to try it out yourself
then you can use the following repository definition in your Grails
application:

grailsRepo "http://grails.org/plugins"

Currently the only known issue is that plugin-info is not working, I
am working to fix this.

Stand by for further updates

Cheers

On Tue, Mar 13, 2012 at 5:32 PM, Peter Ledbrook <[hidden email]> wrote:

> Hi everyone,
>
> As part of our continued efforts to improve the Grails plugin
> infrastructure, we will be moving all existing plugins to our
> Artifactory repository and making the existing Subversion repository
> read-only. This move will be transparent for end users, but it will
> have a significant impact on plugin authors.
>
> First, let me explain what that effect will be. Since the Subversion
> repository will be made read-only, you will not be able to store
> plugin source code in svn.codehaus.org/grails-plugins. We recommend
> you move all plugins to alternative code repositories such as GitHub
> or Google Code. This will also mean you can't publish direct to the
> Subversion Repository. In other words:
>
>    the release-plugin command and all existing versions of the
> Release plugin will cease to work!
>
> Unfortunately, even configuration changes won't get previous versions
> of the Release plugin working because the publication mechanism has
> changed completely. There are very good reasons for this, but it does
> mean some disruption for plugin authors.
>
> Once the transition has happened, you will have to upgrade to the
> latest Release plugin and publish all future versions of your plugins
> using that. Don't worry though, the publish-plugin command remains the
> same and all your existing configuration settings will work as before.
> As an added bonus, you will only require your grails.org credentials
> for publishing plugins.
>
> You will also have to request permission to publish plugins that you
> own or that you're a team member for. Simply send an email to the
> developer mailing list ( [hidden email] ) quoting the name(s)
> of the plugin(s) and your grails.org username. You can do this at any
> time - even now if you want! The earlier the better. You will also
> have to change your current 'grailsCentral' username and password to
> the ones for grails.org (since publishing will happen via
> http://grails.org/ ).
>
> Now for the why. The Subversion repository has served us well for some
> time, but it is limiting what we can now do. For a start, it's not
> possible to restrict who can publish what plugins. In addition, the
> time taken to publish a plugin has become too long. Finally, far more
> of the Java ecosystem works with Maven-compatible repositories than it
> does with Grails ones. Simply by switching to an Artifactory
> repository, Maven users gain access to all published plugins. In
> addition, because we publish via grails.org now, we have a lot of
> potential to do clever things and integrate publishing more closely
> with the plugin portal.
>
> We apologise for the inevitable disruption this will cause, but we
> hope you'll understand how important this change is. To summarise, the
> only actions that you need to take are:
>
> (before the transition)
> 1. send your grails.org username and a list of the plugins you wish to
> publish in an email to the Grails dev mailing list;
>
> (after the transition)
> 2. move your source code out of svn.codehaus.org if you haven't
> already done that;
> 3. upgrade to the new version of the Release plugin (2.0.0); and
> 4. change your grailsCentral repo credentials to your grails.org ones.
>
> Thanks for your patience and we welcome any questions or feedback you have.
>
> Regards,
>
> The Grails Team
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>



--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

houbie
Graeme Rocher-4 wrote
Following up on this. The migrated repository is now live:

http://repo.grails.org/grails/plugins-releases-local/org/grails/plugins/
I assume we can now also publish binary versions op plugins?
Using only binary plugins could speed up compilation significantly.

Grtz,
Ivo
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Plugin Publication

Martin Hauner
In reply to this post by pledbrook
user:   hauner
plugin: http://grails.org/plugin/cucumber

--
Martin


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

pledbrook
In reply to this post by houbie
> I assume we can now also publish binary versions op plugins?
> Using only binary plugins could speed up compilation significantly.

Yes, but plugins built and published with Grails 2 won't work with
earlier versions of Grails due to binary incompatibilities.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plugin Publication

Graeme Rocher-4
Administrator
In reply to this post by Martin Hauner
Done

On Wed, Mar 14, 2012 at 10:06 PM, Martin Hauner <[hidden email]> wrote:

> user:   hauner
> plugin: http://grails.org/plugin/cucumber
>
> --
> Martin
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>



--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

houbie
In reply to this post by pledbrook

On 15 Mar 2012, at 11:57, Peter Ledbrook wrote:

>> I assume we can now also publish binary versions op plugins?
>> Using only binary plugins could speed up compilation significantly.
>
> Yes, but plugins built and published with Grails 2 won't work with
> earlier versions of Grails due to binary incompatibilities.

I know, but I was thinking about releasing a grails 2 version of some of my plugins


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

Jörg Rech
In reply to this post by pledbrook
Hi,
  as you are changing the Grails Plugin infrastructure: will there
still be a XML-based list of all plugins (e.g.,
http://plugins.grails.org/.plugin-meta/plugins-list.xml) after the
change? I was wondering as I'm building an App configurator which
requires a (up-to-date) list of plugins and I'm currently using the
plugins-list.xml one.

Best regards,
Joerg

On Tue, Mar 13, 2012 at 17:32, Peter Ledbrook <[hidden email]> wrote:

> Hi everyone,
>
> As part of our continued efforts to improve the Grails plugin
> infrastructure, we will be moving all existing plugins to our
> Artifactory repository and making the existing Subversion repository
> read-only. This move will be transparent for end users, but it will
> have a significant impact on plugin authors.
>
> First, let me explain what that effect will be. Since the Subversion
> repository will be made read-only, you will not be able to store
> plugin source code in svn.codehaus.org/grails-plugins. We recommend
> you move all plugins to alternative code repositories such as GitHub
> or Google Code. This will also mean you can't publish direct to the
> Subversion Repository. In other words:
>
>    the release-plugin command and all existing versions of the
> Release plugin will cease to work!
>
> Unfortunately, even configuration changes won't get previous versions
> of the Release plugin working because the publication mechanism has
> changed completely. There are very good reasons for this, but it does
> mean some disruption for plugin authors.
>
> Once the transition has happened, you will have to upgrade to the
> latest Release plugin and publish all future versions of your plugins
> using that. Don't worry though, the publish-plugin command remains the
> same and all your existing configuration settings will work as before.
> As an added bonus, you will only require your grails.org credentials
> for publishing plugins.
>
> You will also have to request permission to publish plugins that you
> own or that you're a team member for. Simply send an email to the
> developer mailing list ( [hidden email] ) quoting the name(s)
> of the plugin(s) and your grails.org username. You can do this at any
> time - even now if you want! The earlier the better. You will also
> have to change your current 'grailsCentral' username and password to
> the ones for grails.org (since publishing will happen via
> http://grails.org/ ).
>
> Now for the why. The Subversion repository has served us well for some
> time, but it is limiting what we can now do. For a start, it's not
> possible to restrict who can publish what plugins. In addition, the
> time taken to publish a plugin has become too long. Finally, far more
> of the Java ecosystem works with Maven-compatible repositories than it
> does with Grails ones. Simply by switching to an Artifactory
> repository, Maven users gain access to all published plugins. In
> addition, because we publish via grails.org now, we have a lot of
> potential to do clever things and integrate publishing more closely
> with the plugin portal.
>
> We apologise for the inevitable disruption this will cause, but we
> hope you'll understand how important this change is. To summarise, the
> only actions that you need to take are:
>
> (before the transition)
> 1. send your grails.org username and a list of the plugins you wish to
> publish in an email to the Grails dev mailing list;
>
> (after the transition)
> 2. move your source code out of svn.codehaus.org if you haven't
> already done that;
> 3. upgrade to the new version of the Release plugin (2.0.0); and
> 4. change your grailsCentral repo credentials to your grails.org ones.
>
> Thanks for your patience and we welcome any questions or feedback you have.
>
> Regards,
>
> The Grails Team
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>



--
Dr. Jörg Rech
Kriegsstr. 164
76133 Karlsruhe, Germany

E-Mail:  [hidden email]
Twitter:  http://twitter.com/joergrech
Web:  http://www.joerg-rech.com
Xing: http://www.xing.com/profile/Joerg_Rech/
LinkedIn: http://www.linkedin.com/in/joergrech

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

Graeme Rocher-4
Administrator
Yes it will still exist

Cheers

On Fri, Mar 16, 2012 at 3:57 PM, Jörg Rech <[hidden email]> wrote:

> Hi,
>  as you are changing the Grails Plugin infrastructure: will there
> still be a XML-based list of all plugins (e.g.,
> http://plugins.grails.org/.plugin-meta/plugins-list.xml) after the
> change? I was wondering as I'm building an App configurator which
> requires a (up-to-date) list of plugins and I'm currently using the
> plugins-list.xml one.
>
> Best regards,
> Joerg
>
> On Tue, Mar 13, 2012 at 17:32, Peter Ledbrook <[hidden email]> wrote:
>> Hi everyone,
>>
>> As part of our continued efforts to improve the Grails plugin
>> infrastructure, we will be moving all existing plugins to our
>> Artifactory repository and making the existing Subversion repository
>> read-only. This move will be transparent for end users, but it will
>> have a significant impact on plugin authors.
>>
>> First, let me explain what that effect will be. Since the Subversion
>> repository will be made read-only, you will not be able to store
>> plugin source code in svn.codehaus.org/grails-plugins. We recommend
>> you move all plugins to alternative code repositories such as GitHub
>> or Google Code. This will also mean you can't publish direct to the
>> Subversion Repository. In other words:
>>
>>    the release-plugin command and all existing versions of the
>> Release plugin will cease to work!
>>
>> Unfortunately, even configuration changes won't get previous versions
>> of the Release plugin working because the publication mechanism has
>> changed completely. There are very good reasons for this, but it does
>> mean some disruption for plugin authors.
>>
>> Once the transition has happened, you will have to upgrade to the
>> latest Release plugin and publish all future versions of your plugins
>> using that. Don't worry though, the publish-plugin command remains the
>> same and all your existing configuration settings will work as before.
>> As an added bonus, you will only require your grails.org credentials
>> for publishing plugins.
>>
>> You will also have to request permission to publish plugins that you
>> own or that you're a team member for. Simply send an email to the
>> developer mailing list ( [hidden email] ) quoting the name(s)
>> of the plugin(s) and your grails.org username. You can do this at any
>> time - even now if you want! The earlier the better. You will also
>> have to change your current 'grailsCentral' username and password to
>> the ones for grails.org (since publishing will happen via
>> http://grails.org/ ).
>>
>> Now for the why. The Subversion repository has served us well for some
>> time, but it is limiting what we can now do. For a start, it's not
>> possible to restrict who can publish what plugins. In addition, the
>> time taken to publish a plugin has become too long. Finally, far more
>> of the Java ecosystem works with Maven-compatible repositories than it
>> does with Grails ones. Simply by switching to an Artifactory
>> repository, Maven users gain access to all published plugins. In
>> addition, because we publish via grails.org now, we have a lot of
>> potential to do clever things and integrate publishing more closely
>> with the plugin portal.
>>
>> We apologise for the inevitable disruption this will cause, but we
>> hope you'll understand how important this change is. To summarise, the
>> only actions that you need to take are:
>>
>> (before the transition)
>> 1. send your grails.org username and a list of the plugins you wish to
>> publish in an email to the Grails dev mailing list;
>>
>> (after the transition)
>> 2. move your source code out of svn.codehaus.org if you haven't
>> already done that;
>> 3. upgrade to the new version of the Release plugin (2.0.0); and
>> 4. change your grailsCentral repo credentials to your grails.org ones.
>>
>> Thanks for your patience and we welcome any questions or feedback you have.
>>
>> Regards,
>>
>> The Grails Team
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> Dr. Jörg Rech
> Kriegsstr. 164
> 76133 Karlsruhe, Germany
>
> E-Mail:  [hidden email]
> Twitter:  http://twitter.com/joergrech
> Web:  http://www.joerg-rech.com
> Xing: http://www.xing.com/profile/Joerg_Rech/
> LinkedIn: http://www.linkedin.com/in/joergrech
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>



--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

Matthias Hryniszak
What about the creation of new plugins? Until now it was just a matter of logging in to grails.org, navigating to the non-existent plugin site, filling in the details and releasing the actual plugin (obviously once you've been given publishing rights). Is this process going to change?

Matthias

2012/3/16 Graeme Rocher <[hidden email]>
Yes it will still exist

Cheers

On Fri, Mar 16, 2012 at 3:57 PM, Jörg Rech <[hidden email]> wrote:
> Hi,
>  as you are changing the Grails Plugin infrastructure: will there
> still be a XML-based list of all plugins (e.g.,
> http://plugins.grails.org/.plugin-meta/plugins-list.xml) after the
> change? I was wondering as I'm building an App configurator which
> requires a (up-to-date) list of plugins and I'm currently using the
> plugins-list.xml one.
>
> Best regards,
> Joerg
>
> On Tue, Mar 13, 2012 at 17:32, Peter Ledbrook <[hidden email]> wrote:
>> Hi everyone,
>>
>> As part of our continued efforts to improve the Grails plugin
>> infrastructure, we will be moving all existing plugins to our
>> Artifactory repository and making the existing Subversion repository
>> read-only. This move will be transparent for end users, but it will
>> have a significant impact on plugin authors.
>>
>> First, let me explain what that effect will be. Since the Subversion
>> repository will be made read-only, you will not be able to store
>> plugin source code in svn.codehaus.org/grails-plugins. We recommend
>> you move all plugins to alternative code repositories such as GitHub
>> or Google Code. This will also mean you can't publish direct to the
>> Subversion Repository. In other words:
>>
>>    the release-plugin command and all existing versions of the
>> Release plugin will cease to work!
>>
>> Unfortunately, even configuration changes won't get previous versions
>> of the Release plugin working because the publication mechanism has
>> changed completely. There are very good reasons for this, but it does
>> mean some disruption for plugin authors.
>>
>> Once the transition has happened, you will have to upgrade to the
>> latest Release plugin and publish all future versions of your plugins
>> using that. Don't worry though, the publish-plugin command remains the
>> same and all your existing configuration settings will work as before.
>> As an added bonus, you will only require your grails.org credentials
>> for publishing plugins.
>>
>> You will also have to request permission to publish plugins that you
>> own or that you're a team member for. Simply send an email to the
>> developer mailing list ( [hidden email] ) quoting the name(s)
>> of the plugin(s) and your grails.org username. You can do this at any
>> time - even now if you want! The earlier the better. You will also
>> have to change your current 'grailsCentral' username and password to
>> the ones for grails.org (since publishing will happen via
>> http://grails.org/ ).
>>
>> Now for the why. The Subversion repository has served us well for some
>> time, but it is limiting what we can now do. For a start, it's not
>> possible to restrict who can publish what plugins. In addition, the
>> time taken to publish a plugin has become too long. Finally, far more
>> of the Java ecosystem works with Maven-compatible repositories than it
>> does with Grails ones. Simply by switching to an Artifactory
>> repository, Maven users gain access to all published plugins. In
>> addition, because we publish via grails.org now, we have a lot of
>> potential to do clever things and integrate publishing more closely
>> with the plugin portal.
>>
>> We apologise for the inevitable disruption this will cause, but we
>> hope you'll understand how important this change is. To summarise, the
>> only actions that you need to take are:
>>
>> (before the transition)
>> 1. send your grails.org username and a list of the plugins you wish to
>> publish in an email to the Grails dev mailing list;
>>
>> (after the transition)
>> 2. move your source code out of svn.codehaus.org if you haven't
>> already done that;
>> 3. upgrade to the new version of the Release plugin (2.0.0); and
>> 4. change your grailsCentral repo credentials to your grails.org ones.
>>
>> Thanks for your patience and we welcome any questions or feedback you have.
>>
>> Regards,
>>
>> The Grails Team
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>
>
>
> --
> Dr. Jörg Rech
> Kriegsstr. 164
> 76133 Karlsruhe, Germany
>
> E-Mail:  [hidden email]
> Twitter:  http://twitter.com/joergrech
> Web:  http://www.joerg-rech.com
> Xing: http://www.xing.com/profile/Joerg_Rech/
> LinkedIn: http://www.linkedin.com/in/joergrech
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>



--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

Graeme Rocher-4
Administrator
No the process is the same

Cheers

On Fri, Mar 16, 2012 at 9:53 PM, Matthias Hryniszak <[hidden email]> wrote:

> What about the creation of new plugins? Until now it was just a matter of
> logging in to grails.org, navigating to the non-existent plugin site,
> filling in the details and releasing the actual plugin (obviously once
> you've been given publishing rights). Is this process going to change?
>
> Matthias
>
>
> 2012/3/16 Graeme Rocher <[hidden email]>
>>
>> Yes it will still exist
>>
>> Cheers
>>
>> On Fri, Mar 16, 2012 at 3:57 PM, Jörg Rech <[hidden email]> wrote:
>> > Hi,
>> >  as you are changing the Grails Plugin infrastructure: will there
>> > still be a XML-based list of all plugins (e.g.,
>> > http://plugins.grails.org/.plugin-meta/plugins-list.xml) after the
>> > change? I was wondering as I'm building an App configurator which
>> > requires a (up-to-date) list of plugins and I'm currently using the
>> > plugins-list.xml one.
>> >
>> > Best regards,
>> > Joerg
>> >
>> > On Tue, Mar 13, 2012 at 17:32, Peter Ledbrook <[hidden email]>
>> > wrote:
>> >> Hi everyone,
>> >>
>> >> As part of our continued efforts to improve the Grails plugin
>> >> infrastructure, we will be moving all existing plugins to our
>> >> Artifactory repository and making the existing Subversion repository
>> >> read-only. This move will be transparent for end users, but it will
>> >> have a significant impact on plugin authors.
>> >>
>> >> First, let me explain what that effect will be. Since the Subversion
>> >> repository will be made read-only, you will not be able to store
>> >> plugin source code in svn.codehaus.org/grails-plugins. We recommend
>> >> you move all plugins to alternative code repositories such as GitHub
>> >> or Google Code. This will also mean you can't publish direct to the
>> >> Subversion Repository. In other words:
>> >>
>> >>    the release-plugin command and all existing versions of the
>> >> Release plugin will cease to work!
>> >>
>> >> Unfortunately, even configuration changes won't get previous versions
>> >> of the Release plugin working because the publication mechanism has
>> >> changed completely. There are very good reasons for this, but it does
>> >> mean some disruption for plugin authors.
>> >>
>> >> Once the transition has happened, you will have to upgrade to the
>> >> latest Release plugin and publish all future versions of your plugins
>> >> using that. Don't worry though, the publish-plugin command remains the
>> >> same and all your existing configuration settings will work as before.
>> >> As an added bonus, you will only require your grails.org credentials
>> >> for publishing plugins.
>> >>
>> >> You will also have to request permission to publish plugins that you
>> >> own or that you're a team member for. Simply send an email to the
>> >> developer mailing list ( [hidden email] ) quoting the name(s)
>> >> of the plugin(s) and your grails.org username. You can do this at any
>> >> time - even now if you want! The earlier the better. You will also
>> >> have to change your current 'grailsCentral' username and password to
>> >> the ones for grails.org (since publishing will happen via
>> >> http://grails.org/ ).
>> >>
>> >> Now for the why. The Subversion repository has served us well for some
>> >> time, but it is limiting what we can now do. For a start, it's not
>> >> possible to restrict who can publish what plugins. In addition, the
>> >> time taken to publish a plugin has become too long. Finally, far more
>> >> of the Java ecosystem works with Maven-compatible repositories than it
>> >> does with Grails ones. Simply by switching to an Artifactory
>> >> repository, Maven users gain access to all published plugins. In
>> >> addition, because we publish via grails.org now, we have a lot of
>> >> potential to do clever things and integrate publishing more closely
>> >> with the plugin portal.
>> >>
>> >> We apologise for the inevitable disruption this will cause, but we
>> >> hope you'll understand how important this change is. To summarise, the
>> >> only actions that you need to take are:
>> >>
>> >> (before the transition)
>> >> 1. send your grails.org username and a list of the plugins you wish to
>> >> publish in an email to the Grails dev mailing list;
>> >>
>> >> (after the transition)
>> >> 2. move your source code out of svn.codehaus.org if you haven't
>> >> already done that;
>> >> 3. upgrade to the new version of the Release plugin (2.0.0); and
>> >> 4. change your grailsCentral repo credentials to your grails.org ones.
>> >>
>> >> Thanks for your patience and we welcome any questions or feedback you
>> >> have.
>> >>
>> >> Regards,
>> >>
>> >> The Grails Team
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe from this list, please visit:
>> >>
>> >>    http://xircles.codehaus.org/manage_email
>> >>
>> >>
>> >
>> >
>> >
>> > --
>> > Dr. Jörg Rech
>> > Kriegsstr. 164
>> > 76133 Karlsruhe, Germany
>> >
>> > E-Mail:  [hidden email]
>> > Twitter:  http://twitter.com/joergrech
>> > Web:  http://www.joerg-rech.com
>> > Xing: http://www.xing.com/profile/Joerg_Rech/
>> > LinkedIn: http://www.linkedin.com/in/joergrech
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe from this list, please visit:
>> >
>> >    http://xircles.codehaus.org/manage_email
>> >
>> >
>>
>>
>>
>> --
>> Graeme Rocher
>> Grails Project Lead
>> SpringSource - A Division of VMware
>> http://www.springsource.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>>    http://xircles.codehaus.org/manage_email
>>
>>
>



--
Graeme Rocher
Grails Project Lead
SpringSource - A Division of VMware
http://www.springsource.com

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

pledbrook
In reply to this post by Matthias Hryniszak
> What about the creation of new plugins? Until now it was just a matter of
> logging in to grails.org, navigating to the non-existent plugin site,
> filling in the details and releasing the actual plugin (obviously once
> you've been given publishing rights). Is this process going to change?

You don't have to manually create the page in grails.org if you
publish your plugin using the Release plugin. The page will be created
and populated automatically.

Peter

--
Peter Ledbrook
Grails Advocate
SpringSource - A Division of VMware

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: FAO Plugin Authors - Important changes to plugin publication

Paolo DiCanio
This post has NOT been accepted by the mailing list yet.
Once we've moved the code to a new repo can we then remove all MYPLUGIN-VERSION.zip files from the source repo?
Loading...