Maven initial deploy on production server

2009-12-23 Thread eyal edri
Hi,

i'm looking for the best way to install maven on a production system.
I've already set up the development environment including:

   - maven2
   - artifactory
   - hudson


now i want to be able to give our guys that manages the center servers a
script/pkg so they could install without knowing maven at all,
which after that we'll be able to install java maven projects on the
servers.

what i had in mind was maybe creating an rpm and deploy it to our yum
repository, this rpm could include:

1. maven (the untarred 2.2.1 version).
2. bash script that will set up M2_HOME
3. a pre-defined settings.xml that will define the url for the maven
repository.

does that sound right? am i missing anything?

thanks!



-- 
Eyal Edri


Re: Maven initial deploy on production server

2009-12-23 Thread Henri Gomez
You should find all of these RPMs on :

http://www.jpackage.org/


2009/12/23 eyal edri eyal.e...@gmail.com:
 Hi,

 i'm looking for the best way to install maven on a production system.
 I've already set up the development environment including:

   - maven2
   - artifactory
   - hudson


 now i want to be able to give our guys that manages the center servers a
 script/pkg so they could install without knowing maven at all,
 which after that we'll be able to install java maven projects on the
 servers.

 what i had in mind was maybe creating an rpm and deploy it to our yum
 repository, this rpm could include:

 1. maven (the untarred 2.2.1 version).
 2. bash script that will set up M2_HOME
 3. a pre-defined settings.xml that will define the url for the maven
 repository.

 does that sound right? am i missing anything?

 thanks!



 --
 Eyal Edri


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



RE: ear-plugin and profiles: poor cooperation?

2009-12-23 Thread Rebholz Paul
Hi Anders

We need one and the same ear to contain additional jars in testing,
while for release we want to only include the core jars. This is the
rationale in trying to use a profile. If you can advise us on how to
achieve our goal through different means, we'd highly appreciate. 

Cheers, Paul. 

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
Behalf Of Anders Hammar
Sent: Dienstag, 22. Dezember 2009 17:51
To: Maven Users List
Subject: Re: ear-plugin and profiles: poor cooperation?

I believe that the behavior you see is correct. Maybe not what you want
though...:-)
If you explain why you sometimes would like to add more jars wee could
suggest a different solution.

/Anders

On Tue, Dec 22, 2009 at 16:12, Rebholz Paul
paul.rebh...@six-group.comwrote:

  Hi all!
 
  We have a project producing an ear artifact. The contents of the ear
  file are configured with the maven-ear-plugin. In profiles we want
to
  be able to flexibly add more artifacts to the ear file as shown in
the
  example below. Our tests so far revealed a different behaviour than
  expected. When adding a jar file with the jarModule element, all
other
  entries corresponding to jarModules disappear in the application.xml
  and even some other jar files disappear completely from the ear.
  Moreover, when adding a second profile adding jars, the first is
  eclipsed. Is this a bug in the maven-ear-plugin implementation?
 
  Regards, Paul
 
 
  profile
idmy_test/id
activation
  property
namemy_switch/name
valuetrue/value
  /property
/activation
build
  plugins
plugin
  artifactIdmaven-ear-plugin/artifactId
  configuration
modules
  jarModule
groupIdquartz/groupId
artifactIdquartz/artifactId
 
  includeInApplicationXmltrue/includeInApplicationXml
  /jarModule
/modules
  /configuration
/plugin
  /plugins
/build
dependencies
  dependency
groupIdquartz/groupId
artifactIdquartz/artifactId
typejar/type
version1.5.2/version
  /dependency
/dependencies
  /profile

 This message is for the named person's use only. It may contain
 confidential, proprietary or legally privileged information. If you
receive
 this message in error, please notify the sender urgently and then
 immediately delete the message and any copies of it from your system.
Please
 also immediately destroy any hardcopies of the message.
 The sender's company reserves the right to monitor all e-mail
 communications through their networks.

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



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



Re: Maven initial deploy on production server

2009-12-23 Thread eyal edri
I've set up the jpackage repo on my server.

i don't quite understand how this helps me install the production system.
ok, i can now install various java pkg and maven pkg from the jpackage repo,
but i will have the artifactory for that (after maven will be installed).

