Hi Martin, thank you! It is working (both sites), just wondering what's the difference between them? The same? I think that creating new branch is not necessary (we can create it when some problems occur but not now). Have a nice day! Andrej ----- Original Message ----- From: "Martin Malina" <mmalina(a)redhat.com&gt; To: "Jiri Peterka" <jpeterka(a)redhat.com&gt;, "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; Sent: Friday, April 26, 2013 10:16:30 AM Subject: Re: Red Deer Installation on Juno I created a new job for juno: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Currently it is only set up to use that commit just before the Kepler M6 fix in RedDeer, so it uses this commit: https://github.com/jboss-reddeer/reddeer/commit/31f61195b27ea26504c5185c6... It published the results here: http://download.jboss.org/jbosstools/builds/staging/RedDeer_juno/all/repo/ And I promoted it to this stable location: http://download.jboss.org/jbosstools/updates/stable/juno/core/reddeer/0.2.0/ - this is the repo that should be added to our root pom in the juno branch of integration tests (jbosstools-4.0.x) Andrej, can you check that this works for you? If it does, we can change the root pom to contain this. What is not ideal is that we haven't upversion RedDeer, so we cannot really change this Juno version to anything. So right now the only differentiation is the different update site. On the other hand, we rarely limit bundle dependencies not to be higher than something - so most of the time the only way to ensure older version of something is just to use an older update site and the plugin versions don't really matter, so I guess this is not a real problem. Also, right Andrej agreed that he is fine with just a single build that will be final for Juno. But we could also create a juno branch of RedDeer that could be altered if necessary - this will not do any harm I think. What do you think? Should we do it? Andrej? Jirka? Thanks, Martin On 26. 4. 2013, at 9:43, Jiri Peterka <jpeterka(a)redhat.com&gt; wrote: > After some clarification with Andrej it seems he just needs one single build on some praticular commit (before hamcrest update). So this shouldn't be a problem I think. Martin, can you build some internal update site for this purpose? > > Thanks, > > Jirka > > > On 04/26/2013 09:24 AM, Jiri Peterka wrote: >> Multiple RedDeer versions for Juno and Kepler is an easy but costly solution for the future and exactly something I'd like to avoid. Can't this be fixed simply by more specific hamcrest settings in bot.ext manifest? >> >> And I'd like to hear more voices here. Martin, you as a RedDeer productizator, what do you think? >> >> Jirka >> >> On 04/26/2013 09:02 AM, Andrej Podhradsky wrote: >>> Hi Jirko, >>> >>> the problem now is with ui.bot.ext which causes some troubles with hamcrest 1.3 :( >>> I suggest to create some juno-compatible release of Red Deer (based on hamcrest 1.1) so that tests in jbosstools can be executed without any other modification. >>> This release will be temporary till we remove dependencies on ui.bot.ext. What do you think? >>> >>> Andrej. >>> >>> ----- Original Message ----- >>> From: "Jiri Peterka" <jpeterka(a)redhat.com&gt; >>> To: "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; >>> Cc: "jboss-jbds-qe" <jboss-jbds-qe(a)redhat.com&gt; >>> Sent: Friday, April 26, 2013 7:25:52 AM >>> Subject: Re: Red Deer Installation on Juno >>> >>> Thanks Andrej, >>> I created an issue for that and assigned it to Martin, see >>> >>> https://github.com/jboss-reddeer/reddeer/issues/146 >>> >>> Someone see any problem with this? Sounds good to me. >>> >>> -- Jirka >>> >>> On 04/25/2013 12:07 PM, Andrej Podhradsky wrote: >>>> Hi folks, >>>> >>>> as you know, Red Deer now cannot be installed into Juno due to its dependencies on new junit and hamcrest. >>>> I found out a workaround, just add the orbit update site [1] to the list of available update sites. >>>> This repo includes org.junit.4.11 and org.hamcrest.1.3 >>>> >>>> [1] http://download.eclipse.org/tools/orbit/downloads/drops/I20130423013529/r... >>>> >>>> Best Regards >>>> >> > > > -- > Jiri Peterka > JBoss Developer Studio QE > Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic > IRC: jpeterka #jboss-qa, #devstudio-qa > email: jpeterka(a)redhat.com > -- Martin Malina JBoss QA Engineer Red Hat Czech s.r.o. Purkynova 99 612 45 Brno, Czech Republic Tel.: +420 532 294 265

