Two choices:
(1) Run "mvn -N deploy" in parent dir. This will deploy just the parent pom,
without recursing down into modules.
(2) Make the parent pom into its own project.
The directory structure would then be
rootdir
parentpom-module
a-module
b-module
c-module
In rootdir, you can choose to put a trivial pom if you want, which just
contains a bunch of <module> tags and nothing else. This allows commands to be
run across all modules. Or have nothing there.
The pom in the rootdir (if one exists) is *not* what a-module, b-module etc
reference as their parent pom. They reference the pom in parentpom-module.
Maven doesn't care where the parent pom is; it can be hosted by a different
company in a different country if you want. So having it in a directory which
is not ".." is no problem.
In this case, to release the parent pom, obviously just run "mvn deploy" in the
parentpom-module directory.
Regards, Simon
---- amit kumar <[EMAIL PROTECTED]> schrieb:
> But under the parent of a.jar there are other projects as well which are
> owned by different developers. The scenario is like:
> *Parent Project
> a.jar*(developer1)* c.war*(developer2)* d.jar*(developer3)
>
> All the three developers are responsible for deploying artifacts. So how to
> ensure the Parent Project's pom gets gets installed/deployed in the Intranet
> repository, and who should be installing that? Because every developer does
> like *C:\Parent Project\a>mvn deploy. *This doesn't result in the
> deployment of parent project's pom.
>
>
> Thanks and Regards,
> Amit
>
>
>
> On Feb 5, 2008 7:20 PM, Graham Leggett <[EMAIL PROTECTED]> wrote:
>
> > amit kumar wrote:
> >
> > > Say I have deployed *a.jar* ( whose pom has a parent tag, since it is a
> > > sub-module of the whole project as such), and *b.jar* has *a.jar* in its
> > > dependency.
> > > Now when I run a maven goal I see the error in which it tells that maven
> > was
> > > not able to find the the parent pom ( it sees the parent tag in the *
> > a.jar's
> > > * pom and tries to look for it, which obviously it doesn't find.) The
> > parent
> > > to *a.jar* is just a logical project with packaging type as pom.
> > >
> > > Could someone please help out. This problem kind of brought everything
> > in
> > > release automation on the knees.
> >
> > You need to install and/or deploy and release the parent pom as well as
> > your a.jar and b.jar, and you need to install it first.
> >
> > If you do a deploy or an install from the parent parent project, maven
> > figures out how to do this on its own.
> >
> > Parent pom files go into both local and remote repositories, just like
> > the pom files belonging to the jars, and follow the same rules.
> >
> > Regards,
> > Graham
> > --
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
