I agree. I wouldn't want this to be tied to the classpath.
Richard/Max, is there a JIRA for this?
Thanks,
Lincoln
On Tue, Jan 10, 2012 at 10:51 AM, Dan Allen <dan.j.allen(a)gmail.com
<mailto:dan.j.allen@gmail.com>> wrote:
On Tue, Jan 10, 2012 at 07:28, Max Rydahl Andersen <max.andersen(a)redhat.com
<mailto:max.andersen@redhat.com>> wrote:
…but these things should *not* be loaded via a class path bound getResource API
imo.
I don't see a reason to link this to the classpath either. Though, it would be
nice to support archives (you'd have to read from a JAR then).
Through extension, it should be possible to load from a directory or the classpath.
My point is, just don't hard link it to a classpath location.
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org <mailto:forge-dev@lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.com
http://scrumshark.com
"Keep it Simple"
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev