Pramod, isn't this enough ?
I think you would have to rebuild both HK2 and v3 using this tag, but
you should then have a stable environment as long as you use mvn -O to
build afterwards.
Jerome
Terena Chinn-Fujii wrote:
> Jerome,
>
> Last week's promotion was tagged as "preview2-b04".
>
> Terena
>
>
> Jerome Dochez wrote:
>> Dinesh
>>
>> Do you tag each wednesday's promotion ?
>>
>> Jerome
>>
>> Pramod Gopinath wrote:
>>> Hi
>>> If the subject matter is not clear let me start by listing what I
>>> am looking for :
>>>
>>> In V3 is there a process where in we tag/branch source bits say on a
>>> weekly bits so that developers could use those bits. The aim is to
>>> use stable releases of v3 source bits for development and also to
>>> point others to to it rather than using the current unstable builds
>>> of v3.
>>>
>>> I have been trying to get a v3 build that I could use to create a
>>> JRuby gem and publish it to RubyForge, but for the past 2 weeks have
>>> been failing. The plan is when I release the gem also provide steps
>>> that users of the gem could then make use of, to recreate the gem
>>> themselves. Specifically in the case of the gem, almost all of the
>>> code currently resides in grizzly contribs area with very little
>>> code in v3/rails itself. Based on the current state of the v3 build
>>> this is a very difficult/frustrating task. Hence asking this question ?
>>>
>>> It would be great to have say weekly stable tags/branches of the v3
>>> build which would be self contained (i.e no SNAPSHOT in the
>>> pom.xml's) so that any user could just get that tag and then run
>>> "mvn install" to build and use that GF v3 setup. If there is
>>> something already would be great if someone could point me to it.
>>>
>>> Thanks
>>> Pramod
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>