How about this.
- Checkin all your dependencies to SCM using maven format.
Then mirror it to a web server ( use a cron to regularly update the web
server).
- Then specify the web server as one of your repo.
And if one day, you can convince your team, maven repo is safe to use ;-),
then you dont need the SCM for your dependencies any more.
Really, maven repo is basically a SCM for binary dependency. As long as you
can track, and protect it.
-Dan
On 12/7/05, Vernik, Gary <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I am starting a new project and considering using Maven for it. Our
> build team has a requirement that ALL project dependencies have to be
> stored in the source control system along with the project.
> I was thinking of creating a project (C:\MyProject), adding pom
> (C:\MyProject\pom.xml) and creating an internal repository (containing
> all the dependencies) under the project directory
> (C:\MyProject\repository). Then I need to specify the repository in my
> project pom.xml
> <repository>
> <id>my-repo</id>
> <url>file:///C:/MyProject/repository/</url>
> </repository>
>
> And here is the problem: I don't want to hardcode absolute paths in my
> pom.xml (to be platform independent). Is it possible to specify a
> relative path (like <url>file:///./repository/</url>) or create
> environment variable (set MYPROJ=C:/MyProject) and specify that in pom
> (like <url>file:///MYPROJ/repository/</url>)?
>
> I am sure I am not the first person who has to deal with this kind of
> requirements so I'd appreciate any advise.
>
> Thanks,
> Gary
>
>
>
