Great - thanks for the confirmation! The parent pom should be in jboss nexus though so it should build if you have that configured ? /max On 10 Oct 2012, at 20:39, Bob Brodt <bbrodt(a)redhat.com&gt; wrote:

great! try.github.com is your friend ;) And otherwise - we got a good bunch of guys who have used git actively the last couple of years and others who just started to grok it - we've all been there at the step of having to use git and we've all been beginners once. just ask on the mailinglist, irc, etc. and there will be someone that have been in a similar situation and can lead you and other git-newbies in the right direction. I'm convinced your life will be better once we get over the hurdle :) /max

I have tried portlet, birt, runtime, central and examples. Portlet, birt and runtime work correctly. The examples build fails. Denis fixed it in the svn trunk. The central build has a problem with building org.jboss.central.themes.feature.source. It works on the svn trunk. When the changes from the svn trunk are added to git? Snjeza On 10.10.2012 18:37, Max Rydahl Andersen wrote:

On 10/11/2012 11:20 AM, Max Rydahl Andersen wrote: I'll first need them to confirm they are following instructions from https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3#Building_... And I'll need to know which command-line options they used to specify dependencies. -- Mickael Istria Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

weird - but since this just look like an internal compile error on the repo I would say it would be fixed when doing a fresh migration. I assume this error exist when importing the source into eclipse ? if not, then it must be because you got a newer/older build of the plugins in your .m2e repository that confuses mvn ? /max On 11 Oct 2012, at 11:38, Snjezana Peco <snjezana.peco(a)redhat.com&gt; wrote:

When fixing this compile error on git, central is built correctly. The error has been fixed on svn. Snjeza On 11.10.2012 11:38, Snjezana Peco wrote:

why does it need that folder ? Here is many more changes in here than a missing src folder. these I can understand. annyoing but thats how pde build/tycho works. why should it compile with latest source from svn trunk ? Only thing expected to work together is the temp-jbosstools-* repos - they should be compared with what was there 7 days ago, not trunk now. also waay more changes than just gitkeep. Also a tons of changes. And it compiles fine for me - what are you testing here ? not following at all. same as above - not following why you think latest svn would work against these repos ?

so denis changes to remove from build.properties breaks sourcefeature builds ? yeah - so not relevant for me to look at now since ill be taking stuff from svn not temp git repos. Beta1 is not what is in these repos. its what was there 7 days ago. Thus it will most likely not buildmixed with source from trunk. Why would you expect that to work ? yes, please do the necessary changes for gitkeep in svn - not on github. so you are -1 it because it cant be built when you have done changes to it ? What are the build errors you are getting ? if you update the sources in the forked repo to match whats in trunk you are not testing what the git migration job did.... I can checkout your repos tomrorow - bout would be good to know the actual errors you get instead of just -1. /max

Rules for use of sourceTemplateFeature/.gitkeep files and src/ folders as they apply to Tycho builds: http://wiki.eclipse.org/Minerva#Source N On 10/11/2012 02:50 PM, Rob Cernich wrote: -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

I 'm recalling there were some issues in the first versions of tycho that included support for source builds that would make builds fail if these were not included and would require to hand-maintain the source features instead of just having it build automatically for all ~250 plugin. If that problem does not exist anymore then yes, removing the src should be fine, but if not then there are only 2-3 cases where we have a pure plugin.xml plugin and it seems then simpler (though annoying) to just add the src folder to avoid having to tweak pom.xml and/or source.feature for the inclusion. Mistria - does tycho source feature automatically exclude plugins that doesn't have sources or does it enforce every plugin listed in the original feature to have sources (even if just empty) /max

I wonder why tycho couldn't just exclude those that don't have source available as an option (since I guess its also useful to fail to be able to detect if you always want sources and for some reason got a config error). Anyways, for the git migration the simplest approach is then just to add .gitkeep to those locations. /max

Your email in the import should be set to what your jboss.org user account states as your email (or at least what it said at the time I added you to the gitauthor txt file used for the import) github supports adding multiple emails so it should be possible to be recognized for any mix of emails used afaik. /max On 15 Oct 2012, at 11:16, Xavier Coulon <xcoulon(a)redhat.com&gt; wrote:

On 15. 10. 2012, at 14:56, Andrej Podhradsky <apodhrad(a)redhat.com&gt; wrote: This is expected. As you say, both of these bot tests have been removed from svn trunk. But they are in history. So you won't see them in the migrated repo in HEAD, but they will be there in history and you could retrieve them back and then apply the new changes since they were removed from svn. So there is nothing to do right now - it can be dealt with after the migration. These bot tests will be included in the migration just like all the other bot tests. This is the regexp that will be used: regexp = re.compile('^[^/]*/[^/]*/[^/]*\.bot.*') So basically when creating the new jbosstools-integration-tests git repo, only files that match that reg exp will be preserved. Everything else will be removed. That means that we preserve these kind of folders: _component_/_something_/*.bot* Both teiid designer bot test and modeshape bot test match this. -Martin -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

