Yes - this problem of no unified tag in builds and then how to actually know which version
to use in jira for these components either.
It has a tons of subtle problems with no real good solution besides "more people/more
automation"
/max
On 08 Feb 2013, at 14:57, Denis Golovin <dgolovin(a)exadel.com> wrote:
It saves overlapping problem, but then to see what was actually
included in jbosstools release we should keep this mapping jbosstools-version ->
included-tool-version, or document it in readme for branch or do something else.
Then my personal problems come ;)
I have this dgolovin/jbosstools-fork-submodules and now I can easy build/get any version
of jbosstools using this repo like
git submodule foreach 'git checkout jbosstools-4.0.x'
mvn clean install
or I can get latest commits form upstream projects
git submodule foreach 'git checkout master'
git submodule foreach 'git pull upstream master'
mvn clean install
if branch names are different I need to figure out again how to track relation between
jbosstools release branch and component branch
Denis
On 02/08/2013 11:41 AM, Xavier Coulon wrote:
> So maybe using a branch named after the component version (such as we did for the
WebServices -> 1.5.0.Alpha1) solves this problem of name overlapping ?
>
> Best regards,
> /Xavier
>
>
>
> On Feb 8, 2013, at 8:34 PM, Denis Golovin wrote:
>
>> Was thinking about how we going to tag the release, but didn't notice
>> that it was actually taken care of by having 'x' at the end of branch
name.
>> Will redo branches.
>>
>> Thanks
>> Denis
>>
>> On 02/08/2013 11:09 AM, Max Rydahl Andersen wrote:
>>> Nick/Denis - you guys do realize branch and tag names cannot overlap - the
convention we followed on all previous naming is branch is: jbosstools-4.1.0.Alpha1x and
the *tag* is jbosstools-4.1.0.Alpha1
>>>
>>> Please be aware of that.
>>>
>>> /max
>>>
>>> On 08 Feb 2013, at 13:16, Denis Golovin <dgolovin(a)exadel.com> wrote:
>>>
>>>> Nick,
>>>>
>>>> I'll take care of it.
>>>>
>>>> Denis
>>>>
>>>> On 02/08/2013 09:30 AM, Nick Boldt wrote:
>>>>> The following projects are branched for Alpha1, using a
>>>>> "jbosstools-4.1.0.Alpha1" branch:
>>>>>
>>>>> base
>>>>> hibernate
>>>>> javaee
>>>>> jst
>>>>> build
>>>>> build-ci
>>>>> build-sites
>>>>>
download.jboss.org
>>>>> maven-plugins
>>>>>
>>>>> This project has branched using a "1.5.0.Alpha1" branch:
>>>>>
>>>>> webservices
>>>>>
>>>>> The following projects have not yet created
"jbosstools-4.1.0.Alpha1"
>>>>> branches (if following JBT release convention), or
"x.y.0.Alpha1"
>>>>> branches (if following their own versioning convention):
>>>>>
>>>>> birt
>>>>> central
>>>>> forge
>>>>> freemarker
>>>>> gwt
>>>>> integration-tests
>>>>> openshift
>>>>> portlet
>>>>> server
>>>>> vpe
>>>>>
>>>>> Project Leads, please branch your projects! Or, Denis/Max, can you
>>>>> branch them?
>>>>>
>>>>> Wondering how to branch? Try this gist:
>>>>>
>>>>>
https://gist.github.com/nickboldt/4740072
>>>>>
>>>>> export GITUSER=nickboldt
>>>>> cd ~/trunk/jbosstools-birt
>>>>> ~/bin/git-new-branch.sh jbosstools-4.1.0.Alpha1
>>>>>
>>>>>
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>> jbosstools-dev(a)lists.jboss.org
>>>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>