Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] testing m2e conectors

Using remoterepo actually makes the tests execute much faster.
As for being self-contained, I'm using explicit target platform for tycho build and it accesses the remote P2 repositories on each build, and if the network is down, the build fails. By the way, repository access takes a really long time, about 90s in my case. From what I've read there are problems in Tycho/P2 (bugs 344664, 347477) that cause much more network traffic than necessary. I need to search Tycho docs & mailing lists for possible workarounds. If someone could point me to some useful resources, I'd appreciate it :)

regards,
Rafał

On 07/04/2011 01:43 PM, Igor Fedorenko wrote:
The idea was to keep tests self-contained and not dependent on any
remote system. Although time to execute the tests is important, it was
not our primary concern.

There is no way to disable index download at the moment.

--
Regards,
Igor

On 11-07-04 3:33 PM, Rafał Krzewski wrote:
I have another question regarding resting m2e connectors.

The test modules in m2eclipse-extras contain "remoterepo" directories
that contain slices of maven repository with dependencies required by
the test projects, plugged in as "central" repository using settings.xml.

This strikes me as weird, because NOT putting jars into SCM repositories
is one of core tenets of Maven!

I tried setting up my test project without this, but I found that the
projects' dependencies are downloaded from repo1 without problems, the
build hangs for a long time downloading repository index (not to mention
several hundred MB bandwidth burned / disk space used)

My tests don't need to use the index and I'd be happy to disable the
download. I've looked at
org.eclipse.m2e.core.embedder.IMavenConfiguration, hoping I could
disable index download during initialization of my test case, but first,
IMavenConfiguration does not have setUpdateIndexesOnStartup method,
second, even if it did, that could have been not enough, because when
AbstractMavenProjectTestCase.setUp is executed, the test application is
already running and the index download has started.

This makes me wonder if the repoterepo thing is used only to avoid
repository index download, or is there another reason I am not aware of?
Index download is a showstopper for running tests so I will go forward
with commiting jars to SCM, but if there is any other solution, I'd like
to try it out :)

cheers,
Rafał
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-dev



Back to the top