Sure, but we then need an extra server :/ And even more setup... So
actually what you are saying that on all setups where you are using
dependencies that are not in the common maven repository you need a
repo manager..

2009/4/21 David Hoffer <dhoff...@gmail.com>:
> Good rule of thumb with maven, don't fight convention.  You need a repo
> manager to deploy so why not use the same for your 4 dependencies?  It
> works.
>
> -Dave
>
> On Tue, Apr 21, 2009 at 6:22 AM, nino martinez wael <
> nino.martinez.w...@gmail.com> wrote:
>
>> Ahh, this works just fine if I keep the repositories relative to the
>> sub project:
>>
>> parent
>> |
>> |--Sub\repo
>> |--Sub\repo
>> |--Sub\repo
>>
>> But is a waste of space..
>>
>> This is a very nice way of adding stuff to dependencies that are no
>> available on the public repos, it's also very usefull to deploy things
>> into a CI server where you only have access to the CI server .. So you
>> are saying that I should use a repository manage just to contain the 4
>> dependencies that I have..? It would complicate a lot of things.. I do
>> get the idea to use repository manages, but for just 4 deps, it seems
>> overkill.
>>
>> Anyhow is it a bug that it can be use that way?
>>
>> regards
>>
>>
>> 2009/4/21 Stephen Connolly <stephen.alan.conno...@gmail.com>:
>> > Here's what you are doing wrong:
>> >
>> > you are trying to do things the ANT way (i.e. let's check in a
>> > directory of jars into SCM) using Maven.
>> >
>> > Use a repository manager and don't keep a local repo contained within
>> > your project.
>> >
>> > ;-)
>> >
>> > -Stephen
>> >
>> > 2009/4/21 nino martinez wael <nino.martinez.w...@gmail.com>:
>> >> Hi
>> >>
>> >> I have a multimodule project where I have a local repo contained
>> >> within the project currently it's defined as this:
>> >>
>> >>        <repositories>
>> >>                <repository>
>> >>                        <releases>
>> >>                                <checksumPolicy>warn</checksumPolicy>
>> >>                                <enabled>true</enabled>
>> >>                                <updatePolicy>interval:60</updatePolicy>
>> >>                        </releases>
>> >>                        <id>local.3rd.party</id>
>> >>                        <name>Local 3rd Party repo</name>
>> >>                        <url>file://${basedir}/repo</url>
>> >>                </repository>
>> >>        </repositories>
>> >>
>> >> In my parent pom.xml however that generates a structure relative to
>> >> the sub projects like this:
>> >>
>> >> parent
>> >> |
>> >> |--Sub\repo
>> >>
>> >> however what I want are this:
>> >>
>> >> parent
>> >> |
>> >> |-Repo\dependencies
>> >> |-Sub
>> >>
>> >> I've tried substituting basedir with project.parent.basedir, it's not
>> >> working... What am I doing wrong?
>> >>
>> >> regards Nino
>> >>
>> >> ---------------------------------------------------------------------
>> >> 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
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> 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

Reply via email to