does jpackage servers another purpose other than being an updated yum
repository for java pkgs?

thanks,

On Wed, Dec 23, 2009 at 11:48 AM, Henri Gomez henri.go...@gmail.com wrote:

 You should find all of these RPMs on :

 http://www.jpackage.org/


 2009/12/23 eyal edri eyal.e...@gmail.com:
  Hi,
 
  i'm looking for the best way to install maven on a production system.
  I've already set up the development environment including:
 
- maven2
- artifactory
- hudson
 
 
  now i want to be able to give our guys that manages the center servers a
  script/pkg so they could install without knowing maven at all,
  which after that we'll be able to install java maven projects on the
  servers.
 
  what i had in mind was maybe creating an rpm and deploy it to our yum
  repository, this rpm could include:
 
  1. maven (the untarred 2.2.1 version).
  2. bash script that will set up M2_HOME
  3. a pre-defined settings.xml that will define the url for the maven
  repository.
 
  does that sound right? am i missing anything?
 
  thanks!
 
 
 
  --
  Eyal Edri
 

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




-- 
Eyal Edri


Re: Maven initial deploy on production server

2009-12-23 Thread Henri Gomez
 I've set up the jpackage repo on my server.

 i don't quite understand how this helps me install the production system.
 ok, i can now install various java pkg and maven pkg from the jpackage repo,
 but i will have the artifactory for that (after maven will be installed).

 does jpackage servers another purpose other than being an updated yum
 repository for java pkgs?

A question for the jpackage user list but some answers here :

- consistent filesystem structure (convention instead of configuration)

- of course regular updates

If you wonder about replicable installation processes, you spoke about
doing your own RPMs, jpackage will probably help you to mimic
configuration on all your machines/vm.

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



Re: java 1.4 versus the maven-eclipse-plugin

2009-12-23 Thread Barrie Treloar
On Wed, Dec 23, 2009 at 8:59 AM, Benson Margulies bimargul...@gmail.com wrote:
 A parent pom which I thought was setting source/target for all modules
 was not. This was masked by the fact that some of the other modules
 have their own settings of source/target. So, what I thought was the
 eclipse plugin enforcing the old policy of maven plugins running under
 1.4 was really just what you said it was.

Excellent.

mvn help:effective-pom

will display what maven is using for all the settings.
Unfortunately I dont think it tells you where it gets all these values
from, but after seeing the output not match what you expect then you
can chase the dragon's tail (like you did) to see where it is being
set incorrectly.

Glad its all sorted.

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



EAR assembly as part of an EJB project

2009-12-23 Thread CS Wong
Hi,

Would just like to find out: is it possibly to have an EAR assembly inside
an EJB Maven project? It's really quite a hassle to create another POM
declaration to package the EJB into an EAR. Creating the EAR project isn't
the hassle, maintaining it is. If I can contain it within one project,
that'll be very nice. I know I can use multi-module projects, in fact, I'm
doing so right now, but I'd like to see if there' an even simpler solution.

Thanks!
Wong


Re: ear-plugin and profiles: poor cooperation?

2009-12-23 Thread Anders Hammar
Well, first I would work very hard to be able to use the EXACT same ear in
both testing and production. You want to test the very same thing that you
put in production, IMO.

Instead of using profiles, I would have two different projects - one
producing the ear for testing and the other producing the one for
production. By doing so you can produce both ears in one build. Possibly you
could just have one project and produce the ear for production as the
primary artifact and then the one for testing with a classifier. Having two
different projects is probably easier.

/Anders

