>Or is it some kind of feature for developers to easily get it deployed?
No no it's only a personal prototype that i am creating on my own... I am not really accustomed to maven yet. Creating a separate project for the deployment could be the way for me. Thanks! Valentin Jacquemin On Tue, Sep 15, 2009 at 11:09 AM, Anders Hammar <[email protected]> wrote: > What you have is an aggregating pom, which happens to be the parent pom as > well (I guess). > Why not create a separate project that does the deployment? It should have > dependencies on the artifacts that you want to deploy. You shouldn't > configure the glassfish deploy plugin to use a build/target folder of > another project but you should get the artifact from local/remote repo. I'm > not familiar with the glassfish plugin so I don't know if it can do that > itself or if you need to use the dependency plugin as well to fetch the > artifact first. > > Or you could have the glassfish plugin in each project deploying that > project's artifact. Common configuration for the plugin could be handled in > the parent through pluginManagement. I very much boils down to why you're > doing the deployment. Is it part of integration test for instance? Or is it > some kind of feature for developers to easily get it deployed? > > /Anders > > On Tue, Sep 15, 2009 at 11:01, Valentin Jacquemin <[email protected] > >wrote: > > > Here is my structure: > > > > pom > > |-------- ejb > > | |----- pom > > |--------web > > |----- pom > > > > In parent pom i use the glassfish plugin to deploy each artifact produced > > (ejb, web). In the glassfish plugin i have to specify each component to > > deploy and I wanted to fetch the build directory, project name for each > one > > but I am not able til now.... I use the glassfish plugin in the parent > > because every component will be deployed in the same domain, thus i can > set > > only once the glassfish instance config... > > > > This may sound weird for sure... I am open for better solutions. > > > > Valentin Jacquemin > > > > > > On Tue, Sep 15, 2009 at 10:52 AM, Anders Hammar <[email protected]> > wrote: > > > > > Out of a logical (design) perspective that sounds weird. The parent > > > shouldn't have any dependency on the siblings; it's the other way > around. > > > Are you talking about a parent project or an aggregating project? > > > > > > /Anders > > > > > > On Tue, Sep 15, 2009 at 10:39, Valentin Jacquemin < > [email protected] > > > >wrote: > > > > > > > Hi, > > > > > > > > I created a maven structure with a parent pom and for the moment 2 > > > modules > > > > (web, ejb). I was wondering whether it's possible to references > > > properties > > > > of those underdeath modules from the parent pom? > > > > > > > > Something like ${modules.ejb.build.directory}... Is there a reference > > on > > > > this topic? I were not able to find anything on that subject the > maven > > > > site.... > > > > > > > > Thanks, regards > > > > > > > > Valentin Jacquemin > > > > > > > > > >
