Not to distract from the higher-level discussion, but I'd like to get
into the nuts and bolts of MARTIFACT-25 a bit...in case someone beats me
to it.
We introduced a properties file that tracks resolution attempts for
artifacts that weren't found on the remote repository, and I'd like to
see if we can reuse that file/concept/code to handle artifacts that
don't have accompanying POMs on the remote repo. It's a similar concept,
so the two should dovetail relatively well, and require little code to
accomplish the fix.
The way I see it, the biggest hurdle for this issue is creating a [set
of] good tests to circumscribe the issue and make sure it doesn't
regress later.
My $0.02.
-john
Brett Porter wrote:
Hi all,
As I indicated a couple of weeks back, moving towards a 2.1 alpha
release, I was looking at releasing an alpha of maven-artifact. Brian
was able to locate the issue he was referring to a couple of weeks
back about re-resolving (now MARTIFACT-25), so I've postponed.
Once that's fixed, I think there should be no reason not to proceed
with a release based on the thread we had back then.
Are there any other issues that anyone sees as blocking moving forward
with a release?
I've done all the testing I was planning to already. Oleg, did you
want to take this release, or shall I go ahead after that issue is
sorted?
Cheers,
Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
