I ran into this myself and at first didn't know why suddenly my WAR
was showing up in the wrong contextPath. Then realized it was probably
due to the new EAR release.

So instead of changing the configuration to use my application.xml, I
just added some configuration to the EAR plugin node in pom.xml which
fully specifies my application.xml at build time. For config files
like this, I'd rather let Maven generate it than be responsible for it
myself.

Wayne

On 1/11/07, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
I don't know why the defaults changed...
If you want the previous behaviour, fix your plugin version to 2.2

On 1/11/07, Tobias Jenkner <[EMAIL PROTECTED]> wrote:
> I do not understand the reason for this change?
> why do I have to configure the resources directory on my own? the maven
> approach is convention over configuration, isn't it?
> or is it deprecated to use resources in this place? where should I place
> them instead?
>
> thanks for your help, Tobias.
>
> Tom Huybrechts schrieb:
> > I had the same problem today....
> >
> > Let me quote somebody:
> >
> > you can still make it work if you explicitely set the resources directory
> >
> >  
<configuration><resourcesDir>${project.build.outputDirectory}</resourcesDir>
> >
> >  </configuration>
> >
> > tom
> >
> > On 1/11/07, Tobias Jenkner <[EMAIL PROTECTED]> wrote:
> >> Hello,
> >>
> >> when I use the maven-ear-plugin in its latest (released) version 2.3, it
> >> seams that the plugin does not copy the resources any more. The build
> >> fails because it cannot locate the application.xml any more:
> >>
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [ERROR] BUILD ERROR
> >> [INFO]
> >> ------------------------------------------------------------------------
> >> [INFO] Deployment descriptor:
> >> 
c:\Workspace\server\application\target\mpa-application-M2-SNAPSHOT\META-INF\application.xm
> >>
> >> l does not exist.
> >>
> >> When I use the old version 2.2 everything works fine.
> >> Is this a bug or is the fault on my side? Do I have to change my maven
> >> configuration when using version 2.3?
> >> Issue MEAR-47 is about removing the resourcesDir property - did that
> >> influence the resource handling in general?
> >>
> >> thanks for your comments,
> >> Tobias.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to