On Wed, Dec 23, 2009 at 10:54, Rebholz Paul paul.rebh...@six-group.comwrote:

 Hi Anders

 We need one and the same ear to contain additional jars in testing,
 while for release we want to only include the core jars. This is the
 rationale in trying to use a profile. If you can advise us on how to
 achieve our goal through different means, we'd highly appreciate.

 Cheers, Paul.

 -Original Message-
 From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
 Behalf Of Anders Hammar
 Sent: Dienstag, 22. Dezember 2009 17:51
 To: Maven Users List
 Subject: Re: ear-plugin and profiles: poor cooperation?

 I believe that the behavior you see is correct. Maybe not what you want
 though...:-)
 If you explain why you sometimes would like to add more jars wee could
 suggest a different solution.

 /Anders

 On Tue, Dec 22, 2009 at 16:12, Rebholz Paul
 paul.rebh...@six-group.comwrote:

   Hi all!
  
   We have a project producing an ear artifact. The contents of the ear
   file are configured with the maven-ear-plugin. In profiles we want
 to
   be able to flexibly add more artifacts to the ear file as shown in
 the
   example below. Our tests so far revealed a different behaviour than
   expected. When adding a jar file with the jarModule element, all
 other
   entries corresponding to jarModules disappear in the application.xml
   and even some other jar files disappear completely from the ear.
   Moreover, when adding a second profile adding jars, the first is
   eclipsed. Is this a bug in the maven-ear-plugin implementation?
  
   Regards, Paul
  
  
   profile
 idmy_test/id
 activation
   property
 namemy_switch/name
 valuetrue/value
   /property
 /activation
 build
   plugins
 plugin
   artifactIdmaven-ear-plugin/artifactId
   configuration
 modules
   jarModule
 groupIdquartz/groupId
 artifactIdquartz/artifactId
  
   includeInApplicationXmltrue/includeInApplicationXml
   /jarModule
 /modules
   /configuration
 /plugin
   /plugins
 /build
 dependencies
   dependency
 groupIdquartz/groupId
 artifactIdquartz/artifactId
 typejar/type
 version1.5.2/version
   /dependency
 /dependencies
   /profile
 
  This message is for the named person's use only. It may contain
  confidential, proprietary or legally privileged information. If you
 receive
  this message in error, please notify the sender urgently and then
  immediately delete the message and any copies of it from your system.
 Please
  also immediately destroy any hardcopies of the message.
  The sender's company reserves the right to monitor all e-mail
  communications through their networks.
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 

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




Re: EAR assembly as part of an EJB project

2009-12-23 Thread Anders Hammar
No, there isn't. One Maven project only produces ONE artifact.

/Anders

On Wed, Dec 23, 2009 at 13:29, CS Wong lilw...@gmail.com wrote:

 Hi,

 Would just like to find out: is it possibly to have an EAR assembly inside
 an EJB Maven project? It's really quite a hassle to create another POM
 declaration to package the EJB into an EAR. Creating the EAR project isn't
 the hassle, maintaining it is. If I can contain it within one project,
 that'll be very nice. I know I can use multi-module projects, in fact, I'm
 doing so right now, but I'd like to see if there' an even simpler solution.

 Thanks!
 Wong



typepom/type not working

2009-12-23 Thread TomerL

Hi all,

I have a a project with several modules, all with the same version and
groupId. One of the modules is a pom project contains several other projects
which are jars projects. I managed to build this module and the repository
contains the required artifacts.

When I try to add a dependency for this module:

dependencies
dependency
  groupIdabc/groupId
  artifactIdlanguage/artifactId
  version1.0/version
  typepom/type
/dependency
  /dependencies

The artifact is found but the jars within are not in the classpath and i get
a compilation error.

Is there some limitation on using the pom type dependency within the same
project? I have used it with scala so maybe there is some incompatibility
with the scala compiler.

Thanks,
Tomer
-- 
View this message in context: 
http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: typepom/type not working

2009-12-23 Thread Baptiste MATHUS
You might have a good reason for that, but why are you trying to add a pom
in the classpath?
Do you need to parse it at runtime?

Cheers.

2009/12/23 TomerL shaoli...@gmail.com


 Hi all,

 I have a a project with several modules, all with the same version and
 groupId. One of the modules is a pom project contains several other
 projects
 which are jars projects. I managed to build this module and the repository
 contains the required artifacts.

 When I try to add a dependency for this module:

 dependencies
dependency
  groupIdabc/groupId
  artifactIdlanguage/artifactId
  version1.0/version
  typepom/type
