You might want to look at using the cargo plugin if you want to launch
your web application from Maven instead of a custom mojo.
We do this for debugging plugins for confluence, jira and bamboo.
James
On 18/04/2008, at 3:21 PM, Andrew Hughes wrote:
Well, I most certainly have found some good news!
I'll confirm this with some more testing...
If you have a maven <packaging>war</packaging> project with, a
dependency on
a war (ie geoserver)... the geoserver war's contents are packed into
the war
as well. This means if you wanted to customize your own... all you
would
need to do would be to put your geoserver data in ./src/main/webapp/
data/*
It would be especially easy if there was a classified version of
geoserver
available in a maven repository (geoserver-1.6.3-nodata.war), which
is easy
enough for me to knock up for testing... but I don't know how this
effects
your release mechanism if you want to do it in your project?
Next, I will look at how to embed a jetty or tomcat to launch
geoserver from
the command line. mvn geoserver:start or something.
On Wed, Apr 16, 2008 at 9:30 AM, Andrew Hughes <[EMAIL PROTECTED]>
wrote:
Releasing/Deploying a war to a repository is 'default' behaviour of
the
'mvn release:prepare release:perform' goals - providing the
<packaging>war</packaging>.
One thing that was an annoying problem is the 30MB release, but we
might
be able to save 7MB of that by removing ./data. I had a small think
about
this, and it *should* be possible to release two instances of the
geoserver
war. One version as it is now, and another with a classifier=nodata,
resulting in geoserver-1.6.0-nodata.war. This can be the dependency
that the
"standalone/out the box"...
<dependency>
<groupId>geoserver</groupId>
<artifactId>geoserver</artifactId>
<version>1.6.0</version>
<classifier>nodata</classifier>
</dependency>
Anyway, its all talk for now... but food for thought.
--AH
On Tue, Apr 15, 2008 at 10:56 PM, Andrea Aime <[EMAIL PROTECTED]>
wrote:
Andrew Hughes ha scritto:
...
Hum, ok, but I don't know how to push a .war onto a repository...
I'm
not even sure we would like to do so. Each .war is 30MB, we'd
have
to
make sure the .war are pushed onto the repo only during the
release
process (as opposed to publishing them daily as we for, for
instance,
with the geotools jars)
I would have to say, that this *should* really only be used with
releases
and not SNAPSHOTS, but of course we all like to test.
Very much agreed... thought I have no idea how to make a .war be
deployed,
nor how to make an artifact be deployed only during the release...
probably
using some profile...
Hum, this sounds like a good candidate for a community module.
Interested in working on it and providing some guidance on how to
use it in the
wiki?
I will try to find some time to see how complex this is in the next
couple
of days.
Nice. Looking forward to hear your findings.
Cheers
Andrea
You might want to look at using the cargo plugin if you want to launch
your web application from Maven instead of a custom mojo.
We do this for debugging plugins for confluence, jira and bamboo.
James
On 18/04/2008, at 3:21 PM, Andrew Hughes wrote:
Well, I most certainly have found some good news!
I'll confirm this with some more testing...
If you have a maven <packaging>war</packaging> project with, a
dependency on
a war (ie geoserver)... the geoserver war's contents are packed into
the war
as well. This means if you wanted to customize your own... all you
would
need to do would be to put your geoserver data in ./src/main/webapp/
data/*
It would be especially easy if there was a classified version of
geoserver
available in a maven repository (geoserver-1.6.3-nodata.war), which
is easy
enough for me to knock up for testing... but I don't know how this
effects
your release mechanism if you want to do it in your project?
Next, I will look at how to embed a jetty or tomcat to launch
geoserver from
the command line. mvn geoserver:start or something.
On Wed, Apr 16, 2008 at 9:30 AM, Andrew Hughes <[EMAIL PROTECTED]>
wrote:
Releasing/Deploying a war to a repository is 'default' behaviour of
the
'mvn release:prepare release:perform' goals - providing the
<packaging>war</packaging>.
One thing that was an annoying problem is the 30MB release, but we
might
be able to save 7MB of that by removing ./data. I had a small think
about
this, and it *should* be possible to release two instances of the
geoserver
war. One version as it is now, and another with a classifier=nodata,
resulting in geoserver-1.6.0-nodata.war. This can be the dependency
that the
"standalone/out the box"...
<dependency>
<groupId>geoserver</groupId>
<artifactId>geoserver</artifactId>
<version>1.6.0</version>
<classifier>nodata</classifier>
</dependency>
Anyway, its all talk for now... but food for thought.
--AH
On Tue, Apr 15, 2008 at 10:56 PM, Andrea Aime <[EMAIL PROTECTED]>
wrote:
Andrew Hughes ha scritto:
...
Hum, ok, but I don't know how to push a .war onto a repository...
I'm
not even sure we would like to do so. Each .war is 30MB, we'd
have
to
make sure the .war are pushed onto the repo only during the
release
process (as opposed to publishing them daily as we for, for
instance,
with the geotools jars)
I would have to say, that this *should* really only be used with
releases
and not SNAPSHOTS, but of course we all like to test.
Very much agreed... thought I have no idea how to make a .war be
deployed,
nor how to make an artifact be deployed only during the release...
probably
using some profile...
Hum, this sounds like a good candidate for a community module.
Interested in working on it and providing some guidance on how to
use it in the
wiki?
I will try to find some time to see how complex this is in the next
couple
of days.
Nice. Looking forward to hear your findings.
Cheers
Andrea
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
