The reason I'm getting my team to switch to maven2 is beacuse it makes
life easier to do it the 'right way' and more difficult (if not
impossible) to do it the 'wrong way'.
But alas, when all one knows is a source code management tool, every
build artifact looks like source code.
Keep patience and keep explaining the difference.
On 3/10/08, Marco Mistroni <[EMAIL PROTECTED]> wrote:
> hi all,
> was wondering if someone has any ideas or had to deal with similar cases.
>
> my colleague and i are trying to promote maven at our working place....
> using an internal repository
>
> the problem is that people here want to store artifact / external libraries
> in svn rather than in an internal repository
>
> only thing i could think was to store the maven repository in svn and check
> it out every time, pointing maven to
> look at the localRepository in my custom directory
>
> i was not able to find any maven proxy (either Proximity or Artifactory)
> that are linked to svn..
>
> anyone has any suggestions/comments?
>
> thanks in advance and regards
> marco
>
--
ASCII ribbon campaign:
() against HTML email
/\ against Microsoft attachments
Information: http://www.expita.com/nomime.html
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
