You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Wo...@atosorigin.com on 2008/02/25 14:01:43 UTC

simple question concerning transitive dependencies [Virus checked]

Hi All,

in some projects, we need the same dependencies.
Although there must be a better way, I create a pom by hand containing
those dependencies in my local repository
and declared one dependency in the project to pull in that list.
Unfortunately, it does not work and MAVEN complains, there is no jar file
for this dependency (and there isn't, of cause).

Can someone point me to some docs explaining how to set up these transitive
dependencies ?

And how do I install those into a repository (like archiva) ?

mit freundlichen Grüßen/best regards

Wolfgang Schrecker

"MODEL-DRIVEN DESIGN demands that the model stay in lockstep with the
implementation, but it allows freedom to choose any implementation that
faithfully captures the meaning of the model"
from Eric Evans: Domain-Driven Design p. 230



 --
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
mailto:Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417
 
PS: Besuchen Sie am 21.02.2008 das Achte Kartenforum von Atos Worldline und B+S Card Service.
Infos und Anmeldung unter http://www.kartenforum.de
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstraße 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic data
transmitted by e-mail is not completely guaranteed and that data may be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a letter.
* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *

Re: Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by "simon.kitching@chello.at" <si...@chello.at>.
I'm pretty sure that dependencyManagement settings cannot be imported
from a "dependency" though. They can only be inherited from a parent
pom. So if the original question is really about dependencyManagement,
then the only solution is to use a common parent pom with those settings.

Well, another solution for dependencyManagement is of course to use a
repository that has only the versions that you want to be used. This is
a Frequently Asked Question; search the email archives for "mirrorOf"
for details, and see the maven docs on repositories if this is what is
actually wanted.

Regards,
Simon

Nicole Lacoste schrieb:
> Hi,
>
> Yes sorry I didn't catch that - the other pom should have a dependency
> management not a dependency section!  You want to enforce versions not
> dependencies.
>
> Nicole
>
> On 25/02/2008, simon.kitching@chello.at <si...@chello.at> wrote:
>   
>> Does your setup work when maven is run from the command-line?
>> If so, then that is a bug in the maven-eclipse-plugin, not in maven
>> itself.
>>
>> I'm not entirely convinced that the whole idea of having a block of
>> dependencies that multiple projects depend on is useful. Why would you
>> want such a thing? A project should normally declare exactly the
>> dependencies it needs, no more and no less. It would be odd for several
>> projects to have exactly the same dependencies.
>>
>> Anyway, the obvious way of managing "shared" dependencies (assuming you
>> really want to) would be to have a common parent pom, not by separating
>> out dependencies into a separate pom-project that is used as a dependency.
>>
>> However I cannot see why a pom-only dependency wouldn't work. If it
>> works in maven from the command-line, but the maven-eclipse-plugin
>> cannot handle it, then I suggest you file a bug against the
>> maven-eclipse-plugin.
>>
>> Are you perhaps trying to force specific versions of transient
>> dependencies to be used, eg you are depending on external projects and
>> want to be sure that *if* library Foo is pulled in transiently then a
>> specific version is used? That is handled via dependencyManagement, not
>> dependency declarations...
>>
>> Regards,
>> Simon
>>
>> Wolfgang.Schrecker@atosorigin.com schrieb:
>>     
>>> Hi Nicole,
>>>
>>> Thanks for the prompt reply.
>>> Yes the packaging is POM and it works (therefor) now.
>>> BUT:
>>>       only
>>>              mvn eclipse:eclipse
>>> now just wants to download the jar.
>>>
>>> mit freundlichen Grüßen/best regards
>>>
>>> Wolfgang Schrecker
>>>
>>>
>>>
>>>              "Nicole Lacoste"
>>>              <niki.lacoste@gma
>>>              il.com
>>>                                                    An
>>>                                         "Maven Users List"
>>>              25.02.2008 14:09           <us...@maven.apache.org>
>>>       
>>>                                                                      Kopie
>>>
>>>               Bitte
>>>       
>> antworten                                        Thema
>>     
>>>                     an                  Re: simple question concerning
>>>                "Maven Users             transitive dependencies [Virus
>>>                    List"                checked]
>>>              <users@maven.apac
>>>                   he.org>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Hi Wolfgang,
>>>
>>> Make sure that in the pom that contains the dependencies has right
>>> <packaging>.  It should be pom, if you don't mention packaging the
>>>       
>> default
>>     
>>> is jar.  When you depend on this artifact you need to mention type, I am
>>> not
>>> sure what you put here? Maybe pom too?  We have the same sort of thing,
>>>       
>> but
>>     
>>> we define this artifact as the parent of all our projects.
>>>
>>> Viel Gluck,
>>>
>>> Nicole
>>>
>>> On 25/02/2008, Wolfgang.Schrecker@atosorigin.com <
>>> Wolfgang.Schrecker@atosorigin.com> wrote:
>>>
>>>       
>>>> Hi All,
>>>>
>>>> in some projects, we need the same dependencies.
>>>> Although there must be a better way, I create a pom by hand containing
>>>> those dependencies in my local repository
>>>> and declared one dependency in the project to pull in that list.
>>>> Unfortunately, it does not work and MAVEN complains, there is no jar
>>>>         
>> file
>>     
>>>> for this dependency (and there isn't, of cause).
>>>>
>>>> Can someone point me to some docs explaining how to set up these
>>>> transitive
>>>> dependencies ?
>>>>
>>>> And how do I install those into a repository (like archiva) ?
>>>>
>>>> mit freundlichen Grüßen/best regards
>>>>
>>>> Wolfgang Schrecker
>>>>
>>>>         
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>>     
>
>   


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


Re: Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by Nicole Lacoste <ni...@gmail.com>.
Hi,

Yes sorry I didn't catch that - the other pom should have a dependency
management not a dependency section!  You want to enforce versions not
dependencies.

Nicole

On 25/02/2008, simon.kitching@chello.at <si...@chello.at> wrote:
>
> Does your setup work when maven is run from the command-line?
> If so, then that is a bug in the maven-eclipse-plugin, not in maven
> itself.
>
> I'm not entirely convinced that the whole idea of having a block of
> dependencies that multiple projects depend on is useful. Why would you
> want such a thing? A project should normally declare exactly the
> dependencies it needs, no more and no less. It would be odd for several
> projects to have exactly the same dependencies.
>
> Anyway, the obvious way of managing "shared" dependencies (assuming you
> really want to) would be to have a common parent pom, not by separating
> out dependencies into a separate pom-project that is used as a dependency.
>
> However I cannot see why a pom-only dependency wouldn't work. If it
> works in maven from the command-line, but the maven-eclipse-plugin
> cannot handle it, then I suggest you file a bug against the
> maven-eclipse-plugin.
>
> Are you perhaps trying to force specific versions of transient
> dependencies to be used, eg you are depending on external projects and
> want to be sure that *if* library Foo is pulled in transiently then a
> specific version is used? That is handled via dependencyManagement, not
> dependency declarations...
>
> Regards,
> Simon
>
> Wolfgang.Schrecker@atosorigin.com schrieb:
> > Hi Nicole,
> >
> > Thanks for the prompt reply.
> > Yes the packaging is POM and it works (therefor) now.
> > BUT:
> >       only
> >              mvn eclipse:eclipse
> > now just wants to download the jar.
> >
> > mit freundlichen Grüßen/best regards
> >
> > Wolfgang Schrecker
> >
> >
> >
> >              "Nicole Lacoste"
> >              <niki.lacoste@gma
> >              il.com
> >                                                    An
> >                                         "Maven Users List"
> >              25.02.2008 14:09           <us...@maven.apache.org>
>
> >                                                                      Kopie
> >
> >               Bitte
> antworten                                        Thema
> >                     an                  Re: simple question concerning
> >                "Maven Users             transitive dependencies [Virus
> >                    List"                checked]
> >              <users@maven.apac
> >                   he.org>
> >
> >
> >
> >
> >
> >
> >
> >
> > Hi Wolfgang,
> >
> > Make sure that in the pom that contains the dependencies has right
> > <packaging>.  It should be pom, if you don't mention packaging the
> default
> > is jar.  When you depend on this artifact you need to mention type, I am
> > not
> > sure what you put here? Maybe pom too?  We have the same sort of thing,
> but
> > we define this artifact as the parent of all our projects.
> >
> > Viel Gluck,
> >
> > Nicole
> >
> > On 25/02/2008, Wolfgang.Schrecker@atosorigin.com <
> > Wolfgang.Schrecker@atosorigin.com> wrote:
> >
> >> Hi All,
> >>
> >> in some projects, we need the same dependencies.
> >> Although there must be a better way, I create a pom by hand containing
> >> those dependencies in my local repository
> >> and declared one dependency in the project to pull in that list.
> >> Unfortunately, it does not work and MAVEN complains, there is no jar
> file
> >> for this dependency (and there isn't, of cause).
> >>
> >> Can someone point me to some docs explaining how to set up these
> >> transitive
> >> dependencies ?
> >>
> >> And how do I install those into a repository (like archiva) ?
> >>
> >> mit freundlichen Grüßen/best regards
> >>
> >> Wolfgang Schrecker
> >>
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

Antwort: Re: Antwort: Re: Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by Wo...@atosorigin.com.
Hi Simon,

somewhere in the company there is a group creating something, let's say for
batch import/export.
not all projects need this, but most do.
this [application,component,set of libraries] may be used in at least two
ways:

1.) you include the 15 dependencies from this [application,component,set of
libraries] and you are set.
2.) you include one dependency, which is nothing but a pom in the local
repository, referencing all those 15 dependencies.

when this [application,component,set of libraries] gets updated in just 2
components with two new version numbers,
all from 1.) have to change in their respectice projects the version
numbers accordingly, if they want the changes.
all from 2.) have to change their one component (if they want the changes)
and couldn't care less what exactly in which components have changed.

