Details
-
Type:
New Feature
-
Status:
Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: 1.0-alpha-1
-
Component/s: None
-
Labels:None
-
Number of attachments :
Description
Heard about the repo manager on #maven today. Sounds like a great idea. I am "encouraging" the myGrid and OMII people here in the UK to use m2 as their standard build platform. They are developing a semanticaly-aware directory component - URIs (such as ws end-points) are annotated in the directory and then clients can discover URIs of the type or with the properties that they would like. It would help myGrid to contribute to maven synergystically if a couple of bits of tech could be in-place in the repo manager.
- An RSS feed of all updates
- Full web-service interface to the repo manager
- M2 build-time support for attaching .owl or .rdf documents to artifacts, providing a semantic description of the artifact, which could then be imported into the directory. Perhaps part of the .owl / .rdf would be auto-generated by plugins and part would be under src/main/semanticDescription.
We have hired a team of 5 developers and a manager to re-write the myGrid code - they have an explicit brief to do sw engineering rather than accademic coding. I would expect that if they use m2 extensively, that they would contribute to the project by submitting patches etc. like any good os citizens.
Sorry about the management speak - got my project managers hat on today.
these are all on the roadmap (RSS and web services). M2 can already attach documents to deployed artifacts using a plugin in the package phase (see how the sources plugin works).