Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tracecompass-dev] Splitting the CTF library into a separate project

Hi Alex

See the eclipse-dev mailing list [1] about deploying p2 artifacts on maven central. My understanding is that CBI aggregators can be used to achieve this. Since Neon.2 there are various Eclipse artifacts available on maven central. 

I think this would be an interesting avenue for deploying parts of Trace Compass, e.g. the CTF reader, as maven artifacts.  

I hope this helps. Thanks Marc-Andre for pointing this out to me.



-----Original Message-----
From: tracecompass-dev-bounces@xxxxxxxxxxx [mailto:tracecompass-dev-bounces@xxxxxxxxxxx] On Behalf Of Alexandre Montplaisir
Sent: March-01-17 7:34 PM
To: tracecompass-dev@xxxxxxxxxxx
Subject: [tracecompass-dev] Splitting the CTF library into a separate project

Hi all,

I have been working on splitting Trace Compass's CTF plugins into a separate Maven project. The idea was to do something similar to the tracecompass-test-traces [1] repository, which is to have the same code base generate both a Maven artifact and a p2 repo. That way it can be used by both Eclipse plugins and "standard" Maven projects.

I have put the result on my Github:

and I've verified that:
- the tests pass
- generated temporary files are cleaned up
- making Trace Compass use it seems to work fine

Would you be interested into hosting this version at Eclipse, and having Trace Compass depend on it? If there's interest I could create the repo, create the relevant Hudson jobs, and prepare patches to switch TC to that version of the library.



Back to the top