Re: wro4j grails plugin - where to publish?

[Alex Objelean]

Hi Craig,

first of all, thanks for all the effort you put into updating and publishing the grails plugin.

Regarding the listed options, I don't have a strong preference. I do agree that every new release should be as easy as possible with no special grails expertise required. Otherwise, it most certainly will be outdated at some point in time, unless there is somebody willing to take ownership for maintaining grails plugin. 

I assume that the biggest benefit of getting listed on plugins.grails.org is visibility. If this is true and if there is enough interest in wro4j grails plugin, than most certainly there will be enough people willing to contribute back. As result, changing the grails plugin groupId, shouldn't be a problem. The only suggestion is to apply the groupId rename in a major release (1.7.0 or 2.0.0).

Thanks,

Alex

On Monday, April 29, 2013 7:59:17 PM UTC+3, Craig Andrews wrote:

I'm trying to figure out the best way to publish the wro4j grails plugin.

I believe we have 2 options:
1) Set the groupId to ro.isdc.wro4j and publish the grails plugin to Maven Central along with all the other wro4j artifacts. Grails users add this to their BuildConfig.groovy: compile ":wro4j:1.6.4"
2) Set the groupId to org.grails.plugins, and publish the grails plugin to http://repo.grails.org/ Grails users add this to their BuildConfig.groovy: compile "ro.isdc.wro4j:grails-wro4j:1.6.4"

(1) has a few big advantages - it will ensure that the grails plugin is always up to date, the same process is used for the grails plugin as all the other wro4j artifacts, and the releases will be synchronized. Also, the usual Maven process can be used, so the main wro4j developers/maintainers can keep the Grails plugin up to date and release it, without involving anyone else with special grails knowledge.

(2) has the main advantage of getting the plugin listed on plugins.grails.org.

Since there is no way to publish the plugin to Maven Central, but have it listed on plugins.grails.org (see http://grails.1312388.n4.nabble.com/list-a-plugin-on-plugins-grails-org-that-isn-t-in-the-org-grails-plugins-group-td4644071.html ), we have a decision to make.

As much as I like the idea of the plugin being listed on plugins.grails.org, the additional workflow and complexity of (2) is making me think that (1) is the way to go.

Does anyone have any thoughts on this?

Thanks,
~Craig

[baxx...@gmail.com]

Hi. What the current status of grails plugin? Where it could be released, is there integration with grails resources plugin?

понедельник, 29 апреля 2013 г., 19:59:17 UTC+3 пользователь Craig Andrews написал:

[Alex Objelean]

Though I have little experience with groovy and grails, I'm willing to provide support to contributors willing to publish and/or maintain the grails plugin. 

Regarding the current status, all I can say is that the grails plugin is not published yet and probably Craig could provide more details, since he was the last person who volunteered to work on it.

Regards,

Alex 

[genui...@gmail.com]

I'm not sure if this is closed or is it a WIP. 

I found out that there are new updates appearing on the github project, so I'm guessing the best. :)

Is there any place where we (people that want to move forward the grails plugin) can interact? I'm trying to build a grails 2.3.0.M2 project and it handles Maven dependencies much better than it predecesors.

[Alex Objelean]

Hi,

I'm glad that there are people who are contributing to wro4j grails plugin. I believe that the work is still in progress. Have to check with Craig if anything else has to be done before releasing it. 

Regarding place for interaction for grails contributior, you can use this mailing list, or create your own. I don't mind if it would be developed in maintained by a separate entity. 

I have created the "wro4j" organization on github, which can be used as a host for independent and wro4j related projects, where I can add people willing to maintain and contribute as collaborators. There are more than a single way to achieve that. I'm open to any suggestion.

Cheers,

Alex

[Facundo D]

Excellent. 

I noticed that you created the project and are currently maintaining more and more features.

Also, I found that there is a Travis CI enabled for the entire project. :)

I'll send a new email to the list, commenting on what I'm doing right now.