Sorry for the late response since you have already sent the PR, but I would
suggest using "jboss-javaee7-eap" since javaee7 is a more common term.
On Fri, Oct 9, 2015 at 10:34 AM, Markus Eisele <meisele(a)redhat.com> wrote:
+1
Makes sense to me!
M
On Oct 9, 2015 4:15 PM, "Paul Gier" <pgier(a)redhat.com> wrote:
> Hi Everyone,
>
> I realized the ".0" is probably redundant in "javaee-7.0", since
there
> will never be a "javaee-7.1". And the "7.0" sort of makes it
seem like
> we are referring to the EAP version in some of the BOM artifactIds such
> as "jboss-javaee-7.0-eap". I propose we change these artifactIds to use
> "7" instead of "7.0". So, for example:
>
> jboss-javaee-7.0-eap -> jboss-javaee-7-eap
>
> We haven't released eap 7.0 Alpha yet, so I think these current
> artifactIds have not spread too far into the wild yet to cause much of a
> problem.
>
> The trickier case would be the javaee specs BOM
> (org.jboss.spec:jboss-javaee-7.0) since this does already have some
> official community releases in Nexus. So we should probably just leave
> this one as-is.
>
> Thanks in advance for any feedback!
> _______________________________________________
> jbossdeveloper mailing list
> jbossdeveloper(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
>
_______________________________________________
jbossdeveloper mailing list
jbossdeveloper(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbossdeveloper
--
*Rafael Benevides | Senior Software Engineer*
JBoss Developer Materials lead
M: +1-919-592-6255
Better technology. Faster innovation. Powered by community collaboration.
See how it works at
www.redhat.com