You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Alan D. Cabrera" <li...@toolazydogs.com> on 2005/10/01 20:24:37 UTC
M2 multiproject setup
I have a suggested enhancement. Maybe this is already available. Maybe
it's a bad idea. Here it is.
Frequently, I will have multiple projects that are interdependent.
Their versions will move in tandem as I change the root POM's version.
IIUC, when I change the root POM's version, I must also change the
versions of the projects in the <dependencyManagement> list. What would
be neat is to have an element, say <useRootVersion/> which I could add
to the <version> element. This will inform dependency management that
the version of this dependency is to move in tandem with the root
<model><version/> element.
Thoughts?
Regards,
Alan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M2 multiproject setup
Posted by Stephen Duncan <st...@gmail.com>.
*slaps forehead*
D'oh!
Uh, thanks... :)
-Stephen
On 10/5/05, Brett Porter <br...@apache.org> wrote:
> a) yes, I think its a bug
> b) it's totally unnecessary, version is inherited :)
>
> - Brett
>
> Stephen Duncan wrote:
>
> >I plan on looking at the release plugin eventually, but I can only
> >handle so much new info at once. :) I want to keep the POM's in sync
> >when working on a snapshot too, so I just want to have to manually
> >change less properties when I start work on the next version, and when
> >it comes time to release too...
> >
> >I had:
> >
> ><project xmlns="http://maven.apache.org/POM/4.0.0">
> > <parent>
> > <groupId>mil.jfcom.cie.portal</groupId>
> > <artifactId>cdcie-project-portletframework</artifactId>
> > <version>1.2</version>
> > </parent>
> > <modelVersion>4.0.0</modelVersion>
> > <artifactId>cdcie-portlet-portletframeworksample</artifactId>
> > <packaging>war</packaging>
> > <name>Portlet Framework Sample</name>
> > <version>${project.parent.version}</version>
> >
> > ....
> ></project>
> >
> >Then I get the following error:
> >
> >[INFO] ----------------------------------------------------------------------------
> >[INFO] BUILD FAILURE
> >[INFO] ----------------------------------------------------------------------------
> >[INFO] Reason: Error building project from
> >'c:\workspace\PortletFramework\sample\pom.xml':
> >mil.jfcom.cie.portal:cdcie-po
> >rtlet-portletframeworksample:war:${project.parent.version}
> >
> >So, is this a bug?
> >
> >-Stephen
> >
> >On 10/5/05, Brett Porter <br...@apache.org> wrote:
> >
> >
> >>You can, but it is what you give in the <parent> element, you can't omit
> >>that.
> >>
> >>If you need a tool to keep versions in sync in a multiproject, check the
> >>release plugin.
> >>
> >>- Brett
> >>
> >>Stephen Duncan wrote:
> >>
> >>
> >>
> >>>But you can't do this?:
> >>>
> >>><version>${project.parent.version}</version>
> >>>
> >>>Sure would be nice to be able to keep my versions in sync more easily
> >>>if I don't want to bother independently versioning
> >>>modules/sub-projects.
> >>>
> >>>-Stephen
> >>>
> >>>
> >>>
> >>>
> >>>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >>
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Stephen Duncan Jr
www.stephenduncanjr.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M2 multiproject setup
Posted by Brett Porter <br...@apache.org>.
a) yes, I think its a bug
b) it's totally unnecessary, version is inherited :)
- Brett
Stephen Duncan wrote:
>I plan on looking at the release plugin eventually, but I can only
>handle so much new info at once. :) I want to keep the POM's in sync
>when working on a snapshot too, so I just want to have to manually
>change less properties when I start work on the next version, and when
>it comes time to release too...
>
>I had:
>
><project xmlns="http://maven.apache.org/POM/4.0.0">
> <parent>
> <groupId>mil.jfcom.cie.portal</groupId>
> <artifactId>cdcie-project-portletframework</artifactId>
> <version>1.2</version>
> </parent>
> <modelVersion>4.0.0</modelVersion>
> <artifactId>cdcie-portlet-portletframeworksample</artifactId>
> <packaging>war</packaging>
> <name>Portlet Framework Sample</name>
> <version>${project.parent.version}</version>
>
> ....
></project>
>
>Then I get the following error:
>
>[INFO] ----------------------------------------------------------------------------
>[INFO] BUILD FAILURE
>[INFO] ----------------------------------------------------------------------------
>[INFO] Reason: Error building project from
>'c:\workspace\PortletFramework\sample\pom.xml':
>mil.jfcom.cie.portal:cdcie-po
>rtlet-portletframeworksample:war:${project.parent.version}
>
>So, is this a bug?
>
>-Stephen
>
>On 10/5/05, Brett Porter <br...@apache.org> wrote:
>
>
>>You can, but it is what you give in the <parent> element, you can't omit
>>that.
>>
>>If you need a tool to keep versions in sync in a multiproject, check the
>>release plugin.
>>
>>- Brett
>>
>>Stephen Duncan wrote:
>>
>>
>>
>>>But you can't do this?:
>>>
>>><version>${project.parent.version}</version>
>>>
>>>Sure would be nice to be able to keep my versions in sync more easily
>>>if I don't want to bother independently versioning
>>>modules/sub-projects.
>>>
>>>-Stephen
>>>
>>>
>>>
>>>
>>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M2 multiproject setup
Posted by Stephen Duncan <st...@gmail.com>.
I plan on looking at the release plugin eventually, but I can only
handle so much new info at once. :) I want to keep the POM's in sync
when working on a snapshot too, so I just want to have to manually
change less properties when I start work on the next version, and when
it comes time to release too...
I had:
<project xmlns="http://maven.apache.org/POM/4.0.0">
<parent>
<groupId>mil.jfcom.cie.portal</groupId>
<artifactId>cdcie-project-portletframework</artifactId>
<version>1.2</version>
</parent>
<modelVersion>4.0.0</modelVersion>
<artifactId>cdcie-portlet-portletframeworksample</artifactId>
<packaging>war</packaging>
<name>Portlet Framework Sample</name>
<version>${project.parent.version}</version>
....
</project>
Then I get the following error:
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ----------------------------------------------------------------------------
[INFO] Reason: Error building project from
'c:\workspace\PortletFramework\sample\pom.xml':
mil.jfcom.cie.portal:cdcie-po
rtlet-portletframeworksample:war:${project.parent.version}
So, is this a bug?
-Stephen
On 10/5/05, Brett Porter <br...@apache.org> wrote:
> You can, but it is what you give in the <parent> element, you can't omit
> that.
>
> If you need a tool to keep versions in sync in a multiproject, check the
> release plugin.
>
> - Brett
>
> Stephen Duncan wrote:
>
> >But you can't do this?:
> >
> ><version>${project.parent.version}</version>
> >
> >Sure would be nice to be able to keep my versions in sync more easily
> >if I don't want to bother independently versioning
> >modules/sub-projects.
> >
> >-Stephen
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M2 multiproject setup
Posted by Brett Porter <br...@apache.org>.
You can, but it is what you give in the <parent> element, you can't omit
that.
If you need a tool to keep versions in sync in a multiproject, check the
release plugin.
- Brett
Stephen Duncan wrote:
>But you can't do this?:
>
><version>${project.parent.version}</version>
>
>Sure would be nice to be able to keep my versions in sync more easily
>if I don't want to bother independently versioning
>modules/sub-projects.
>
>-Stephen
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M2 multiproject setup
Posted by Stephen Duncan <st...@gmail.com>.
But you can't do this?:
<version>${project.parent.version}</version>
Sure would be nice to be able to keep my versions in sync more easily
if I don't want to bother independently versioning
modules/sub-projects.
-Stephen
On 10/1/05, Brett Porter <br...@apache.org> wrote:
> <version>${project.version}</version>
>
> will do the trick. You can still self reference the model.
>
> - Brett
>
> Alan D. Cabrera wrote:
>
> > I have a suggested enhancement. Maybe this is already available.
> > Maybe it's a bad idea. Here it is.
> >
> > Frequently, I will have multiple projects that are interdependent.
> > Their versions will move in tandem as I change the root POM's
> > version. IIUC, when I change the root POM's version, I must also
> > change the versions of the projects in the <dependencyManagement>
> > list. What would be neat is to have an element, say <useRootVersion/>
> > which I could add to the <version> element. This will inform
> > dependency management that the version of this dependency is to move
> > in tandem with the root <model><version/> element.
> >
> > Thoughts?
> >
> >
> > Regards,
> > Alan
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Stephen Duncan Jr
www.stephenduncanjr.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: M2 multiproject setup
Posted by Brett Porter <br...@apache.org>.
<version>${project.version}</version>
will do the trick. You can still self reference the model.
- Brett
Alan D. Cabrera wrote:
> I have a suggested enhancement. Maybe this is already available.
> Maybe it's a bad idea. Here it is.
>
> Frequently, I will have multiple projects that are interdependent.
> Their versions will move in tandem as I change the root POM's
> version. IIUC, when I change the root POM's version, I must also
> change the versions of the projects in the <dependencyManagement>
> list. What would be neat is to have an element, say <useRootVersion/>
> which I could add to the <version> element. This will inform
> dependency management that the version of this dependency is to move
> in tandem with the root <model><version/> element.
>
> Thoughts?
>
>
> Regards,
> Alan
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org