these are all inherint of a bigger problem - that the tagged release
depends on something outside the release.

We recommend you publish the parent POM to the repository, then use
${maven.repo.local}/groupId/poms/artifactId-version.pom

There is a JIRA issue filed to make it possible to get this from the
remote repository if needed.

- Brett

On Sun, 25 Jul 2004 10:59:01 +0200, Carlos Sanchez
<[EMAIL PROTECTED]> wrote:
> Hi,
> 
> You can add a pregoal to scm:checkout-project
> 
>    <!-- copy parent project files when checking out -->
>    <preGoal name="scm:checkout-project">
>        <maven:pluginVar plugin="maven-scm-plugin"
> property="maven.scm.checkout.dir" var="dir" />
>        <ant:delete dir="${dir}/common/maven"/>
>        <ant:mkdir dir="${dir}/common/maven" />
>        <ant:copy todir="${dir}/common/maven">
>            <ant:fileset dir="${common.maven.dir}"/>
>        </ant:copy>
>    </preGoal>
> 
> This will be improved in next versions
> 
> Regards
> 
> Carlos Sanchez
> A Coruņa, Spain
> 
> Oness Project
> http://oness.sourceforge.net
> 
> 
> 
> 
> > -----Original Message-----
> > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > Sent: Sunday, July 25, 2004 8:25 AM
> > To: Maven Users List
> > Subject: Re: Inherited project.xml
> >
> > I just dont use perform release.
> >
> > You could always pre-goal it and copy the file to the
> > appropriate directory.
> >
> > On Sat, 24 Jul 2004 22:25:34 -0400, STRAYER, JON (SBCSI)
> > <[EMAIL PROTECTED]> wrote:
> > > I have a project.xml that starts off
> > > <extend>${basedir}/../wfa_billing/project.xml</extend>
> > >
> > > That works fine when I'm doing things in the main directory
> > of the project.
> > > But when I do a scm:perform-release that path doesn't work.
> >  I could
> > > give it an absolute path, but that would suck for other
> > (obvious) reasons.
> > >
> > > I could break the dependence on the other project.xml, but
> > that opens
> > > up other problems (I'm going to have 25 or more projects, I
> > don't want
> > > to have to change 25 project.properties files when I change servers.
> > >
> > > I suppose I could just not use scm:perform-release.  Can
> > anyone think
> > > of another solution?
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > http://www.multitask.com.au/people/dion/
> >
> > ---------------------------------------------------------------------
> > 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