Alternative bundle on initial import

Is there a way to specify a diferent initial import bundle (zip) for weceem? Now it always reads org.weceem.resources.default-template-space.zip. can I specify an alternative file?

Hi Nestor,

No there isn't yet. Please raise a JIRA for this at http://jira.jcatalog.com

Presumably you would want to configure the name of the default space template in Config.groovy

hi, Did this get implemented? If not, can I replace the .zip file with my own so that if the event of a restart I don't lose the admin data?
Thanks,
Alan

Hi Alan,

I'm afraid this is not yet implemented.

I think if you can put a replaced file with the same name and path on the JVM classpath *before* weceem's classes, then it will load yours.

Please check there is a JIRA for this, and if so, vote for it

My God, I just saw the list of issues - you look like you could do with a hand - anything simple I could tackle to get me up to speed?

Help is always welcome. Try checking out the source and see if anything open takes your fancy.

marcpalmer wrote:Hi Alan,

I'm afraid this is not yet implemented.

I think if you can put a replaced file with the same name and path on the JVM classpath *before* weceem's classes, then it will load yours.

Please check there is a JIRA for this, and if so, vote for it

I never saw a response to this, so I thought I'd let any future readers know that this does appear to work just fine... Which is awesome.

Thanks for the great plugin, I just started using 0.9.2 and really like what I've seen so far!

Hi Chad,

Nice one - thanks for the follow up.

How about voting/commenting on the JIRA as to how you'd like this to work? The issue is here:

http://jira.jcatalog.com/browse/WCM-432

Will do... Just as soon as I verify that what I've done (placed an identically named file in my project's src/groovy/org/weceem/resources package) works consistently in any environment. While I know Java up and down, I'm very new to Grails, so I need to make sure that the behavior I'm seeing when running in IDEA also works in Eclipse, etc.

Chad

This message was edited 1 time. Last update was at 08/11/2010 17:58:18

According to the Grails docs:

Java & Groovy code that the plugin provides within the lib and src/java and src/groovy directories will be compiled into the main project's web-app/WEB-INF/classes directory so that they are made available at runtime.

Can anyone who knows more about Grails confirm that this functionality will avoid clobbering a similarly named File that already exists in the main project (it certainly appears to be case, and is why the above works)?

Chad

Hi Chad,

Any file that is on the java classpath will probably take precedence over any such file inside your application or plugins. This is, I believe, why this "hackaround" works to override the default import zip/

Marc