What I ended up doing was mirroring the repositories, and setting in the
setting.xml file, a mirrorOf entry, that pointed back to our local Nexus
repo, which had the checksum set to Warn.
Dave
On 07/26/2011 12:03 AM, Pradeep Fernando wrote:
Hi,
I too got this problem while migrating carbon-core to maven3 build
system. The shown error is valid in the sense, we dont have poms for
osgi related artifacts in our maven2 repository.[1]. Ideally we should
have deployed the third-party eclipse jars with generated poms.
I was able to get my build going by changing the checksum policy to
warn[2] in the repositories section of my local poms. In the carbon
code base you will find this in the carbon platform pom.
[1]
http://dist.wso2.org/maven2/org/eclipse/osgi/org.eclipse.osgi.services/3.2.0.v20090520-1800/
[2]<checksumPolicy>warn</checksumPolicy>
thanks,
--Pradeep
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
_______________________________________________
Carbon-dev mailing list
[email protected]
http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
