Will these listeners be provided with the necessary references (Stream,
etc.) to support artifact transformation? In other words, is this a
super-set of the filtering functionality I described?
On Fri, Sep 5, 2008 at 5:15 PM, Oleg Gusakov
<[EMAIL PROTECTED]>wrote:
>
>
> Shane Isbell wrote:
>
>>
Shane Isbell wrote:
Personally, I'd like to be able
to register listener events within Mercury, if there is say an dotnet:exe
type resolved, I'd like it to invoke a listener (actually a transaction with
a list of listeners, that could provide rollback hooks) that would make the
copies to vario
Within the current 2.0.x releases, Maven provides extensions for downloading
just about any type of artifact, with or without versions in the filenames.
There are, of course, some problems. First the plugins make assumptions
about formats (like versions in the filename). With the exception of
snaps
James Carpenter wrote:
If I wait a few months will all my problems simply disappear with maven
magicially supporting what I need?
As Oleg pointed out: no. Even if Mercury landed today and it were
bug-free, you can bet that a significant portion of the Maven plugin
ecosystem wouldn't work pr
Overview of Slight Mercury Enhancement which Solves the Problem:
If a pre-process filter is supported by the RepositoryWriter and a
post-process filter is supported by the RepositoryReader (equates to the 2nd
solution in the original post) no custom repository manager would be
needed. If I unders
James Carpenter wrote:
Sounds like good news to me.
Can you please define "not too distant a future"? Are you talking days,
weeks, months, quarters? I realize you probably don't have an exact answer.
James, I am working hard to make it weeks, not months. Currently, there
are two pieces s
Sounds like good news to me.
Can you please define "not too distant a future"? Are you talking days,
weeks, months, quarters? I realize you probably don't have an exact answer.
Will Mercury be used to entirely replace the existing
DefaultArtifactResolver mechanism? What I'm really trying to as
James,
There is alternative to the approaches you mentioned:
http://docs.codehaus.org/display/MAVEN/Mercury
This project was started to address, among others, the issues you raise.
What it does in this field - isolate client code from the files -
Resolver operates metadata, not files, Reposi
Introduction:
What mechanism can be used to store artifacts in the repository which are
sensitive to having versions in the filename? This is a concern for certain
artifacts such as .NET assemblies (particularly closed source 3rd party
assemblies) which contain internal meta-data which is aware o