/dependency
  /dependencies

 The artifact is found but the jars within are not in the classpath and i
 get
 a compilation error.

 Is there some limitation on using the pom type dependency within the same
 project? I have used it with scala so maybe there is some incompatibility
 with the scala compiler.

 Thanks,
 Tomer
 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !


Re: typepom/type not working

2009-12-23 Thread TomerL

Maybe I am doing something completely wrong. I have read that I can
automatically add the modules within another module (which is defined as
pom) as dependencies if I put a dependency for that pom module and add the
typepom/type tag. I try only to have the jars defined as submodules of
the pom project in the classpath.

Thanks,
Tomer


Baptiste MATHUS wrote:
 
 You might have a good reason for that, but why are you trying to add a pom
 in the classpath?
 Do you need to parse it at runtime?
 
 Cheers.
 
 2009/12/23 TomerL shaoli...@gmail.com
 

 Hi all,

 I have a a project with several modules, all with the same version and
 groupId. One of the modules is a pom project contains several other
 projects
 which are jars projects. I managed to build this module and the
 repository
 contains the required artifacts.

 When I try to add a dependency for this module:

 dependencies
dependency
  groupIdabc/groupId
  artifactIdlanguage/artifactId
  version1.0/version
  typepom/type
/dependency
  /dependencies

 The artifact is found but the jars within are not in the classpath and i
 get
 a compilation error.

 Is there some limitation on using the pom type dependency within the same
 project? I have used it with scala so maybe there is some incompatibility
 with the scala compiler.

 Thanks,
 Tomer
 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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


 
 
 -- 
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 
 

-- 
View this message in context: 
http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902438.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: typepom/type not working

2009-12-23 Thread Baptiste MATHUS
Well, not sure to understand.
If you want to build a multimodules project, that is: a projet composed of
several projects, then you should use modules tag in you parent pom.
But generally you won't depend on a pom project.

Adding dependencies on a parent pom is also used to centralize dependencies
declaration for all submodules of that pom.

Could you still clarify a bit more what you want to do?

Cheers

2009/12/23 TomerL shaoli...@gmail.com


 Maybe I am doing something completely wrong. I have read that I can
 automatically add the modules within another module (which is defined as
 pom) as dependencies if I put a dependency for that pom module and add the
 typepom/type tag. I try only to have the jars defined as submodules of
 the pom project in the classpath.

 Thanks,
 Tomer


 Baptiste MATHUS wrote:
 
  You might have a good reason for that, but why are you trying to add a
 pom
  in the classpath?
  Do you need to parse it at runtime?
 
  Cheers.
 
  2009/12/23 TomerL shaoli...@gmail.com
 
 
  Hi all,
 
  I have a a project with several modules, all with the same version and
  groupId. One of the modules is a pom project contains several other
  projects
  which are jars projects. I managed to build this module and the
  repository
  contains the required artifacts.
 
  When I try to add a dependency for this module:
 
  dependencies
 dependency
   groupIdabc/groupId
   artifactIdlanguage/artifactId
   version1.0/version
   typepom/type
 /dependency
   /dependencies
 
  The artifact is found but the jars within are not in the classpath and i
  get
  a compilation error.
 
  Is there some limitation on using the pom type dependency within the
 same
  project? I have used it with scala so maybe there is some
 incompatibility
  with the scala compiler.
 
  Thanks,
  Tomer
  --
  View this message in context:
 
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
  Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !
 
 

 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902438.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !


Re: typepom/type not working

2009-12-23 Thread TomerL

Thanks for your help. As I explain very badly, I will give an example:

I have a module with the following pom.xml

artifactIdlanguage/artifactId
 modules
modulelambda/module
modulehol/module
modulefol/module
  /modules

In another module I would like to create a dependency to all the submodules
of language:

dependency
  groupId../groupId
  artifactIdlanguage/artifactId
  version1.0/version
  typepom/type
/dependency

So automatically lambda, hol and fol will be added as dependencies. I get no
error from maven about this but the scala compiler tells me it cannot find
specific classes within the jars of lambda, hol and fol. when I do instead:

dependency
  groupId../groupId
  artifactIdlambda/artifactId
  version1.0/version
/dependency

etc.

it works OK.

I was wondering if I am not using this recursive dependency correctly.

