<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On May 2, 2013, at 7:11 AM, Jaromir Hamala <<a href="mailto:jaromir.hamala@gmail.com">jaromir.hamala@gmail.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">Hi,</span><div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">does it mean the same classes will be under different packages in EAP and WildFly? Wouldn't this make a transition from WildFly to EAP harder?</div></div></div></blockquote><div><br></div><div>No the same packages would be in EAP and wildfly. So it effectively means that you will be eventually using org.wildfly in EAP.</div><br><blockquote type="cite"><div><div dir="ltr">
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">Cheers,</div><div style="font-family:arial,sans-serif;font-size:13px">Jaromir</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Thu, May 2, 2013 at 12:53 PM, Tomaž Cerar <span dir="ltr"><<a href="mailto:tomaz.cerar@gmail.com" target="_blank">tomaz.cerar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div><div>We never said we are going to be renaming existing packages. <br></div>Especially because we don't want to break compatibly or make back porting harder.<br><br></div>What we did agree on is that new stuff should be in new package names. <br>
Old packages could be renamed only when the got some big upgrade/change that would break compatibility anyway.<br><br><div><div>--<br></div><div>tomaz<br></div><div><br><br><br></div></div></div><div class="HOEnZb"><div class="h5">
<div class="gmail_extra"><br>
<br><div class="gmail_quote">On Thu, May 2, 2013 at 12:48 PM, Bill Burke <span dir="ltr"><<a href="mailto:bburke@redhat.com" target="_blank">bburke@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Are you sure a package name change is a good idea? Won't it make it<br>
harder to pull/push changes upstream and downstream? And create<br>
additional work for those who already are the bottleneck in the release<br>
process? What does Fedora/RHEL do?<br>
<span><font color="#888888">--<br>
Bill Burke<br>
JBoss, a division of Red Hat<br>
<a href="http://bill.burkecentral.com" target="_blank">http://bill.burkecentral.com</a><br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</font></span></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”<br>Antoine de Saint Exupéry
</div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>wildfly-dev mailing list</span><br><span><a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></span><br></div></blockquote></body></html>