What you described is the way I would do it, but as you say, this is probably a preference
thing.
----- Original Message -----
From: "Darran Lofthouse"
<darran.lofthouse(a)jboss.com>
To: jdf-dev(a)lists.jboss.org
Sent: Wednesday, January 16, 2013 8:10:22 AM
Subject: [jdf-dev] Quickstarts - Single or Multiple Projects
Hello all,
I have a quick question that I think partly comes down to personal
preference so I wanted to get some feedback on other options.
When developing a quickstart that contains a deployment and a client
to
call the deployment is it preferable to contain this within a single
maven artefact or split it out with a common parent?
As an Eclipse user provided the client is simple my preference is to
keep this in a single Maven artefact so when imported into Eclipse it
will be a single project. As a command line user I also prefer this
as
I don't need two terminal tabs or a change of working directory to
switch between deploying and running the quickstart.
There a some quickstarts that have to be split up to achieve the
packaging being demonstrated but I think those have a clear
justification for doing so.
I understand for IntelliJ users if split with a common parent the sub
modules are still represented within the parent module so they don't
experience the three project like in Eclipse.
So overall just looking for some feedback on which direction is
preferable.
Thanks for your time.
Regards,
Darran Lofthouse.
_______________________________________________
jdf-dev mailing list
jdf-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jdf-dev