> To: dev@maven.apache.org
> Subject: Re: More hard problems...
> Date: Tue, 26 Nov 2013 22:57:45 +0100
> From: e...@zusammenkunft.net
>
> Am 26.11.2013, 22:02 Uhr, schrieb Robert Scholte <rfscho...@apache.org>:
> > In addition to this story: There's an open issue called MDEPLOY-118
> > which describes a related issue: how to release the same version for
> > different platforms?
>
> Related there is also the need for "features". Larger projects typically
> have a lot of optional dependencies but dont help to requesat a specific
> subset. For example a Scheduler like Quartz offers a core engine but also
MG>Here are the Quartz configuration properties i have
org.quartz.scheduler.instanceName = JBossQuartzScheduler
org.quartz.threadPool.class = org.quartz.simpl.SimpleThreadPool
org.quartz.threadPool.threadCount = 10
org.quartz.threadPool.threadPriority = 5
org.quartz.threadPool.threadsInheritContextClassLoaderOfInitializingThread =
true
MG>would you know of a plugin that will update my quartz.properties
MG>in org\jboss\resource\adapter\quartz\inflow
> EJB APIs or a Servlet manager implementation. In an ideal world the
> project would be split into multiple artifacts, but even then there can be
> a complexity explosion. Depending on the "core scheduler" feature of
> "quartz" would then skip all optional dependencies (like servlet and EJB
> API).
MG>How best to configure quartz core scheduler feature?
MG>What would this look like?
>
> (This is similiar to the testing scope, which could be implemented as a
> well known "feature"). And this also goes in line with
> platforms/implementations: the "jdk1.4" feature can depend on a
> concurrent-backport wherees the java7 does not.
>
> Gruss
> Bernd
MG>Beste Grüße
MG>Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