Hi Max, in temp-jbosstools-integration-tests isn't the whole project for bpel bot tests. The following folder is missing http://anonsvn.jboss.org/repos/jbosstools/trunk/bpel/tests/org.jboss.tool... Note that this isn't new folder, was added in 2011. Have a nice day! Andrej. ----- Original Message ----- From: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; Sent: Wednesday, October 10, 2012 6:37:52 PM Subject: [jbosstools-dev] [gitmigration] ACTION REQUIRED please respond back wether your project git repo is ok or not! Hi, If you have not yet taken a look at the temp-* repositories on https://github.com/jbosstools please do so ASAP If I haven't heard back a +1 or "hey - this works great, except for this and this" for the content of the repositories by Wednesday next week (17th) the git migration will be delayed/postponed *after* GA. Thus if you want to use git *now* is the time to go help verify the content of the repositories are sane. thank you! /max _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

On 16. 10. 2012, at 10:54, Andrej Podhradsky <apodhrad(a)redhat.com&gt; wrote: You are right again. It has to do something with the fact that the missing directories were forked from somewhere else. Compare this: https://github.com/jbosstools/jbosstools-full-svn-mirror/tree/trunk/bpel/... with https://github.com/jbosstools/temp-jbosstools-integration-tests/tree/trun... On the first link you can see that all the folders that disappear in the second link have this last commit message: https://github.com/jbosstools/jbosstools-full-svn-mirror/commit/b4ea72bf2... https://issues.jboss.org/browse/JBDS-1810 new bpel in trunk (forked from old bpel-old/ folder) What I don't understand is that there is no commit containing the addition of the files. Because this last commit contains all these files under different filename - they must have been moved in bulk inside the bot test folder sometime later. But since there is no commit for it in git, when the fast filter filters the files in commit, it simply skips all these files :( We need to fix this. -Martin -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

....so bpel-old *was* actually used ?! wtf... pinging you on irc.... /max On 16 Oct 2012, at 19:38, Martin Malina <mmalina(a)redhat.com&gt; wrote:

...and its a reminder how wrong it is to just svn rename something to signify deprecation/"oldness" if something is not used anymore - *delete* it - dont rename it. its a SCM that has history - you can always go back and get it. /max On 17 Oct 2012, at 12:42, Martin Malina <mmalina(a)redhat.com&gt; wrote:

Thanks. I pulled the new repo and was able to run my tests - that's a good sign. Also, both tests/org.jboss.tools.bpel.ui.bot.test/src/org/jboss/tools/bpel/ui/bot/ext/widgets and projects in tests/org.jboss.tools.bpel.ui.bot.test/projects/ that were missing are there now. Andrej, can you please check if everything is ok? You can use my fork here git://github.com/mmalina/temp-jbosstools-integration-tests.git This contains pom.xml, tests/pom.xml and also fixed parent definition for your tests/org.jboss.tools.bpel.ui.bot.test/pom.xml so it should work right away. Max, there are still both master and trunk branches. Why is that? Thanks, Martin On 18. 10. 2012, at 18:25, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

