That's strange. I see that the e-mail is sent to cheeser_at_dev.java.net.
Justin Lee wrote:
> No email yet... Of course it might be hung waiting to the server
> start to time out...
>
> Jane Young wrote:
>> BTW: Justin, you should have received an e-mail from RE Hudson that
>> the v3 trunk build became unstable after your commit:
>> Also, see the trunk continuous job here:
>> http://hudson.glassfish.org/job/gf-trunk-build-continuous
>>
>> Thanks,
>> Jane
>>
>>
>> Jerome Dochez wrote:
>>> that's my fault, I forgot to update the hk2 version in trunk to
>>> 1.0.0. Will do it right now then.
>>>
>>> jerome
>>>
>>> On Dec 2, 2009, at 1:49 PM, Justin Lee wrote:
>>>
>>>
>>>> Here's the story. I worked on a new deployment of grizzly
>>>> targetted to be applied to the v3 branch which has
>>>> hk2.version=1.0.0. At the last minute, I was told to commit to the
>>>> v3 trunk instead. I wasn't aware that the trunk lists 0.4.xx
>>>> instead and figured the drift between the branches was
>>>> insignificant relative to the minor patch I made. It fails on the
>>>> trunk because the trunk publishes an "older" version of hk2.
>>>>
>>>> Now, I can either push a new version of grizzly with that older hk2
>>>> version listed (which i'd rather not do because that takes
>>>> considerable time) or we can bump the v3 trunk to hk2 1.0.0. Is
>>>> there an issue with bumping that up in the v3 trunk?
>>>>
>>>> Tim Quinn wrote:
>>>>
>>>>> Hi.
>>>>>
>>>>> I've updated my v3 trunk workspace and rebuilt, and the server
>>>>> does not start. It starts to start (the log stops after the
>>>>> "INFO: Successfully launched in 27 msec." message).
>>>>>
>>>>> When I use
>>>>>
>>>>> asadmin start-domain --verbose
>>>>>
>>>>> I see the reason why: many errors caused by this:
>>>>>
>>>>> Caused by: org.osgi.framework.BundleException: Unresolved
>>>>> constraint in bundle com.sun.grizzly.grizzly-config [95]: package;
>>>>> (&(package=com.sun.hk2.component)(version>=1.0.0))
>>>>>
>>>>>
>>>>> Is this a case of me needing to wait for a maven repository to be
>>>>> updated, or is there something more serious here?
>>>>>
>>>>> Is anyone else seeing this?
>>>>>
>>>>> - Tim
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> 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
>>>
>>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>