Re: module question

[Wayne Fay]

> But that's not my decision to make.

M3 is vastly superior and almost completely backwards compatible. This
shouldn't be a very hard sell considering the variety of bug fixes
(such as this one) from M2.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: module question

[Robert Egan]

Thanks

But that's not my decision to make.


On Tue, Apr 17, 2012 at 9:38 PM, Wayne Fay  wrote:

> > The real answer is that in the multi-module project, someone calls the
> > 'standard' assembly plugin before I do (there are many other EARs, WARs
> and
> > JARs in the build). So it is the one in memory when the module that needs
> > mine is invoked. I need to find a way to insure that my assembly plugin
> is
> > loaded first, and therefore loads the required dependency.
>
> Or you could just move to Maven3 where this bug in M2 was resolved...
> assuming that I understand what you are saying. Otherwise if you are
> on M3, you need to adjust your dependencies and declare things in such
> a way that Maven can properly calculate the build path.
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: module question

[Wayne Fay]

> The real answer is that in the multi-module project, someone calls the
> 'standard' assembly plugin before I do (there are many other EARs, WARs and
> JARs in the build). So it is the one in memory when the module that needs
> mine is invoked. I need to find a way to insure that my assembly plugin is
> loaded first, and therefore loads the required dependency.

Or you could just move to Maven3 where this bug in M2 was resolved...
assuming that I understand what you are saying. Otherwise if you are
on M3, you need to adjust your dependencies and declare things in such
a way that Maven can properly calculate the build path.

Wayne

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: module question

[Robert Egan]

Thanks

The real answer is that in the multi-module project, someone calls the
'standard' assembly plugin before I do (there are many other EARs, WARs and
JARs in the build). So it is the one in memory when the module that needs
mine is invoked. I need to find a way to insure that my assembly plugin is
loaded first, and therefore loads the required dependency.


On Tue, Apr 17, 2012 at 7:25 PM, Stevo Slavić  wrote:

> Hello Robert,
>
> My guess is that the other pom defines a repository which cannot be
> accessed (e.g. due to security constraints). Having failing build output,
> not to mention pom files themselves, would help a lot to better diagnose
> root cause.
>
> Regards,
> Stevo.
> On Apr 18, 2012 1:17 AM, "Robert Egan" 
> wrote:
>
> > I have a POM hat works correctly when it is the 'root' POM but fails to
> > resolve a dependency when it is invoked as a module from another POM.
> >
> > How does one go about resolving an issue like this?
> >
>

Re: module question

[Stevo Slavić]

Hello Robert,

My guess is that the other pom defines a repository which cannot be
accessed (e.g. due to security constraints). Having failing build output,
not to mention pom files themselves, would help a lot to better diagnose
root cause.

Regards,
Stevo.
On Apr 18, 2012 1:17 AM, "Robert Egan"  wrote:

> I have a POM hat works correctly when it is the 'root' POM but fails to
> resolve a dependency when it is invoked as a module from another POM.
>
> How does one go about resolving an issue like this?
>

module question

[Robert Egan]

I have a POM hat works correctly when it is the 'root' POM but fails to
resolve a dependency when it is invoked as a module from another POM.

How does one go about resolving an issue like this?

RE: maven site multi-module question

[Ashley Williams]

Cunning idea, but it wouldn't work for us, since the /websitedir is 
actually in the target
directory of another project. So a more accurate picture would be as 
follows:

/mvnparentdir   [pom.xml]
|
|_project1  [pom.xml]
|
|_project2  [pom.xml]
|
|_jettyproj [pom.xml]
  |
  |target   [jettyproj.jar]
 |
 |__classes
   |
   |__websitedir


The jettyproj.jar is an executable jar that we can take onto another
machine and run from there. We do this so that we can have different 
documentation jars for different branches and don't wish to administer a
full on Apache installation.

We also use continuum for our builds so the projects get checked out
into various different directories, and managing these locations
in the settings.xml file would get quite tricky.

It seems a pretty fundamental ability for a site plugin to be able
to create the finished version of the actual site without only being
available when tacked onto the deployment, so I'm hoping there is
some combination of settings that will do this for us.



"Prystash,John" <[EMAIL PROTECTED]> wrote on 01/05/2008 17:47:07:

> 
> Hey Ashley, I've been able to do something similar by putting the
> following in the POM of the parent.
> 
> 
>   
> file://${user.dir}/site
>   
>  
> 
> This puts the site directory inside the parent directory however when I
> run site-deploy.
> 
> -Original Message-
> From: Ashley Williams [mailto:[EMAIL PROTECTED] 
> Sent: Thursday, May 01, 2008 12:31 PM
> To: users@maven.apache.org
> Subject: maven site multi-module question
> 
> Hi,
> 
> I'm having trouble generating a maven site in the directory of my
> choosing. I don't want to actually deploy the site (onto a remote
> server), but instead I want to copy the resulting website into a local
> directory.
> The directory then gets picked up by a company process and gets placed
> into a webserver directory some time later.
> 
> The trouble is that no combination of site:site or site:stage seem to
> work.
> Here is the project structure:
> 
> 
> /mvnparentdir   [pom.xml]
> |
> |_project1  [pom.xml]
> |
> |_project2  [pom.xml]
> |
> |...
> 
> /websitedir
> 
> 
> So what combination of settings do I need to specify in the various 
> pom.xml files in order
> to generate the fully formed website in the websitedir directory, which 
> I'm assuming is a
> sibling to the /mvnparentdir directory?
> 
> Thanks
> - Ashley
> 
> ---
> 
> This e-mail may contain confidential and/or privileged information. If
> you are not the intended recipient (or have received this e-mail in
> error) please notify the sender immediately and delete this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden.
> 
> Please refer to http://www.db.com/en/content/eu_disclosures.htm for
> additional EU corporate and regulatory disclosures.
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional 
EU corporate and regulatory disclosures.

