| Re: [triquetrum-dev] Setting up an RCP build for Triquetrum |
Lots of build changes all around today. I made a ton of changes on ICE's build as well.
Jay
Done.
I haven't deleted the dependencies project yet, but the target.platform already no longer has the ptolemy binaries.
Remark that the Triquetrum.product file has moved (and changed contents).
It's now no longer in the editor project, but in the repository project.
(thanks ICE, I took that setup from there)
more info tomorrow, first let's see what the HIPPo-CI-tamus does with this...
erwin
Op 10/02/2016 om 23:46 schreef Christopher Brooks:
Agreed. Please go ahead and push. Don't fear the CI.
_C
On 2/10/16 2:34 PM, Jay Jay Billings wrote:
In my experience, yes, you push into master and wait with your fingers crossed until the CI engine breaks. :-PJay
On Wed, Feb 10, 2016 at 5:29 PM, Erwin de Ley <erwin.de.ley@xxxxxxxxxx> wrote:
To finalize the #48 issue, we need a reproducible and p2-enabled RCP build for Triquetrum.
And then it's possible to use the standard eclipse workbench "Install new software" to upload new actors and other Triquetrum extensions, either from a p2 site or a plain feature zip.
To get that rolling, I've been doing the following :
- implement an example of an extra actor + feature definition + p2.inf instructions to let it auto-start when installed in the RCP
- define feature projects for the different parts of Triquetrum and for its non-std-eclipse dependencies
- define a feature-based product file
- add a repository project with a pom to define the build for the triquetrum p2 repository and a packaged RCP
- adapted the parent pom to add a bunch of new modules etc
- probably some more stuff that I've already forgotten about
- and finally created a personal p2 site for ptolemy's bundles at http://users.telenet.be/triquetrum-ptolemy-p2/
- adapted the pom and target to point only to p2 repositories
(So now we can remove the ptolemy dependencies from the github repository if we want.)
- tested the resulting build and : it WORKS! And there's even a working RCP there, somewhere deep in the maven build folders.
Question is now : "to commit and merge" or "not to commit and merge" ? ;-)
Christopher, can you evaluate what this would mean for the HIPP build?
Do I just push and merge into master and then fingers-crossed?
cheers
erwin
_______________________________________________
triquetrum-dev mailing list
triquetrum-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/triquetrum-dev
--
Jay Jay Billings
Oak Ridge National LaboratoryTwitter Handle: @jayjaybillings
-- Christopher Brooks, PMP University of California Academic Program Manager & Software Engineer US Mail: 337 Cory Hall CHESS/iCyPhy/Ptolemy/TerraSwarm Berkeley, CA 94720-1774 cxh@xxxxxxxxxxxxxxxxx, 707.332.0670 (Office: 545Q Cory)
_______________________________________________ triquetrum-dev mailing list triquetrum-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/triquetrum-dev
_______________________________________________
triquetrum-dev mailing list
triquetrum-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/triquetrum-dev