Started to play with tomcat plugin sources in order to make a minimal resin plugin working...It sucks when there is no plugin development documentation. Did I miss something?
No, you didn't miss anything, there is really almost no documentation, just the plugin examples and a lot of try and error... :(
unika wrote:
Started to play with tomcat plugin sources in order to make a minimal resin plugin working...It sucks when there is no plugin development documentation. Did I miss something?
Started to play with tomcat plugin sources in order to make a minimal resin plugin working...It sucks when there is no plugin development documentation. Did I miss something?
I know. Until a plugin is ready (hopefully in a week or two) I have configured an external tool that kind of works. I take advantage of that the $project variable is expanded in resin.conf. Hence I have something like in the external tools def
Program: r:\bin\httpd.exe Parameters: -standalone -conf $FilePath$ -Dproject=$OutputPath$ Working directory: $OutputPath$
with a resin.conf (like below) in the project I can right-click it and choose the external tool resin and run it. I doesn't give you debugging tough
This resin.conf assumes the module build path is xxx/classes and the exploded dir is xxx/webroot
0
index.html
]]>
Another way would be some clever usage of a Run configuration
Not yet. I haven't had the time
/magnus
unika wrote:
Does it work if I'll compile it using cvs sources?
Nope
unika wrote:
it is a pity :(
hope you will get some free time soon :)
I hope you find time as well. Your plug-in makes developing with Resin easier.
BacMan
Started to play with tomcat plugin sources in order to make a minimal resin plugin working...It sucks when there is no plugin development documentation. Did I miss something?
No, you didn't miss anything, there is really almost no documentation,
just the plugin examples and a lot of try and error... :(
unika wrote:
unika wrote:
I know. Until a plugin is ready (hopefully in a week or two) I have
configured an external tool that kind of works. I take advantage of
that the $project variable is expanded in resin.conf. Hence I have
something like in the external tools def
Program: r:\bin\httpd.exe
Parameters: -standalone -conf $FilePath$ -Dproject=$OutputPath$
Working directory: $OutputPath$
with a resin.conf (like below) in the project I can right-click it
and choose the external tool resin and run it. I doesn't give you
debugging tough
This resin.conf assumes the module build path is xxx/classes and
the exploded dir is xxx/webroot
0 index.html ]]>
Another way would be some clever usage of a Run configuration
/magnus