And it does work, if you set it up by copy/paste/edit in your local
repository.


mit freundlichen Grüßen/best regards

Wolfgang Schrecker

"MODEL-DRIVEN DESIGN demands that the model stay in lockstep with the
implementation, but it allows freedom to choose any implementation that
faithfully captures the meaning of the model"
from Eric Evans: Domain-Driven Design p. 230



 --
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
mailto:Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417
 
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstraße 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic data
transmitted by e-mail is not completely guaranteed and that data may be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a letter.
* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *

Re: Antwort: Re: Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by simon <si...@chello.at>.
On Mon, 2008-02-25 at 18:09 +0100, Wolfgang.Schrecker@atosorigin.com
wrote:
> Hi Simon,
> 
>  yes, I think it does make sense, just as transitive dependencies make
> sense.
> 
>   if you publish a component containing another set of jars and their
> various versions, you may want it to be known as a single version e.g. 3.5
>   and if update your bundle only advance the components version (say to
> 3.5.1)
>   with no need for every deveoper to change the version of every component
> but just the main version (here 3.5->3.5.1).

Sorry Wolfgang bug I still have no idea what you are trying to say here.

There are two types of things that get published:
  * applications
  * libraries

When publishing an application, there is no need to worry about
transitive dependencies; everything the user needs is bundled with the
application and the user really doesn't care what libs are used
internally.

