Nexus plugins?

[De Smet Ringo]



Hello,

 

I am using Nexus OpenSource edition. Due to our internal release strategy, we have a whole series of module releases leading to a lot of disk space usage. Since we have parallel releases, we can't just scrape the repository for artifacts older than x days. I would like to have a Scheduled Task that removes all artifacts except the last X within a certain release. As such, I want to configure the task with a repository to scrape, a groupId, a major/minor version combination and the amount of releases to leave in the repository.

 

In SVN, I see the beginnings of a plugin model popping up. Can I already use a Scheduled Task plugin in 1.2.1 or do I have to wait for 1.3?

 

Ringo

*************************************************************

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen.

This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes �ventuelles peuvent contenir des informations confidentielles et/ou prot�g�es par des droits de propri�t� intellectuelle. Ce message est adress� exclusivement � son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou compl�te sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez re�u ce message par erreur, veuillez pr�venir l'exp�diteur du message et en d�truire le contenu.

*************************************************************

[Brian E Fox]

Some parts of this message have been removed. Learn more about Nabble's security policy.

It should be possible to build a scheduled task as a plugin in 1.2.x but I’m not sure if we have any examples to look at. 1.4 will be the next major change with regards to plugin api so it is worth attempting to do it on the current version. (or 1.3 which is very close and the trunk is stable)

 

From: De Smet Ringo [mailto:Ringo.De.Smet@...]
Sent: Tuesday, February 10, 2009 10:10 AM
To: nexus-dev@...
Subject: [nexus-dev] Nexus plugins?

 

Hello,

 

I am using Nexus OpenSource edition. Due to our internal release strategy, we have a whole series of module releases leading to a lot of disk space usage. Since we have parallel releases, we can't just scrape the repository for artifacts older than x days. I would like to have a Scheduled Task that removes all artifacts except the last X within a certain release. As such, I want to configure the task with a repository to scrape, a groupId, a major/minor version combination and the amount of releases to leave in the repository.

 

In SVN, I see the beginnings of a plugin model popping up. Can I already use a Scheduled Task plugin in 1.2.1 or do I have to wait for 1.3?

 

Ringo

*************************************************************

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen.

This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes ventuelles peuvent contenir des informations confidentielles et/ou protges par des droits de proprit intellectuelle. Ce message est adress exclusivement son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complte sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reu ce message par erreur, veuillez prvenir l'expditeur du message et en dtruire le contenu.

*************************************************************

[De Smet Ringo]

Some parts of this message have been removed. Learn more about Nabble's security policy.



Brian,

 

Yesterday evening, I managed to create a separate jar containing a Plexus component for a scheduled task, built against Nexus 1.2.1. Although the doRun() is still empty, it shows up correctly in the web UI and the parameters are correctly listed and filled in.

 

So it seems to work fine!

 

Ringo

---

From: Brian E. Fox [mailto:brianf@...]
Sent: dinsdag 10 februari 2009 22:35
To: nexus-dev@...
Subject: RE: [nexus-dev] Nexus plugins?

It should be possible to build a scheduled task as a plugin in 1.2.x but I’m not sure if we have any examples to look at. 1.4 will be the next major change with regards to plugin api so it is worth attempting to do it on the current version. (or 1.3 which is very close and the trunk is stable)

 

 

*************************************************************

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen.

This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes �ventuelles peuvent contenir des informations confidentielles et/ou prot�g�es par des droits de propri�t� intellectuelle. Ce message est adress� exclusivement � son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou compl�te sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez re�u ce message par erreur, veuillez pr�venir l'exp�diteur du message et en d�truire le contenu.

*************************************************************

[Tamás Cservenák]

Yup, you can do it, but the things will change later (in 1.4?)

Until then, you can create a new task just as you described. For ideas, i would suggest the snapshot remover task, that does something similar...

~t~

On Wed, Feb 11, 2009 at 8:26 AM, De Smet Ringo <Ringo.De.Smet@...> wrote:

Brian,

 

Yesterday evening, I managed to create a separate jar containing a Plexus component for a scheduled task, built against Nexus 1.2.1. Although the doRun() is still empty, it shows up correctly in the web UI and the parameters are correctly listed and filled in.

 

So it seems to work fine!

 

Ringo

---

From: Brian E. Fox [mailto:brianf@...]
Sent: dinsdag 10 februari 2009 22:35

To: nexus-dev@...

Subject: RE: [nexus-dev] Nexus plugins?

It should be possible to build a scheduled task as a plugin in 1.2.x but I'm not sure if we have any examples to look at. 1.4 will be the next major change with regards to plugin api so it is worth attempting to do it on the current version. (or 1.3 which is very close and the trunk is stable)

 

 

*************************************************************

Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen.

This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents.

Ce courriel et les annexes éventuelles peuvent contenir des informations confidentielles et/ou protégées par des droits de propriété intellectuelle. Ce message est adressé exclusivement à son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou complète sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez reçu ce message par erreur, veuillez prévenir l'expéditeur du message et en détruire le contenu.

*************************************************************