Hi Martin, thank you, now it is ok. Have a nice day! Andrej. ----- Original Message ----- From: "Martin Malina" <mmalina(a)redhat.com&gt; To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; Cc: "Andrej Podhradsky" <apodhrad(a)redhat.com&gt;, "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; Sent: Thursday, October 18, 2012 9:46:52 PM Subject: Re: [jbosstools-dev] [gitmigration] ACTION REQUIRED please respond back wether your project git repo is ok or not! Thanks. I pulled the new repo and was able to run my tests - that's a good sign. Also, both tests/org.jboss.tools.bpel.ui.bot.test/src/org/jboss/tools/bpel/ui/bot/ext/widgets and projects in tests/org.jboss.tools.bpel.ui.bot.test/projects/ that were missing are there now. Andrej, can you please check if everything is ok? You can use my fork here git://github.com/mmalina/temp-jbosstools-integration-tests.git This contains pom.xml, tests/pom.xml and also fixed parent definition for your tests/org.jboss.tools.bpel.ui.bot.test/pom.xml so it should work right away. Max, there are still both master and trunk branches. Why is that? Thanks, Martin On 18. 10. 2012, at 18:25, Max Rydahl Andersen < max.andersen(a)redhat.com > wrote: reran the git migration for the tests with mmalinas fix plus another fix ;) https://github.com/jbosstools/temp-jbosstools-integration-tests/tree/mast... now exist. Please take it for a spin and see if anything else missing. /max On 17 Oct 2012, at 13:01, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: ...and its a reminder how wrong it is to just svn rename something to signify deprecation/"oldness" if something is not used anymore - *delete* it - dont rename it. its a SCM that has history - you can always go back and get it. /max On 17 Oct 2012, at 12:42, Martin Malina <mmalina(a)redhat.com&gt; wrote: Summarizing our discussion here: This should be fixed with https://github.com/maxandersen/jbosstools-gitmigration/pull/4/ The solution is to add the excludes to our jbosstools-integration-tests filter. Thanks catching this, Andrej! And thanks Max for seeing exactly what happened. Long boring explanation of what happened: Our filter only preserves files in _component_/_something_/*.bot*. So it preserved bpel/tests/org.jboss.tools.bpel.ui.bot.test AND ALSO bpel_old/tests/org.jboss.tools.bpel.ui.bot.test . But the filter also renames _component_/_something_/_random.bot.plugin_ to tests/_random.bot.plugin_. So both bpel/tests/org.jboss.tools.bpel.ui.bot.test and bpel_old/tests/org.jboss.tools.bpel.ui.bot.test were renamed to tests/org.jboss.tools.bpel.ui.bot.test. So basically we merged two dirs into one dir. And since the last commit in this merged dir was removing bpel_old completely, it also removed everything from this new merged dir. The fix is to exclude bpel_old altogether. -Martin On 17. 10. 2012, at 11:28, Max Rydahl Andersen <max.andersen(a)redhat.com&gt; wrote: ....so bpel-old *was* actually used ?! wtf... pinging you on irc.... /max On 16 Oct 2012, at 19:38, Martin Malina <mmalina(a)redhat.com&gt; wrote: Hi Max, I'm resending this just to make sure it doesn't fall through. This is quite a big problem that we need to solve somehow. It seems that any file that was originally committed under some other path (not matching the regexp that we use for jbosstools-integration-tests) and then moved in svn under bot tests won't be included in the filtered git repo :( Let's talk on irc tomorrow. -Martin On 16. 10. 2012, at 19:28, Martin Malina <mmalina(a)redhat.com&gt; wrote: On 16. 10. 2012, at 10:54, Andrej Podhradsky <apodhrad(a)redhat.com&gt; wrote: I'm looking that some resources are also missing, namely http://anonsvn.jboss.org/repos/jbosstools/trunk/bpel/tests/org.jboss.tool... You are right again. It has to do something with the fact that the missing directories were forked from somewhere else. Compare this: https://github.com/jbosstools/jbosstools-full-svn-mirror/tree/trunk/bpel/... with https://github.com/jbosstools/temp-jbosstools-integration-tests/tree/trun... On the first link you can see that all the folders that disappear in the second link have this last commit message: https://github.com/jbosstools/jbosstools-full-svn-mirror/commit/b4ea72bf2... https://issues.jboss.org/browse/JBDS-1810 new bpel in trunk (forked from old bpel-old/ folder) What I don't understand is that there is no commit containing the addition of the files. Because this last commit contains all these files under different filename - they must have been moved in bulk inside the bot test folder sometime later. But since there is no commit for it in git, when the fast filter filters the files in commit, it simply skips all these files :( We need to fix this. -Martin Andrej. ----- Original Message ----- From: "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; To: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; Sent: Tuesday, October 16, 2012 10:04:18 AM Subject: Re: [jbosstools-dev] [gitmigration] ACTION REQUIRED please respond back wether your project git repo is ok or not! Hi Max, in temp-jbosstools-integration-tests isn't the whole project for bpel bot tests. The following folder is missing http://anonsvn.jboss.org/repos/jbosstools/trunk/bpel/tests/org.jboss.tool... Note that this isn't new folder, was added in 2011. Have a nice day! Andrej. ----- Original Message ----- From: "Max Rydahl Andersen" <max.andersen(a)redhat.com&gt; To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; Sent: Wednesday, October 10, 2012 6:37:52 PM Subject: [jbosstools-dev] [gitmigration] ACTION REQUIRED please respond back wether your project git repo is ok or not! Hi, If you have not yet taken a look at the temp-* repositories on https://github.com/jbosstools please do so ASAP If I haven't heard back a +1 or "hey - this works great, except for this and this" for the content of the repositories by Wednesday next week (17th) the git migration will be delayed/postponed *after* GA. Thus if you want to use git *now* is the time to go help verify the content of the repositories are sane. thank you! /max _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265 _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265 -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265 -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

On 16. 10. 2012, at 10:04, Andrej Podhradsky <apodhrad(a)redhat.com&gt; wrote: You are right, this is missing. That is very strange. Note that it is present in the full svn mirror: https://github.com/jbosstools/jbosstools-full-svn-mirror/tree/trunk/bpel/... But it's not here: https://github.com/jbosstools/temp-jbosstools-integration-tests/tree/mast... Again, the regexp used is '^[^/]*/[^/]*/[^/]*\.bot.*' so that should be safe - how could that pick everything else in the bpel bot tests but not that single folder? Max, do you have any idea what could have eaten that subdirectory and its contents? Thanks, Martin -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

On 16 Oct 2012, at 17:06, Brian Fitzpatrick <bfitzpat(a)redhat.com&gt; wrote: okey - so yeah, the git repo reproduced the same bugs ;) thats a good sign. until friday SVN is king - github is just *temporary* repos as in *temp-*jbosstools-ws /max