You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Guillaume Nodet (JIRA)" <ji...@apache.org> on 2008/05/09 08:40:43 UTC
[jira] Commented: (SMX4KNL-34) snapshot jar name mismatch in
startup.properties and in the system folder
[ https://issues.apache.org/activemq/browse/SMX4KNL-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42606#action_42606 ]
Guillaume Nodet commented on SMX4KNL-34:
----------------------------------------
You're right. I'm not sure what happens, but this does not occur if you build the snapshot dependencies yourself.
Anyway, I will switch to released versions of pax-logging and gshell asap.
> snapshot jar name mismatch in startup.properties and in the system folder
> -------------------------------------------------------------------------
>
> Key: SMX4KNL-34
> URL: https://issues.apache.org/activemq/browse/SMX4KNL-34
> Project: ServiceMix Kernel
> Issue Type: Bug
> Reporter: Freeman Fang
> Priority: Minor
>
> for instance, we specify the pax-logging-api-1.1-SNAPSHOT.jar in startup.properties, but it's real name in the system folder is pax-logging-api-1.1-20080507.113353-4.jar, the snapshot with timestamp is picked up
> this will cause fail when start servicemix4 kernel
> I saw in the kit assembly, we already use filter like
> ${pax.logging.version} to pick up the correct jar, so I guess the maven snapshot jar match mechinasm cause this problem
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.