Yep, implement a new RepositoryLayout and put it in the M2_HOME/lib
Check the LegacyRepositoryLayout

On 6/26/06, Russell, Mark <[EMAIL PROTECTED]> wrote:
Here is my scenario...



I'm in the process of creating a new project (with some specialized
plugins).  This new project needs to fetch some jars create in-house
from our existing repository which is similar in structure to maven 1.x
repositories (the structure is from the maven 1 alpha days).  The jars
it needs to fetch need to become part of the compile dependencies.
Unfortunately our repository structure IS NOT a maven 1.x structure as
1.x is today.  This means that there is no poms directory.



So my problem is that maven 2.x looks for a .pom file in our existing
repository that simply does not exist, and probably won't unless I
handcraft them.  So my question... Is it possible to define a repository
handler and bind it to a new type (ie instead of legacy, maybe an
inhouse-legacy type) to get around this?



Eventually I intend to convert everything to m2, but that isn't feasible
at this point in time.  Thus if I can't find a way around this, I'm
probably going to need to write a bunch of ant tasks to handle what I
need, which I'd rather not due since I much prefer the m2 plug-in
methodology.





Thanks,



Mark Russell





--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
                            -- The Princess Bride

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to