When publishing a library, you publish *just* your code, plus
information about what libs your code needs, and the version-ranges that
are acceptable for it (ie a pom file). The application that uses your
library may well then override your recommended dependency versions if
they prefer to use other versions for any reason.

What exactly is the use-case you are trying to support?

Regards,
Simon


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


Antwort: Re: Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by Wo...@atosorigin.com.
Hi Simon,

 yes, I think it does make sense, just as transitive dependencies make
sense.

  if you publish a component containing another set of jars and their
various versions, you may want it to be known as a single version e.g. 3.5
  and if update your bundle only advance the components version (say to
3.5.1)
  with no need for every deveoper to change the version of every component
but just the main version (here 3.5->3.5.1).

  And of cause you are right, why should a pom only version not work.

 I agree, if it is a bug it is maven-eclipse-plugin ' bug.

mit freundlichen Grüßen/best regards

Wolfgang Schrecker

"MODEL-DRIVEN DESIGN demands that the model stay in lockstep with the
implementation, but it allows freedom to choose any implementation that
faithfully captures the meaning of the model"
from Eric Evans: Domain-Driven Design p. 230



 --
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
mailto:Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


                                                                           
             "simon.kitching@c                                             
             hello.at"                                                     
             <simon.kitching@c                                          An 
             hello.at>                  Maven Users List                   
                                        <us...@maven.apache.org>           
             25.02.2008 15:58                                        Kopie 
                                                                           
                                                                     Thema 
              Bitte antworten           Re: Antwort: Re: simple question   
                    an                  concerning transitive dependencies 
               "Maven Users             [Virus checked]                    
                   List"                                                   
             <users@maven.apac                                             
                  he.org>                                                  
                                                                           
                                                                           
                                                                           




