You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "STRAYER, JON (SBCSI)" <js...@sbc.com> on 2004/07/25 04:25:34 UTC
Inherited project.xml
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Inherited project.xml
Posted by Brett Porter <br...@gmail.com>.
that's what the JIRA issue was about - some way to resolve that.
On Fri, 30 Jul 2004 16:47:54 +0200, Carlos Sanchez
<ap...@carlos.cousas.net> wrote:
> But in that way maven will fail until you manually download the parent pom
> to the local repo, won't it?
>
>
>
> > -----Original Message-----
> > From: Brett Porter [mailto:brett.porter@gmail.com]
> > Sent: Friday, July 30, 2004 4:35 PM
> > To: Maven Users List
> > Subject: Re: Inherited project.xml
> >
> > 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
> > <ap...@carlos.cousas.net> 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:dion.gillard@gmail.com]
> > > > 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)
> > > > <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> > > > > For additional commands, e-mail: users-help@maven.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > http://www.multitask.com.au/people/dion/
> > > >
> > > >
> > --------------------------------------------------------------------
> > > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > > >
> > >
> > >
> > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Inherited project.xml
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
But in that way maven will fail until you manually download the parent pom
to the local repo, won't it?
> -----Original Message-----
> From: Brett Porter [mailto:brett.porter@gmail.com]
> Sent: Friday, July 30, 2004 4:35 PM
> To: Maven Users List
> Subject: Re: Inherited project.xml
>
> 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
> <ap...@carlos.cousas.net> 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:dion.gillard@gmail.com]
> > > 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)
> > > <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> > > > For additional commands, e-mail: users-help@maven.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > http://www.multitask.com.au/people/dion/
> > >
> > >
> --------------------------------------------------------------------
> > > - To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> > >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Inherited project.xml
Posted by Brett Porter <br...@gmail.com>.
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
<ap...@carlos.cousas.net> 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:dion.gillard@gmail.com]
> > 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)
> > <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: users-help@maven.apache.org
> > >
> > >
> >
> >
> > --
> > http://www.multitask.com.au/people/dion/
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Inherited project.xml
Posted by Carlos Sanchez <ap...@carlos.cousas.net>.
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:dion.gillard@gmail.com]
> 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)
> <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> http://www.multitask.com.au/people/dion/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Inherited project.xml
Posted by Dion Gillard <di...@gmail.com>.
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) <js...@sbc.com> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
http://www.multitask.com.au/people/dion/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org