The problem I see with what you are trying to do here is to actually mix orthogonal issues i.e. on one axis you have a functional set (web-profile, full-profile, just-tomcat) and on another axis you have things such as clustering/dev-friendly/secure, etc.<br>
<br>Actually, I am not sure what is on the other axis (clustering, etc.) are so much a single axis (since you could decide to apply multiple of those at the same time i.e. secure+clustering.<br><br>Anyway, can anybody see a solution where attributes "on the second axis" (we could call that "modes") could be applied to each and every configuration profile?<br>
<br>Probably not the best way to do it but:<br> - we could have a limited set of true profiles (i.e. full-ee, web-ee, etc.)<br> - we could have a "--mode" configuration on the jboss.bat/sh command line with a syntax such as (not strictly correct, but you get the idea):<br>
[--mode { clustered | secured | development | whatever-else }[/+]+ ]<br> - in configuration files, we would use a "ifdef" kind of syntax to activate specific features based on those modes<br><br>Am I making any sense?<br>
<br>Obviously, as suggested by Brian, that might not be ideal for the QE team though.<br><br>Cheers,<br><br><br>sacha<br><br><br><br><div class="gmail_quote">On Thu, Feb 11, 2010 at 16:47, Stan Silvert <span dir="ltr"><<a href="mailto:ssilvert@redhat.com">ssilvert@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Hi Sacha, when did you come back to work? :-)<br>
<br>
I like Sacha's basic idea here. Having EE6 in the name helps a lot.<br>
And I also like 'bootstrap' better than 'minimal'.<br>
<br>
I think we still need to decide exactly how many configurations we are<br>
going to ship. Awhile back, Brian asked me to open a jira to change<br>
this stuff in M3. It looks like that would be the time to nail this down.<br>
<a href="https://jira.jboss.org/jira/browse/JBAS-7651" target="_blank">https://jira.jboss.org/jira/browse/JBAS-7651</a><br>
<br>
Besides EE6, the other two things that we seem to need in the shipped<br>
configurations are (clustered or not-clustered) and (development or<br>
production).<br>
<br>
Here's another stab at the naming:<br>
bootstrap - same as minimal<br>
EE6-web - EE6 web profile<br>
EE6-standard - same as today's 'standard'. I guess we still need this<br>
for TCK?<br>
EE6-full-dev - super-fast boot time, less logging, delayed startup of<br>
admin console, unsecured consoles, JSF2 PROJECT_STAGE set to "Development"<br>
EE6-full-prod - immediate startup of admin console, secured consoles,<br>
JSF2 PROJECT_STAGE set to "Production"<br>
EE6-dev-cluster - same as full-EE6-dev, but with clustered services<br>
available<br>
EE6-prod-cluster - same as full-EE6-prod, but with clustered services<br>
available<br>
<div><div></div><div class="h5"><br>
Sacha Labourey wrote:<br>
> Hello, since I've been contributing lots of code recently, let me<br>
> chime in ;)<br>
><br>
> What about:<br>
><br>
> * EE6-full (aka all)<br>
> * EE6-web (aka default)<br>
> * bootstrap (aka minimal)<br>
><br>
><br>
> Reasoning:<br>
><br>
> * reading the thread, even yourself aren't sure if all=default or<br>
> all=default+more stuff, what is the difference between standard<br>
> and default, etc. Why not making it explicit IN THE NAME itself?<br>
> * "minimal" name is not good IMO since people might think it is<br>
> minimal in terms of middleware development (or related), but<br>
> this is really just a bootstrap with nothing on it. So call it<br>
> bootstrap, or WebOS or kernel.<br>
> * "default" is really just a trick to know which one to load "by<br>
> default", but it doesn't give any clue on what it actually<br>
> contains. Why not make JBoss AS start by default the<br>
> configuration that has a "++" in front of its name - or<br>
> something similar i.e. "++bootstrap" or "++EE6-web". Or, if you<br>
> don't want people to rename configuration folders, create a<br>
> "XXX.is.the.default" empty file in the server folder, where XXX<br>
> is the default configuration that will be started unless asked<br>
> otherwise.<br>
> * I agree that jbossweb might need to be rebranded. I'd relate to<br>
> the Tomcat brand somehow (such as Tamcot or Tomchat or Tomkatz<br>
> ;) well, I am sure you'll find smarter ideas :) )<br>
><br>
><br>
> BTW, are all "server/XXX/lib" now centralized in a common folder and<br>
> refered to by name in a configuration file or are they still being<br>
> replicated all over the place in each and every configuration?<br>
><br>
> Cheers,<br>
><br>
><br>
> sacha<br>
><br>
><br>
><br>
> On Thu, Feb 11, 2010 at 14:39, Dimitris Andreadis <<a href="mailto:dandread@redhat.com">dandread@redhat.com</a><br>
</div></div><div class="im">> <mailto:<a href="mailto:dandread@redhat.com">dandread@redhat.com</a>>> wrote:<br>
><br>
> I see it's changed already, but doesn't it look horrible? Maybe<br>
> just drop '-standalone' or<br>
> where are our naming gurus? :-)<br>
><br>
> ./server/<br>
> all<br>
> default<br>
> jbossweb-standalone<br>
> minimal<br>
> standard<br>
> _______________________________________________<br>
> jboss-development mailing list<br>
> <a href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a><br>
</div>> <mailto:<a href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a>><br>
<div class="im">> <a href="https://lists.jboss.org/mailman/listinfo/jboss-development" target="_blank">https://lists.jboss.org/mailman/listinfo/jboss-development</a><br>
><br>
><br>
</div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><br>
> _______________________________________________<br>
> jboss-development mailing list<br>
> <a href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/jboss-development" target="_blank">https://lists.jboss.org/mailman/listinfo/jboss-development</a><br>
<br>
<br>
_______________________________________________<br>
jboss-development mailing list<br>
<a href="mailto:jboss-development@lists.jboss.org">jboss-development@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jboss-development" target="_blank">https://lists.jboss.org/mailman/listinfo/jboss-development</a><br>
</div></div></blockquote></div><br>