Thanks again for your help,
Tomer


Baptiste MATHUS wrote:
 
 Well, not sure to understand.
 If you want to build a multimodules project, that is: a projet composed of
 several projects, then you should use modules tag in you parent pom.
 But generally you won't depend on a pom project.
 
 Adding dependencies on a parent pom is also used to centralize
 dependencies
 declaration for all submodules of that pom.
 
 Could you still clarify a bit more what you want to do?
 
 Cheers
 
 2009/12/23 TomerL shaoli...@gmail.com
 

 Maybe I am doing something completely wrong. I have read that I can
 automatically add the modules within another module (which is defined as
 pom) as dependencies if I put a dependency for that pom module and add
 the
 typepom/type tag. I try only to have the jars defined as submodules
 of
 the pom project in the classpath.

 Thanks,
 Tomer


 Baptiste MATHUS wrote:
 
  You might have a good reason for that, but why are you trying to add a
 pom
  in the classpath?
  Do you need to parse it at runtime?
 
  Cheers.
 
  2009/12/23 TomerL shaoli...@gmail.com
 
 
  Hi all,
 
  I have a a project with several modules, all with the same version and
  groupId. One of the modules is a pom project contains several other
  projects
  which are jars projects. I managed to build this module and the
  repository
  contains the required artifacts.
 
  When I try to add a dependency for this module:
 
  dependencies
 dependency
   groupIdabc/groupId
   artifactIdlanguage/artifactId
   version1.0/version
   typepom/type
 /dependency
   /dependencies
 
  The artifact is found but the jars within are not in the classpath and
 i
  get
  a compilation error.
 
  Is there some limitation on using the pom type dependency within the
 same
  project? I have used it with scala so maybe there is some
 incompatibility
  with the scala compiler.
 
  Thanks,
  Tomer
  --
  View this message in context:
 
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
  Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !
 
 

 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902438.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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


 
 
 -- 
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 
 

-- 
View this message in context: 
http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26903026.html
Sent from the Maven - Users mailing list archive at Nabble.com.


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



Re: typepom/type not working

2009-12-23 Thread kristian
as far I understand (so did not try it) but you can use composition
but the ONLY the dependencies from pom dependency will be included, in
the same fashion as maven resolve transitive dependencies.

in your example I you would need a pom with three dependencies to
lambda, hol and fol and reference that pom via a dependencies.

the modules do not play any role in dependency resolution (as far I know).

with regards,
Kristian


On Wed, Dec 23, 2009 at 8:10 PM, TomerL shaoli...@gmail.com wrote:

 Thanks for your help. As I explain very badly, I will give an example:

 I have a module with the following pom.xml

 artifactIdlanguage/artifactId
  modules
    modulelambda/module
    modulehol/module
    modulefol/module
  /modules

 In another module I would like to create a dependency to all the submodules
 of language:

 dependency
      groupId../groupId
      artifactIdlanguage/artifactId
      version1.0/version
      typepom/type
 /dependency

 So automatically lambda, hol and fol will be added as dependencies. I get no
 error from maven about this but the scala compiler tells me it cannot find
 specific classes within the jars of lambda, hol and fol. when I do instead:

 dependency
      groupId../groupId
      artifactIdlambda/artifactId
      version1.0/version
 /dependency

 etc.

 it works OK.

 I was wondering if I am not using this recursive dependency correctly.

 Thanks again for your help,
 Tomer


 Baptiste MATHUS wrote:

 Well, not sure to understand.
 If you want to build a multimodules project, that is: a projet composed of
 several projects, then you should use modules tag in you parent pom.
 But generally you won't depend on a pom project.

 Adding dependencies on a parent pom is also used to centralize
 dependencies
 declaration for all submodules of that pom.

 Could you still clarify a bit more what you want to do?

 Cheers

 2009/12/23 TomerL shaoli...@gmail.com


 Maybe I am doing something completely wrong. I have read that I can
 automatically add the modules within another module (which is defined as
 pom) as dependencies if I put a dependency for that pom module and add
 the
 typepom/type tag. I try only to have the jars defined as submodules
 of
 the pom project in the classpath.

 Thanks,
 Tomer


 Baptiste MATHUS wrote:
 
  You might have a good reason for that, but why are you trying to add a
 pom
  in the classpath?
  Do you need to parse it at runtime?
 
  Cheers.
 
  2009/12/23 TomerL shaoli...@gmail.com
 
 
  Hi all,
 
  I have a a project with several modules, all with the same version and
  groupId. One of the modules is a pom project contains several other
  projects
  which are jars projects. I managed to build this module and the
  repository
  contains the required artifacts.
 
  When I try to add a dependency for this module:
 
  dependencies
     dependency
       groupIdabc/groupId
       artifactIdlanguage/artifactId
       version1.0/version
       typepom/type
     /dependency
   /dependencies
 
  The artifact is found but the jars within are not in the classpath and
 i
  get
  a compilation error.
 
  Is there some limitation on using the pom type dependency within the
 same
  project? I have used it with scala so maybe there is some
 incompatibility
  with the scala compiler.
 
  Thanks,
  Tomer
  --
  View this message in context:
 
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
  Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !
 
 

 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902438.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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




 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !



 --
 View this message in context: 
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26903026.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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





-- 
Kristian Meier + Saumya Sharma + Sanuka Meier
Vadakkethu House,
Edayanmula West PO - 689532,
Pathanamthitta District, Kerala, INDIA

tel: +91 468 2319577

protect your privacy while searching the net: www.ixquick.com

 _=_
   q(-_-)p
'_) (_`
/__/  \
 _(_   / )_
  (__\_\_|_/__)


Re: typepom/type not working

2009-12-23 Thread TomerL

Thanks!

I was not aware of that. 


kristian-2 wrote:
 
 as far I understand (so did not try it) but you can use composition
 but the ONLY the dependencies from pom dependency will be included, in
 the same fashion as maven resolve transitive dependencies.
 
 in your example I you would need a pom with three dependencies to
 lambda, hol and fol and reference that pom via a dependencies.
 
 the modules do not play any role in dependency resolution (as far I know).
 
 with regards,
 Kristian
 
 
 On Wed, Dec 23, 2009 at 8:10 PM, TomerL shaoli...@gmail.com wrote:

 Thanks for your help. As I explain very badly, I will give an example:

 I have a module with the following pom.xml

 artifactIdlanguage/artifactId
  modules
    modulelambda/module
    modulehol/module
    modulefol/module
  /modules

 In another module I would like to create a dependency to all the
 submodules
 of language:

 dependency
      groupId../groupId
      artifactIdlanguage/artifactId
      version1.0/version
      typepom/type
 /dependency

 So automatically lambda, hol and fol will be added as dependencies. I get
 no
 error from maven about this but the scala compiler tells me it cannot
 find
 specific classes within the jars of lambda, hol and fol. when I do
 instead:

 dependency
      groupId../groupId
      artifactIdlambda/artifactId
      version1.0/version
 /dependency

 etc.

 it works OK.

 I was wondering if I am not using this recursive dependency correctly.

 Thanks again for your help,
 Tomer


 Baptiste MATHUS wrote:

 Well, not sure to understand.
 If you want to build a multimodules project, that is: a projet composed
 of
 several projects, then you should use modules tag in you parent pom.
 But generally you won't depend on a pom project.

 Adding dependencies on a parent pom is also used to centralize
 dependencies
 declaration for all submodules of that pom.

 Could you still clarify a bit more what you want to do?

 Cheers

 2009/12/23 TomerL shaoli...@gmail.com


 Maybe I am doing something completely wrong. I have read that I can
 automatically add the modules within another module (which is defined
 as
 pom) as dependencies if I put a dependency for that pom module and add
 the
 typepom/type tag. I try only to have the jars defined as submodules
 of
 the pom project in the classpath.

 Thanks,
 Tomer


 Baptiste MATHUS wrote:
 
  You might have a good reason for that, but why are you trying to add
 a
 pom
  in the classpath?
  Do you need to parse it at runtime?
 
  Cheers.
 
  2009/12/23 TomerL shaoli...@gmail.com
 
 
  Hi all,
 
  I have a a project with several modules, all with the same version
 and
  groupId. One of the modules is a pom project contains several other
  projects
  which are jars projects. I managed to build this module and the
  repository
  contains the required artifacts.
 
  When I try to add a dependency for this module:
 
  dependencies
     dependency
       groupIdabc/groupId
       artifactIdlanguage/artifactId
       version1.0/version
       typepom/type
     /dependency
   /dependencies
 
  The artifact is found but the jars within are not in the classpath
 and
 i
  get
  a compilation error.
 
  Is there some limitation on using the pom type dependency within the
 same
  project? I have used it with scala so maybe there is some
 incompatibility
  with the scala compiler.
 
  Thanks,
  Tomer
  --
  View this message in context:
 
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902026.html
  Sent from the Maven - Users mailing list archive at Nabble.com.
 
 
 
 -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  --
  Baptiste Batmat MATHUS - http://batmat.net
  Sauvez un arbre,
  Mangez un castor !
 
 

 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26902438.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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




 --
 Baptiste Batmat MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !



 --
 View this message in context:
 http://old.nabble.com/%3Ctype%3Epom%3C-type%3E-not-working-tp26902026p26903026.html
 Sent from the Maven - Users mailing list archive at Nabble.com.


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


 
 
 
 -- 
 Kristian Meier + Saumya Sharma + Sanuka Meier
 Vadakkethu House,
 Edayanmula West PO - 689532,
 Pathanamthitta District, Kerala, INDIA
 
 tel: +91 468 2319577
 
 protect your privacy while searching the net: www.ixquick.com
 
  _=_