Where is the 0.2.0 tag or branch in red deer repo ?

Also looks like red deer is still versioned as 0.0.1-SNAPSHOT - that does not sound right. https://github.com/jboss-reddeer/reddeer/blob/v0.0.2/org.jboss.reddeer.ec...

/max On Fri, Apr 26, 2013 at 05:26:09AM -0400, Andrej Podhradsky wrote: > Hi Martin, > > thank you! It is working (both sites), just wondering what's the difference between them? The same? > > I think that creating new branch is not necessary (we can create it when some problems occur but not now). > > Have a nice day! > > Andrej > > ----- Original Message ----- > From: "Martin Malina" <mmalina(a)redhat.com&gt; > To: "Jiri Peterka" <jpeterka(a)redhat.com&gt;, "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; > Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; > Sent: Friday, April 26, 2013 10:16:30 AM > Subject: Re: Red Deer Installation on Juno > > I created a new job for juno: > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > > Currently it is only set up to use that commit just before the Kepler M6 fix in RedDeer, so it uses this commit: > https://github.com/jboss-reddeer/reddeer/commit/31f61195b27ea26504c5185c6... > > It published the results here: > http://download.jboss.org/jbosstools/builds/staging/RedDeer_juno/all/repo/ > > And I promoted it to this stable location: > http://download.jboss.org/jbosstools/updates/stable/juno/core/reddeer/0.2.0/ > - this is the repo that should be added to our root pom in the juno branch of integration tests (jbosstools-4.0.x) > > Andrej, can you check that this works for you? If it does, we can change the root pom to contain this. > > What is not ideal is that we haven't upversion RedDeer, so we cannot really change this Juno version to anything. So right now the only differentiation is the different update site. On the other hand, we rarely limit bundle dependencies not to be higher than something - so most of the time the only way to ensure older version of something is just to use an older update site and the plugin versions don't really matter, so I guess this is not a real problem. > > Also, right Andrej agreed that he is fine with just a single build that will be final for Juno. But we could also create a juno branch of RedDeer that could be altered if necessary - this will not do any harm I think. What do you think? Should we do it? Andrej? Jirka? > > Thanks, > Martin > > On 26. 4. 2013, at 9:43, Jiri Peterka <jpeterka(a)redhat.com&gt; wrote: > >> After some clarification with Andrej it seems he just needs one single build on some praticular commit (before hamcrest update). So this shouldn't be a problem I think. Martin, can you build some internal update site for this purpose? >> >> Thanks, >> >> Jirka >> >> >> On 04/26/2013 09:24 AM, Jiri Peterka wrote: >>> Multiple RedDeer versions for Juno and Kepler is an easy but costly solution for the future and exactly something I'd like to avoid. Can't this be fixed simply by more specific hamcrest settings in bot.ext manifest? >>> >>> And I'd like to hear more voices here. Martin, you as a RedDeer productizator, what do you think? >>> >>> Jirka >>> >>> On 04/26/2013 09:02 AM, Andrej Podhradsky wrote: >>>> Hi Jirko, >>>> >>>> the problem now is with ui.bot.ext which causes some troubles with hamcrest 1.3 :( >>>> I suggest to create some juno-compatible release of Red Deer (based on hamcrest 1.1) so that tests in jbosstools can be executed without any other modification. >>>> This release will be temporary till we remove dependencies on ui.bot.ext. What do you think? >>>> >>>> Andrej. >>>> >>>> ----- Original Message ----- >>>> From: "Jiri Peterka" <jpeterka(a)redhat.com&gt; >>>> To: "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; >>>> Cc: "jboss-jbds-qe" <jboss-jbds-qe(a)redhat.com&gt; >>>> Sent: Friday, April 26, 2013 7:25:52 AM >>>> Subject: Re: Red Deer Installation on Juno >>>> >>>> Thanks Andrej, >>>> I created an issue for that and assigned it to Martin, see >>>> >>>> https://github.com/jboss-reddeer/reddeer/issues/146 >>>> >>>> Someone see any problem with this? Sounds good to me. >>>> >>>> -- Jirka >>>> >>>> On 04/25/2013 12:07 PM, Andrej Podhradsky wrote: >>>>> Hi folks, >>>>> >>>>> as you know, Red Deer now cannot be installed into Juno due to its dependencies on new junit and hamcrest. >>>>> I found out a workaround, just add the orbit update site [1] to the list of available update sites. >>>>> This repo includes org.junit.4.11 and org.hamcrest.1.3 >>>>> >>>>> [1] http://download.eclipse.org/tools/orbit/downloads/drops/I20130423013529/r... >>>>> >>>>> Best Regards >>>>> >>> >> >> >> -- >> Jiri Peterka >> JBoss Developer Studio QE >> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic >> IRC: jpeterka #jboss-qa, #devstudio-qa >> email: jpeterka(a)redhat.com >> > > -- > 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

