Re: How to implement an organisational super pom ?
Here is a god example of a organisational super pom http://maven.sateh.com/repository/org/apache/apache/2/ I have created one for my compnay that contains the following... internal-released scp://192.168.6.194/var/mvn/internal-released internal-snapshot scp://192.168.6.194/var/mvn/internal-snapshot Although each developer has to have the login details, for the repos, in thier settings.xml. But so far its working fine. Ben On 6/22/06, Alexandre Poitras <[EMAIL PROTECTED]> wrote: You confuse multi-modules project and super pom. A super pom doesn't need to declare any modules. It is an independant project which has its own version and distributed in your internal repository so that any project can download whenever it needs it. It should fix your problems. On 6/20/06, Dhananjay Nene <[EMAIL PROTECTED]> wrote: > Although the question wasn't addressed to me, I have run into some > problems (hence the question in the first place) so just adding my 2c. > > If the super pom modeled as a top level module (ie. each project > declares it as a parent), I get into a lot of issues when using the > release plugin for the individuaal projects (You can just try it out to > see what I mean). One of the issues I also get into is that the cvs > repository needs to be structured with the superpom module at the top > and each of the projects as a sub directory in the cvs module > representing the super pom which is not exactly the most convenient > mechanism for conducting version control across multiple independent > projects. > > Having said that since maven itself does use a super pom which does not > suffer from these limitations hopefully there's some way to implement - > but I couldn't figure it out so far. > > Dhananjay > > Roald Bankras wrote: > > Nathan > > > > What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. > > > > Roald Bankras > > Software Engineer > > JTeam b.v. > > > > -----Original Message----- > > From: Beyer,Nathan [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 20, 2006 12:29 AM > > To: Maven Users List > > Subject: RE: How to implement an organisational super pom ? > > > > >From my adventures in trying to do this, I've found that it's just not a > > good idea in the current state of things. There are some things that can > > be done with dependencyManagement and pluginManagement, but that only > > goes so far. > > > > My suggestion is to standardize things via archetypes to generate POMs > > in a certain fashion. For common "automated build" stuff use profile > > settings for the build user. > > > > -Nathan > > > > -Original Message- > > From: Dhananjay Nene [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 19, 2006 1:34 PM > > To: Maven Users List > > Subject: How to implement an organisational super pom ? > > > > I need to implement a common pom which can be inherited by a large > > number of projects. However the common pom does not reflect a top level > > module and does not have any sources or artifacts (since it is used only > > for inheritance). My attempts so far lead me to believe that maven > > requires me to assign a version to the common pom, and the release > > management workflow tries to checkout a project corresponding to top > > level pom which obviously fails in my case. How can I implement a common > > pom (like the maven super pom) so that the common pom is used only for > > inheritance, and each pom which refers to it (as a parent ??) is in fact > > a top level application (and not a module/sub module) ? > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > > CONFIDENTIALITY NOTICE This message and any included attachments > > are from Cerner Corporation and are intended only for the > > addressee. The information contained in this message is > > confidential and may constitute inside or non-public information > > under international, federal, or state securities laws. > > Unauthorized forwarding, printing, copying, distribution, or use of > > such information is strictly prohibited and may be unlawful. If you > > are not the addressee, please promptly delete this message and > > notify the sender of the delivery error by e-mail or y
Re: How to implement an organisational super pom ?
You confuse multi-modules project and super pom. A super pom doesn't need to declare any modules. It is an independant project which has its own version and distributed in your internal repository so that any project can download whenever it needs it. It should fix your problems. On 6/20/06, Dhananjay Nene <[EMAIL PROTECTED]> wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: > Nathan > > What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. > > Roald Bankras > Software Engineer > JTeam b.v. > > -Original Message- > From: Beyer,Nathan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 20, 2006 12:29 AM > To: Maven Users List > Subject: RE: How to implement an organisational super pom ? > > >From my adventures in trying to do this, I've found that it's just not a > good idea in the current state of things. There are some things that can > be done with dependencyManagement and pluginManagement, but that only > goes so far. > > My suggestion is to standardize things via archetypes to generate POMs > in a certain fashion. For common "automated build" stuff use profile > settings for the build user. > > -Nathan > > -Original Message- > From: Dhananjay Nene [mailto:[EMAIL PROTECTED] > Sent: Monday, June 19, 2006 1:34 PM > To: Maven Users List > Subject: How to implement an organisational super pom ? > > I need to implement a common pom which can be inherited by a large > number of projects. However the common pom does not reflect a top level > module and does not have any sources or artifacts (since it is used only > for inheritance). My attempts so far lead me to believe that maven > requires me to assign a version to the common pom, and the release > management workflow tries to checkout a project corresponding to top > level pom which obviously fails in my case. How can I implement a common > pom (like the maven super pom) so that the common pom is used only for > inheritance, and each pom which refers to it (as a parent ??) is in fact > a top level application (and not a module/sub module) ? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > CONFIDENTIALITY NOTICE This message and any included attachments > are from Cerner Corporation and are intended only for the > addressee. The information contained in this message is > confidential and may constitute inside or non-public information > under international, federal, or state securities laws. > Unauthorized forwarding, printing, copying, distribution, or use of > such information is strictly prohibited and may be unlawful. If you > are not the addressee, please promptly delete this message and > notify the sender of the delivery error by e-mail or you may call > Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) > (816)221-1024. --- > > > - > 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]
Re: How to implement an organisational super pom ?
Dhananjay Nene wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. You don't need to have your super-pom in cvs. Use a versioning number scheme for the pom like this 1, 2, 3.. i.e. incremental numbers. Install each new version of the pom into your company Maven repository. That way you have copies of the released versions of your super-pom in your Maven repo. -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
What factors/bases should be taken into account when thinking to create super POM or not? Create parent -> child model or not, especially if the components also used in another different projects? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos Sanchez Sent: Tuesday, June 20, 2006 3:18 PM To: Maven Users List Subject: Re: How to implement an organisational super pom ? You can override any configuraion you want, version or anything. We use parent poms all the time with no problems at all On 6/20/06, Dhananjay Nene <[EMAIL PROTECTED]> wrote: > Although the question wasn't addressed to me, I have run into some > problems (hence the question in the first place) so just adding my 2c. > > If the super pom modeled as a top level module (ie. each project > declares it as a parent), I get into a lot of issues when using the > release plugin for the individuaal projects (You can just try it out > to see what I mean). One of the issues I also get into is that the > cvs repository needs to be structured with the superpom module at the > top and each of the projects as a sub directory in the cvs module > representing the super pom which is not exactly the most convenient > mechanism for conducting version control across multiple independent > projects. > > Having said that since maven itself does use a super pom which does > not suffer from these limitations hopefully there's some way to > implement - but I couldn't figure it out so far. > > Dhananjay > > Roald Bankras wrote: > > Nathan > > > > What kind of problems did you ran into? I'm currently working on a > > super pom for my company, but haven't seen any problems yet. > > > > Roald Bankras > > Software Engineer > > JTeam b.v. > > > > -----Original Message----- > > From: Beyer,Nathan [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, June 20, 2006 12:29 AM > > To: Maven Users List > > Subject: RE: How to implement an organisational super pom ? > > > > >From my adventures in trying to do this, I've found that it's just > > >not a > > good idea in the current state of things. There are some things that > > can be done with dependencyManagement and pluginManagement, but that > > only goes so far. > > > > My suggestion is to standardize things via archetypes to generate > > POMs in a certain fashion. For common "automated build" stuff use > > profile settings for the build user. > > > > -Nathan > > > > -Original Message- > > From: Dhananjay Nene [mailto:[EMAIL PROTECTED] > > Sent: Monday, June 19, 2006 1:34 PM > > To: Maven Users List > > Subject: How to implement an organisational super pom ? > > > > I need to implement a common pom which can be inherited by a large > > number of projects. However the common pom does not reflect a top > > level module and does not have any sources or artifacts (since it is > > used only for inheritance). My attempts so far lead me to believe > > that maven requires me to assign a version to the common pom, and > > the release management workflow tries to checkout a project > > corresponding to top level pom which obviously fails in my case. How > > can I implement a common pom (like the maven super pom) so that the > > common pom is used only for inheritance, and each pom which refers > > to it (as a parent ??) is in fact a top level application (and not a > > module/sub module) ? > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > > CONFIDENTIALITY NOTICE This message and any included attachments are > > from Cerner Corporation and are intended only for the addressee. The > > information contained in this message is confidential and may > > constitute inside or non-public information under international, > > federal, or state securities laws. Unauthorized forwarding, > > printing, copying, distribution, or use of such information is > > strictly prohibited and may be unlawful. If you are not the > > addressee, please promptly delete this message and notify the sender > > of the delivery error by e-mail or you may call Cerner's corporate > > offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. > > --- > > > > > > > >
Re: How to implement an organisational super pom ?
You can override any configuraion you want, version or anything. We use parent poms all the time with no problems at all On 6/20/06, Dhananjay Nene <[EMAIL PROTECTED]> wrote: Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: > Nathan > > What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. > > Roald Bankras > Software Engineer > JTeam b.v. > > -Original Message- > From: Beyer,Nathan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 20, 2006 12:29 AM > To: Maven Users List > Subject: RE: How to implement an organisational super pom ? > > >From my adventures in trying to do this, I've found that it's just not a > good idea in the current state of things. There are some things that can > be done with dependencyManagement and pluginManagement, but that only > goes so far. > > My suggestion is to standardize things via archetypes to generate POMs > in a certain fashion. For common "automated build" stuff use profile > settings for the build user. > > -Nathan > > -Original Message- > From: Dhananjay Nene [mailto:[EMAIL PROTECTED] > Sent: Monday, June 19, 2006 1:34 PM > To: Maven Users List > Subject: How to implement an organisational super pom ? > > I need to implement a common pom which can be inherited by a large > number of projects. However the common pom does not reflect a top level > module and does not have any sources or artifacts (since it is used only > for inheritance). My attempts so far lead me to believe that maven > requires me to assign a version to the common pom, and the release > management workflow tries to checkout a project corresponding to top > level pom which obviously fails in my case. How can I implement a common > pom (like the maven super pom) so that the common pom is used only for > inheritance, and each pom which refers to it (as a parent ??) is in fact > a top level application (and not a module/sub module) ? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > CONFIDENTIALITY NOTICE This message and any included attachments > are from Cerner Corporation and are intended only for the > addressee. The information contained in this message is > confidential and may constitute inside or non-public information > under international, federal, or state securities laws. > Unauthorized forwarding, printing, copying, distribution, or use of > such information is strictly prohibited and may be unlawful. If you > are not the addressee, please promptly delete this message and > notify the sender of the delivery error by e-mail or you may call > Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) > (816)221-1024. --- > > > - > 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] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
- The release plugin issue, sounds to me like a bug. - For SCM I think that you can just override the scm configuration for the project. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 10:40 AM To: Maven Users List Subject: Re: How to implement an organisational super pom ? Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: > Nathan > > What kind of problems did you ran into? I'm currently working on a super pom > for my company, but haven't seen any problems yet. > > Roald Bankras > Software Engineer > JTeam b.v. > > -Original Message- > From: Beyer,Nathan [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 20, 2006 12:29 AM > To: Maven Users List > Subject: RE: How to implement an organisational super pom ? > > >From my adventures in trying to do this, I've found that it's just not a > good idea in the current state of things. There are some things that can > be done with dependencyManagement and pluginManagement, but that only > goes so far. > > My suggestion is to standardize things via archetypes to generate POMs > in a certain fashion. For common "automated build" stuff use profile > settings for the build user. > > -Nathan > > -Original Message- > From: Dhananjay Nene [mailto:[EMAIL PROTECTED] > Sent: Monday, June 19, 2006 1:34 PM > To: Maven Users List > Subject: How to implement an organisational super pom ? > > I need to implement a common pom which can be inherited by a large > number of projects. However the common pom does not reflect a top level > module and does not have any sources or artifacts (since it is used only > for inheritance). My attempts so far lead me to believe that maven > requires me to assign a version to the common pom, and the release > management workflow tries to checkout a project corresponding to top > level pom which obviously fails in my case. How can I implement a common > pom (like the maven super pom) so that the common pom is used only for > inheritance, and each pom which refers to it (as a parent ??) is in fact > a top level application (and not a module/sub module) ? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > - > CONFIDENTIALITY NOTICE This message and any included attachments > are from Cerner Corporation and are intended only for the > addressee. The information contained in this message is > confidential and may constitute inside or non-public information > under international, federal, or state securities laws. > Unauthorized forwarding, printing, copying, distribution, or use of > such information is strictly prohibited and may be unlawful. If you > are not the addressee, please promptly delete this message and > notify the sender of the delivery error by e-mail or you may call > Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) > (816)221-1024. --- > > > - > 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] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.1/369 - Release Date: 6/19/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.1/369 - Release Date: 6/19/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to implement an organisational super pom ?
Although the question wasn't addressed to me, I have run into some problems (hence the question in the first place) so just adding my 2c. If the super pom modeled as a top level module (ie. each project declares it as a parent), I get into a lot of issues when using the release plugin for the individuaal projects (You can just try it out to see what I mean). One of the issues I also get into is that the cvs repository needs to be structured with the superpom module at the top and each of the projects as a sub directory in the cvs module representing the super pom which is not exactly the most convenient mechanism for conducting version control across multiple independent projects. Having said that since maven itself does use a super pom which does not suffer from these limitations hopefully there's some way to implement - but I couldn't figure it out so far. Dhananjay Roald Bankras wrote: Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? >From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common "automated build" stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - 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]
RE: How to implement an organisational super pom ?
Nathan What kind of problems did you ran into? I'm currently working on a super pom for my company, but haven't seen any problems yet. Roald Bankras Software Engineer JTeam b.v. -Original Message- From: Beyer,Nathan [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 20, 2006 12:29 AM To: Maven Users List Subject: RE: How to implement an organisational super pom ? >From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common "automated build" stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 6/16/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.9.0/368 - Release Date: 6/16/2006 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to implement an organisational super pom ?
>From my adventures in trying to do this, I've found that it's just not a good idea in the current state of things. There are some things that can be done with dependencyManagement and pluginManagement, but that only goes so far. My suggestion is to standardize things via archetypes to generate POMs in a certain fashion. For common "automated build" stuff use profile settings for the build user. -Nathan -Original Message- From: Dhananjay Nene [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 1:34 PM To: Maven Users List Subject: How to implement an organisational super pom ? I need to implement a common pom which can be inherited by a large number of projects. However the common pom does not reflect a top level module and does not have any sources or artifacts (since it is used only for inheritance). My attempts so far lead me to believe that maven requires me to assign a version to the common pom, and the release management workflow tries to checkout a project corresponding to top level pom which obviously fails in my case. How can I implement a common pom (like the maven super pom) so that the common pom is used only for inheritance, and each pom which refers to it (as a parent ??) is in fact a top level application (and not a module/sub module) ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - CONFIDENTIALITY NOTICE This message and any included attachments are from Cerner Corporation and are intended only for the addressee. The information contained in this message is confidential and may constitute inside or non-public information under international, federal, or state securities laws. Unauthorized forwarding, printing, copying, distribution, or use of such information is strictly prohibited and may be unlawful. If you are not the addressee, please promptly delete this message and notify the sender of the delivery error by e-mail or you may call Cerner's corporate offices in Kansas City, Missouri, U.S.A at (+1) (816)221-1024. --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
