Possibly the nexus-dev mailing list is more appropriate for this.
A Nexus plugin is just a Plexus component (or a group of components).
The thing is to figure out what "type" of Plexus component (the role)
you need to implement. I would start by finding the source code for
the existing virtual repo plugins and look at how things are done
there
/Anders
On Wed, May 27, 2009 at 12:36, Rainer Himmeroeder
<
rainer.himmeroeder@...> wrote:
>
> Hi,
>
> we are trying to find a way to use build artefacts residing on a file share
> for Maven builds without deploying them into a Maven repository.
> Of course these build artefacts can be directly deployed into an existing
> Maven repository. However for technical reasons like the mount of data and
> continuous rebuilds we think it is better to omit the deploy step and
> provide (direct) access to the share as a virtual repository.
>
> Therefore our current approach is to write a Nexus plugin that allows adding
> the file share as a virtual repository into Nexus.
> In order to give a proof of this concept we are looking for information that
> explains how to write a Nexus plugin.
> So far we haven’t found comprehensive documentation about this topic.
>
> Could you please point us to information that we can take as starting point
> for Nexus plugin development?
>
> Regards,
> Rainer
>
> --
> View this message in context:
http://www.nabble.com/How-to-add-a-file-share-as-%28virtual%29-repository-into-Nexus-tp23739940p23739940.html> Sent from the Nexus Maven Repository Manager Users List mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
nexus-user-unsubscribe@...
> For additional commands, e-mail:
nexus-user-help@...
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
nexus-user-unsubscribe@...
For additional commands, e-mail:
nexus-user-help@...