On Fri, Apr 26, 2013 at 04:40:42PM +0200, Martin Malina wrote: > On 26. 4. 2013, at 16:24, Max Rydahl Andersen <manderse(a)redhat.com&gt; wrote: > >> Where is the 0.2.0 tag or branch in red deer repo ? > > RedDeer 0.2.0 should be released soon: > https://github.com/jboss-reddeer/reddeer/issues/milestones > > Currently it's still just master and the version is 0.2.0-SNAPSHOT. > > But because we (I) broke juno compatibility before there was any release to be used with juno (the previous version was a very long time ago) there was no other version to be used with juno now. Had I realized I would break it with https://github.com/jboss-reddeer/reddeer/pull/100 (committed to master) we could have released 0.2.0 right away and move on to 0.3.0. > > Yes, I know we agreed there would be a stable version so that juno testing is reproducible. But I was waiting for the 0.2.0 release for that - and then jbosstools-4.0.x branch of jbosstools-integration-tests would use that. But since I broke it before that, the solution I came up with for now is to build 0.2.0-SNAPSHOT of RedDeer from a commit just before I broke it for Juno. (This PR made use of the newly build RedDeer repo: https://github.com/jbosstools/jbosstools-integration-tests/pull/242 ) Andrej says he thinks he won't need any more changes for Juno. If they do require changes, we will create a branch based on this commit. But not sure if we can do anything about the version. > > Do you have a suggestion for a better solution in this situation? then git tag that SHA1 you built as the 0.2 release -

but it just seems like all the versions numbers aren't set in reddeer - i..e where does it actually say 0.2 in this release?

