Hi, dan.
But I would like to run jalopy on submodule level as well as root level. And
I dont want to duplicate info in all pom.xml file. So this tip is not very
useful.
Seems that putting jalopy.xml under HTTP is only way here.
On 4/29/06, dan tran <[EMAIL PROTECTED]> wrote:
I just take quick look at the source. The param name for convention field
is "jalopy.convention",
so your configuration must be like this
<configuration>
<jalopy.convention>../../......./src/main/resources/jalopy.xml<
jalopy.convention>
</configuration>
how many "../" you need to do dependening on where you are relative to
your
root.
-D
On 4/29/06, dan tran <[EMAIL PROTECTED]> wrote:
>
> Use ".." to walking up the source tree instead of basedir.
>
> -D
>
>
> On 4/29/06, Anatol Pomozov <[EMAIL PROTECTED]> wrote:
> >
> > Hi.
> >
> > I am trying to configure jalopy plugin for maven2. I have single
jalopy
> > configuration file that will be used in my project for all submodules.
> > I would like to store jalopy in VCS (it means on filesystem not on
HTTP
> > server)
> >
> > Jalopy configuration stored in root project
> > ${root}/src/main/resources/jalopy.xml
> >
> > Now I need to tell jalopy plugin where this configuration file
located.
> > I am
> > trying to configure plugin in following way
> >
> > <build>
> > <plugins>
> > <plugin>
> > <groupId>org.codehaus.mojo</groupId>
> > <artifactId>jalopy-maven-plugin</artifactId>
> > <version>1.0-SNAPSHOT</version>
> > <configuration>
> >
> > <convention>${basedir}/src/main/resources/jalopy.xml</convention>
> > </configuration>
> > </plugin>
> > </plugins>
> > </build>
> >
> > But it does not work when I try to run jalopy plugin from submodule,
> > because
> > ${basedir} calculated relatively to submodule directory.
> >
> > So there is a question. Is any way to get path relatively root
project??
> > (I
> > have 3 layer in POM hierarchy rootPom->applicationPom->submodulePom)
> >
> >
> > Thanks for your help.
> > --
> > anatol ( http://pomozov.info
--
anatol (http://pomozov.info)
