The AS7 module system seems like the way I would prefer to go, need to look into that and see if it would be compatible with maven dependencies (or possible to make that way with a little hackery.)<br><br>If anyone wants to look into this as well, I'd welcome the analysis.<br>
<br>I've added a JIRA to track progress on this effort:<br><br><a href="https://issues.jboss.org/browse/SEAMFORGE-136">https://issues.jboss.org/browse/SEAMFORGE-136</a><br><br>~Lincoln<br><br><div class="gmail_quote">
On Mon, Apr 11, 2011 at 12:59 PM, Paul Bakker <span dir="ltr"><<a href="http://paul.bakker.nl">paul.bakker.nl</a>@<a href="http://gmail.com">gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
That's what I mean by the module system in AS7 :-)<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Mon, Apr 11, 2011 at 6:50 PM, Rodney Russ <span dir="ltr"><<a href="mailto:rruss@redhat.com" target="_blank">rruss@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">How about JBoss Modules?<br>
<br>
<a href="http://relation.to/16904.lace" target="_blank">http://relation.to/16904.lace</a><br>
<br>
----- "Paul Bakker" <<a href="http://paul.bakker.nl" target="_blank">paul.bakker.nl</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>> wrote:<br>
<br>
> From: "Paul Bakker" <<a href="http://paul.bakker.nl" target="_blank">paul.bakker.nl</a>@<a href="http://gmail.com" target="_blank">gmail.com</a>><br>
> To: "forge-dev List" <<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>><br>
> Sent: Monday, April 11, 2011 10:32:19 AM GMT -07:00 US/Canada Mountain<br>
> Subject: Re: [forge-dev] shading!?<br>
<div><div></div><div>><br>
> The ultimate solution would be to use a completely isolated<br>
> classloader for plugins and plugin dependencies so that plugins would<br>
> even be able to package different versions of libraries that are also<br>
> used by Forge. Running Forge in an OSGi container seems to be the<br>
> obvious solution. I'm no OSGi expert though, so I can't really see the<br>
> consequences. No idea if Weld still works within OSGi bundles for<br>
> example, but it's something to consider. Besides OSGi there's the<br>
> module system that's part of AS7, maybe that's another option.<br>
><br>
><br>
> Paul<br>
><br>
><br>
> On Mon, Apr 11, 2011 at 4:00 PM, Lincoln Baxter, III <<br>
> <a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a> > wrote:<br>
><br>
><br>
> Yeah, shading is currently the recommended approach. Conflicts should<br>
> be avoided by using relocations. I know this is... not a great method,<br>
> but for now it's all we've got. Open to suggestions.<br>
><br>
> ~Lincoln<br>
><br>
><br>
><br>
><br>
><br>
> On Mon, Apr 11, 2011 at 3:41 AM, Max Rydahl Andersen <<br>
> <a href="mailto:max.andersen@redhat.com" target="_blank">max.andersen@redhat.com</a> > wrote:<br>
><br>
><br>
> Heya,<br>
><br>
> Lincoln, I just saw your commits to hibernattools plugin at (<br>
> <a href="https://github.com/forge/plugin-hibernate-tools/commit/8b208b4a8e79dbb8a01d10d266ee81afd2cf7106" target="_blank">https://github.com/forge/plugin-hibernate-tools/commit/8b208b4a8e79dbb8a01d10d266ee81afd2cf7106</a><br>
> )<br>
><br>
> Is shading of jars really the recommended approach for plugins in<br>
> Forge ?<br>
><br>
> How are you going to share/avoid collisions of libraries across<br>
> plugins if they need to bundle via shading ?<br>
><br>
> /max<br>
> <a href="http://about.me/maxandersen" target="_blank">http://about.me/maxandersen</a><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
><br>
><br>
><br>
> --<br>
> Lincoln Baxter, III<br>
> <a href="http://ocpsoft.com" target="_blank">http://ocpsoft.com</a><br>
> <a href="http://scrumshark.com" target="_blank">http://scrumshark.com</a><br>
> "Keep it Simple"<br>
><br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</div></div></blockquote></div><br>
</div></div><br>_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>"Keep it Simple"<br>