Specifying maven-assembly-plugin descriptors from separate profiles

2009-12-23 Thread Ricky Clarkson
Hi,

I have one profile, windows, which configures the
maven-assembly-plugin with the src/main/assembly/win32.xml assembly
descriptor, and another profile, installer, which configures it with
the src/main/assembly/executable.xml assembly descriptor.
Unfortunately specifying -Pinstaller makes it so that the
effective-pom only refers to the src/main/assembly/executable.xml
descriptor.

Is there a way of making it so that the descriptors get aggregated
rather than replaced when specified from separate profiles, or is
there a better way of going about this problem that I'm missing?

Thanks,
Ricky.

-- 
Ricky Clarkson
Java and Scala Programmer, AD Holdings
Skype: ricky_clarkson
Google Talk: ricky.clark...@gmail.com
Google Wave: ricky.clark...@googlewave.com

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



Re: Specifying maven-assembly-plugin descriptors from separate profiles

2009-12-23 Thread Ricky Clarkson
I think I have an answer.

Have the windows profile set the property
os-specific-descriptorwindows/os-specific-descriptor, then in the
installer profile, specify
descriptor${os-specific-descriptor}/descriptor
descriptorsrc/main/assembly/executable.xml/descriptor.  To reduce
duplication, I'll need a no-installer profile which is activated
whenever installer isn't, but for the moment each OS-specific profile
will specify the descriptor name twice, which is still duplication,
but more localised than before!

Ricky.

2009/12/23 Ricky Clarkson ricky.clark...@gmail.com:
 Hi,

 I have one profile, windows, which configures the
 maven-assembly-plugin with the src/main/assembly/win32.xml assembly
 descriptor, and another profile, installer, which configures it with
 the src/main/assembly/executable.xml assembly descriptor.
 Unfortunately specifying -Pinstaller makes it so that the
 effective-pom only refers to the src/main/assembly/executable.xml
 descriptor.

 Is there a way of making it so that the descriptors get aggregated
 rather than replaced when specified from separate profiles, or is
 there a better way of going about this problem that I'm missing?

 Thanks,
 Ricky.

 --
 Ricky Clarkson
 Java and Scala Programmer, AD Holdings
 Skype: ricky_clarkson
 Google Talk: ricky.clark...@gmail.com
 Google Wave: ricky.clark...@googlewave.com




-- 
Ricky Clarkson
Java and Scala Programmer, AD Holdings
Skype: ricky_clarkson
Google Talk: ricky.clark...@gmail.com
Google Wave: ricky.clark...@googlewave.com

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