Does your setup work when maven is run from the command-line?
If so, then that is a bug in the maven-eclipse-plugin, not in maven itself.

I'm not entirely convinced that the whole idea of having a block of
dependencies that multiple projects depend on is useful. Why would you
want such a thing? A project should normally declare exactly the
dependencies it needs, no more and no less. It would be odd for several
projects to have exactly the same dependencies.

Anyway, the obvious way of managing "shared" dependencies (assuming you
really want to) would be to have a common parent pom, not by separating
out dependencies into a separate pom-project that is used as a dependency.

However I cannot see why a pom-only dependency wouldn't work. If it
works in maven from the command-line, but the maven-eclipse-plugin
cannot handle it, then I suggest you file a bug against the
maven-eclipse-plugin.

Are you perhaps trying to force specific versions of transient
dependencies to be used, eg you are depending on external projects and
want to be sure that *if* library Foo is pulled in transiently then a
specific version is used? That is handled via dependencyManagement, not
dependency declarations...

Regards,
Simon

Wolfgang.Schrecker@atosorigin.com schrieb:
> Hi Nicole,
>
> Thanks for the prompt reply.
> Yes the packaging is POM and it works (therefor) now.
> BUT:
>       only
>              mvn eclipse:eclipse
> now just wants to download the jar.
>
> mit freundlichen Grüßen/best regards
>
> Wolfgang Schrecker
>
>
>

>              "Nicole Lacoste"

>              <niki.lacoste@gma

>              il.com>
An
>                                         "Maven Users List"

>              25.02.2008 14:09           <us...@maven.apache.org>

>
Kopie
>

>               Bitte antworten
Thema
>                     an                  Re: simple question concerning

>                "Maven Users             transitive dependencies [Virus

>                    List"                checked]

>              <users@maven.apac

>                   he.org>

>

>

>

>

