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
When I run release:prepare, I think
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.forn...@gmail.com:
Hi All,
reverting this topic
WOW! it worked! thanks a lot.
Shall I file a bug?
Ste
On Sat, Mar 2, 2013 at 12:38 PM, Robert Scholte rfscho...@apache.orgwrote:
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
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.forn...@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
rfscho...@apache.orgwrote:
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
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/
|
|-
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,
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
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
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
You say the git way of doing things is 1 project - 1 git repository, I
understand, and it's not very far of having a svn repo for every project in
svn altough the release plugin do not enforce this.
The current state of the release plugin force you to have the pom.xml at the
root of your git
Jean-Laurent de Morlhon wrote:
You say the git way of doing things is 1 project - 1 git repository,
I understand, and it's not very far of having a svn repo for every
project in svn altough the release plugin do not enforce this.
Subversion doesn't enforce this. In fact, Subversion is designed
Thanks !
Migration would be a bit stiffer than I thought, but it make sense.
Jean-Laurent
On Mon, Apr 26, 2010 at 10:18 PM, Justin Edelson justinedel...@gmail.comwrote:
Jean-Laurent de Morlhon wrote:
You say the git way of doing things is 1 project - 1 git repository, I
understand, and
Although you can create a new git repo, add a remote, and then pull a single
branch. Not the same as checking out a directory from svn, but you don't *have*
to get the entire repo.
I use this in my wagon-gitsite app to push docs to the gh-pages branch of
github projects.
-K
On Apr 26, 2010,
14 matches
Mail list logo
