Hi,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?
Cheers,JaromirOn Thu, May 2, 2013 at 12:53 PM, Tomaž Cerar <tomaz.cerar@gmail.com> wrote:What we did agree on is that new stuff should be in new package names.We never said we are going to be renaming existing packages.Especially because we don't want to break compatibly or make back porting harder.
Old packages could be renamed only when the got some big upgrade/change that would break compatibility anyway.--tomaz
On Thu, May 2, 2013 at 12:48 PM, Bill Burke <bburke@redhat.com> wrote:Are you sure a package name change is a good idea? Won't it make it
harder to pull/push changes upstream and downstream? And create
additional work for those who already are the bottleneck in the release
process? What does Fedora/RHEL do?
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
--
“Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.”
Antoine de Saint Exupéry
_______________________________________________
wildfly-dev mailing list
wildfly-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev