I've already pushed hk2-0.2 and updated GFv3 trunk to use that.
As of now the HK2 trunk is 0.3-SNAPSHOT and v3 trunk uses 0.2.
Jerome Dochez wrote:
> Kohsuke Kawaguchi wrote:
>> Jerome Dochez wrote:
>>> I agree, I am a bit unclear how you can locally test hk2 changes
>>> with V3. You mentioned using snapshots hk2 and then build v3
>>> changing the hk2 version to snapshot ?
>>
>> You'd have to run Maven with -Dhk2.version=0.5-SNAPSHOT or something
>> to have your local build pick up a version of your choice. Or make a
>> temporary modification to POM.
> that's good enough, go ahead with you proposal after we created the TP2
> branch tomorrow.
>
> thanks, jerome
>
>>
>>
>>
>>> otherwise I think it makes sense, I have broken the builds multiple
>>> times doing updates in hk2 and v3 due to build time differences in
>>> hudson.
>>>
>>> jerome
>>>
>>> On Apr 14, 2008, at 5:04 PM, Kohsuke Kawaguchi wrote:
>>>>
>>>> I've started test-driving the maven release plugin toward the TP2
>>>> release, and the first step was to make this work for HK2.
>>>>
>>>> I now believe I made all the necessary changes for the release
>>>> plugin to work correctly. I changed HK2 to auto-complete OSGi
>>>> version from Maven version, tweaked the site generation a bit to
>>>> work around a Maven bug, and finally did some more nasty hacking to
>>>> work around the cyclic reference issue between the hk2-maven-plugin
>>>> vs hk2.
>>>>
>>>>
>>>> For us to run the release plugin on GFv3, one of the prerequisite
>>>> is for all its dependencies to be non-SNAPSHOT. So I propose we
>>>> switch GFv3 to depend on a released version of HK2, instead of the
>>>> current SNAPSHOT dependency.
>>>>
>>>> There are several implications in doing this, but most notably,
>>>> when we make changes in HK2 that need to be picked up by GFv3, HK2
>>>> needs to be released and the new version must be given. For us to
>>>> test the local SNAPSHOT HK2 with GFv3, we'd have to build GFv3
>>>>
>>>> But I think going forward this is the right thing to do. This
>>>> should also fix the temporary build breakage problem when you make
>>>> a change that spans across HK2 and GFv3.
>>>>
>>>> I can set up a Hudson task so that we can automate the release
>>>> process.
>>>>
>>>>
>>>> WDYT?
>>>>
>>>> ----
>>>>
>>>> Before I lose this note, this is the exact instruction to run a
>>>> successful release
>>>>
>>>> # base line
>>>> mvn clean install
>>>> # this fails citing maven-hk2-plugin is not available
>>>> mvn -B -P release release:prepare
>>>> # so we build it...
>>>> mvn -P release-phase1 install
>>>> # then retry the release
>>>> mvn -B -P release release:prepare
>>>>
>>>> # now I need this again, just so that POM loads
>>>> mvn -P release-phase1 install
>>>> # finally a release
>>>> mvn -B release:perform
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Kohsuke Kawaguchi
>>>> Sun Microsystems kohsuke.kawaguchi_at_sun.com
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_hk2.dev.java.net
>>> For additional commands, e-mail: dev-help_at_hk2.dev.java.net
>>>
>>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_hk2.dev.java.net
> For additional commands, e-mail: dev-help_at_hk2.dev.java.net
>
>
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com