<div dir="ltr"><div>What would this result into in practice?<br><br></div>Having snapshot dependencies in build as long as WildFly is in snapshot version?<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, May 20, 2014 at 6:37 PM, Darran Lofthouse <span dir="ltr"><<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
We have a number of additional maven projects that are pulled into<br>
WildFly where in general their predominant purpose is for use within<br>
WildFly.<br>
<br>
For these kinds of projects I am wondering if it would make more sense<br>
to drop using a version qualifier, this is compatible with our agreed<br>
scheme: -<br>
<br>
<a href="https://community.jboss.org/wiki/JBossProjectVersioning" target="_blank">https://community.jboss.org/wiki/JBossProjectVersioning</a><br>
<br>
The major and minor numbers are still available for us to be able to<br>
branch off for maintenance, the micro then just becomes a tag counter.<br>
<br>
At the moment we end up in situations where components need to move from<br>
Beta to CR to Final at the appropriate time for a WildFly release even<br>
though the modules are not actually being pushed as independent<br>
projects, this creates additional work tagging and then processing the<br>
component upgrades.<br>
<br>
A couple of projects where this would make sense to me are JBoss<br>
Negotiation and JBoss SASL, both of these are tied so closely to the<br>
WildFly release that having their own qualifier does not add much.<br>
<br>
An example project where retaining the qualifier is good would be JBoss<br>
Remoting where it could easily be conceived that the chances are higher<br>
it would be used as a stand alone project.<br>
<br>
Regards,<br>
Darran Lofthouse.<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
</blockquote></div><br></div>