Karan Malhi wrote:
That would be awesome. I've been updating the update site manually - is
this necessary or is there a way to publish builds from Continuum?
Not sure about that. I think running the following deploys the snapshot
mvn clean deploy
Thanks, I'll give that a go - I hadn't considered that. If it works
it'll be a lot easier than my current manual method of scp-ing the .zip
up to the server and unzipping it, setting the permissions etc etc.
Also, what are people's thoughts on perhaps moving the code from the
sandbox?
That would be cool. The only thing I am thinking of is that the first time
one needs to download the plugin it would take a long time. If this was
moved out of sandbox, would there be a way to not have it downloaded part of
the trunk i.e. the OpenEJB stuff (I am not sure I know how to explain it).
Let me put it in another way , could we have a separate svn site for the
plugin and still move it out of sandbox so that when I checkout openejb from
svn, I do not also checkout the plugin.
I was really just thinking of moving it up a level. There's already a
https://svn.apache.org/repos/asf/openejb/trunk/openejb-eclipse
directory, which I guess is old. Perhaps that might be a good place for
this stuff to go? As you rightly point out, the first build of the
plugin takes *ages* so I wouldn't look to include it in the openejb3
directory.
(Could we do something similar with examples too where the users could
simply just checkout *all* the examples *only*)
We certainly could. Although if you just want the examples, a checkout
and build of
https://svn.apache.org/repos/asf/openejb/trunk/openejb3/examples has
just worked for me. Obviously you can't get the server without the
examples though ;-)
Jon