RE: maven site multi-module question

[Prystash,John]

Hey Ashley, I've been able to do something similar by putting the
following in the POM of the parent.


  
file://${user.dir}/site
  
   

This puts the site directory inside the parent directory however when I
run site-deploy.

-Original Message-
From: Ashley Williams [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 01, 2008 12:31 PM
To: users@maven.apache.org
Subject: maven site multi-module question

Hi,

I'm having trouble generating a maven site in the directory of my
choosing. I don't want to actually deploy the site (onto a remote
server), but instead I want to copy the resulting website into a local
directory.
The directory then gets picked up by a company process and gets placed
into a webserver directory some time later.

The trouble is that no combination of site:site or site:stage seem to
work.
Here is the project structure:


/mvnparentdir   [pom.xml]
|
|_project1  [pom.xml]
|
|_project2  [pom.xml]
|
|...

/websitedir


So what combination of settings do I need to specify in the various 
pom.xml files in order
to generate the fully formed website in the websitedir directory, which 
I'm assuming is a
sibling to the /mvnparentdir directory?

Thanks
- Ashley

---

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and delete this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

maven site multi-module question

[Ashley Williams]

Hi,

I'm having trouble generating a maven site in the directory of my 
choosing. I don't want to actually deploy
the site (onto a remote server), but instead I want to copy the resulting 
website into a local directory.
The directory then gets picked up by a company process and gets placed 
into a webserver directory
some time later.

The trouble is that no combination of site:site or site:stage seem to 
work.
Here is the project structure:


/mvnparentdir   [pom.xml]
|
|_project1  [pom.xml]
|
|_project2  [pom.xml]
|
|...

/websitedir


So what combination of settings do I need to specify in the various 
pom.xml files in order
to generate the fully formed website in the websitedir directory, which 
I'm assuming is a
sibling to the /mvnparentdir directory?

Thanks
- Ashley

---

This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and delete this e-mail. Any unauthorized copying, 
disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional 
EU corporate and regulatory disclosures.

Multi-module question

[Adam Leggett]

Hi all,

When adding an m2 multi-module project via a url (file based) I always
get multiple continuum projects for the parent and children. Is there a
way to make continuum not add the children as projects? I simply want
the parent to be added.

TIA

Adam

Adam Leggett <[EMAIL PROTECTED]>
Senior Consultant
UPCO
Direct Line: 0113 20 10 631
Fax: 0113 20 10 666





===
The contents of this email are intended for the named addresses and may 
contain confidential and/or privileged material. If received in error, 
please contact UPCO head office on +44(0)113 201 0600 and then delete 
the entire mail from your system. Unauthorised review, distribution, 
disclosure or other use of information could constitute a breach of 
confidence. Your co-operation in this matter is greatly appreciated.

Every effort has been taken to ensure that this email and any 
attachments are virus-free. However, UPCO does not make any warranty 
to this effect, and is not liable for any damage done by an infected 
email message or attachment. UPCO recommends that all emails and 
attachments are checked before opening.

All views or opinions expressed in this electronic message and its 
attachements are those of the sender and do not necessarily reflect 
the views and opinions of The Ultimate People Company Ltd.
===

Re: [m2] multi-module question

[Brett Porter]

Hi Chris,

Yes, you can list a greater depth in two ways:
- add the extra path
- add extra parent poms at different levels, if that is appropriate

For the first, in top:

  g/h
  ...


For the second, it would be this in top:

  g


and in g:

  h


These are effectively the same, but if you have that inheritance
structure the second gives a more natural grouping (eg, you can cd
into "g" and build all its subprojects only).

If you do the first solution, the children poms sohuld have the
following hint in the parent element:


  ...
  top
  ../../pom.xml


The repository is still used if ../../pom.xml is not found or the
versions don't match, but the hint makes it easier to use local
modifcations without installing the parent.

- Brett

On 1/5/06, Chris Berry <[EMAIL PROTECTED]> wrote:
> Greetings,
> Is it possible to specify multiple  in a POM that are "deeper" than
> 1 level.
> In other words, say I have the following structure:
> /top/pom.xml   <== the multi-module POM
> /top/a/b/c/d/pom.xml<== build 1
> /top/a/e/f/pom.xml<== build 2
> /top/g/h/pom.xml  <== build 3
>
> How can I type "maven install" in /top and have build 1,2,3 built
> I have searched the List archives and the site docs, and cannot find any
> pertinent info. My apologies if I missed it...
> Thanks,
> -- Chris
>
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[m2] multi-module question

[Chris Berry]

Greetings,
Is it possible to specify multiple  in a POM that are "deeper" than
1 level.
In other words, say I have the following structure:
/top/pom.xml   <== the multi-module POM
/top/a/b/c/d/pom.xml<== build 1
/top/a/e/f/pom.xml<== build 2
/top/g/h/pom.xml  <== build 3

How can I type "maven install" in /top and have build 1,2,3 built
I have searched the List archives and the site docs, and cannot find any
pertinent info. My apologies if I missed it...
Thanks,
-- Chris