You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by 陈思淼 <ch...@gmail.com> on 2008/10/07 18:49:16 UTC
where should I put my config file?
I have write a plugin which read from a config some mapping information and
do some thing.Of cause I can put the config file into src/resources, but I
will and more and more mapping information into the config file. I dont want
to deploy the plugin artifact after I modify the config file. Can I put the
config file in some independent location where my own plugin can access but
not contain in the src/resources, Is there any mechanism support this kind
of needs? do I need to write a new packaging type called config-file, and
deploy it to the repository?
Re: where should I put my config file?
Posted by Wayne Fay <wa...@gmail.com>.
This is described in the documentation:
http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html
And here it is in the source code for the plugin:
http://maven.apache.org/plugins/maven-checkstyle-plugin/xref/org/apache/maven/plugin/checkstyle/CheckstyleReport.html#1127
Wayne
2008/10/7 陈思淼 <ch...@gmail.com>:
> can you give me a example?
>
> 2008/10/8 陈思淼 <ch...@gmail.com>
>
>> thanks for Brett 's advice. can you make it more specific? I'm Interesting
>> about you mention about：locate from the repository。
>> can you give me some example,how can I put the checktyle.xml in the
>> repository, and the plugin get it thought a URL。
>>
>> 2008/10/8 Brett Porter <br...@gmail.com>
>>
>> I suggest looking at the Checkstyle plugin and similar for examples of
>>> how to do this. They tend to offer the option of:
>>> - built in (the example you gave)
>>> - download from an URL (for a single file)
>>> - locate from the repository (better since it makes it easy to
>>> relocate/manage)
>>>
>>> Cheers,
>>> Brett
>>>
>>> 2008/10/8 陈思淼 <ch...@gmail.com>:
>>> > I have write a plugin which read from a config some mapping information
>>> and
>>> > do some thing.Of cause I can put the config file into src/resources, but
>>> I
>>> > will and more and more mapping information into the config file. I dont
>>> want
>>> > to deploy the plugin artifact after I modify the config file. Can I put
>>> the
>>> > config file in some independent location where my own plugin can access
>>> but
>>> > not contain in the src/resources, Is there any mechanism support this
>>> kind
>>> > of needs? do I need to write a new packaging type called config-file,
>>> and
>>> > deploy it to the repository?
>>> >
>>>
>>>
>>>
>>> --
>>> Brett Porter
>>> Blog: http://blogs.exist.com/bporter/
>>>
>>
>>
>
Re: where should I put my config file?
Posted by 陈思淼 <ch...@gmail.com>.
can you give me a example?
2008/10/8 陈思淼 <ch...@gmail.com>
> thanks for Brett 's advice. can you make it more specific? I'm Interesting
> about you mention about：locate from the repository。
> can you give me some example,how can I put the checktyle.xml in the
> repository, and the plugin get it thought a URL。
>
> 2008/10/8 Brett Porter <br...@gmail.com>
>
> I suggest looking at the Checkstyle plugin and similar for examples of
>> how to do this. They tend to offer the option of:
>> - built in (the example you gave)
>> - download from an URL (for a single file)
>> - locate from the repository (better since it makes it easy to
>> relocate/manage)
>>
>> Cheers,
>> Brett
>>
>> 2008/10/8 陈思淼 <ch...@gmail.com>:
>> > I have write a plugin which read from a config some mapping information
>> and
>> > do some thing.Of cause I can put the config file into src/resources, but
>> I
>> > will and more and more mapping information into the config file. I dont
>> want
>> > to deploy the plugin artifact after I modify the config file. Can I put
>> the
>> > config file in some independent location where my own plugin can access
>> but
>> > not contain in the src/resources, Is there any mechanism support this
>> kind
>> > of needs? do I need to write a new packaging type called config-file,
>> and
>> > deploy it to the repository?
>> >
>>
>>
>>
>> --
>> Brett Porter
>> Blog: http://blogs.exist.com/bporter/
>>
>
>
Re: where should I put my config file?
Posted by 陈思淼 <ch...@gmail.com>.
thanks for Brett 's advice. can you make it more specific?I'm Interesting
about you mention about：locate from the repository。
can you give me some example,how can I put the checktyle.xml in the
repository, and the plugin get it thought a URL。
2008/10/8 Brett Porter <br...@gmail.com>
> I suggest looking at the Checkstyle plugin and similar for examples of
> how to do this. They tend to offer the option of:
> - built in (the example you gave)
> - download from an URL (for a single file)
> - locate from the repository (better since it makes it easy to
> relocate/manage)
>
> Cheers,
> Brett
>
> 2008/10/8 陈思淼 <ch...@gmail.com>:
> > I have write a plugin which read from a config some mapping information
> and
> > do some thing.Of cause I can put the config file into src/resources, but
> I
> > will and more and more mapping information into the config file. I dont
> want
> > to deploy the plugin artifact after I modify the config file. Can I put
> the
> > config file in some independent location where my own plugin can access
> but
> > not contain in the src/resources, Is there any mechanism support this
> kind
> > of needs? do I need to write a new packaging type called config-file, and
> > deploy it to the repository?
> >
>
>
>
> --
> Brett Porter
> Blog: http://blogs.exist.com/bporter/
>
Re: where should I put my config file?
Posted by Brett Porter <br...@gmail.com>.
I suggest looking at the Checkstyle plugin and similar for examples of
how to do this. They tend to offer the option of:
- built in (the example you gave)
- download from an URL (for a single file)
- locate from the repository (better since it makes it easy to relocate/manage)
Cheers,
Brett
2008/10/8 陈思淼 <ch...@gmail.com>:
> I have write a plugin which read from a config some mapping information and
> do some thing.Of cause I can put the config file into src/resources, but I
> will and more and more mapping information into the config file. I dont want
> to deploy the plugin artifact after I modify the config file. Can I put the
> config file in some independent location where my own plugin can access but
> not contain in the src/resources, Is there any mechanism support this kind
> of needs? do I need to write a new packaging type called config-file, and
> deploy it to the repository?
>
--
Brett Porter
Blog: http://blogs.exist.com/bporter/