On 19/12/2007, Matt Brozowski <[EMAIL PROTECTED]> wrote:
>
> I am having trouble building pax with an empty repository because the
> version set for the maven-bundle-plugin is RELEASE. Is this supposed
> to work like this? I haven't seen this before.
yes, it's been like that for many months now - Maven should check the
repository
metadata for the latest release version and use that to download the latest
release
of the OPS4J patched bundleplugin.
could you post the actual error / exception you see ("having trouble" is
very vague)
things to look into:
are you behind a company firewall? (ie. do other OPS4J artifacts
download ok)
are you using a Maven repository proxy? (such as Archiva or Proximity)
do you have a customized settings.xml? (ie. any proxy or update
settings)
try mvn -U -X clean install (send us the last set of lines where the
error occurs)
try removing .m2/repository/org/ops4j/pax/maven (in case it's been
corrupted)
if all else fails, you could try manually updating the pax project pom in
your local
repository to point to 0.9.15 (the latest release) - but this is really a
last resort,
as you should be able to get it to work without hacking around :)
HTH
Matt
>
> ___________________________________________________________________________
> Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984
> The OpenNMS Group, Inc. Fax: +1 503 961 7746
> Email: [EMAIL PROTECTED] URL: http://www.opennms.com
>
>
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
>
--
Cheers, Stuart
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
