Yes. This could be generated via maven though...
On 12/13/10 12:42 PM, Galder ZamarreƱo wrote:
On Dec 12, 2010, at 11:08 AM, Bela Ban wrote:
> +1
+1 to prefixing config files with "infinispan-"
>
> Fo example, if you named a file udp.xml, it could be either picked from
> the Infinispan JAR or the JGroups JAR, or even somewhere else on the
> classpath.
>
> Hey, you guys might even suffix an XML file with the Infinispan version,
> e.g. infinispan-jgroups-4.2.1.CR1.jar, to prevent a user to pick up a
> config file with the same name from a previous version of Infinispan,
> that happens to linger around somewhere on the classpath...
Not so sure about this. It would mean that with each new release, you'd have to
change the config file or system property to point to a new file, wouldn't you?
>
> On 12/11/10 4:02 PM, Tristan Tarrant wrote:
>> Oops, I forgot something else I wanted to say:
>> aren't those filenames a bit too generic ? Shouldn't we prefix them with
>> infinispan-* ? I was thinking that in future JBoss AS releases, Infinispan
>> might be part of the core distribution, but applications may want to use
>> JGroups by itself and want to use exactly those filenames, but Infinispan's
>> would be found first in the classpath ... Am I being paranoid ?
>
> --
> Bela Ban
> Lead JGroups / Clustering Team
> JBoss
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder ZamarreƱo
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev