morph-deploy blows up with gant.TargetMissingPropertyException: No such property: stagingDir for class: _Events

[Jacek Laskowski]

Hi,

(resending from a proper email address - sorry for a possible duplicate)

Just gave morph-deploy a shot and it blew up with
"gant.TargetMissingPropertyException: No such property: stagingDir for
class: _Events". It is in
plugins\morph-deploy-0.1\scripts\_Events.groovy where stagingDir is
needed, but it turns out that it's never initialized. Besides, the
step to remove jdbc2_0-stdext.jar is not longer valid, I believe.
Shall I report an issue in a JIRA to not let the issue fall through
the cracks? Where?

Jacek

--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

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

    http://xircles.codehaus.org/manage_email

[Marc Palmer Local]

On 12 Mar 2009, at 09:36, Jacek Laskowski wrote:

> Hi,
>
> (resending from a proper email address - sorry for a possible  
> duplicate)
>
> Just gave morph-deploy a shot and it blew up with
> "gant.TargetMissingPropertyException: No such property: stagingDir for
> class: _Events". It is in
> plugins\morph-deploy-0.1\scripts\_Events.groovy where stagingDir is
> needed, but it turns out that it's never initialized. Besides, the
> step to remove jdbc2_0-stdext.jar is not longer valid, I believe.
> Shall I report an issue in a JIRA to not let the issue fall through
> the cracks? Where?

Yes it needs fixing for 1.1 due to breaking changes in the event  
handling for WARs.

I'll try to do it at some point today, depending on workload

Marc

~ ~ ~
Marc Palmer
Blog         > http://www.anyware.co.uk
Twitter      > http://twitter.com/wangjammer5
Grails Rocks > http://www.grailsrocks.com







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

    http://xircles.codehaus.org/manage_email

[Jacek Laskowski]

On Thu, Mar 12, 2009 at 11:33 AM, Marc Palmer <marc@...> wrote:

> I'll try to do it at some point today, depending on workload

Just remove _Events.groovy and it should do the trick. It worked fine
for me and let me deploy my first Grails app to Mor.ph.

Jacek

--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

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

    http://xircles.codehaus.org/manage_email

[Marc Palmer Local]

On 12 Mar 2009, at 10:41, Jacek Laskowski wrote:

> On Thu, Mar 12, 2009 at 11:33 AM, Marc Palmer <marc@...>  
> wrote:
>
>> I'll try to do it at some point today, depending on workload
>
> Just remove _Events.groovy and it should do the trick. It worked fine
> for me and let me deploy my first Grails app to Mor.ph.
>
>

It shouldn't work properly once deployed - it needs to remove some jar  
files to prevent conflicts with Morph. Unless Morph have changed their  
setup since.

~ ~ ~
Marc Palmer
Blog         > http://www.anyware.co.uk
Twitter      > http://twitter.com/wangjammer5
Grails Rocks > http://www.grailsrocks.com







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

    http://xircles.codehaus.org/manage_email

[Jacek Laskowski]

On Thu, Mar 12, 2009 at 4:10 PM, Marc Palmer <marc@...> wrote:

> It shouldn't work properly once deployed - it needs to remove some jar files
> to prevent conflicts with Morph. Unless Morph have changed their setup
> since.

Grails has. The conflicting jar file is not included in the war.

Jacek

--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

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

    http://xircles.codehaus.org/manage_email

[MarkAtHarvest]

Is there a workaround, if I need to use _Events.groovy for omitting the unwanted jar dependancies.. its makes building wars so easy.

Jacek Laskowski wrote:

On Thu, Mar 12, 2009 at 4:10 PM, Marc Palmer <[e-mail]> wrote:

> It shouldn't work properly once deployed - it needs to remove some jar files
> to prevent conflicts with Morph. Unless Morph have changed their setup
> since.

Grails has. The conflicting jar file is not included in the war.

Jacek

--
Jacek Laskowski
Notatnik Projektanta Java EE - http://www.JacekLaskowski.pl

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

    http://xircles.codehaus.org/manage_email

[Marc Palmer Local]

On 6 Apr 2009, at 11:48, MarkAtHarvest wrote:

>
> Is there a workaround, if I need to use _Events.groovy for omitting  
> the
> unwanted jar dependancies.. its makes building wars so easy.


The morph-deploy in svn trunk works with Grails 1.1 and 1.0.4 and  
excludes these files.

Marc

~ ~ ~
Marc Palmer
Blog         > http://www.anyware.co.uk
Twitter      > http://twitter.com/wangjammer5
Grails Rocks > http://www.grailsrocks.com







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

    http://xircles.codehaus.org/manage_email

[MarkAtHarvest]

Thanks Marc, but
I want to generate war files for my own Tomcat, not for Morph.
I tried to both putting it in config.groovy as mentioned and _Events.groovy, but none of them seem to work, to eliminate the jar files I do not need.
Currently, the work around is I am doin it manually.

Marc Palmer Local wrote:

On 6 Apr 2009, at 11:48, MarkAtHarvest wrote:

>
> Is there a workaround, if I need to use _Events.groovy for omitting  
> the
> unwanted jar dependancies.. its makes building wars so easy.


The morph-deploy in svn trunk works with Grails 1.1 and 1.0.4 and  
excludes these files.

Marc

~ ~ ~
Marc Palmer
Blog         > http://www.anyware.co.uk
Twitter      > http://twitter.com/wangjammer5
Grails Rocks > http://www.grailsrocks.com







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

    http://xircles.codehaus.org/manage_email