maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte" <rfscho...@apache.org>
Subject Re: Release plugin & git repo with multiple projects
Date Sat, 02 Mar 2013 13:29:02 GMT
I assume you hit https://jira.codehaus.org/browse/SCM-709

Robert

Op Sat, 02 Mar 2013 14:15:50 +0100 schreef Stefano Fornari  
<stefano.fornari@gmail.com>:

> WOW! it worked! thanks a lot.
>
> Shall I file a bug?
>
> Ste
>
>
> On Sat, Mar 2, 2013 at 12:38 PM, Robert Scholte  
> <rfscholte@apache.org>wrote:
>
>> Hi,
>>
>> There are some issues with Git and the maven-release-plugin 2.4 due to
>> changes in the scm-git-provider.
>> For Git it is better to use maven-release-plugin 2.3.2
>>
>> Robert
>>
>>
>> Op Sat, 02 Mar 2013 12:24:11 +0100 schreef Stefano Fornari <
>> stefano.fornari@gmail.com>:
>>
>>  Hi All,
>>> reverting this topic on a more recent version, Maven 3.0.5... I have a
>>> project built of two submodules:
>>>
>>> beanshellweb
>>>  + beanshelweb (lib)
>>>  + beanshelweb (webapp)
>>>
>>> They are under a unique git repository
>>> https://github.com/**stefanofornari/beanshellweb<https://github.com/stefanofornari/beanshellweb>
>>>
>>> When I run release:prepare, I think maven rightly asks me for one tag
>>> only:
>>>
>>> ...
>>> What is the release version for "BeanShellWeb (lib)"?
>>> (ste.web:beanshellweb-lib) 1.2: : 1.1.1
>>> What is the release version for "BeanShellWeb (webapp)"?
>>> (ste.web:beanshellweb-webapp) 1.2: : 1.1.1
>>> What is the release version for "BeanShellWeb"? (ste.web:beanshellweb)
>>> 1.2:
>>> : 1.1.1
>>> What is SCM release tag or label for "BeanShellWeb"?
>>> (ste.web:beanshellweb)
>>> beanshellweb-1.1.1: :
>>> ...
>>> What is the new development version for "BeanShellWeb (lib)"?
>>> (ste.web:beanshellweb-lib) 1.1.2-SNAPSHOT: : 1.2-SNAPSHOT
>>> What is the new development version for "BeanShellWeb (webapp)"?
>>> (ste.web:beanshellweb-webapp) 1.1.2-SNAPSHOT: : 1.2-SNAPSHOT
>>> What is the new development version for "BeanShellWeb"?
>>> (ste.web:beanshellweb) 1.1.2-SNAPSHOT: : 1.2-SNAPSHOT
>>>
>>> But then it fails trying to create the tag. The failing command is:
>>>
>>> Executing: /bin/sh -c cd /home/ste/Projects && git tag -F
>>> /tmp/maven-scm-1273059077.**commit beanshellweb-1.1.1
>>>
>>> It seems to me it is just failing CDing in the wrong directory
>>> (/home/ste/Projects instead of /home/ste/Projects/**beanshellweb).
>>>
>>> Any hints? Do I really need to have one repository per module? But in  
>>> that
>>> case, can I have nested git repositories?
>>>
>>> Thanks a lot in advance.
>>>
>>> Ste
>>>
>>>
>>> On Tue, Apr 27, 2010 at 11:16 AM, Nicola Musatti <
>>> Nicola.Musatti@objectway.it> wrote:
>>>
>>>  I believe there's a very similar problem with Subversion too, when you
>>>> have a repository for each module which are linked to the aggregator
>>>> project by means of svn:externals. This is an approach which, as far  
>>>> as I
>>>> can tell, is not supported by the release plugin.
>>>>
>>>> Cheers,
>>>> Nicola Musatti
>>>>
>>>> Justin Edelson wrote:
>>>>
>>>>  OK. Then we're on the same page...
>>>>>
>>>>> On 4/26/10 11:32 AM, Kathryn Huxtable wrote:
>>>>>
>>>>>
>>>>>  Perhaps I wasn't clear. I don't support multiple projects in one
>>>>>> repository. Definitely not. I was trying to criticize the  
>>>>>> svn-centric
>>>>>> thinking, not support it.
>>>>>>
>>>>>> I think there should be a JIRA issue to make modules work, given
 
>>>>>> that
>>>>>> they'll be in separate repositories.
>>>>>>
>>>>>> I'm not going to file this because I have almost zero experience
 
>>>>>> with
>>>>>> nested projects. There have been places it would have made sense
 
>>>>>> and I
>>>>>> shied away.
>>>>>>
>>>>>> But the release plugin should work with git projects that have  
>>>>>> modules
>>>>>> and it should do it in the standard git manner, which is one  
>>>>>> repository
>>>>>> containing one project. (Distributed, of course.)
>>>>>>
>>>>>> -K
>>>>>>
>>>>>> On Apr 26, 2010, at 9:06 AM, Justin Edelson wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>  Kathryn-
>>>>>>> Maybe I'm misunderstanding what you mean, but I think you have
this
>>>>>>> exactly backwards. The "svn-centric thinking" is what's inspired
>>>>>>> someone
>>>>>>> to put multiple projects in the same repository. AFAIK, this
is  
>>>>>>> simply
>>>>>>> not supported by git, i.e. there's no way to clone, branch or
tag
>>>>>>> _part_
>>>>>>> of a repository.
>>>>>>>
>>>>>>> I am by no means a git expert, so I could be mistaken about this.
>>>>>>>
>>>>>>> Justin
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On 4/26/10 9:21 AM, Kathryn Huxtable wrote:
>>>>>>>
>>>>>>>
>>>>>>>  Having recently switched from svn to git for most of my projects,
 
>>>>>>> I
>>>>>>>> have an opinion.
>>>>>>>>
>>>>>>>> I think you should create a JIRA ticket and consider this
a bug.
>>>>>>>>
>>>>>>>> What we're dealing with here is a bit of svn-centric thinking
 
>>>>>>>> during
>>>>>>>> design. It needs to be fixed.
>>>>>>>>
>>>>>>>> -K
>>>>>>>>
>>>>>>>> On Apr 26, 2010, at 8:08 AM, Jean-Laurent de Morlhon wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>  We're considering migrating from svn to git, we stumble
on the
>>>>>>>>> maven-release-plugin usage with git.
>>>>>>>>> We think we prefer to use a single repository for many
 
>>>>>>>>> independently
>>>>>>>>> built
>>>>>>>>> projects like :
>>>>>>>>>
>>>>>>>>> foobar-repo.git
>>>>>>>>>   |->  project-foo/
>>>>>>>>>   |    |->  pom.xml
>>>>>>>>>   |    |–>  module A/
>>>>>>>>>   |    |->  module B/
>>>>>>>>>   |
>>>>>>>>>   |->  project-bar/
>>>>>>>>>        |->  pom.xml
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> project-bar scm url looks like :
>>>>>>>>> <connection>scm:git:ssh://****somehost.nowhere:/foobar-repo.****
>>>>>>>>>
>>>>>>>>> git</connection>
>>>>>>>>>
>>>>>>>>> This hints to the right repository but I can't write
that the  
>>>>>>>>> actual
>>>>>>>>> project-bar is in the project-bar subdirectory.
>>>>>>>>>
>>>>>>>>> mvn release:prepare goes well and ends succesfully.
>>>>>>>>>
>>>>>>>>> mvn release:perform fails whenever it tries to build
the project
>>>>>>>>> from
>>>>>>>>> the
>>>>>>>>> tag. It effectively clone correctly the repository.
>>>>>>>>> But use the root of the repository rather than going
into
>>>>>>>>> project-bar
>>>>>>>>> subdirectory whenever it tries to clean deploy the tag.
>>>>>>>>>
>>>>>>>>> This prevent using git and multiple projects in the same
 
>>>>>>>>> directory.
>>>>>>>>> Some may think we should use gitmodules but
>>>>>>>>> 1) the release plugin does not support it [1]
>>>>>>>>> 2) gitmodules is an aggregate of single repository
>>>>>>>>>
>>>>>>>>> Should I issue a "new feature" ticket into jira project
MRELEASE  
>>>>>>>>> or
>>>>>>>>> SCM ?
>>>>>>>>> Or should I fall back to the current convention of 1
project = 1  
>>>>>>>>> git
>>>>>>>>> repository ??
>>>>>>>>> Or maybe someone managed to do it ?
>>>>>>>>>
>>>>>>>>> any advice appreciated.
>>>>>>>>>
>>>>>>>>> [1] :  
>>>>>>>>> http://jira.codehaus.org/****browse/SCM-530<http://jira.codehaus.org/**browse/SCM-530>
>>>>>>>>> <http://jira.**codehaus.org/browse/SCM-530<http://jira.codehaus.org/browse/SCM-530>
>>>>>>>>> >
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>> ------------------------------****----------------------------**--**
>>>>>>>> ---------
>>>>>>>> To unsubscribe, e-mail:  
>>>>>>>> users-unsubscribe@maven.**apac**he.org<http://apache.org>
>>>>>>>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache.org>
>>>>>>>> >
>>>>>>>>
>>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>> ------------------------------****----------------------------**--**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail:  
>>>>>>> users-unsubscribe@maven.**apac**he.org<http://apache.org>
>>>>>>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache.org>
>>>>>>> >
>>>>>>>
>>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> ------------------------------****----------------------------**--**
>>>>>> ---------
>>>>>> To unsubscribe, e-mail:  
>>>>>> users-unsubscribe@maven.**apac**he.org<http://apache.org>
>>>>>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache.org>
>>>>>> >
>>>>>>
>>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail:  
>>>>> users-unsubscribe@maven.**apac**he.org<http://apache.org>
>>>>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache.org>
>>>>> >
>>>>>
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>> ------------------------------****----------------------------**
>>>> --**---------
>>>> To unsubscribe, e-mail:  
>>>> users-unsubscribe@maven.**apac**he.org<http://apache.org>
>>>> <users-unsubscribe@**maven.apache.org<users-unsubscribe@maven.apache.org>
>>>> >
>>>>
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>>
>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail:  
>> users-unsubscribe@maven.**apache.org<users-unsubscribe@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message