You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@harmony.apache.org by Alexei Zakharov <al...@gmail.com> on 2008/03/21 13:25:04 UTC
[build-test] new ant target
Hi Stepan,
Today I was trying to update the buildtest workspace and found that
you've made several changes to it. I tried to read README.txt but this
was not very helpful since the file itself looks outdated. Then from
svn logs I understand that you've added new 'install' target to main
build.xml . So what is the correct sequence now
ant install
ant -Dtest.suites=struts_test setup
ant -Dtest.suites=struts_test run
?
Regards,
Alexei
Re: [build-test] new ant target
Posted by Stepan Mishura <st...@gmail.com>.
Thanks!
Fixed at r640783.
-Stepan.
On 3/25/08, Eugene Ostrovsky <eu...@gmail.com> wrote:
> Hi, Stepan.
>
> I've got 2 failures with BTI build.xml (r640391)
>
> 1. when I run
>
> ant -Dtest.suites=tptp install
>
> I've got the following output:
>
> BUILD FAILED
> .../infra/build.xml:144: java.io.FileNotFoundException:
> .../infra/build/config/resources.location (No such file or directory)
>
> I've managed to fix it by adding the following line
>
> <mkdir dir="${config.dir}" />
>
> to -init-instal target
>
> 2. After that the same command produced:
>
> BUILD FAILED
> .../infra/build.xml:220: The following error occurred while executing this line:
> .../infra/scripts/config.xml:52:
> The following error occurred while executing this line:
> .../infra/scripts/config.xml:114:
> Source resource does not exist: .../infra/framework.local.properties
>
> I've fixed it by adding create-local-configuration dependency to
> generate-config target.
>
> Thanks, Eugene.
>
> On Tue, Mar 25, 2008 at 11:38 AM, Stepan Mishura
> <st...@gmail.com> wrote:
> > On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > > Hi Stepan,
> > > >
> > > > Today I was trying to update the buildtest workspace and found that
> > > > you've made several changes to it. I tried to read README.txt but this
> > > > was not very helpful since the file itself looks outdated. Then from
> > > > svn logs I understand that you've added new 'install' target to main
> > > > build.xml . So what is the correct sequence now
> > > >
> > > > ant install
> > > > ant -Dtest.suites=struts_test setup
> > > > ant -Dtest.suites=struts_test run
> > > >
> > >
> > > Yes, this is correct sequence now, but install should has
> > > -Dtest.suites=struts_test param too.
> > >
> > > I'm sorry that I didn't warned about the change and not updated
> > > README. Currently I'm working on infra's improvements to make work
> > > flow more simple/transparent and resolve several issues mentioned on
> > > the dev-list. Please be patient to me if I broke something or the doc
> > > is inconsistent.
> >
> > BTW, if you find something broken please let me know.
> > Also in this case you may use BTI's svn revision < 639550 - it should work.
> >
> > Thanks,
> > Stepan.
> >
> >
> >
> > > After I complete improvements I'm going to align the
> > > README and the page on the web-site.
> > >
> > > Thanks,
> > > Stepan.
> > >
> > > > ?
> > > >
> > > > Regards,
> > > > Alexei
> > > >
> > >
> >
>
Re: [build-test] new ant target
Posted by Eugene Ostrovsky <eu...@gmail.com>.
Hi, Stepan.
I've got 2 failures with BTI build.xml (r640391)
1. when I run
ant -Dtest.suites=tptp install
I've got the following output:
BUILD FAILED
.../infra/build.xml:144: java.io.FileNotFoundException:
.../infra/build/config/resources.location (No such file or directory)
I've managed to fix it by adding the following line
<mkdir dir="${config.dir}" />
to -init-instal target
2. After that the same command produced:
BUILD FAILED
.../infra/build.xml:220: The following error occurred while executing this line:
.../infra/scripts/config.xml:52:
The following error occurred while executing this line:
.../infra/scripts/config.xml:114:
Source resource does not exist: .../infra/framework.local.properties
I've fixed it by adding create-local-configuration dependency to
generate-config target.
Thanks, Eugene.
On Tue, Mar 25, 2008 at 11:38 AM, Stepan Mishura
<st...@gmail.com> wrote:
> On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > Hi Stepan,
> > >
> > > Today I was trying to update the buildtest workspace and found that
> > > you've made several changes to it. I tried to read README.txt but this
> > > was not very helpful since the file itself looks outdated. Then from
> > > svn logs I understand that you've added new 'install' target to main
> > > build.xml . So what is the correct sequence now
> > >
> > > ant install
> > > ant -Dtest.suites=struts_test setup
> > > ant -Dtest.suites=struts_test run
> > >
> >
> > Yes, this is correct sequence now, but install should has
> > -Dtest.suites=struts_test param too.
> >
> > I'm sorry that I didn't warned about the change and not updated
> > README. Currently I'm working on infra's improvements to make work
> > flow more simple/transparent and resolve several issues mentioned on
> > the dev-list. Please be patient to me if I broke something or the doc
> > is inconsistent.
>
> BTW, if you find something broken please let me know.
> Also in this case you may use BTI's svn revision < 639550 - it should work.
>
> Thanks,
> Stepan.
>
>
>
> > After I complete improvements I'm going to align the
> > README and the page on the web-site.
> >
> > Thanks,
> > Stepan.
> >
> > > ?
> > >
> > > Regards,
> > > Alexei
> > >
> >
>
Re: [build-test] new ant target
Posted by Alexei Zakharov <al...@gmail.com>.
Yeah, forgot to say this in my previous message: +1 for Stepan's solution.
Regards,
Alexei
2008/3/26, Alexei Fedotov <al...@gmail.com>:
> Stepan,
> I like your idea about flexibility. It satisfies both use cases.
>
> With best regards, Alexei
>
> On Wed, Mar 26, 2008 at 8:04 AM, Stepan Mishura
>
> <st...@gmail.com> wrote:
> > On 3/25/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > Thanks Stepan. By the way, I also noticed that by default all test
> > > sources are downloaded from
> > >
> > > http://svn.apache.org/repos/....
> > >
> >
> > HTTP is used intentionally - it was assumed that on a test system
> > there is no need in committing updates for test suites.
> >
> > But I think you are right - the infra should be more flexible and let
> > committer do her/his work without additional (i.e. switch --relocate)
> > steps. I think that the infra should follow federated build's way. So
> > if the infra is checked out using HTTPS then tests sources are also
> > checked out via HTTPS.
> >
> > Thanks,
> > Stepan.
> >
> >
> >
> > > This is a bit inconvenient if you are a committer and trying to commit
> > > changes in tests. Because svn refuses to commit anything if the
> > > repository URL doesn't start with HTTPS. So yesterday I had to
> > > recheckout all sources in order to commit a trivial change to struts
> > > tests.
> > >
> > > Thanks,
> > > Alexei
> > >
> > > 2008/3/25, Stepan Mishura <st...@gmail.com>:
> > > > On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > > > > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > > > > Hi Stepan,
> > > > > >
> > > > > > Today I was trying to update the buildtest workspace and found that
> > > > > > you've made several changes to it. I tried to read README.txt but this
> > > > > > was not very helpful since the file itself looks outdated. Then from
> > > > > > svn logs I understand that you've added new 'install' target to main
> > > > > > build.xml . So what is the correct sequence now
> > > > > >
> > > > > > ant install
> > > > > > ant -Dtest.suites=struts_test setup
> > > > > > ant -Dtest.suites=struts_test run
> > > > > >
> > > > >
> > > > > Yes, this is correct sequence now, but install should has
> > > > > -Dtest.suites=struts_test param too.
> > > > >
> > > > > I'm sorry that I didn't warned about the change and not updated
> > > > > README. Currently I'm working on infra's improvements to make work
> > > > > flow more simple/transparent and resolve several issues mentioned on
> > > > > the dev-list. Please be patient to me if I broke something or the doc
> > > > > is inconsistent.
> > > >
> > > >
> > > > BTW, if you find something broken please let me know.
> > > > Also in this case you may use BTI's svn revision < 639550 - it should work.
> > > >
> > > > Thanks,
> > > >
> > > > Stepan.
> > > >
> > > >
> > > > > After I complete improvements I'm going to align the
> > > > > README and the page on the web-site.
> > > > >
> > > > > Thanks,
> > > > > Stepan.
> > > > >
> > > > > > ?
> > > > > >
> > > > > > Regards,
> > > > > > Alexei
> > >
> >
>
>
>
>
> --
> With best regards,
>
> Alexei
>
Re: [build-test] new ant target
Posted by Alexei Fedotov <al...@gmail.com>.
Stepan,
I like your idea about flexibility. It satisfies both use cases.
With best regards, Alexei
On Wed, Mar 26, 2008 at 8:04 AM, Stepan Mishura
<st...@gmail.com> wrote:
> On 3/25/08, Alexei Zakharov <al...@gmail.com> wrote:
> > Thanks Stepan. By the way, I also noticed that by default all test
> > sources are downloaded from
> >
> > http://svn.apache.org/repos/....
> >
>
> HTTP is used intentionally - it was assumed that on a test system
> there is no need in committing updates for test suites.
>
> But I think you are right - the infra should be more flexible and let
> committer do her/his work without additional (i.e. switch --relocate)
> steps. I think that the infra should follow federated build's way. So
> if the infra is checked out using HTTPS then tests sources are also
> checked out via HTTPS.
>
> Thanks,
> Stepan.
>
>
>
> > This is a bit inconvenient if you are a committer and trying to commit
> > changes in tests. Because svn refuses to commit anything if the
> > repository URL doesn't start with HTTPS. So yesterday I had to
> > recheckout all sources in order to commit a trivial change to struts
> > tests.
> >
> > Thanks,
> > Alexei
> >
> > 2008/3/25, Stepan Mishura <st...@gmail.com>:
> > > On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > > > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > > > Hi Stepan,
> > > > >
> > > > > Today I was trying to update the buildtest workspace and found that
> > > > > you've made several changes to it. I tried to read README.txt but this
> > > > > was not very helpful since the file itself looks outdated. Then from
> > > > > svn logs I understand that you've added new 'install' target to main
> > > > > build.xml . So what is the correct sequence now
> > > > >
> > > > > ant install
> > > > > ant -Dtest.suites=struts_test setup
> > > > > ant -Dtest.suites=struts_test run
> > > > >
> > > >
> > > > Yes, this is correct sequence now, but install should has
> > > > -Dtest.suites=struts_test param too.
> > > >
> > > > I'm sorry that I didn't warned about the change and not updated
> > > > README. Currently I'm working on infra's improvements to make work
> > > > flow more simple/transparent and resolve several issues mentioned on
> > > > the dev-list. Please be patient to me if I broke something or the doc
> > > > is inconsistent.
> > >
> > >
> > > BTW, if you find something broken please let me know.
> > > Also in this case you may use BTI's svn revision < 639550 - it should work.
> > >
> > > Thanks,
> > >
> > > Stepan.
> > >
> > >
> > > > After I complete improvements I'm going to align the
> > > > README and the page on the web-site.
> > > >
> > > > Thanks,
> > > > Stepan.
> > > >
> > > > > ?
> > > > >
> > > > > Regards,
> > > > > Alexei
> >
>
--
With best regards,
Alexei
Re: [build-test] new ant target
Posted by Stepan Mishura <st...@gmail.com>.
On 3/25/08, Alexei Zakharov <al...@gmail.com> wrote:
> Thanks Stepan. By the way, I also noticed that by default all test
> sources are downloaded from
>
> http://svn.apache.org/repos/....
>
HTTP is used intentionally - it was assumed that on a test system
there is no need in committing updates for test suites.
But I think you are right - the infra should be more flexible and let
committer do her/his work without additional (i.e. switch --relocate)
steps. I think that the infra should follow federated build's way. So
if the infra is checked out using HTTPS then tests sources are also
checked out via HTTPS.
Thanks,
Stepan.
> This is a bit inconvenient if you are a committer and trying to commit
> changes in tests. Because svn refuses to commit anything if the
> repository URL doesn't start with HTTPS. So yesterday I had to
> recheckout all sources in order to commit a trivial change to struts
> tests.
>
> Thanks,
> Alexei
>
> 2008/3/25, Stepan Mishura <st...@gmail.com>:
> > On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > > Hi Stepan,
> > > >
> > > > Today I was trying to update the buildtest workspace and found that
> > > > you've made several changes to it. I tried to read README.txt but this
> > > > was not very helpful since the file itself looks outdated. Then from
> > > > svn logs I understand that you've added new 'install' target to main
> > > > build.xml . So what is the correct sequence now
> > > >
> > > > ant install
> > > > ant -Dtest.suites=struts_test setup
> > > > ant -Dtest.suites=struts_test run
> > > >
> > >
> > > Yes, this is correct sequence now, but install should has
> > > -Dtest.suites=struts_test param too.
> > >
> > > I'm sorry that I didn't warned about the change and not updated
> > > README. Currently I'm working on infra's improvements to make work
> > > flow more simple/transparent and resolve several issues mentioned on
> > > the dev-list. Please be patient to me if I broke something or the doc
> > > is inconsistent.
> >
> >
> > BTW, if you find something broken please let me know.
> > Also in this case you may use BTI's svn revision < 639550 - it should work.
> >
> > Thanks,
> >
> > Stepan.
> >
> >
> > > After I complete improvements I'm going to align the
> > > README and the page on the web-site.
> > >
> > > Thanks,
> > > Stepan.
> > >
> > > > ?
> > > >
> > > > Regards,
> > > > Alexei
>
Re: [build-test] new ant target
Posted by Alexei Zakharov <al...@gmail.com>.
IMO this depends on whom you see as a target user for BTI. AFAIU there
are two persons who make daily snapshot testing and aware of all BTI
parameters and configuration tips - Stepan and you. And both of you
probably well informed on how to configure BTI properly - where is the
place to change URLs from HTTPS to HTTP and vise versa. All other
users (many of which are committers) are interested only in couple of
test suites and in the most convenient way to run tests, view results
and propagate possible changes in test sources to svn. So for the
current default BTI configuration a quick start guide contains more
required steps (i.e. an extra svn switch) than it may be,
Regards,
Alexei
2008/3/26, Alexey Varlamov <al...@gmail.com>:
> 2008/3/25, Alexei Zakharov <al...@gmail.com>:
>
> > I've tried this, but it reported
> >
> > svn: 'https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/trunk/tests/struts_test'
> > is not the same repository as
> > 'http://svn.apache.org/repos/asf'
> >
> > Now I recall that I probably used "--relocate" switch in the same
> > situation in the past. However, yesterday I wasn't smart enough.
> > Anyway, I don't see much reason in setting the default location to
> > "http://svn.apache.org/blah/blah/blah". Is this a special feature of
> > our BTI? IMO Apache's svn server can afford using HTTPS in case if our
> > CC is not hitting it every two seconds.
>
>
> Anyway HTTPS imposes higher strain on Apache servers - don't forget
> you're not alone hosting CC instance. Besides it increases response
> time for clients (startup time of CCs) - which is noticeable for
> highly charged CC (like our snapshot testing).
> So the _default_ should be HTTP, and in _special cases_ swn switch is
> the friend as they say ;)
>
> Regards,
>
> Alexey
>
>
> >
> > Thanks,
> > Alexei
> >
> > 2008/3/25, Tim Ellison <t....@gmail.com>:
> > > Alexei Zakharov wrote:
> > > > Thanks Stepan. By the way, I also noticed that by default all test
> > > > sources are downloaded from
> > > >
> > > > http://svn.apache.org/repos/....
> > > >
> > > > This is a bit inconvenient if you are a committer and trying to commit
> > > > changes in tests. Because svn refuses to commit anything if the
> > > > repository URL doesn't start with HTTPS. So yesterday I had to
> > > > recheckout all sources in order to commit a trivial change to struts
> > > > tests.
> > >
> > >
> > > In cases like this, where you know it is the same resources at a
> > > different URL, svn switch is your friend.
> > >
> > > Regards,
> > >
> > > Tim
> > >
> > >
> > >
> > > > 2008/3/25, Stepan Mishura <st...@gmail.com>:
> > > >> On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > > >> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > >> > > Hi Stepan,
> > > >> > >
> > > >> > > Today I was trying to update the buildtest workspace and found that
> > > >> > > you've made several changes to it. I tried to read README.txt but this
> > > >> > > was not very helpful since the file itself looks outdated. Then from
> > > >> > > svn logs I understand that you've added new 'install' target to main
> > > >> > > build.xml . So what is the correct sequence now
> > > >> > >
> > > >> > > ant install
> > > >> > > ant -Dtest.suites=struts_test setup
> > > >> > > ant -Dtest.suites=struts_test run
> > > >> > >
> > > >> >
> > > >> > Yes, this is correct sequence now, but install should has
> > > >> > -Dtest.suites=struts_test param too.
> > > >> >
> > > >> > I'm sorry that I didn't warned about the change and not updated
> > > >> > README. Currently I'm working on infra's improvements to make work
> > > >> > flow more simple/transparent and resolve several issues mentioned on
> > > >> > the dev-list. Please be patient to me if I broke something or the doc
> > > >> > is inconsistent.
> > > >>
> > > >>
> > > >> BTW, if you find something broken please let me know.
> > > >> Also in this case you may use BTI's svn revision < 639550 - it should work.
> > > >>
> > > >> Thanks,
> > > >>
> > > >> Stepan.
> > > >>
> > > >>
> > > >> > After I complete improvements I'm going to align the
> > > >> > README and the page on the web-site.
> > > >> >
> > > >> > Thanks,
> > > >> > Stepan.
> > > >> >
> > > >> > > ?
> > > >> > >
> > > >> > > Regards,
> > > >> > > Alexei
> > > >
> > >
> >
>
Re: [build-test] new ant target
Posted by Alexey Varlamov <al...@gmail.com>.
2008/3/25, Alexei Zakharov <al...@gmail.com>:
> I've tried this, but it reported
>
> svn: 'https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/trunk/tests/struts_test'
> is not the same repository as
> 'http://svn.apache.org/repos/asf'
>
> Now I recall that I probably used "--relocate" switch in the same
> situation in the past. However, yesterday I wasn't smart enough.
> Anyway, I don't see much reason in setting the default location to
> "http://svn.apache.org/blah/blah/blah". Is this a special feature of
> our BTI? IMO Apache's svn server can afford using HTTPS in case if our
> CC is not hitting it every two seconds.
Anyway HTTPS imposes higher strain on Apache servers - don't forget
you're not alone hosting CC instance. Besides it increases response
time for clients (startup time of CCs) - which is noticeable for
highly charged CC (like our snapshot testing).
So the _default_ should be HTTP, and in _special cases_ swn switch is
the friend as they say ;)
Regards,
Alexey
>
> Thanks,
> Alexei
>
> 2008/3/25, Tim Ellison <t....@gmail.com>:
> > Alexei Zakharov wrote:
> > > Thanks Stepan. By the way, I also noticed that by default all test
> > > sources are downloaded from
> > >
> > > http://svn.apache.org/repos/....
> > >
> > > This is a bit inconvenient if you are a committer and trying to commit
> > > changes in tests. Because svn refuses to commit anything if the
> > > repository URL doesn't start with HTTPS. So yesterday I had to
> > > recheckout all sources in order to commit a trivial change to struts
> > > tests.
> >
> >
> > In cases like this, where you know it is the same resources at a
> > different URL, svn switch is your friend.
> >
> > Regards,
> >
> > Tim
> >
> >
> >
> > > 2008/3/25, Stepan Mishura <st...@gmail.com>:
> > >> On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > >> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > >> > > Hi Stepan,
> > >> > >
> > >> > > Today I was trying to update the buildtest workspace and found that
> > >> > > you've made several changes to it. I tried to read README.txt but this
> > >> > > was not very helpful since the file itself looks outdated. Then from
> > >> > > svn logs I understand that you've added new 'install' target to main
> > >> > > build.xml . So what is the correct sequence now
> > >> > >
> > >> > > ant install
> > >> > > ant -Dtest.suites=struts_test setup
> > >> > > ant -Dtest.suites=struts_test run
> > >> > >
> > >> >
> > >> > Yes, this is correct sequence now, but install should has
> > >> > -Dtest.suites=struts_test param too.
> > >> >
> > >> > I'm sorry that I didn't warned about the change and not updated
> > >> > README. Currently I'm working on infra's improvements to make work
> > >> > flow more simple/transparent and resolve several issues mentioned on
> > >> > the dev-list. Please be patient to me if I broke something or the doc
> > >> > is inconsistent.
> > >>
> > >>
> > >> BTW, if you find something broken please let me know.
> > >> Also in this case you may use BTI's svn revision < 639550 - it should work.
> > >>
> > >> Thanks,
> > >>
> > >> Stepan.
> > >>
> > >>
> > >> > After I complete improvements I'm going to align the
> > >> > README and the page on the web-site.
> > >> >
> > >> > Thanks,
> > >> > Stepan.
> > >> >
> > >> > > ?
> > >> > >
> > >> > > Regards,
> > >> > > Alexei
> > >
> >
>
Re: [build-test] new ant target
Posted by Alexei Zakharov <al...@gmail.com>.
I've tried this, but it reported
svn: 'https://svn.apache.org/repos/asf/harmony/enhanced/buildtest/trunk/tests/struts_test'
is not the same repository as
'http://svn.apache.org/repos/asf'
Now I recall that I probably used "--relocate" switch in the same
situation in the past. However, yesterday I wasn't smart enough.
Anyway, I don't see much reason in setting the default location to
"http://svn.apache.org/blah/blah/blah". Is this a special feature of
our BTI? IMO Apache's svn server can afford using HTTPS in case if our
CC is not hitting it every two seconds.
Thanks,
Alexei
2008/3/25, Tim Ellison <t....@gmail.com>:
> Alexei Zakharov wrote:
> > Thanks Stepan. By the way, I also noticed that by default all test
> > sources are downloaded from
> >
> > http://svn.apache.org/repos/....
> >
> > This is a bit inconvenient if you are a committer and trying to commit
> > changes in tests. Because svn refuses to commit anything if the
> > repository URL doesn't start with HTTPS. So yesterday I had to
> > recheckout all sources in order to commit a trivial change to struts
> > tests.
>
>
> In cases like this, where you know it is the same resources at a
> different URL, svn switch is your friend.
>
> Regards,
>
> Tim
>
>
>
> > 2008/3/25, Stepan Mishura <st...@gmail.com>:
> >> On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> >> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> >> > > Hi Stepan,
> >> > >
> >> > > Today I was trying to update the buildtest workspace and found that
> >> > > you've made several changes to it. I tried to read README.txt but this
> >> > > was not very helpful since the file itself looks outdated. Then from
> >> > > svn logs I understand that you've added new 'install' target to main
> >> > > build.xml . So what is the correct sequence now
> >> > >
> >> > > ant install
> >> > > ant -Dtest.suites=struts_test setup
> >> > > ant -Dtest.suites=struts_test run
> >> > >
> >> >
> >> > Yes, this is correct sequence now, but install should has
> >> > -Dtest.suites=struts_test param too.
> >> >
> >> > I'm sorry that I didn't warned about the change and not updated
> >> > README. Currently I'm working on infra's improvements to make work
> >> > flow more simple/transparent and resolve several issues mentioned on
> >> > the dev-list. Please be patient to me if I broke something or the doc
> >> > is inconsistent.
> >>
> >>
> >> BTW, if you find something broken please let me know.
> >> Also in this case you may use BTI's svn revision < 639550 - it should work.
> >>
> >> Thanks,
> >>
> >> Stepan.
> >>
> >>
> >> > After I complete improvements I'm going to align the
> >> > README and the page on the web-site.
> >> >
> >> > Thanks,
> >> > Stepan.
> >> >
> >> > > ?
> >> > >
> >> > > Regards,
> >> > > Alexei
> >
>
Re: [build-test] new ant target
Posted by Tim Ellison <t....@gmail.com>.
Alexei Zakharov wrote:
> Thanks Stepan. By the way, I also noticed that by default all test
> sources are downloaded from
>
> http://svn.apache.org/repos/....
>
> This is a bit inconvenient if you are a committer and trying to commit
> changes in tests. Because svn refuses to commit anything if the
> repository URL doesn't start with HTTPS. So yesterday I had to
> recheckout all sources in order to commit a trivial change to struts
> tests.
In cases like this, where you know it is the same resources at a
different URL, svn switch is your friend.
Regards,
Tim
> 2008/3/25, Stepan Mishura <st...@gmail.com>:
>> On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
>> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
>> > > Hi Stepan,
>> > >
>> > > Today I was trying to update the buildtest workspace and found that
>> > > you've made several changes to it. I tried to read README.txt but this
>> > > was not very helpful since the file itself looks outdated. Then from
>> > > svn logs I understand that you've added new 'install' target to main
>> > > build.xml . So what is the correct sequence now
>> > >
>> > > ant install
>> > > ant -Dtest.suites=struts_test setup
>> > > ant -Dtest.suites=struts_test run
>> > >
>> >
>> > Yes, this is correct sequence now, but install should has
>> > -Dtest.suites=struts_test param too.
>> >
>> > I'm sorry that I didn't warned about the change and not updated
>> > README. Currently I'm working on infra's improvements to make work
>> > flow more simple/transparent and resolve several issues mentioned on
>> > the dev-list. Please be patient to me if I broke something or the doc
>> > is inconsistent.
>>
>>
>> BTW, if you find something broken please let me know.
>> Also in this case you may use BTI's svn revision < 639550 - it should work.
>>
>> Thanks,
>>
>> Stepan.
>>
>>
>> > After I complete improvements I'm going to align the
>> > README and the page on the web-site.
>> >
>> > Thanks,
>> > Stepan.
>> >
>> > > ?
>> > >
>> > > Regards,
>> > > Alexei
>
Re: [build-test] new ant target
Posted by Alexei Zakharov <al...@gmail.com>.
Thanks Stepan. By the way, I also noticed that by default all test
sources are downloaded from
http://svn.apache.org/repos/....
This is a bit inconvenient if you are a committer and trying to commit
changes in tests. Because svn refuses to commit anything if the
repository URL doesn't start with HTTPS. So yesterday I had to
recheckout all sources in order to commit a trivial change to struts
tests.
Thanks,
Alexei
2008/3/25, Stepan Mishura <st...@gmail.com>:
> On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > Hi Stepan,
> > >
> > > Today I was trying to update the buildtest workspace and found that
> > > you've made several changes to it. I tried to read README.txt but this
> > > was not very helpful since the file itself looks outdated. Then from
> > > svn logs I understand that you've added new 'install' target to main
> > > build.xml . So what is the correct sequence now
> > >
> > > ant install
> > > ant -Dtest.suites=struts_test setup
> > > ant -Dtest.suites=struts_test run
> > >
> >
> > Yes, this is correct sequence now, but install should has
> > -Dtest.suites=struts_test param too.
> >
> > I'm sorry that I didn't warned about the change and not updated
> > README. Currently I'm working on infra's improvements to make work
> > flow more simple/transparent and resolve several issues mentioned on
> > the dev-list. Please be patient to me if I broke something or the doc
> > is inconsistent.
>
>
> BTW, if you find something broken please let me know.
> Also in this case you may use BTI's svn revision < 639550 - it should work.
>
> Thanks,
>
> Stepan.
>
>
> > After I complete improvements I'm going to align the
> > README and the page on the web-site.
> >
> > Thanks,
> > Stepan.
> >
> > > ?
> > >
> > > Regards,
> > > Alexei
Re: [build-test] new ant target
Posted by Stepan Mishura <st...@gmail.com>.
On 3/22/08, Stepan Mishura <st...@gmail.com> wrote:
> On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > Hi Stepan,
> >
> > Today I was trying to update the buildtest workspace and found that
> > you've made several changes to it. I tried to read README.txt but this
> > was not very helpful since the file itself looks outdated. Then from
> > svn logs I understand that you've added new 'install' target to main
> > build.xml . So what is the correct sequence now
> >
> > ant install
> > ant -Dtest.suites=struts_test setup
> > ant -Dtest.suites=struts_test run
> >
>
> Yes, this is correct sequence now, but install should has
> -Dtest.suites=struts_test param too.
>
> I'm sorry that I didn't warned about the change and not updated
> README. Currently I'm working on infra's improvements to make work
> flow more simple/transparent and resolve several issues mentioned on
> the dev-list. Please be patient to me if I broke something or the doc
> is inconsistent.
BTW, if you find something broken please let me know.
Also in this case you may use BTI's svn revision < 639550 - it should work.
Thanks,
Stepan.
> After I complete improvements I'm going to align the
> README and the page on the web-site.
>
> Thanks,
> Stepan.
>
> > ?
> >
> > Regards,
> > Alexei
> >
>
Re: [build-test] new ant target
Posted by Stepan Mishura <st...@gmail.com>.
On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> Hi Stepan,
>
> Today I was trying to update the buildtest workspace and found that
> you've made several changes to it. I tried to read README.txt but this
> was not very helpful since the file itself looks outdated. Then from
> svn logs I understand that you've added new 'install' target to main
> build.xml . So what is the correct sequence now
>
> ant install
> ant -Dtest.suites=struts_test setup
> ant -Dtest.suites=struts_test run
>
Yes, this is correct sequence now, but install should has
-Dtest.suites=struts_test param too.
I'm sorry that I didn't warned about the change and not updated
README. Currently I'm working on infra's improvements to make work
flow more simple/transparent and resolve several issues mentioned on
the dev-list. Please be patient to me if I broke something or the doc
is inconsistent. After I complete improvements I'm going to align the
README and the page on the web-site.
Thanks,
Stepan.
> ?
>
> Regards,
> Alexei
>
Re: [build-test] new ant target
Posted by Alexei Zakharov <al...@gmail.com>.
Yeah, I found the link, thanks. However, it's not required if I do
ant -Dtest.suites=struts_test install
as Stepan has just suggested. Previously by typing
ant install
I was trying to download all dependencies for all suites. And one of
the suite required maven, probably maven_test. I.e. struts scenario
itself does not require maven.
Thanks,
Alexei
2008/3/23, Sean Qiu <se...@gmail.com>:
> http://archive.apache.org/dist/maven/binaries/maven-2.0.7-bin.zip
>
> This one is ok.
>
> 2008/3/22, Stepan Mishura <st...@gmail.com>:
>
> > On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > > BTW, 'ant install' fails with the following error:
> > >
> > > <---
> > > -download:
> > > [echo] ==> Do Download from
> > > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > > [get] Getting:
> > > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > > [get] To:
> > > /home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
> > > [get] Error opening connection java.io.FileNotFoundException:
> > > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > > [get] Error opening connection java.io.FileNotFoundException:
> > > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > > [get] Error opening connection java.io.FileNotFoundException:
> > > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > > [get] Can't get
> > > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip to
> > > /home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
> > >
> > > BUILD FAILED
> > > <---
> > >
> > > It looks like maven is no longer available at
> > > 'http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip'
> > >
> >
> > Have you found a valid link to the archive?
> >
> > -Stepan.
> >
> > > Regards,
> > > Alexei
> > >
> > > 2008/3/21, Alexei Zakharov <al...@gmail.com>:
> > > > Hi Stepan,
> > > >
> > > > Today I was trying to update the buildtest workspace and found that
> > > > you've made several changes to it. I tried to read README.txt but this
> > > > was not very helpful since the file itself looks outdated. Then from
> > > > svn logs I understand that you've added new 'install' target to main
> > > > build.xml . So what is the correct sequence now
> > > >
> > > > ant install
> > > > ant -Dtest.suites=struts_test setup
> > > > ant -Dtest.suites=struts_test run
> > > >
> > > > ?
> > > >
> > > > Regards,
> > > >
> > > > Alexei
> > > >
> > >
> >
>
>
>
> --
> Best Regards
> Sean, Xiao Xia Qiu
>
> China Software Development Lab, IBM
>
Re: [build-test] new ant target
Posted by Sean Qiu <se...@gmail.com>.
http://archive.apache.org/dist/maven/binaries/maven-2.0.7-bin.zip
This one is ok.
2008/3/22, Stepan Mishura <st...@gmail.com>:
> On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> > BTW, 'ant install' fails with the following error:
> >
> > <---
> > -download:
> > [echo] ==> Do Download from
> > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > [get] Getting:
> > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > [get] To:
> > /home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
> > [get] Error opening connection java.io.FileNotFoundException:
> > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > [get] Error opening connection java.io.FileNotFoundException:
> > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > [get] Error opening connection java.io.FileNotFoundException:
> > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> > [get] Can't get
> > http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip to
> > /home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
> >
> > BUILD FAILED
> > <---
> >
> > It looks like maven is no longer available at
> > 'http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip'
> >
>
> Have you found a valid link to the archive?
>
> -Stepan.
>
> > Regards,
> > Alexei
> >
> > 2008/3/21, Alexei Zakharov <al...@gmail.com>:
> > > Hi Stepan,
> > >
> > > Today I was trying to update the buildtest workspace and found that
> > > you've made several changes to it. I tried to read README.txt but this
> > > was not very helpful since the file itself looks outdated. Then from
> > > svn logs I understand that you've added new 'install' target to main
> > > build.xml . So what is the correct sequence now
> > >
> > > ant install
> > > ant -Dtest.suites=struts_test setup
> > > ant -Dtest.suites=struts_test run
> > >
> > > ?
> > >
> > > Regards,
> > >
> > > Alexei
> > >
> >
>
--
Best Regards
Sean, Xiao Xia Qiu
China Software Development Lab, IBM
Re: [build-test] new ant target
Posted by Stepan Mishura <st...@gmail.com>.
On 3/21/08, Alexei Zakharov <al...@gmail.com> wrote:
> BTW, 'ant install' fails with the following error:
>
> <---
> -download:
> [echo] ==> Do Download from
> http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> [get] Getting:
> http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> [get] To:
> /home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
> [get] Error opening connection java.io.FileNotFoundException:
> http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> [get] Error opening connection java.io.FileNotFoundException:
> http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> [get] Error opening connection java.io.FileNotFoundException:
> http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
> [get] Can't get
> http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip to
> /home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
>
> BUILD FAILED
> <---
>
> It looks like maven is no longer available at
> 'http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip'
>
Have you found a valid link to the archive?
-Stepan.
> Regards,
> Alexei
>
> 2008/3/21, Alexei Zakharov <al...@gmail.com>:
> > Hi Stepan,
> >
> > Today I was trying to update the buildtest workspace and found that
> > you've made several changes to it. I tried to read README.txt but this
> > was not very helpful since the file itself looks outdated. Then from
> > svn logs I understand that you've added new 'install' target to main
> > build.xml . So what is the correct sequence now
> >
> > ant install
> > ant -Dtest.suites=struts_test setup
> > ant -Dtest.suites=struts_test run
> >
> > ?
> >
> > Regards,
> >
> > Alexei
> >
>
Re: [build-test] new ant target
Posted by Alexei Zakharov <al...@gmail.com>.
BTW, 'ant install' fails with the following error:
<---
-download:
[echo] ==> Do Download from
http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
[get] Getting:
http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
[get] To:
/home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
[get] Error opening connection java.io.FileNotFoundException:
http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
[get] Error opening connection java.io.FileNotFoundException:
http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
[get] Error opening connection java.io.FileNotFoundException:
http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip
[get] Can't get
http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip to
/home/ayzakhar/projects/harmony/buildtest/infra/build/temp/maven-2.0.7-bin.zip
BUILD FAILED
<---
It looks like maven is no longer available at
'http://apache.hkmirror.org/maven/binaries/maven-2.0.7-bin.zip'
Regards,
Alexei
2008/3/21, Alexei Zakharov <al...@gmail.com>:
> Hi Stepan,
>
> Today I was trying to update the buildtest workspace and found that
> you've made several changes to it. I tried to read README.txt but this
> was not very helpful since the file itself looks outdated. Then from
> svn logs I understand that you've added new 'install' target to main
> build.xml . So what is the correct sequence now
>
> ant install
> ant -Dtest.suites=struts_test setup
> ant -Dtest.suites=struts_test run
>
> ?
>
> Regards,
>
> Alexei
>