You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Trent Rosenbaum <tr...@gmail.com> on 2009/08/18 14:44:21 UTC

${packageInPathFormat} is remains in files under webapp folder

Hi there,
I am trying to create a new Archetype based a standard web application, but
I am finding that a number of resources under the 'webapp' folder are not
processed correctly and still contain the ${packageInPathFormat} string of
characters.
When working with then plugin I have noticed that files under the resources
folders do not get processed correctly either, (the original folder
structure means and resouces are not placed under the new folder structure
for the new package structure).  Does the archetype plugin only work with
resources under the 'java' folder?  Should I expect the plugin to process
the resources under the 'webapp' and 'recources' folders?  I am only asking
this because the plugin has attempted to process the resources and instead
has left me with an broken archetype that was generated from a correct and
working example project.

Does anyone have any ideas about how to get around this problem?

Many thanks
Trent

Re: ${packageInPathFormat} is remains in files under webapp folder

Posted by Trent Rosenbaum <tr...@gmail.com>.
Hi,
Just thought I would give an update.  I have been generating projects from
archetypes using the 'new project wizard' from the M2 eclipse plugin.  This
seemed to generate projects with the ${packageInPathFormat} still present
within some of the files.  I then ran the archetype plugin on the command
line with the generate target and this processed all of the resources
correctly.

Does the M2 eclipse plugin use the archetype project artifacts in a
different way compared to the standard plugin?  I thought they would have
work in the same way?

Trent

2009/8/18 Trent Rosenbaum <tr...@gmail.com>

> Hi there,
> I am trying to create a new Archetype based a standard web application, but
> I am finding that a number of resources under the 'webapp' folder are not
> processed correctly and still contain the ${packageInPathFormat} string of
> characters.
> When working with then plugin I have noticed that files under the resources
> folders do not get processed correctly either, (the original folder
> structure means and resouces are not placed under the new folder structure
> for the new package structure).  Does the archetype plugin only work with
> resources under the 'java' folder?  Should I expect the plugin to process
> the resources under the 'webapp' and 'recources' folders?  I am only asking
> this because the plugin has attempted to process the resources and instead
> has left me with an broken archetype that was generated from a correct and
> working example project.
>
> Does anyone have any ideas about how to get around this problem?
>
> Many thanks
> Trent
>