I will work on a patch.
Spring DM import in 1.2.0 final is a version range [2.5.6,4.0.0), i.e.
org.springframework.aop.framework;version="[2.5.6,4.0)"
But it will bind to the one from startup.properties unless refreshed I
presume. So including extra version in a feature could cause issues.
SpringSource DM server 1.x is locked down to a single version of
springframework.
What version of spring jars should I use in a patch? One from main maven
repo or from BRITS?
The once used in karaf right now are "old" style artifacts.
The "new" style are like this:
<dependency>
<groupId>org.springframework</groupId>
*<artifactId>org.springframework.core</artifactId>*
<version>2.5.6.A</version>
</dependency>
It looks like this style will survive into 3.0 release.
Thanks again
Dmitry
On Tue, May 12, 2009 at 12:40 PM, Guillaume Nodet <[email protected]> wrote:
> On Tue, May 12, 2009 at 17:43, Dmitry Sklyut
> <[email protected]> wrote:
> > Thank you Gert. I will take a look at the poms that you pointed out (
> they
> > do look a little fat :).
> >
> > Issue raised: *FELIX-1147 <
> https://issues.apache.org/jira/browse/FELIX-1147>
> >
> > *I wanted to try to up the version of spring to 2.5.6.A and later 3.0.
> That
> > is why I was trying to override startup.properties.
> > I also wanted to bump spring-osgi to 1.2.0 final vs. RC release.
>
> I think it makes sense to bump those in Karaf directly. Would you
> want to raise a JIRA and attach a patch for that maybe ?
>
> > Would multiple versions of springframework conflict in the kernel in
> regards
> > to imports and package resolution?
>
> Not sure how spring-dm reacts if multiple versions are deployed. I
> haven't tried it.
> It's worth investigating though. Let us know if you find anything.
>
> > Thanks in advance
> >
> > Dmitry
> >
> > 2009/5/12 Gert Vanthienen <[email protected]>
> >
> >> Dmitry,
> >>
> >> The easiest way to do this is by creating a features descriptor that
> >> contains a list of all the bundles you need for your application. You
> >> can then use the features-maven-plugin add-features-to-repo goal to
> >> copy all the required bundles into a folder. Once that is done, you
> >> can use the Maven assembly plugin to package everything up.
> >>
> >> You can find examples on how to use this in
> >> http://svn.apache.org/viewvc/servicemix/smx4/nmr/trunk/assembly/ and
> >> http://svn.apache.org/viewvc/servicemix/smx4/features/trunk/assembly/.
> >> Looking at the pom files myself now, I guess we really want to put
> >> some effort in making this a little bit easier (either by documenting
> >> it properly or by providing a Maven archetype or plugin) -- could you
> >> raise a JIRA issue for this?
> >>
> >> Regards,
> >>
> >> Gert Vanthienen
> >> ------------------------
> >> Open Source SOA: http://fusesource.com
> >> Blog: http://gertvanthienen.blogspot.com/
> >>
> >>
> >>
> >> 2009/5/12 Dmitry Sklyut <[email protected]>:
> >> > Hi All,
> >> >
> >> > I wonder if there is any examples or documentation on creating custom
> >> > assemblies of karaf?
> >> >
> >> > I need to customize kernel a little bit to package in extra bundles
> and
> >> > features as well as customize startup.properties a tiny bit.
> >> >
> >> > Thanks in advance
> >> >
> >> > Dmitry
> >> >
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [email protected]
> >> For additional commands, e-mail: [email protected]
> >>
> >>
> >
>
>
>
> --
> Cheers,
> Guillaume Nodet
> ------------------------
> Blog: http://gnodet.blogspot.com/
> ------------------------
> Open Source SOA
> http://fusesource.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
