n/p we all do that kind of mistakes.
the 2.0.x branch had also an issue the <scm> portion of the parent pom was not
correct (pointing to /trunk instead of /branches/2.0.x) causing the maven release plugin
to make wrong release of the branch (which I did with two screwed release of 2.0.2).
I have released 2.0.2 to harmonize dependencies with an update of common to 2.0.3-GA and
released pc 2.2.0-Beta03 that consumes wci 2.0.2.
the gatein trunk is up to date with those now.
On Sep 21, 2010, at 3:19 PM, Matt Wringe wrote:
On Tue, 2010-09-21 at 09:51 +0200, Julien Viet wrote:
> Hi Matt,
>
> you mispelled the SVN tag name of Alpha01 "wci-parent-2.1.0-Alpha01" a
simple svn move would be OK with me.
That teaches me to look more closely at what the defaults mvn is using
for naming things. Thanks to whomever fixed it.
> On Sep 21, 2010, at 7:08 AM, Matt Wringe wrote:
>
>> Ok, the 2.0.x branch is created, the jira versions has been added, the
>> common component has been updated to 2.0.3 and 2.1.0-Alpha01 has been
>> released.
>>
>> On Mon, 2010-09-20 at 15:35 +0200, Julien Viet wrote:
>>> by the way there is an odd situation with dependencies.
>>>
>>> PC 2.2.0 snapshot depends on WCI 2.0.1 and commons 2.0.3
>>>
>>> but WCI 2.0.1 depends on common 2.0.2, I know it is not big deal but we
should try to keep some harmony there.
>>>
>>> So this branch should also update commons dependency in trunk on common 3.0.2
and make a 2.1.0-Alpha01 release to be consumed in PC 2.2.0 snapshot.
>>>
>>>
>>>
>>>
>>> On Sep 20, 2010, at 3:21 PM, Julien Viet wrote:
>>>
>>>> Hi Matt,
>>>>
>>>> I would like to branch WCI to 2.0.x and update the trunk to
2.1.0-Beta01-SNAPSHOT, could you proceed and create the corresponding JIRA version ?
>>>>
>>>> this is necessary because we are going to implement some features in WCI
soon.
>>>>
>>>> thanks
>>>>
>>>> Julien
>>>
>>>
>>> _______________________________________________
>>> gatein-dev mailing list
>>> gatein-dev(a)lists.jboss.org
>>>
https://lists.jboss.org/mailman/listinfo/gatein-dev
>>
>>
>