On 29 Oct 07, at 11:04 AM 29 Oct 07, Brett Porter wrote:
What is the expected behaviour of legacy repository definitions in
2.1?
Not supported. By the time 2.1 is actually released it will have been
well over two years since 2.0. The support can exist in 2.0.x but
anyone starting with 2.1 won't use it and with the conversion tools
and native support in repositories managers it's not required.
I realise much of the handling was removed - is it expected it will
just error out gracefully if one is encountered? Or the repo ignored?
Just warn and continue on its business.
Currently, it appears as if the path gets translated correctly, but
it chokes on the lack of a POM file in the repository (this may also
be an issue with builds that don't have POM files in the m2 repo,
haven't checked).
Just wondering what to file in the bug :)
That it should just ignore it.
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