/max >> >> Also looks like red deer is still versioned as 0.0.1-SNAPSHOT - that does not sound right. >> >> https://github.com/jboss-reddeer/reddeer/blob/v0.0.2/org.jboss.reddeer.ec... > > This is very old - 0.0.2 as opposed to 0.2.0 that we have now. But yes, that one had wrong version in it. > > -Martin > >> >> /max >> >> On Fri, Apr 26, 2013 at 05:26:09AM -0400, Andrej Podhradsky wrote: >>> Hi Martin, >>> >>> thank you! It is working (both sites), just wondering what's the difference between them? The same? >>> >>> I think that creating new branch is not necessary (we can create it when some problems occur but not now). >>> >>> Have a nice day! >>> >>> Andrej >>> >>> ----- Original Message ----- >>> From: "Martin Malina" <mmalina(a)redhat.com&gt; >>> To: "Jiri Peterka" <jpeterka(a)redhat.com&gt;, "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; >>> Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt; >>> Sent: Friday, April 26, 2013 10:16:30 AM >>> Subject: Re: Red Deer Installation on Juno >>> >>> I created a new job for juno: >>> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >>> >>> Currently it is only set up to use that commit just before the Kepler M6 fix in RedDeer, so it uses this commit: >>> https://github.com/jboss-reddeer/reddeer/commit/31f61195b27ea26504c5185c6... >>> >>> It published the results here: >>> http://download.jboss.org/jbosstools/builds/staging/RedDeer_juno/all/repo/ >>> >>> And I promoted it to this stable location: >>> http://download.jboss.org/jbosstools/updates/stable/juno/core/reddeer/0.2.0/ >>> - this is the repo that should be added to our root pom in the juno branch of integration tests (jbosstools-4.0.x) >>> >>> Andrej, can you check that this works for you? If it does, we can change the root pom to contain this. >>> >>> What is not ideal is that we haven't upversion RedDeer, so we cannot really change this Juno version to anything. So right now the only differentiation is the different update site. On the other hand, we rarely limit bundle dependencies not to be higher than something - so most of the time the only way to ensure older version of something is just to use an older update site and the plugin versions don't really matter, so I guess this is not a real problem. >>> >>> Also, right Andrej agreed that he is fine with just a single build that will be final for Juno. But we could also create a juno branch of RedDeer that could be altered if necessary - this will not do any harm I think. What do you think? Should we do it? Andrej? Jirka? >>> >>> Thanks, >>> Martin >>> >>> On 26. 4. 2013, at 9:43, Jiri Peterka <jpeterka(a)redhat.com&gt; wrote: >>> >>>> After some clarification with Andrej it seems he just needs one single build on some praticular commit (before hamcrest update). So this shouldn't be a problem I think. Martin, can you build some internal update site for this purpose? >>>> >>>> Thanks, >>>> >>>> Jirka >>>> >>>> >>>> On 04/26/2013 09:24 AM, Jiri Peterka wrote: >>>>> Multiple RedDeer versions for Juno and Kepler is an easy but costly solution for the future and exactly something I'd like to avoid. Can't this be fixed simply by more specific hamcrest settings in bot.ext manifest? >>>>> >>>>> And I'd like to hear more voices here. Martin, you as a RedDeer productizator, what do you think? >>>>> >>>>> Jirka >>>>> >>>>> On 04/26/2013 09:02 AM, Andrej Podhradsky wrote: >>>>>> Hi Jirko, >>>>>> >>>>>> the problem now is with ui.bot.ext which causes some troubles with hamcrest 1.3 :( >>>>>> I suggest to create some juno-compatible release of Red Deer (based on hamcrest 1.1) so that tests in jbosstools can be executed without any other modification. >>>>>> This release will be temporary till we remove dependencies on ui.bot.ext. What do you think? >>>>>> >>>>>> Andrej. >>>>>> >>>>>> ----- Original Message ----- >>>>>> From: "Jiri Peterka" <jpeterka(a)redhat.com&gt; >>>>>> To: "Andrej Podhradsky" <apodhrad(a)redhat.com&gt; >>>>>> Cc: "jboss-jbds-qe" <jboss-jbds-qe(a)redhat.com&gt; >>>>>> Sent: Friday, April 26, 2013 7:25:52 AM >>>>>> Subject: Re: Red Deer Installation on Juno >>>>>> >>>>>> Thanks Andrej, >>>>>> I created an issue for that and assigned it to Martin, see >>>>>> >>>>>> https://github.com/jboss-reddeer/reddeer/issues/146 >>>>>> >>>>>> Someone see any problem with this? Sounds good to me. >>>>>> >>>>>> -- Jirka >>>>>> >>>>>> On 04/25/2013 12:07 PM, Andrej Podhradsky wrote: >>>>>>> Hi folks, >>>>>>> >>>>>>> as you know, Red Deer now cannot be installed into Juno due to its dependencies on new junit and hamcrest. >>>>>>> I found out a workaround, just add the orbit update site [1] to the list of available update sites. >>>>>>> This repo includes org.junit.4.11 and org.hamcrest.1.3 >>>>>>> >>>>>>> [1] http://download.eclipse.org/tools/orbit/downloads/drops/I20130423013529/r... >>>>>>> >>>>>>> Best Regards >>>>>>> >>>>> >>>> >>>> >>>> -- >>>> Jiri Peterka >>>> JBoss Developer Studio QE >>>> Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic >>>> IRC: jpeterka #jboss-qa, #devstudio-qa >>>> email: jpeterka(a)redhat.com >>>> >>> >>> -- >>> 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 > > > >