Hi Ryan,
I could confirm the update from repository.
Thank you again.
Additionally, I have another question.
Sometimes, the "maven-source-plugin" is useful because the maven downloads
original sources automatically if a user hasn't checked out them.
The Grizzly project also includes the plugin in ${grizzly_home}/pom.xml
,but the plugin is only declared by "release-profile" profile in pom.xml.
So if I didn't used the release version but the snapshot version of
grizzly in other project, I couldn't download sources automatically by
maven.
Perhaps, is it grizzly project's policy?
I was just curious about that. :-)
Thanks!
Regards,
Bongjae Chang
On 12/19/11 7:46 PM, "Ryan Lubke" <ryan.lubke_at_oracle.com> wrote:
>Nightly jobs for 1.9, 2.1, and 2.2 are in place. They are set to run
>serially at midnight (GMT+8), so the whole process should be done by
>around 3AM (starting Monday/Today).
>
>I've manually pushed the jobs to the build queue, so I would expect to
>see results around 6 or 7 this morning
>as there are some other jobs in the queue before them.
>
>
>
>On 12/16/11 9:09 PM, Bongjae Chang wrote:
>> Hi Ryan,
>>
>> Thank you for your information!
>>
>> Regards,
>> Bongjae Chang
>>
>>
>> On 12/17/11 8:21 AM, "Ryan Lubke"<ryan.lubke_at_oracle.com> wrote:
>>
>>> On 12/16/11 5:24 AM, Bongjae Chang wrote:
>>>> Hi,
>>>>
>>>> If I have understood correctly, the release binary will be uploaded to
>>>> maven central(http://repo1.maven.org) whenever the new version will be
>>>> released and the snapshot which is under construction will be uploaded
>>>> to another
>>>> repository("https://maven.java.net/content/repositories/snapshots").
>>>>
>>>> So I would like to know when the snapshot will be updated into
>>>> "https://maven.java.net/content/repositories/snapshots".
>>>>
>>>> Currently, the "grizzly-thrift-2.2-20111214.004429-7.jar" snapshot is
>>>> the latest one in the repository but it doesn't include the latest
>>>> classes(source changes) of git.
>>>>
>>>> Thanks.
>>>>
>>>> Regards,
>>>> Bongjae Chang
>>>>
>>>>
>>> Hi Bonjae,
>>>
>>> Sorry for the delayed response. The current cycle is "when ever we
>>> think we should push a snapshot". This was mostly due to historical
>>> reasons with the old java.net maven repo being problematic. However,
>>> we're going to setup a new job to publish the snapshots nightly.
>>>
>>> We'll follow up again once the job is in place.
>>>
>>>
>>
>