Archiva

introduce an event API

Details

  • Type: New Feature New Feature
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: None
  • Fix Version/s: Backlog
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

it would be better for the current consumer api to migrate towards an event api that can handle more than just database scan processing

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. MRM-1260 Indexing tasks are lost when server goes down or re-starts

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Marc Lustig added a comment -

http://cwiki.apache.org/confluence/display/ARCHIVA/Event+Framework
http://jira.codehaus.org/browse/MRM-976
http://svn.apache.org/viewvc/archiva/branches/MRM-976/branch-working-notes.txt?revision=706263&view=markup

Show
Marc Lustig added a comment - http://cwiki.apache.org/confluence/display/ARCHIVA/Event+Framework http://jira.codehaus.org/browse/MRM-976 http://svn.apache.org/viewvc/archiva/branches/MRM-976/branch-working-notes.txt?revision=706263&view=markup
Hide
Permalink
Brett Porter added a comment -

see also the event package in the repository-layer module for the most basic of starting points

Show
Brett Porter added a comment - see also the event package in the repository-layer module for the most basic of starting points
Hide
Permalink
Marc Lustig added a comment -

hi Brett, do you think it makes sense to continue working on that branch (http://svn.apache.org/repos/asf/archiva/branches/MRM-976) even thou it was created a year ago?
I'm afraid the final merge will be a mess.

Wouldn't it be easier to create a new branch from current trunk and move the work that you have already done there?

Til then, let me try to understand what you have done there already...

Show
Marc Lustig added a comment - hi Brett, do you think it makes sense to continue working on that branch ( http://svn.apache.org/repos/asf/archiva/branches/MRM-976 ) even thou it was created a year ago? I'm afraid the final merge will be a mess. Wouldn't it be easier to create a new branch from current trunk and move the work that you have already done there? Til then, let me try to understand what you have done there already...
Hide
Permalink
Brett Porter added a comment -

this wasn't actually my work, I just rebased it to trunk a year ago

it's just a small commit: http://svn.apache.org/viewvc?view=revision&revision=706263

So, I'd say if you'd like to work on it, you can take or leave what is there. I'll move the notes over to the branch they belonged to, which is MRM-1025.

Show
Brett Porter added a comment - this wasn't actually my work, I just rebased it to trunk a year ago it's just a small commit: http://svn.apache.org/viewvc?view=revision&revision=706263 So, I'd say if you'd like to work on it, you can take or leave what is there. I'll move the notes over to the branch they belonged to, which is MRM-1025 .

People

  • Assignee:
    Unassigned
    Reporter:
    Brett Porter
Vote (2)
Watch (1)

Dates

  • Created:
    Updated: