I think one repo per mojo is required ;) It might be possible to do
something with submodules to create the feeling of a single
repo but I haven't tried practically working with such a large number
of submodules.
From the link Brett set up it seems to me like we're looking at an
in-place migratio
On 31/05/2011, at 7:24 AM, Robert Scholte wrote:
> FWIW: http://docs.codehaus.org/display/CODEHAUS/Git
>
> I agree on the first vote proposal. I don't know if the second one is
> discussable. I wouldn't be suprised if it's all or nothing.
Not sure an "all or nothing" makes sense, especially i
FWIW: http://docs.codehaus.org/display/CODEHAUS/Git
I agree on the first vote proposal. I don't know if the second one is
discussable. I wouldn't be suprised if it's all or nothing.
-Robert
From: aherit...@codehaus.org
Date: Mon, 30 May 2011 20:55:08 +0200
To: dev@mojo.codehaus.org
Subjec
[
http://jira.codehaus.org/browse/MLATEX-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269050#action_269050
]
Karl Heinz Marbaise commented on MLATEX-12:
---
I found out after diving into the source code o
For the Git part @ codehaus we have to see with ben to know how/who is
responsible to convert SVN repositories to Git. The most annoying is to
create one repo per mojo. I don't know if Ben already did that for some
others projects and if he could help us. I don't know what is the process to
create
FWIW github quite frequently mirror upstream masters from elsewhere, for
instance a set of canonical masters hosted at codehaus.
This is the general setup that is used not only by apache but also quite
a few other mirrors on github, and it's really totally seamless (but
no-one really needs push ac
I'm -0 for moving the master to github. However, I'm very -1 for putting the
individual plugins in different locations. Where one goes, all go I think.
/Anders
On Mon, May 30, 2011 at 19:03, Robert Scholte wrote:
> Olivier said: "agree too. As our sources depends on a non profitable
> orgarnisa
Olivier said: "agree too. As our sources depends on a non profitable
orgarnisation
(codehaus). (we can simply merge back @codehaus git repos)
Perso I don't like a lot the idea about depends on a private company (github)."
Exactly my thoughts. The infrastructure of codehaus with xircles is very
XMLBeans will not consider the project.build.sourceEncoding property when
generating source files
-
Key: MXMLBEANS-68
URL: http://jira.codehaus.org/browse/MXMLBEANS-68
just for moving the scm.
Regarding the "issue" with depending on github as canonical repo, we can
have a clone at codehaus and a cron to pull changes, so that it's easy to
switch if things change on github side
2011/5/30 Brett Porter
> Shouldn't it be codehaus-mojo? I'm unclear if you're intendi
+1 to name it codehaus-mojo on github side.
+999... to keep canonical git repositories at codehaus and use GitHub
services just to improve/ease the contribution part
The next question will be how to manage such infrastructure (sync between
git and codehaus repos, creation of repos, users managemen
2011/5/30 Brett Porter :
> Shouldn't it be codehaus-mojo? I'm unclear if you're intending to move the
> plugin away from codehaus, or stay here for lists, issues & repository but
> move source control.
yup done too :-) : https://github.com/codehaus-mojo
>
> I would have thought setting up a can
Shouldn't it be codehaus-mojo? I'm unclear if you're intending to move the
plugin away from codehaus, or stay here for lists, issues & repository but move
source control.
I would have thought setting up a canonical git repo @ codehaus made more sense
(you can still use github just as effectivel
[
http://jira.codehaus.org/browse/MOJO-1214?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kent Soelvsten updated MOJO-1214:
-
Fix Version/s: chronos-maven-plugin-1.1
> Add possibility to monitor metrics through jmx
> -
[
http://jira.codehaus.org/browse/MOJO-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kent Soelvsten closed MOJO-1679.
Resolution: Fixed
This issue should be fixed in the latest snapshot.
Can You please retest?
> Chronos Jm
[
http://jira.codehaus.org/browse/MOJO-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269027#action_269027
]
Kent Soelvsten edited comment on MOJO-1672 at 5/30/11 7:53 AM:
---
A new sn
[
http://jira.codehaus.org/browse/MOJO-1672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269027#action_269027
]
Kent Soelvsten commented on MOJO-1672:
--
A new snapshot is now available.
The serialization issue
FYI, I have just created the organization maven-mojo
https://github.com/maven-mojo . (https://github.com/mojo was already
used).
2011/5/30 nicolas de loof :
> The idea is to move the code repo to github and deprecate the svn one (last
> commit will be a README.txt file
> GitHub is more than just G
The idea is to move the code repo to github and deprecate the svn one (last
commit will be a README.txt file
GitHub is more than just Git hosting as you noticed. Pull Request, online
code editing and notes, and more nice web-based tools are great improvements
to make contributing easier. Hosting G
I like Git too but we should take care of few things :
* We have to take care of giving the ability to all mojo projects. Perhaps
under a dedicated mojo organization @ GitHub ? Or by working with Ben to
have a Git support that satisfies our needs
* The success of Github is mainly due to the fact th
Hello,
What I understand here : Nicolas like to move "canonical"
gwt-maven-plugin scm repo to git (means sources not anymore in svn
@codehaus : or I misunderstand :-) )
So two solutions :
* move to github
* ask ben or bob to have a git repo @codehaus (AFAIK it's supported )
Perso, I like git so wh
How will you manage the synchro between SVN@Codehaus and GitHub ??
On Mon, May 30, 2011 at 11:10 AM, nicolas de loof
wrote:
> Hi folks,
>
> I'll start preparation for a 2.3.0 release soon,
>
> starting with this release, I'd like to move the canonical repo to gitHub
> to encourage more contributi
Hi folks,
I'll start preparation for a 2.3.0 release soon,
starting with this release, I'd like to move the canonical repo to gitHub to
encourage more contributions, either via pull-request or direct commit.
I'd like to follow the jenkins-way, with more releases (lets say, one per
month) and lowe
[
http://jira.codehaus.org/browse/MOJO-1658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Anders Sørensen updated MOJO-1658:
--
Priority: Minor (was: Major)
Nice feature, but it will have to wait for version 1.x
> Graph jppm fil
24 matches
Mail list logo
