Can you explain that a little bit more?
With Maven 1, we currently use this structure:
+ module-name
+ build
project.xml
+ resources
+ src
Should I put the pom.xml in the module-name directory? Why is it a problem
if I would have it in the build directory?
regards,
Wim
2005/10/31, Brett Porter <[EMAIL PROTECTED]>:
>
> basedir is always the location of the POM file, it can't be changed.
>
> You can do something using custom properties in the POM. Note however
> that using relative paths including .. is discouraged as it prevents
> the subprojects from being checked out and built in isolation.
>
> - Brett
>
> On 10/31/05, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> > I have build files in a separate directory structure from the actual
> project
> > files, so I have relative paths such as:
> > <sourceDirectory>../../core-library/src/java</sourceDirectory>
> >
> > In m1, I could set arbitrary properties in project.properties and then
> use
> > those in the build files.
> >
> > With m2, I see that ${basedir} is referred to in the defaults for
> plugins,
> > such as for maven-site-plugin, siteDirectory as ${basedir}/src/site.
> >
> > How do I set ${basedir} in m2 so I don't have to keep repeating the same
> > relative path?
> >
> > Thanks,
> > --
> > Wendy
> >
> >
> >
> > ---------------------------------------------------------------------
> > 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]
>
>
