On Feb 2, 2011, at 8:32 AM, Grégory Joseph wrote:
> > Hey Jörg, > > On 01 Feb 2011, at 21:29, Jörg Schaible wrote: > >>> <...> >>> desired version and hence complains. Should be enough to adapt the >>> stk-dependency in your module descriptor to <version>1.4.2</version> or >>> maybe something like <version>1.4/*</version>. >> >> Shhhhhhhh, OK, got it. I thought that updating the POM is enough, but I >> forgot >> that module descriptor ... I'm tempted to filter it as resource ;-) > > Yeah, that's sometimes a pita. Maven-filtering might work, but I'm afraid the > range syntax in Maven is different than ours (albeit much more > comprehensive). I've laid down a few ideas to write a Maven plugin that would > completely generate the module descriptors (MAGNOLIA-3518), and now I wonder > if we should adopt the Maven (and OSGI, iirc) notation for version ranges, or > have that plugin "transform" them into our much more limited notation. > > Thoughts ? Personally I'd prefer if Magnolia adopted the "standard" maven/osgi syntax ... it's easier to sync with systems that already use the syntax and since it's used much more often, chances are that more people will understand it straight away. > -g > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
