Re: Centrally managing configuration files in a multi-module project
Thanks Brett!
It turns out that the jalopy plug-in does support multi-module projects ...
http://mojo.codehaus.org/jalopy-maven-plugin/examples/multimodule.html
Sorry for not looking at the docs a bit closer before firing off
questions on the mailing
list. But thanks anyway for drawing my attention to the dependency
plug-in. I think
I have some other problems that can be solved with it.
Best regards,
Jan van Mansum.
2008/8/28 Brett Porter <[EMAIL PROTECTED]>:
> The general approach used here can be seen in the checkstyle plugin - the
> configuration is able to be provided at either a file, URL, or within a
> repository artifact. The last option is the best since it makes advantage of
> Maven's resolution and local caching but also makes it referencable from any
> project regardless of the source hierachy.
> If jalopy doesn't support this, you can use the dependency plugin to grab
> the config, unpack it to the target directory, and then use it from there.
>
> - Brett
>
> 2008/8/27 Jan van Mansum <[EMAIL PROTECTED]>
>
>> Sorry, for the confusing message, I hit a gmail shortcut that sent the
>> mail out prematurely.
>>
>> So, again: I tried adding the following configuration to the main pom.xml:
>>
>>
>>org.codehaus.mojo
>>jalopy-maven-plugin
>>1.0-alpha-1
>>
>>${basedir}/docs/jalopy/jalopy.xml
>>
>>
>>
>>process-classes
>>
>>format
>>
>>
>>
>>
>>
>> and putting the jalopy.xml in the directory docs/jalopy relative to
>> the main project's pom.xml.
>> However, ${basedir} resolves to the base directory of the pom.xml that
>> is executed, so this
>> won't work. Is there a way to refer to the pom.xml that actually
>> declares the plugin element?
>>
>> Thanks and regards,
>>
>> Jan van Mansum.
>>
>>
>>
>>
>>
>> 2008/8/27 Jan van Mansum <[EMAIL PROTECTED]>:
>> > Hello group,
>> >
>> > I have a multi-module project and I want to use the same jalopy (code
>> > formatting)
>> > settings for all the modules. I tried to add the following to the main
>> pom.xml:
>> >
>> >
>> > ...
>> >
>> >org.codehaus.mojo
>> >jalopy-maven-plugin
>> >1.0-alpha-1
>> >
>> >
>> ${basedir}/docs/jalopy/jalopy.xml
>> >
>> >
>> >
>> >process-classes
>> >
>> >format
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Jan van Mansum
>> >
>>
>>
>>
>> --
>> Jan van Mansum
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
--
Jan van Mansum
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Centrally managing configuration files in a multi-module project
The general approach used here can be seen in the checkstyle plugin - the
configuration is able to be provided at either a file, URL, or within a
repository artifact. The last option is the best since it makes advantage of
Maven's resolution and local caching but also makes it referencable from any
project regardless of the source hierachy.
If jalopy doesn't support this, you can use the dependency plugin to grab
the config, unpack it to the target directory, and then use it from there.
- Brett
2008/8/27 Jan van Mansum <[EMAIL PROTECTED]>
> Sorry, for the confusing message, I hit a gmail shortcut that sent the
> mail out prematurely.
>
> So, again: I tried adding the following configuration to the main pom.xml:
>
>
>org.codehaus.mojo
>jalopy-maven-plugin
>1.0-alpha-1
>
>${basedir}/docs/jalopy/jalopy.xml
>
>
>
>process-classes
>
>format
>
>
>
>
>
> and putting the jalopy.xml in the directory docs/jalopy relative to
> the main project's pom.xml.
> However, ${basedir} resolves to the base directory of the pom.xml that
> is executed, so this
> won't work. Is there a way to refer to the pom.xml that actually
> declares the plugin element?
>
> Thanks and regards,
>
> Jan van Mansum.
>
>
>
>
>
> 2008/8/27 Jan van Mansum <[EMAIL PROTECTED]>:
> > Hello group,
> >
> > I have a multi-module project and I want to use the same jalopy (code
> > formatting)
> > settings for all the modules. I tried to add the following to the main
> pom.xml:
> >
> >
> > ...
> >
> >org.codehaus.mojo
> >jalopy-maven-plugin
> >1.0-alpha-1
> >
> >
> ${basedir}/docs/jalopy/jalopy.xml
> >
> >
> >
> >process-classes
> >
> >format
> >
> >
> >
> >
> >
> >
> > --
> > Jan van Mansum
> >
>
>
>
> --
> Jan van Mansum
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/
Re: Centrally managing configuration files in a multi-module project
Sorry, for the confusing message, I hit a gmail shortcut that sent the
mail out prematurely.
So, again: I tried adding the following configuration to the main pom.xml:
org.codehaus.mojo
jalopy-maven-plugin
1.0-alpha-1
${basedir}/docs/jalopy/jalopy.xml
process-classes
format
and putting the jalopy.xml in the directory docs/jalopy relative to
the main project's pom.xml.
However, ${basedir} resolves to the base directory of the pom.xml that
is executed, so this
won't work. Is there a way to refer to the pom.xml that actually
declares the plugin element?
Thanks and regards,
Jan van Mansum.
2008/8/27 Jan van Mansum <[EMAIL PROTECTED]>:
> Hello group,
>
> I have a multi-module project and I want to use the same jalopy (code
> formatting)
> settings for all the modules. I tried to add the following to the main
> pom.xml:
>
>
> ...
>
>org.codehaus.mojo
>jalopy-maven-plugin
>1.0-alpha-1
>
>${basedir}/docs/jalopy/jalopy.xml
>
>
>
>process-classes
>
>format
>
>
>
>
>
>
> --
> Jan van Mansum
>
--
Jan van Mansum
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Centrally managing configuration files in a multi-module project
Hello group,
I have a multi-module project and I want to use the same jalopy (code
formatting)
settings for all the modules. I tried to add the following to the main pom.xml:
...
org.codehaus.mojo
jalopy-maven-plugin
1.0-alpha-1
${basedir}/docs/jalopy/jalopy.xml
process-classes
format
--
Jan van Mansum
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
