|
Hello Peter and all Grails folk,
We (3.musket33rs team) would like to publish 2 new grails plugins: html5-mobile-scaffolding and jsonp documentation could be found at: http://3musket33rs.github.com/html5-mobile-scaffolding/ source code on github at: https://github.com/3musket33rs/html5-mobile-scaffolding https://github.com/3musket33rs/jsonp/ Html5-mobile-scaffolding plugin has a dependency on jsonp plugin. Our grails username is 3musket33rs. Cheers, Athos alias Corinne. http://3musket33rs.github.com |
|
> documentation could be found at:
> http://3musket33rs.github.com/html5-mobile-scaffolding/ > > source code on github at: > https://github.com/3musket33rs/html5-mobile-scaffolding > https://github.com/3musket33rs/jsonp/ > > Html5-mobile-scaffolding plugin has a dependency on jsonp plugin. > > Our grails username is 3musket33rs. Approved. Thanks for the contribution! You may need to do a bit of a hack to publish, because MIT is not currently in the list of known licenses: https://github.com/grails-plugins/grails-release/blob/master/scripts/_GrailsMaven.groovy#L31 You can modify that in the installed plugin, but a pull request would be great! Alternatively, create an _Events.groovy script in the plugin and include the code: eventGeneratePomStart = { globalLicenses["MIT"] = [name: "...", url: "..."] } And for any others reading this, suggestions for making the list of licenses more easily extensible would be appreciated. Or even contributions of other licenses! Thanks, Peter -- Peter Ledbrook Grails Advocate SpringSource - A Division of VMware --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Looking at the code you linked, it seems like it would be relatively trivial to add the ability for the plugin developer to specify a licences in the model you're following with "globalLicenses". Would you like me to submit a pull request to show you what I mean, or does it make sense by itself?
I'd just like to make sure there aren't any problems with this approach before coding it up. Nathan Wells On Tue, Jul 31, 2012 at 2:54 AM, Peter Ledbrook <[hidden email]> wrote:
|
|
Also, I'll voluteer to make a pull request for the following licenses:
BSD2 BSD3 EPL MPL AGPL LGPL-2.1 LGPL-3 MIT This is a small subset of open source licenses endorsed by OSI. The full list is here: Nathan Wells On Tue, Jul 31, 2012 at 3:16 AM, Nathan Wells <[hidden email]> wrote: Looking at the code you linked, it seems like it would be relatively trivial to add the ability for the plugin developer to specify a licences in the model you're following with "globalLicenses". Would you like me to submit a pull request to show you what I mean, or does it make sense by itself? |
|
In reply to this post by Nathan Wells
> Looking at the code you linked, it seems like it would be relatively trivial
> to add the ability for the plugin developer to specify a licences in the > model you're following with "globalLicenses". Would you like me to submit a > pull request to show you what I mean, or does it make sense by itself? > > I'd just like to make sure there aren't any problems with this approach > before coding it up. Pull requests would be good. Any follow-up can be discussed on the pull request itself. Thanks, Peter -- Peter Ledbrook Grails Advocate SpringSource - A Division of VMware --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Hi Peter,
Thanks for the quick approval, I should be able to announce the release of the plugins today at the Gr8Conf, I will check with my the other 3musket33rs members why they choose for this licence.
Seb On Tue, Jul 31, 2012 at 5:06 AM, Peter Ledbrook <[hidden email]> wrote:
|
|
Peter,
I've submitted the pull request for custom licenses. Nathan Wells On Tue, Jul 31, 2012 at 5:30 AM, Sebastien Blanc <[hidden email]> wrote: Hi Peter, |
|
> I've submitted the pull request for custom licenses.
Thanks. I'd always meant to add support for the map syntax on 'license', but never got round to it. Peter -- Peter Ledbrook Grails Advocate SpringSource - A Division of VMware --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
In reply to this post by 3musket33rs
Hello Peter,
Could you grant publish for jsonp plugin too as html5-mobile-scaffolding is dependent on this jsonp. Cheers, Cheers, Athos alias Corinne. http://3musket33rs.github.com On Mon, Jul 30, 2012 at 10:18 PM, 3 musket33rs <[hidden email]> wrote: Hello Peter and all Grails folk, |
|
> Could you grant publish for jsonp plugin too as html5-mobile-scaffolding is
> dependent on this jsonp. You already have permission for this. Is it not working? What error message are you seeing? Peter -- Peter Ledbrook Grails Advocate SpringSource - A Division of VMware --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
Hello Peter
I managed to publish htm5-mocbile-scaffolding without problem but when trying json it prompts me to enter a svn username. ~/workspace/jsonp$ grails publish-plugin ---no-scm | Plugin packaged grails-jsonp-0.1.zip | Plugin packaged grails-jsonp-0.1.zip | POM generated: /home/fabrice/workspace/jsonp/target/pom.xml > Enter extra commit message text for this release (optional): ff > Project is not under source control. Do you want to import it now? (Y,n) n Publishing to Grails Central Creating path 'grails-jsonp/trunk' in the repository > Enter your Subversion username: Something I'm doing wrong? Cheers, Corinne On Thu, Aug 2, 2012 at 10:02 AM, Peter Ledbrook <[hidden email]> wrote:
|
|
If you're seeing anything to do with svn you're using the wrong version of the release plugin.
Your code on Github ( https://github.com/3musket33rs/jsonp/blob/master/grails-app/conf/BuildConfig.groovy ) has a dependency on v1.0.0 and an unnecessary declaration of the Tomcat plugin. Use this in BuildConfig.groovy: plugins { build(':release:2.0.4', ':rest-client-builder:1.0.2') { export = false } } By explicitly depending on the release plugin's rest-client-builder dependency but excluding them both with export=false you keep the rest-client-builder plugin from leaking into the containing app's dependencies. Burt
|
|
I sent a pull request with this fixed and some other cleanup.
Burt
|
|
Hello Burt
Thanks for your pull request. I merged it and I was able to publish. Every thing is ok But one thing I don't understand is why should I have a dependency on the rest-client-builder? Athos alias Corinne 3musket33rs On 8/5/12, burtbeckwith <[hidden email]> wrote: > I sent a pull request with this fixed and some other cleanup. > > Burt > > > burtbeckwith wrote >> >> If you're seeing anything to do with svn you're using the wrong version >> of >> the release plugin. >> >> Your code on Github ( >> https://github.com/3musket33rs/jsonp/blob/master/grails-app/conf/BuildConfig.groovy >> ) has a dependency on v1.0.0 and an unnecessary declaration of the Tomcat >> plugin. >> >> Use this in BuildConfig.groovy: >> >> plugins { >> build(':release:2.0.4', ':rest-client-builder:1.0.2') { >> export = false >> } >> } >> >> By explicitly depending on the release plugin's rest-client-builder >> dependency but excluding them both with export=false you keep the >> rest-client-builder plugin from leaking into the containing app's >> dependencies. >> >> Burt >> >> >> 3musket33rs wrote >>> >>> Hello Peter >>> >>> I managed to publish htm5-mocbile-scaffolding without problem but when >>> trying json it prompts me to enter a svn username. >>> >>> ~/workspace/jsonp$ grails publish-plugin ---no-scm >>> | Plugin packaged grails-jsonp-0.1.zip >>> | Plugin packaged grails-jsonp-0.1.zip >>> | POM generated: /home/fabrice/workspace/jsonp/target/pom.xml >>>> Enter extra commit message text for this release (optional): ff >>>> Project is not under source control. Do you want to import it now? >>>> (Y,n) >>>> n >>> Publishing to Grails Central >>> Creating path 'grails-jsonp/trunk' in the repository >>>> Enter your Subversion username: >>> >>> >>> Something I'm doing wrong? >>> >>> Cheers, >>> Corinne >>> >> > > > > > -- > View this message in context: > http://grails.1312388.n4.nabble.com/Publication-of-html5-mobile-scaffolding-plugin-and-jsonp-plugin-tp4632422p4632723.html > Sent from the Grails - dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
|
That's because of a Grails bug. The release plugin depends on rest-client-builder but export=false for just the release plugin won't keep the rest-client-builder plugin from being exported - applications that install the plugin would end up with rest-client-builder installed. By adding the same dependency and explicitly excluding it, both get excluded.
Burt
|
| Powered by Nabble | Edit this page |
