Title: Message Title
Karl Heinz Marbaise updated an issue
Title: Message Title
Dan Tran updated an issue
Title: Message Title
Dan Tran updated an issue
Title: Message Title
Dan Tran created an issue
This can be a source of inspiration for issue migration:
https://github.com/google/github-issue-mover
Am 12.04.2015 um 23:14 schrieb Jörg Hohwiller:
> Hi there,
>
> I guess jira export is not the problem. GH support for automated
> import will be more of a challange.
> In the worst case we will l
And indeed, from the log, that may be what happened: svn import some tree
content instead of copying the trunk:
➜ appassembler git:(master) svn log
file:///home/tiste/MOJOHAUS-TO-GIT/SVN-MOJO-WIP/tags/appassembler-1.0-alpha-1/
-
It fails like this:
20500 = 1e1607958c9761c3a035b480e76b088303001eb8
(refs/remotes/origin/trunk)
Compression automatique du dépôt en tâche de fond pour optimiser les
performances.
Voir "git help gc" pour toute information sur le nettoyage manuel.
Checked out HEAD:
file:///home/tiste/MOJOHAUS-TO-G
perfect from my POV
On Mon, May 4, 2015 at 10:16 PM, Baptiste Mathus wrote:
> I just drafted that for informing about the ML terminations:
> https://github.com/mojohaus/mojohaus.github.io/wiki/Termination-mail
>
> WDYT?
>
> 2015-05-04 21:49 GMT+02:00 Robert Scholte :
>
>> some statistics:
>>
>>
Looking good, very good.
Robert
Op Mon, 04 May 2015 22:16:32 +0200 schreef Baptiste Mathus
:
I just drafted that for informing about the ML terminations:
https://github.com/mojohaus/mojohaus.github.io/wiki/Termination-mail
WDYT?
2015-05-04 21:49 GMT+02:00 Robert Scholte :
some statistic
Hello Baptiste,
nice E-Mail you prepared.
Regards
Mirko
--
Sent from my mobile
On May 4, 2015 10:31 PM, "Karl Heinz Marbaise" wrote:
> Hi Baptiste,
>
> On 5/4/15 10:16 PM, Baptiste Mathus wrote:
>
>> I just drafted that for informing about the ML terminations:
>> https://github.com/mojohaus/mo
Hi Baptiste,
could it be caused by using the wrong name, cause i have written in the
CSV list:
appassembler-maven-plugin trunk/mojo/appassembler appassembler-
where the first column might be better be named "appassembler" instead
of "appassembler-maven-plugin" ?
Makes more s
Hi Baptiste,
On 5/4/15 10:26 PM, Baptiste Mathus wrote:
Currently converting all the repositories added by some of you.
Please have a look at the repositories you're interested in to check if
you find things you expect: https://github.com/mojohaus
Note : there seems to be an issue with appassem
Hi Baptiste,
On 5/4/15 10:16 PM, Baptiste Mathus wrote:
I just drafted that for informing about the ML terminations:
https://github.com/mojohaus/mojohaus.github.io/wiki/Termination-mail
WDYT?
Looks great for me...
Good work...
Kind regards
Karl Heinz Marbaise
2015-05-04 21:49 GMT+02:00 R
Currently converting all the repositories added by some of you.
Please have a look at the repositories you're interested in to check if you
find things you expect: https://github.com/mojohaus
Note : there seems to be an issue with appassembler. Don't know yet why,
but it seems it's the only one be
+1
On 5/3/15 9:48 PM, Baptiste Mathus wrote:
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to put the SVN in RO
> mo
I just drafted that for informing about the ML terminations:
https://github.com/mojohaus/mojohaus.github.io/wiki/Termination-mail
WDYT?
2015-05-04 21:49 GMT+02:00 Robert Scholte :
> some statistics:
>
> user: 645 subscribers
> dev: 334 subscribers
> announce: 92 subscribers
> scm: 63 subscribers
+1
El 04/05/2015, a las 21:51, Werner Guttmann escribió:
> +1
>
> Werner
>
> On 03.05.2015 21:48, Baptiste Mathus wrote:
>> Hi all,
>>
>> As a followup to previous threads, I guess it's time for us to try and
>> move on.
>> Indeed, the announcement says services should be shut down the 17 Ma
+1
On 4 May 2015 at 14:36, Baptiste Mathus wrote:
> Hi,
>
> So, as a followup with the upcoming Codehaus shutdown, to go forward and
> try to attract attention to those who may have missed the other quite
> verbose threads .
>
> Let's
>
> Vote open for 72h max (don't know if we could/should wait
+1
Werner
On 03.05.2015 21:48, Baptiste Mathus wrote:
Hi all,
As a followup to previous threads, I guess it's time for us to try and
move on.
Indeed, the announcement says services should be shut down the 17 May.
So, to go forward, I'd like to ask Codehaus support to put the SVN in RO
mode.
+1
Werner
On 04.05.2015 15:38, Anders Hammar wrote:
+1
/Anders (mobile)
Den 4 maj 2015 15:37 skrev "Baptiste Mathus" mailto:bmat...@batmat.net>>:
Hi,
So, as a followup with the upcoming Codehaus shutdown, to go forward
and try to attract attention to those who may have missed th
some statistics:
user: 645 subscribers
dev: 334 subscribers
announce: 92 subscribers
scm: 63 subscribers
So the user ML is by far the largest. However, its topics often concern a
specific plugin. It would be nice if Github had some sort of space to ask
per-(sub)project questions.
Even though
agreed.
for Commits List developers/users can use github notifications I think.
On Mon, May 4, 2015 at 8:57 PM, Anders Hammar wrote:
> Sounds good to me!
>
> /Anders
>
> On Mon, May 4, 2015 at 8:52 PM, Baptiste Mathus
> wrote:
>
>> OK, so, to try and sum up the discussions and reading the ML we
Sounds good to me!
/Anders
On Mon, May 4, 2015 at 8:52 PM, Baptiste Mathus wrote:
> OK, so, to try and sum up the discussions and reading the ML we currently
> have under http://mojo.codehaus.org/mail-lists.html, I think the current
> agreement is as follows:
>
>
>- Development List : alrea
OK, so, to try and sum up the discussions and reading the ML we currently
have under http://mojo.codehaus.org/mail-lists.html, I think the current
agreement is as follows:
- Development List : already moved to
https://groups.google.com/forum/#!forum/mojohaus-dev
- Commits List : let it d
If the google group is fully up and running, then I don't see any reason
for voting.
You could do a (pre-)announcement saying this ML will be unavailable soon
and still interested subscribers should move to google groups.
Looking at Xircles, I don't see an option to really close a mailing list,
Yes. My point was more indeed more to make people aware that this is NOW.
About the ML, we already have a new one created on google groups. I could
have started a vote, granted, but as the discussion didn't give much
feedback nor candidates (ggroups and freelists by Alexandre), so I went for
the s
Hi,
I don't think we have a real choice here. Once the Codehaus domain is gone
including its infra then there are no mailinglists anymore.
The vote should be about the move to X and how to register it for Markmail
and Nabble.
Robert
Op Mon, 04 May 2015 15:36:52 +0200 schreef Baptiste Mathu
+1
On Mon, May 4, 2015 at 1:08 PM, Robert Scholte
wrote:
> +1
>
> Op Sun, 03 May 2015 21:48:41 +0200 schreef Baptiste Mathus <
> bmat...@batmat.net>:
>
> Hi all,
>>
>> As a followup to previous threads, I guess it's time for us to try and
>> move
>> on.
>> Indeed, the announcement says services
+1
Op Sun, 03 May 2015 21:48:41 +0200 schreef Baptiste Mathus
:
Hi all,
As a followup to previous threads, I guess it's time for us to try and
move
on.
Indeed, the announcement says services should be shut down the 17 May.
So, to go forward, I'd like to ask Codehaus support to put the S
+1
On Sunday, May 3, 2015, Baptiste Mathus wrote:
> Hi all,
>
> As a followup to previous threads, I guess it's time for us to try and
> move on.
> Indeed, the announcement says services should be shut down the 17 May.
>
> So, to go forward, I'd like to ask Codehaus support to put the SVN in RO
+1
On Mon, May 4, 2015 at 3:36 PM, Baptiste Mathus wrote:
> Hi,
>
> So, as a followup with the upcoming Codehaus shutdown, to go forward and
> try to attract attention to those who may have missed the other quite
> verbose threads .
>
> Let's
>
> Vote open for 72h max (don't know if we could/sho
Hi Baptiste,
+1 on this...
Kind regards
Karl Heinz Marbaise
On 5/4/15 3:36 PM, Baptiste Mathus wrote:
Hi,
So, as a followup with the upcoming Codehaus shutdown, to go forward and
try to attract attention to those who may have missed the other quite
verbose threads .
Let's
Vote open for 72h
+1
De : Baptiste Mathus
À : "dev@mojo.codehaus.org"
Envoyé le : Lundi 4 mai 2015 15h36
Objet : [mojo-dev] [VOTE] Deprecate/disable all ML of MOJO@Codehaus
Hi,
So, as a followup with the upcoming Codehaus shutdown, to go forward and try to
attract attention to those who may have mis
On Mon, May 04, 2015 at 03:36:52PM +0200, Baptiste Mathus wrote:
> Hi,
>
> So, as a followup with the upcoming Codehaus shutdown, to go forward and
> try to attract attention to those who may have missed the other quite
> verbose threads .
>
> Let's
>
> Vote open for 72h max (don't know if we co
+1
/Anders (mobile)
Den 4 maj 2015 15:37 skrev "Baptiste Mathus" :
> Hi,
>
> So, as a followup with the upcoming Codehaus shutdown, to go forward and
> try to attract attention to those who may have missed the other quite
> verbose threads .
>
> Let's
>
> Vote open for 72h max (don't know if we c
Hi,
So, as a followup with the upcoming Codehaus shutdown, to go forward and
try to attract attention to those who may have missed the other quite
verbose threads .
Let's
Vote open for 72h max (don't know if we could/should wait less), will NOT
succeed by lazy consensus.
[ ] +1 : deprecate/disa
On Mon, May 4, 2015 at 9:05 AM, jieryn wrote:
> Yes, sorry I wasn't clear. I meant if the groupId=codehaus.org is an
> Apache issue without owning/controlling actual dns-a=codehaus.org,
> then the easiest and fastest solution, for both users and devs, is
> just to own the dns-a record. I am not t
Yes, sorry I wasn't clear. I meant if the groupId=codehaus.org is an
Apache issue without owning/controlling actual dns-a=codehaus.org,
then the easiest and fastest solution, for both users and devs, is
just to own the dns-a record. I am not talking about any complex
mirrorOf or relocating packages
I have just disabled something here
https://github.com/organizations/mojohaus/settings/oauth_application_policy
but I didn't even enabled something manually.
Maybe it was a consequence of using the API to create repositories.
2015-05-04 14:41 GMT+02:00 Karl Heinz Marbaise :
> On 5/4/15 10:43 AM,
I think he was suggesting Apache would be the caretaker of the domain, on
behalf of both Codehaus projects that move to Apache and those that don't,
and just the www.codehaus.org main page would redirect to an Apache page
(though I'd prefer to redirect to an Apache page that describes the
Codehaus
On 5/4/15 10:43 AM, Baptiste Mathus wrote:
Yes, I'm asking for help to enrich that file with the right informations.
I just didn't spend much time to analyze the dozens of different
projects to migrate (which branches, which tags...) and I indeed thought
that part could easily and more effective
On Mon, May 4, 2015 at 8:40 AM, Benson Margulies
wrote:
>
>
> On Mon, May 4, 2015 at 8:35 AM, jieryn wrote:
>
>> Apache, and Apache Maven, should just purchase the codehaus.org domain
>> name and set a permanent redirect to Apache Maven site.
>>
>
> Why? Who cares? There's no important relations
On Mon, May 4, 2015 at 8:35 AM, jieryn wrote:
> Apache, and Apache Maven, should just purchase the codehaus.org domain
> name and set a permanent redirect to Apache Maven site.
>
Why? Who cares? There's no important relationship between a Maven gid and a
DNS domain name. Codehaus.org contained t
Apache, and Apache Maven, should just purchase the codehaus.org domain
name and set a permanent redirect to Apache Maven site.
Maybe Ben would be willing to give that last gift to the community and
transfer ownership to Apache. It expires on 2016-02-26 anyway..
On Mon, May 4, 2015 at 8:20 AM, And
Anyone who knows if it actually possible for us to keep the groupId when
moving, as we don't own the codehaus.org domain? I think that most of us
can agree on it's best (at least in short term) and easier to keep the same
groupId. But can we really do that?
/Anders
On Mon, May 4, 2015 at 2:07 PM,
+1 to move ASAP
Perhaps a message to say it bye bye and we close it to be sure that people
are switching ASAP to the new one
On Mon, May 4, 2015 at 10:17 AM, Baptiste Mathus wrote:
> In the same vein of the SVN freeze, how about moving our new discussions
> onto the newly created Google group? M
+1 keep codehaus.org for existing plugins
perhaps prepare a new groupId with required resources (central sync ..) for
new plugins and add it in the default list of plugins groups for future
maven releases
On Mon, May 4, 2015 at 1:12 PM, Olivier Lamy wrote:
> Agree. We must take take it easy for
Title: Message Title
Junio Fernandes commented on an issue
Agree. We must take take it easy for users.
Folks who managed central knows the situation. So IMHO this will not be a
big problem.
On 4 May 2015 at 20:27, Trygve Laugstøl wrote:
> I think it is best to just keep the group id for all existing Mojos.
> Repackaging the code and having all clients i
I would suggest we all migrate to the new structure as soon as possible.
Currently, we are in a somewhat fluid state about how to do things...
... and I believe we all need to solidify the working process.
:)
2015-05-04 10:17 GMT+02:00 Baptiste Mathus :
> In the same vein of the SVN freeze, how
I think it is best to just keep the group id for all existing Mojos.
Repackaging the code and having all clients is a lot of hassle for no gain. For
new plugins, I guess they could use the new group id.
--
Trygve
On Mon, May 04, 2015 at 09:48:59AM +, Julien HENRY wrote:
> Hi guys,
> Sorry
Hi guys,
Sorry if it was already discussed but do you know what will be the future of
the groupId? Now that all plugins are moving to GitHub are we still allowed to
deploy on central with groupId org.codehaus.mojo? AFAIK Maven conventions are
that we should own the domain codehaus.org to deploy
+1
De : Baptiste Mathus
À : "dev@mojo.codehaus.org"
Envoyé le : Dimanche 3 mai 2015 21h48
Objet : [mojo-dev] [VOTE] Put our SVN in readonly and ask for dump for
migration
Hi all,
As a followup to previous threads, I guess it's time for us to try and move
on.Indeed, the announcemen
Great, just checking that we're on the same page here.
/Anders
On Mon, May 4, 2015 at 10:43 AM, Baptiste Mathus wrote:
> Yes, I'm asking for help to enrich that file with the right informations.
>
> I just didn't spend much time to analyze the dozens of different projects
> to migrate (which br
Yes, I'm asking for help to enrich that file with the right informations.
I just didn't spend much time to analyze the dozens of different projects
to migrate (which branches, which tags...) and I indeed thought that part
could easily and more effectively be crowd sourced.
2015-05-04 10:33 GMT+02
>
> I also enriched the csv file describing the projects to migrate. Nicely
> presented thanks to Github btw:
> https://github.com/mojohaus/convert-to-git/blob/master/repo-infos.csv
>
> Please add the mojos you want inside.
>
I've assumed we were going to include all mojos, at least all released
o
Title: Message Title
Alexander Reelsen updated an issue
Title: Message Title
Alexander Reelsen created an issue
In the same vein of the SVN freeze, how about moving our new discussions
onto the newly created Google group? Mailing lists are also gonna be shut
down with the rest...
We would still monitor this list and inform potential people still posting
here about the new list?
WDYT?
2015-05-03 8:32 GMT+0
Yes,but imo shouldn't be an issue since the commits are actually already
done, and anyway the release should be finished (or cancelled) way before
the end of the 72h for putting the svn in RO.
2015-05-04 6:27 GMT+02:00 Anders Hammar :
>
> There is no release in progress it seems, thus+1
>> let's
Hi,
I pushed a slightly improved version of the conversion script.
https://github.com/mojohaus/convert-to-git/blob/master/convert.sh
I also enriched the csv file describing the projects to migrate. Nicely
presented thanks to Github btw:
https://github.com/mojohaus/convert-to-git/blob/master/repo-
61 matches
Mail list logo
