Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [tycho-user] Conditional checkout of component prior to build

I’m not using Subversion myself, so I can’t really say if this setup makes sense or not. Maybe others have something interesting experience to share?


Generally, I don’t know if checking out sources as part of the Maven build will ever work. This is because you’d need to do this before the POM model is built up by Maven. This implies that you cannot use the POM to configure these checkout actions, so you’d need a separate source file for this. You might be able to make this to work by making a Maven build trigger a Maven build. But then really the question is why not to use some scripting language to trigger the (inner) Maven build, which seems easier.






From: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx] On Behalf Of Alex Kravets
Sent: Donnerstag, 22. August 2013 19:43
To: Tycho user list
Subject: Re: [tycho-user] Conditional checkout of component prior to build


Thanks Tobias,


So when you say "Things that you want to build together should also be in one SCM repository", do you mean that if let's say I have branch that is a subset of plugins that are in trunk, there should really be a branch that reflects the whole structure of the trunk and you work on changes from that location (branch)? After that you merge the things that were changed in branch into trunk? If so, then that's fine, but I found myself in situations where branch is being worked on for a long time and it deviates from trunk and when it's time to merge back there is a lot of (potentially) code to cover. Unless you do daily check between state of branch and trunk.


If multiple developers work on their branches they have to make sure their plugins are always up to date with trunk. The reason I wrote this script is so that I can create a hybrid workspace in CIS and build off that, this way developers don't care about state of trunk and their branch because once the created workspace is build it will build off components from branch and trunk.


This is one of the features that was really useful in Buckminster and I wanted to bring it into my Maven/Tycho builds, or any builds for that matter.




Back to the top