>
>
>
>
> Hi Wolfgang,
>
> Make sure that in the pom that contains the dependencies has right
> <packaging>.  It should be pom, if you don't mention packaging the
default
> is jar.  When you depend on this artifact you need to mention type, I am
> not
> sure what you put here? Maybe pom too?  We have the same sort of thing,
but
> we define this artifact as the parent of all our projects.
>
> Viel Gluck,
>
> Nicole
>
> On 25/02/2008, Wolfgang.Schrecker@atosorigin.com <
> Wolfgang.Schrecker@atosorigin.com> wrote:
>
>> Hi All,
>>
>> in some projects, we need the same dependencies.
>> Although there must be a better way, I create a pom by hand containing
>> those dependencies in my local repository
>> and declared one dependency in the project to pull in that list.
>> Unfortunately, it does not work and MAVEN complains, there is no jar
file
>> for this dependency (and there isn't, of cause).
>>
>> Can someone point me to some docs explaining how to set up these
>> transitive
>> dependencies ?
>>
>> And how do I install those into a repository (like archiva) ?
>>
>> mit freundlichen Grüßen/best regards
>>
>> Wolfgang Schrecker
>>
>


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



 
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstraße 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic data
transmitted by e-mail is not completely guaranteed and that data may be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a letter.
* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *

Re: Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by "simon.kitching@chello.at" <si...@chello.at>.
Does your setup work when maven is run from the command-line?
If so, then that is a bug in the maven-eclipse-plugin, not in maven itself.

I'm not entirely convinced that the whole idea of having a block of
dependencies that multiple projects depend on is useful. Why would you
want such a thing? A project should normally declare exactly the
dependencies it needs, no more and no less. It would be odd for several
projects to have exactly the same dependencies.

Anyway, the obvious way of managing "shared" dependencies (assuming you
really want to) would be to have a common parent pom, not by separating
out dependencies into a separate pom-project that is used as a dependency.

However I cannot see why a pom-only dependency wouldn't work. If it
works in maven from the command-line, but the maven-eclipse-plugin
cannot handle it, then I suggest you file a bug against the
maven-eclipse-plugin.

Are you perhaps trying to force specific versions of transient
dependencies to be used, eg you are depending on external projects and
want to be sure that *if* library Foo is pulled in transiently then a
specific version is used? That is handled via dependencyManagement, not
dependency declarations...

Regards,
Simon

Wolfgang.Schrecker@atosorigin.com schrieb:
> Hi Nicole,
>
> Thanks for the prompt reply.
> Yes the packaging is POM and it works (therefor) now.
> BUT:
>       only
>              mvn eclipse:eclipse
> now just wants to download the jar.
>
> mit freundlichen Grüßen/best regards
>
> Wolfgang Schrecker
>
>
>                                                                            
>              "Nicole Lacoste"                                              
>              <niki.lacoste@gma                                             
>              il.com>                                                    An 
>                                         "Maven Users List"                 
>              25.02.2008 14:09           <us...@maven.apache.org>           
>                                                                      Kopie 
>                                                                            
>               Bitte antworten                                        Thema 
>                     an                  Re: simple question concerning     
>                "Maven Users             transitive dependencies [Virus     
>                    List"                checked]                           
>              <users@maven.apac                                             
>                   he.org>                                                  
>                                                                            
>                                                                            
>                                                                            
>                                                                            
>
>
>
>
> Hi Wolfgang,
>
> Make sure that in the pom that contains the dependencies has right
> <packaging>.  It should be pom, if you don't mention packaging the default
> is jar.  When you depend on this artifact you need to mention type, I am
> not
> sure what you put here? Maybe pom too?  We have the same sort of thing, but
> we define this artifact as the parent of all our projects.
>
> Viel Gluck,
>
> Nicole
>
> On 25/02/2008, Wolfgang.Schrecker@atosorigin.com <
> Wolfgang.Schrecker@atosorigin.com> wrote:
>   
>> Hi All,
>>
>> in some projects, we need the same dependencies.
>> Although there must be a better way, I create a pom by hand containing
>> those dependencies in my local repository
>> and declared one dependency in the project to pull in that list.
>> Unfortunately, it does not work and MAVEN complains, there is no jar file
>> for this dependency (and there isn't, of cause).
>>
>> Can someone point me to some docs explaining how to set up these
>> transitive
>> dependencies ?
>>
>> And how do I install those into a repository (like archiva) ?
>>
>> mit freundlichen Grüßen/best regards
>>
>> Wolfgang Schrecker
>>     
>


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


Antwort: Re: simple question concerning transitive dependencies [Virus checked]

Posted by Wo...@atosorigin.com.
Hi Nicole,

Thanks for the prompt reply.
Yes the packaging is POM and it works (therefor) now.
BUT:
      only
             mvn eclipse:eclipse
now just wants to download the jar.

mit freundlichen Grüßen/best regards

Wolfgang Schrecker

"MODEL-DRIVEN DESIGN demands that the model stay in lockstep with the
implementation, but it allows freedom to choose any implementation that
faithfully captures the meaning of the model"
from Eric Evans: Domain-Driven Design p. 230



 --
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstrasse 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
mailto:Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


                                                                           
             "Nicole Lacoste"                                              
             <niki.lacoste@gma                                             
             il.com>                                                    An 
                                        "Maven Users List"                 
             25.02.2008 14:09           <us...@maven.apache.org>           
                                                                     Kopie 
                                                                           
              Bitte antworten                                        Thema 
                    an                  Re: simple question concerning     
               "Maven Users             transitive dependencies [Virus     
                   List"                checked]                           
             <users@maven.apac                                             
                  he.org>                                                  
                                                                           
                                                                           
                                                                           
                                                                           




Hi Wolfgang,

Make sure that in the pom that contains the dependencies has right
<packaging>.  It should be pom, if you don't mention packaging the default
is jar.  When you depend on this artifact you need to mention type, I am
not
sure what you put here? Maybe pom too?  We have the same sort of thing, but
we define this artifact as the parent of all our projects.

Viel Gluck,

Nicole

On 25/02/2008, Wolfgang.Schrecker@atosorigin.com <
Wolfgang.Schrecker@atosorigin.com> wrote:
>
> Hi All,
>
> in some projects, we need the same dependencies.
> Although there must be a better way, I create a pom by hand containing
> those dependencies in my local repository
> and declared one dependency in the project to pull in that list.
> Unfortunately, it does not work and MAVEN complains, there is no jar file
> for this dependency (and there isn't, of cause).
>
> Can someone point me to some docs explaining how to set up these
> transitive
> dependencies ?
>
> And how do I install those into a repository (like archiva) ?
>
> mit freundlichen Grüßen/best regards
>
> Wolfgang Schrecker
>
> "MODEL-DRIVEN DESIGN demands that the model stay in lockstep with the
> implementation, but it allows freedom to choose any implementation that
> faithfully captures the meaning of the model"
> from Eric Evans: Domain-Driven Design p. 230
>
>
>
>   --
> --------------------------------------------------
>
> Atos Worldline Processing GmbH
> Hahnstrasse 25
> 60528 Frankfurt/Main
> Germany
> Phone: +49 69/6657-1176
> mailto:Wolfgang.Schrecker@atosorigin.com
> http://www.atosworldline.com
>
> Geschäftsführer: Erik Munk Koefoed
> Aufsichtsratsvorsitzender: Didier Dhennin
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister: Frankfurt/Main HRB 40 417
>
> PS: Besuchen Sie am 21.02.2008 das Achte Kartenforum von Atos Worldline
> und B+S Card Service.
> Infos und Anmeldung unter http://www.kartenforum.de
> --------------------------------------------------
>
> Atos Worldline Processing GmbH
> Hahnstraße 25
> 60528 Frankfurt/Main
> Germany
> Phone: +49 69/6657-1176
> Fax :
> mailto: Wolfgang.Schrecker@atosorigin.com
> http://www.atosworldline.com
>
> Geschäftsführer: Erik Munk Koefoed
> Aufsichtsratsvorsitzender: Didier Dhennin
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister: Frankfurt/Main HRB 40 417
>
>
> * * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
> This e-mail is destined for the above mentioned recipient. In case you
> received this e-mail by accident, we would appreciate it if you could
> contact the sender and delete all copies stored on your computer.
> Please be aware that the security and confidentiality of electronic data
> transmitted by e-mail is not completely guaranteed and that data may be
> seen,
> copied, downloaded or changed by third persons during transmission.
> Atos Origin accepts no liability for the security and confidentiality of
> data and documents sent by e-mail. Please make sure that all important
> messages will be confirmed in writing by means of a telefax or a letter.
> * * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
>

 
--------------------------------------------------

Atos Worldline Processing GmbH
Hahnstraße 25
60528 Frankfurt/Main
Germany
Phone: +49 69/6657-1176
Fax :
mailto: Wolfgang.Schrecker@atosorigin.com
http://www.atosworldline.com

Geschäftsführer: Erik Munk Koefoed
Aufsichtsratsvorsitzender: Didier Dhennin
Sitz der Gesellschaft: Frankfurt/Main
Handelsregister: Frankfurt/Main HRB 40 417


* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
This e-mail is destined for the above mentioned recipient. In case you
received this e-mail by accident, we would appreciate it if you could
contact the sender and delete all copies stored on your computer.
Please be aware that the security and confidentiality of electronic data
transmitted by e-mail is not completely guaranteed and that data may be seen,
copied, downloaded or changed by third persons during transmission.
Atos Origin accepts no liability for the security and confidentiality of
data and documents sent by e-mail. Please make sure that all important
messages will be confirmed in writing by means of a telefax or a letter.
* * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *

Re: simple question concerning transitive dependencies [Virus checked]

Posted by Nicole Lacoste <ni...@gmail.com>.
Hi Wolfgang,

Make sure that in the pom that contains the dependencies has right
<packaging>.  It should be pom, if you don't mention packaging the default
is jar.  When you depend on this artifact you need to mention type, I am not
sure what you put here? Maybe pom too?  We have the same sort of thing, but
we define this artifact as the parent of all our projects.

Viel Gluck,

Nicole

On 25/02/2008, Wolfgang.Schrecker@atosorigin.com <
Wolfgang.Schrecker@atosorigin.com> wrote:
>
> Hi All,
>
> in some projects, we need the same dependencies.
> Although there must be a better way, I create a pom by hand containing
> those dependencies in my local repository
> and declared one dependency in the project to pull in that list.
> Unfortunately, it does not work and MAVEN complains, there is no jar file
> for this dependency (and there isn't, of cause).
>
> Can someone point me to some docs explaining how to set up these
> transitive
> dependencies ?
>
> And how do I install those into a repository (like archiva) ?
>
> mit freundlichen Grüßen/best regards
>
> Wolfgang Schrecker
>
> "MODEL-DRIVEN DESIGN demands that the model stay in lockstep with the
> implementation, but it allows freedom to choose any implementation that
> faithfully captures the meaning of the model"
> from Eric Evans: Domain-Driven Design p. 230
>
>
>
>   --
> --------------------------------------------------
>
> Atos Worldline Processing GmbH
> Hahnstrasse 25
> 60528 Frankfurt/Main
> Germany
> Phone: +49 69/6657-1176
> mailto:Wolfgang.Schrecker@atosorigin.com
> http://www.atosworldline.com
>
> Geschäftsführer: Erik Munk Koefoed
> Aufsichtsratsvorsitzender: Didier Dhennin
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister: Frankfurt/Main HRB 40 417
>
> PS: Besuchen Sie am 21.02.2008 das Achte Kartenforum von Atos Worldline
> und B+S Card Service.
> Infos und Anmeldung unter http://www.kartenforum.de
> --------------------------------------------------
>
> Atos Worldline Processing GmbH
> Hahnstraße 25
> 60528 Frankfurt/Main
> Germany
> Phone: +49 69/6657-1176
> Fax :
> mailto: Wolfgang.Schrecker@atosorigin.com
> http://www.atosworldline.com
>
> Geschäftsführer: Erik Munk Koefoed
> Aufsichtsratsvorsitzender: Didier Dhennin
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister: Frankfurt/Main HRB 40 417
>
>
> * * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
> This e-mail is destined for the above mentioned recipient. In case you
> received this e-mail by accident, we would appreciate it if you could
> contact the sender and delete all copies stored on your computer.
> Please be aware that the security and confidentiality of electronic data
> transmitted by e-mail is not completely guaranteed and that data may be
> seen,
> copied, downloaded or changed by third persons during transmission.
> Atos Origin accepts no liability for the security and confidentiality of
> data and documents sent by e-mail. Please make sure that all important
> messages will be confirmed in writing by means of a telefax or a letter.
> * * * * * * * * L E G A L    D I S C L A I M E R * * * * * * * *
>