Hi Richard,
You can use the property ${basedir} to refer to root of the project, so
the directory in question would be ${basedir}/src/main/config
- Russ
On Jul 11, 2013, at 1:24 AM, "Richard Sand" <[email protected]> wrote:
> I've several projects that were created before we began using maven and
> which we've added maven to subsequently. Obviously these projects were not
> created with an archetype. Is there a "standard" folder that is commonly
> used in archetypes for holding files such as application configuration files
> or templates? The types of files I'm thinking of would not be put into
> packaging (e.g. they wouldn't be placed into the jar, war etc. created by
> maven) but would potentially be used in the install or deploy lifecycles. A
> folder such as "src/main/config"?
>
> If such an animal exists, what property would I used to reference it in a
> plugin? e.g. the equivalent of "${project.build.sourceDirectory}". Is there
> such a property?
>
> If not, is there a property that references the "src" or "src/main" folder?
> ${project.build.sourceDirectory} references "src/main/java" - it would seem
> to be a hack to use "../config" from there but it would work.
>
> Thanks!
>
> Richard Sand | CEO
> IDF Connect, Inc.
> 2207 Concord Ave, #359
> Wilmington | Delaware 19803 | USA
> Office: +1 302 425 0516 | Fax: +1 856 866 1899
> Mobile: +1 267 984 3651
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
-----------------
Come read my webnovel, Take a Lemon <http://www.takealemon.com>,
and listen to the Misfile radio play
<http://www.gold-family.us/audio/misfile.html>!
