[wildfly-dev] Mixing org.jboss.as and org.wildfly packages

Josef Cacek jcacek at redhat.com
Thu Apr 6 02:56:52 EDT 2017


I think, Tomaz should share his view (CC-ing)

During our discussion related to Elytron testing, his preference was to use org.wildfly package names.

-- Josef

----- Original Message -----
> From: "Stuart Douglas" <stuart.w.douglas at gmail.com>
> To: wildfly-dev at lists.jboss.org
> Sent: Monday, April 3, 2017 3:45:59 AM
> Subject: [wildfly-dev] Mixing org.jboss.as and org.wildfly packages
> 
> Hi,
> 
> So this is a minor issue, but it annoys me so I thought I would see what
> other people think about it. In the test suite I have noticed that some new
> code is being added under the org.wildfly package, even though all the
> existing code is still under org.jboss.as .
> 
> I don't think this is a good idea, as it means there is two potential places
> to look for something, with no real reason why something is in a particular
> package other than the date it was added.
> 
> I propose that we move all the org.wildfly code into org.jboss.as to keep
> everything consistent (moving everything to org.wildfly would also be an
> option, but it has implications for backporting and has the potential to
> create a lot more work).
> 
> Does anyone have any objections to this? If not I will prepare some PR's.
> 
> Stuart
> 
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev


More information about the wildfly-dev mailing list