Normally, if it is a property used by a plugin, it is documented in the
plugin's doc. However, for the configId and configDirectory properties that
you talk about, I think that they are something GeoServer specific and not
for a plugin. Possibly they are used in the pom or during filtering.

/Anders

On Fri, Dec 4, 2009 at 08:39, maven apache <[email protected]> wrote:

> 2009/12/4 Kalle Korhonen <[email protected]>
>
> > + any plugin should publish their plugin documentation, e.g.
> > http://maven.apache.org/plugins/maven-install-plugin/plugin-info.html.
> > Once you know which plugin you want to use, it's almost trivial.
> >
> I know this,it is configed in the pom.xml.
> What I mean is the parameter in the command line:
> see
>
> http://docs.geoserver.org/2.0.x/en/developer/maven-guide/index.html#building-the-web-module
> <
> http://docs.geoserver.org/2.0.x/en/developer/maven-guide/index.html#building-the-web-module
> >mvn
> clean install -DconfigId=release
> -DconfigDirectory=/home/jdeolive/geoserver_1.7.x/data
> there is a parameter named configId and configDirectory,but I can not find
> where are they defined....
>
> >
> > Kalle
> >
> >
> > On Thu, Dec 3, 2009 at 10:41 PM, Stephen Connolly
> > <[email protected]> wrote:
> > > these properties are used by plugins.
> > >
> > > first you need to find what plugins are bound to your project lifecycle
> > >
> > > then you need to find what goals are used for each plugin
> > >
> > > then you need to look at the params available for each goal
> > >
> > > the maven-help-plugin may be able to help you
> > >
> > > Sent from my [rhymes with tryPod] ;-)
> > >
> > > On 4 Dec 2009, at 06:31, maven apache <[email protected]> wrote:
> > >
> > >> Hi:
> > >> Some maven command like "mvn install -Dmaven.test.skip=true" have
> > >> some parameters(here is the maven.test.skip),I want to know which
> > >> parameter
> > >> I can use?
> > >> I mean how do I know there is a parameter I can use? Is there a
> document
> > ?
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>

Reply via email to