Hi all,
last update around this topic.
I committed an update of the CreateKar and InstallKar goal of the Karaf
maven plugin. In the mean time, I made a refactoring of the MvnUrlUtil
class renamed as MavenUtil class including a static method dedicated for
metadata generation.
Now:
- createKar detects SNAPSHOT artifact and generate a
maven-metadata-repo.xml in the repository/ folder of the KAR file.
- in addition of the KAR file, the installKar goal now does the same for
the features XML artifact (at installation time).
It tries first to use the maven-metadata-repo.xml present in the local
repo, else it generates the file (using the Artifact information).
It means that now, Karaf will download a SNAPSHOT artifact from a remote
repo only if it's more recent (lastUpdate tag of the maven-metadata)
than the one present in the sytem repo.
It's only valid for SNAPSHOT, as the lifecycle is different for a release.
Regards
JB
On 02/10/2012 08:39 AM, Jean-Baptiste Onofré wrote:
Hi guys,
Following the Achim's latest commit, I updated my patch around artifact
resolution.
However, I saw a side effect, depending the repositories defined in the
etc/org.ops4j.pax.url.mvn.cfg file (it only affects SNAPSHOT).
I'm working on it.
Regards
JB
On 02/09/2012 07:55 AM, Jean-Baptiste Onofré wrote:
Hi all,
I have something ready and it looks good. I will add the "offline" mode.
I will commit today.
Regards
JB
--
Jean-Baptiste Onofré
jbono...@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
