[esb-issues] [JBoss JIRA] (JBESB-3982) Can't update a SNAPSHOT osgi bundle to "latest" version with Jboss Fuse 7

[Marco Tenti (Jira)]

     [ https://issues.jboss.org/browse/JBESB-3982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marco Tenti updated JBESB-3982:
-------------------------------
         Original Estimate: 0 minutes
        Remaining Estimate: 0 minutes
    Workaround Description: 
After a week end of tentatives, i found out a workaround.

You must set the updatepolicy to always like suggested from the 
https://access.redhat.com/solutions/2097131

after that return to the file of Fuse 
/fuse-karaf-7.3.0/etc/org.ops4j.pax.url.mvn.cfg

and comment all the default local repository, so :
BEFORE

{code:xml}
org.ops4j.pax.url.mvn.defaultRepositories = \
    file:${karaf.home}/${karaf.default.repository}@snapshots at id=karaf.${karaf.default.repository}, \
    file:${user.home}/.m2/repository at snapshots@id=local, \
    file:${karaf.base}/${karaf.default.repository}@snapshots at id=karaf.child.${karaf.default.repository}
{code}

AFTER

{code:xml}
# org.ops4j.pax.url.mvn.defaultRepositories = \
#    file:${karaf.home}/${karaf.default.repository}@snapshots at id=karaf.${karaf.default.repository}, \
#    file:${user.home}/.m2/repository at snapshots@id=local, \
#    file:${karaf.base}/${karaf.default.repository}@snapshots at id=karaf.child.${karaf.default.repository}
{code}



and now  when i update a bundle on the karaf shell "DOWNLOAD AND INSTALL THE LATEST VERSION".

Hope to save someone else time with this solution







  was:
After a week end of tentatives, i found out a workaround.

You must set the updatepolicy to always like suggested from the 
https://access.redhat.com/solutions/2097131

after that return to the file of Fuse 
/fuse-karaf-7.3.0/etc/org.ops4j.pax.url.mvn.cfg

and comment all the default local repository, so :
BEFORE

{code:xml}
org.ops4j.pax.url.mvn.defaultRepositories = \
    file:${karaf.home}/${karaf.default.repository}@snapshots at id=karaf.${karaf.default.repository}, \
    file:${user.home}/.m2/repository at snapshots@id=local, \
    file:${karaf.base}/${karaf.default.repository}@snapshots at id=karaf.child.${karaf.default.repository}
{code}

AFTER

{code:xml}
# org.ops4j.pax.url.mvn.defaultRepositories = \
#    file:${karaf.home}/${karaf.default.repository}@snapshots at id=karaf.${karaf.default.repository}, \
#    file:${user.home}/.m2/repository at snapshots@id=local, \
#    file:${karaf.base}/${karaf.default.repository}@snapshots at id=karaf.child.${karaf.default.repository}
{code}



and now  when i update a bunlde on the karaf shell "DOWNLOAD AND INSTALL THE LATEST VERSION".

Hope to save someone else time withthis solution









RESOLVED WITH WORK AROUND

> Can't update a SNAPSHOT osgi bundle to "latest" version with Jboss Fuse 7
> -------------------------------------------------------------------------
>
>                 Key: JBESB-3982
>                 URL: https://issues.jboss.org/browse/JBESB-3982
>             Project: JBoss ESB
>          Issue Type: Bug
>          Components: Configuration
>         Environment: JBOSS FUSE KARAF : 7.3.0
> S.O. : CENTO-OS 7.X.X
> JAVA JDK : OpenJDK 64-Bit Server VM (build 25.212-b04, mixed mode)
>            Reporter: Marco Tenti
>            Priority: Major
>              Labels: Fuse, Maven, bundle, bundles, fuse, maven2
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have installed a Jboss Fuse Karaf version 7.3.0.
> I'm trying to update a SNAPSHOT osgi bundle, but it's keep to not download the latest version, but instead use the version already downloaded on the maven repository (/root/.m2 or standard /opt/fues-7.3.0/data/repository).
> I have tried the solution confirmed in this thread 
> https://access.redhat.com/solutions/2097131
> but it's seems no to work.
> The only ugly solution i find is to delete the maven jar donwloaded on the repository and then the maven is force to call the remote repository and download the "latest" version.ù
> But i can't use the hawtio console in this use case.
> It's seems some configuration problem anyone have suggestion?



--
This message was sent by Atlassian Jira
(v7.12.1#712002)