org.jboss.bom:jboss-wfk-arquillian should be renamed to com.redhat.jboss.wfk.boms:jboss-wfk-arquillian to correspond with other WFK BOMs groupId.
Well, if we are doing a full groupId change, the question is if we need to keep jboss-wfk-arquillian at all. It can be merged into com.redhat.jboss.wfk:*-with-tools directly.
It depends on you, Karel. You are the author of jboss-wfk-arquillian and I recall only that it was split on purpose from that *-with-tools BOM. So I am fine with both solutions. Decide what you want more.
What would make the productization simpler? Would we keep jboss-wfk-arquillian in EAP -with-tools version?
I chatted with Karel and agreed on all WFK BOMs should have the same groupId.
jboss-arquillian-bom should have same groupId as *-with* BOMs. This change would move it to the correct location, as currently it is placed in a wrong directory in Maven repository.
Karel, do we need jboss-wfk-arquillian at all if we have our own WFK jboss-javaee-6.0-with-tools? I recall you said something similar on IRC.
Marek, we can make our own javaee-6.0-with-tools and move the content of jboss-wfk-arquillian there. So the file itself is not needed.
I merged jboss-wfk-arquillian with javaee-6.0-with-tools and the result is at http://git.app.eng.bos.redhat.com/?p=jboss/jboss-bom.git;a=blob_plain;f=jboss-javaee-6.0-with-tools/pom.xml;hb=1399b369ce5dffd172c4d2daf73acdee8daf8f13 Karel, review it, whether the content is correct.
Marek, the merge seems ok. Do you want me to file another bz for component updates (e.g. adding tomcat7, a few version bumps?) or should I paste it here?
I would not mix other customization of that BOM into this issue, the main reason is this issue probably not required RN, but your proposed customization will require it.
Verified in CR1, the file was removed.
Distributed as a part of WFK 2.1.0.GA release.