Closed MarkusAmshove closed 4 years ago
where does the try for 2.20 / mwe 2.11.1 come from do you use nightlies? do you use repo type p2 in poms too?
you may also try to specify an explict maven repo location on server and local
-Dmaven.repo.local=somedir
as well as telling tycho to ignore local things
-Dtycho.localArtifacts=ignore
I've removed the p2 repositories from the poms in the update from 2.17 -> 2.19, because the generated new project from 2.19 doesn't contain them anymore (only the "disable codehaus-snapshots"). Should I readd them?
The repositories from the target definition point to http://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/
and tycho doesn't seem to fetch 2.20 (according to the logs).
I've just tried localArtifacts=ignore
, which didn't help
Please check your Artifactory. Would the same error occur without the Artifactory proxy and direct usage of the official p2 repos?
are you sure this stems from tycho and not maven deps?
I've consolidated the parent projects pom against the newly generated again and found another difference which fixed the issue.
The fix was to bump maven-clean-plugin
from 2.5 to 3.1.0.
Do you have any idea why this could be related to the versioning?
This is what Jenkins calls:
mvn -Dtycho.localArtifacts=ignore -B verify
no i dont
No idea.
Hi,
I'm currently trying to repair a build for a Xtext based project which uses Tycho to create the plugins and an update site, which I then deploy to Artifactory.
We're working behind a corporate proxy which means we need Artifactory as a repository aggregator, because the workstations and build servers can't access things like mavencentral, download.eclipse.org etc.
I'm trying to update a Xtext project which was untouched for quite some while from 2.17 to 2.19, as I'll have to work on this again. I started by creating a new one and merging the
pom
s with the original project. They are now identical (aside from package/projectnames).I've also consolidated the
MANIFEST.MF
files to match the versions of the newly created 2.19 project.My local build with
mvn verify
now works fine, but in CI it breaks with:This is my target definition:
I think the names of the repositories speak for themselfes. The
xtext-composite
repository points tohttp://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/
I'm not really sure why the CI build is trying to resolve
2.20
, as it shows up nowhere except for the errorThe same happens when I'm trying to use a former version (e.g. 2.18, 2.17, 2.16, ...)
I've also tried to "pin" all bundle dependencies of
xtend.lib
to 2.19 in theMANIFEST.MF
files, but the build was still looking for 2.20.Any advice/guidance on how to resolve this?