Hello
I do agree with Camille
Release should use a specific
version,
For instance maven release plugin
(http://maven.apache.org/maven-release/maven-release-plugin/)
, do not authorized to reference any –SNAPSHOT version in a
pom for dependencies.
You have to switch them to a specific
version.
But I am still not able to build
papyrus locally due to a missing file in mirror.
How can I get this file?
As a non commiter, I have no access
to the Hudson workspace, so I cannot retrieve the file from
Hudson web site.
Why we do not activate a profile that
use the official eclipse nexus repository as mirror to
predownload all stuff?
Thanks
Have a good day.
Francois
[INFO] Fetching
org.eclipse.swt.win32.win32.x86_64_3.104.0.v20150528-0211.jar.pack.gz
from
http://eclipse.mirror.garr.it/mirrors/eclipse//eclipse/updates/4.5milestones/S-4.5RC4-201506032000/plugins/
(0B of 1,13MB at 0B/s)
[INFO] Fetching
lpg.runtime.java_2.0.17.v201004271640.jar.pack.gz from
http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.0.0/S201506090403/plugins/
(0B of 48,93kB at 0B/s)
[ERROR] An error occurred while
transferring artifact packed:
osgi.bundle,org.eclipse.ocl.common,1.3.0.v20150519-0914 from
repository
http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.0.0/S201506090403:
[ERROR] Retry another mirror:
[ERROR] Artifact not found:
http://mirror.netcologne.de/eclipse//modeling/mdt/ocl/updates/milestones/6.0.0/plugins/org.eclipse.ocl.common_1.3.0.v20150519-0914.jar.pack.gz.
[ERROR] Internal error:
org.eclipse.tycho.repository.local.MirroringArtifactProvider$MirroringFailedException:
Could not mirror artifact
osgi.bundle,org.eclipse.ocl.common,1.3.0.v20150519-0914 into
the local Maven repository.See log output for details.
http://mirror.netcologne.de/eclipse//modeling/mdt/ocl/updates/milestones/6.0.0/plugins/org.eclipse.ocl.common_1.3.0.v20150519-0914.jar.pack.gz
-> [Help 1]
org.apache.maven.InternalErrorException:
Internal error:
org.eclipse.tycho.repository.local.MirroringArtifactProvider$MirroringFailedException:
Could not mirror artifact
osgi.bundle,org.eclipse.ocl.common,1.3.0.v20150519-0914 into
the local Maven repository.See log output for details.
at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
at
org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
at
org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
at
org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
at
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at
java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
Caused by:
org.eclipse.tycho.repository.local.MirroringArtifactProvider$MirroringFailedException:
Could not mirror artifact
osgi.bundle,org.eclipse.ocl.common,1.3.0.v20150519-0914 into
the local Maven repository.See log output for details.
at
org.eclipse.tycho.repository.local.MirroringArtifactProvider.downloadArtifact(MirroringArtifactProvider.java:226)
at
org.eclipse.tycho.repository.local.PackedFormatMirroringArtifactProvider.makeOneFormatLocallyAvailable(PackedFormatMirroringArtifactProvider.java:38)
at
org.eclipse.tycho.repository.local.MirroringArtifactProvider.makeLocallyAvailable(MirroringArtifactProvider.java:182)
at
org.eclipse.tycho.repository.local.MirroringArtifactProvider.getArtifactFile(MirroringArtifactProvider.java:121)
at
org.eclipse.tycho.repository.p2base.artifact.provider.CompositeArtifactProvider.getArtifactFile(CompositeArtifactProvider.java:85)
at
org.eclipse.tycho.p2.target.TargetPlatformBaseImpl.getLocalArtifactFile(TargetPlatformBaseImpl.java:128)
at
org.eclipse.tycho.p2.resolver.P2ResolverImpl.addUnit(P2ResolverImpl.java:254)
at
org.eclipse.tycho.p2.resolver.P2ResolverImpl.toResolutionResult(P2ResolverImpl.java:217)
at
org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:209)
at
org.eclipse.tycho.p2.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:116)
at
org.eclipse.tycho.p2.resolver.P2DependencyResolver.doResolveDependencies(P2DependencyResolver.java:367)
at
org.eclipse.tycho.p2.resolver.P2DependencyResolver.resolveDependencies(P2DependencyResolver.java:335)
at
org.eclipse.tycho.core.resolver.DefaultTychoResolver.resolveProject(DefaultTychoResolver.java:117)
at
org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:95)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:266)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
... 11 more
Caused by:
java.io.FileNotFoundException:
http://mirror.netcologne.de/eclipse//modeling/mdt/ocl/updates/milestones/6.0.0/plugins/org.eclipse.ocl.common_1.3.0.v20150519-0914.jar.pack.gz
at
org.eclipse.equinox.internal.p2.transport.ecf.RepositoryStatusHelper.checkFileNotFound(RepositoryStatusHelper.java:297)
at
org.eclipse.equinox.internal.p2.transport.ecf.FileReader.checkException(FileReader.java:478)
at
org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:435)
at
org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:358)
at
org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
at
org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
at
org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:669)
at
org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:591)
at
org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getRawArtifact(SimpleArtifactRepository.java:732)
at
org.eclipse.tycho.repository.p2base.artifact.repository.RepositoryArtifactProvider.getRawArtifactFromRepository(RepositoryArtifactProvider.java:275)
at
org.eclipse.tycho.repository.p2base.artifact.repository.RepositoryArtifactProvider.getRawArtifactFromAnySource(RepositoryArtifactProvider.java:259)
at
org.eclipse.tycho.repository.p2base.artifact.provider.CompositeArtifactProviderBaseImpl.getRawArtifact(CompositeArtifactProviderBaseImpl.java:70)
at
org.eclipse.tycho.repository.local.PackedFormatMirroringArtifactProvider.downloadRawArtifact(PackedFormatMirroringArtifactProvider.java:70)
at
org.eclipse.tycho.repository.local.PackedFormatMirroringArtifactProvider.downloadMostSpecificNeededFormatOfArtifact(PackedFormatMirroringArtifactProvider.java:57)
at
org.eclipse.tycho.repository.local.MirroringArtifactProvider.downloadArtifact(MirroringArtifactProvider.java:222)
... 27 more
[ERROR]
[ERROR] To see the full stack trace
of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X
switch to enable full debug logging.
[ERROR]
[ERROR] For more information about
the errors and possible solutions, please read the following
articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
Hi Ed,
That’s a recommended good practice
for the release train: be as accurate as possible when
specifying build dependencies, to avoid random errors
These update sites may indeed be
broken during each milestone, but they are automatically
generated anyway, so that’s not an issue (And at least we
know when our dependencies change. Unless they use a
“/latest” update site, in which case we just find new random
errors from time to time...)
I’d rather have a build that fails
early and is easy to fix than something more robust which
allows unexpected changes to sneak into the build, and may
sometimes cause hard-to-detect side effects
Camille
Hi
Shouldn't you either be flexible so that the development setup
uses the latest from
http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.0.0
or autogenerate the content so that it
does not break so regularly?
Anything referencing an explicit milestone is just about
guaranteed to be broken within 3 months, certainly within a
year.
Regards
Ed Willink
On 15/06/2015 14:41, LETAVERNIER Camille wrote:
Hi,
All POMs are configured to use this
update site:
<repository>
<id>mdt-ocl</id>
<layout>p2</layout>
<!--
updateFrom("MDT OCL 6.0",0) -->
<url>http://download.eclipse.org/modeling/mdt/ocl/updates/milestones/6.0.0/S201506090403</url>
</repository>
And I’ve had the same error when
building Papyrus locally (“Main” and “Extra” I think, but
tests were OK), after cleaning my local Maven repository
Also, Eclipse seems to work fine
for Main, Extra and Main-Tests (Failing on Extra-Tests for
a different mysterious reason)
Ø However
Eclipse projects are prohibited from premature release so
you probably shouldn't be trying to install it.
Well, that doesn’t really apply to “building” and
“testing”. It’s mostly a matter of communication and
“making artifacts visible”.
Camille
On 15/06/2015 12:50, LE FEVRE FRANCOIS
wrote:
Hi
That is OCL RC2. The OCL retention policy is two milestones,
and in preparation for Mars release dead milestones have
been pruned. You should be accessing RC3 or RC4 from
milestones or the true release from releases. However
Eclipse projects are prohibited from premature release so
you probably shouldn't be trying to install it.
It would appear that the Papyrus maven artefacts are stale.
Regards
Ed Willink
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2015.0.6030 / Virus Database: 4360/10019 - Release
Date: 06/15/15