Re: Release of Maven Indexer 5.0

[Aleksandar Kurtakov]

That's exactly what I think too!!

Alexander Kurtakov
Red Hat Eclipse team

- Original Message -
> From: "Manfred Moser" 
> To: "Maven Developers List" 
> Sent: Thursday, September 13, 2012 7:04:09 AM
> Subject: Re: Release of Maven Indexer 5.0
> 
> On Wed, September 12, 2012 6:06 pm, Chris Graham wrote:
> > On Wed, Sep 12, 2012 at 9:46 PM, Anders Hammar 
> > wrote:
> >
> >> I fully agree with you and I'm actually of the opinion that the
> >> Java
> >> community has a responsibility to provide enough reasons for those
> >> on
> >> older Java platforms to upgrade. But as long as we provide
> >> libraries
> >>
> >
> > Simple.
> >
> > Two reasons actually.
> >
> > Without going off on an essay about the psychology of developers
> > and being
> > obsessed with "shiny new things" (and a Dev centric view of the
> > world)...
> >
> > 1. Cost.
> >
> > 2. Especially in the corporate world, they are far more concerned
> > with
> > function rather than form (ie the underlying technology). In short,
> > if it
> > works, leave it. Which also relates to #1.
> >
> > Case in point: My current project is a multi million dollar one
> > that is
> > *finally* moving from 5-7 YO tech to the newest stack. Partly due
> > to the
> > support issues, but mostly due to the cost of support of the older
> > versions; it's finally become cheaper to upgrade than to continue
> > paying
> > the huge support costs.
> >
> > But my basic point is, that the act of upgrading large systems is
> > not a
> > cheap one, so it is NOT done lightly.
> 
> I think that the cost is only so high because companies keep waiting
> until
> it is too painful. If you constantly keep upgrading a bit here and
> there
> and stay up to date with your operating systems, runtime
> environments,
> browsers and client site frameworks and so on you would actually be
> able
> to save a LOT of money in the long run. But you would have to
> constantly
> invest rather than waiting with no investment until things fall apart
> and
> then being forced to large costly upgrades.
> 
> So it is mostly short sighted management and an absence of real
> technology
> leadership in organizations causing this problem imho. And forcing
> the
> pain to stay on old stuff higher (like Oracle is doing with
> deprecating
> Java 6 earlier) is actually a good thing.
> 
> imho Maven 2 should have long been deprecated and removed from the
> downloads pages..
> 
> just my 2c though ;-)
> 
> manfred
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> 

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Manfred Moser]

On Wed, September 12, 2012 6:06 pm, Chris Graham wrote:
> On Wed, Sep 12, 2012 at 9:46 PM, Anders Hammar  wrote:
>
>> I fully agree with you and I'm actually of the opinion that the Java
>> community has a responsibility to provide enough reasons for those on
>> older Java platforms to upgrade. But as long as we provide libraries
>>
>
> Simple.
>
> Two reasons actually.
>
> Without going off on an essay about the psychology of developers and being
> obsessed with "shiny new things" (and a Dev centric view of the world)...
>
> 1. Cost.
>
> 2. Especially in the corporate world, they are far more concerned with
> function rather than form (ie the underlying technology). In short, if it
> works, leave it. Which also relates to #1.
>
> Case in point: My current project is a multi million dollar one that is
> *finally* moving from 5-7 YO tech to the newest stack. Partly due to the
> support issues, but mostly due to the cost of support of the older
> versions; it's finally become cheaper to upgrade than to continue paying
> the huge support costs.
>
> But my basic point is, that the act of upgrading large systems is not a
> cheap one, so it is NOT done lightly.

I think that the cost is only so high because companies keep waiting until
it is too painful. If you constantly keep upgrading a bit here and there
and stay up to date with your operating systems, runtime environments,
browsers and client site frameworks and so on you would actually be able
to save a LOT of money in the long run. But you would have to constantly
invest rather than waiting with no investment until things fall apart and
then being forced to large costly upgrades.

So it is mostly short sighted management and an absence of real technology
leadership in organizations causing this problem imho. And forcing the
pain to stay on old stuff higher (like Oracle is doing with deprecating
Java 6 earlier) is actually a good thing.

imho Maven 2 should have long been deprecated and removed from the
downloads pages..

just my 2c though ;-)

manfred

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Chris Graham]

On Wed, Sep 12, 2012 at 9:46 PM, Anders Hammar  wrote:

> I fully agree with you and I'm actually of the opinion that the Java
> community has a responsibility to provide enough reasons for those on
> older Java platforms to upgrade. But as long as we provide libraries
>

Simple.

Two reasons actually.

Without going off on an essay about the psychology of developers and being
obsessed with "shiny new things" (and a Dev centric view of the world)...

1. Cost.

2. Especially in the corporate world, they are far more concerned with
function rather than form (ie the underlying technology). In short, if it
works, leave it. Which also relates to #1.

Case in point: My current project is a multi million dollar one that is
*finally* moving from 5-7 YO tech to the newest stack. Partly due to the
support issues, but mostly due to the cost of support of the older
versions; it's finally become cheaper to upgrade than to continue paying
the huge support costs.

But my basic point is, that the act of upgrading large systems is not a
cheap one, so it is NOT done lightly.

Re: [VOTE] Release Maven Indexer version 5.0.0

[Milos Kleint]

+1

basic testing inside netbeans codebase, all seems to work.

Milos

On Wed, Sep 12, 2012 at 8:20 PM, Tamás Cservenák  wrote:
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=18722
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12112&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-058/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
>
> Thanks,
> ~t~

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Changes Plugin version 2.8

[Robert Scholte]

+1

Op Wed, 12 Sep 2012 15:05:27 +0200 schreef Tony Chemit  
:



On Tue, 11 Sep 2012 21:55:16 +0200
Dennis Lundberg  wrote:

+1,

works fine to me,

thanks,

tony.


Hi,

We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=18484

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-053/
https://repository.apache.org/content/repositories/maven-053/org/apache/maven/plugins/maven-changes-plugin/2.8/maven-changes-plugin-2.8-source-release.zip

Staging site (wait for the sync):
http://maven.apache.org/plugins/maven-changes-plugin-2.8/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1






-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[VOTE] Release Maven Indexer version 5.0.0

[Tamás Cservenák]

Hi,

We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=12112&version=18722

There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=12112&status=1

Staging repo:
https://repository.apache.org/content/repositories/maven-058/

Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html

Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1



Thanks,
~t~

Re: Plan for git migration

[Mark Struberg]

I'm +1 for keep em. 

Reason is that this allows quicker digging for some history info. I'm e.g. not 
sure if moves and stuff gets fully resolved with git-svn. Structure changes are 
another candidate of loosing history in git-svn (that would hit the maven-3 
module).

LieGrue,
strub




- Original Message -
> From: Kristian Rosenvold 
> To: Maven Developers List 
> Cc: 
> Sent: Wednesday, September 12, 2012 2:47 PM
> Subject: Re: Plan for git migration
> 
> Are you thinking about the svn references etched into each commit ?
> 
> The current git-svn repos all have this information appended at the
> end of each commit:
> git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> 13f79535-47bb-0310-9956-ffa450edef68
> 
> Personally I think we should keep them, since they contain the
> historical reference to the SVN commit number. And technically we have
> a lot
> of jiras referencing "r990909" so removing them is not a good idea wrt
> traceability of changes.
> 
> I know some projects (spring-framework) removed them and others kept
> them. But they have value for us; at least the revision number. We
> could consider rewriting it to just "r900900" although personally I
> think it's just uneccesary work.
> 
> Kristian
> 
> 
> 
> 
> 
> 
> 2012/9/12 Nord, James :
>>  The existing ones will likely have a lot of svn metadata which would tnhen 
> be broken / wrong and then could cause issues/confusion in the future
>> 
>>  I have migrated svn repos using the scrips at 
> https://github.com/nirvdrum/svn2git which tidies up this extra info and does 
> some extra housekeeping.
>> 
>>  Should you wish to split the svn structure then this allows you to do that.
>> 
>>  YMMV - but also something that you may not have been aware of.
>> 
>>  /James
>> 
>>>  -Original Message-
>>>  From: Olivier Lamy [mailto:ol...@apache.org]
>>>  Sent: 12 September 2012 13:26
>>>  To: Maven Developers List
>>>  Subject: Re: Plan for git migration
>>> 
>>>  2012/9/12 Kristian Rosenvold :
>>>  > Just to clarify additionally: There are existing read-only clones 
> of a
>>>  > lot of our projects (i'm sure infra can make the rest if they 
> have
>>>  > value)
>>>  >
>>>  > Some of these are excellent and  of high quality (surefire, m3 + 
> it's
>>>  > are the ones I know of) while at least maven-plugins is useless 
> (due
>>>  > to a strange interpretation of tags - try checking out a tag in 
> the
>>>  > current maven-plugins git clone !!!). So we need to collect the
>>>  > assessments of which repos are "migration ready" and 
> which are not.
>>>  > Any community input on this would be great! (If you've used 
> the clone
>>>  > and find that tags/branches etc work according to expectations 
> we're
>>>  > cool)
>>>  >
>>>  > For those that are migration ready the process is is something 
> like this:
>>>  >
>>>  > 1. Have infra make the existing read-only mirror the official 
> master.
>>>  > 2. Change scm url in pom
>>>  > 3. Update github mirroring url (file issue with github)
>>>  that's something we maintain @asf infra.
>>>  I recommend you lurking on infra@ mailing list (if you don't 
> already) as some
>>>  discussions will start here. (see
>>>  http://www.apache.org/dev/infra-mail.html)
>>> 
>>>  > 4. Celebrate
>>>  >
>>>  >
>>>  > For those that for /some/ reason are not ready, we need to resolve
>>>  > what needs to be done.
>>>  >
>>>  > Kristian
>>>  >
>>>  >
>>>  >
>>>  >
>>>  >
>>>  > 2012/9/12 Baptiste MATHUS :
>>>  >> Hi,
>>>  >>
>>>  >> +1.
>>>  >> Though I'm volunteering to help, as I'm not Maven 
> committer, I don't
>>>  >> know if I'm really allowed to help.
>>>  >> I could help on some projects if needed (I can see maybe 
> enforcer &
>>>  >> release for example).
>>>  >>
>>>  >> By the way, I'm not sure how this is supposed to work. 
> After reading
>>>  >> Kristian comment, I discovered there's actually already 
> many (if not
>>>  >> all) Maven projects that seem migrated (?).
>>>  >> http://git.apache.org/ Is this something that was done by 
> someone
>>>  >> during the night? :-).
>>>  >>
>>>  >> Or maybe that repos are not correct in some way 
> (Kristian's comment
>>>  >> say some are already usable as-is)?
>>>  >>
>>>  >> What makes a repo correct or not to be used as-is?
>>>  >>
>>>  >> Looking at the repo structure from the HTTP interface, I'm 
> under the
>>>  >> impression this is a git repo created by git svn (or 
> svn2git?), .
>>>  >> My naive first guess understanding is that there already may 
> be a
>>>  >> batch of "maven git scripts" running on the 
> infrastructure that would
>>>  >> git-svn the main repo, then filter-branch this repo for a 
> bunch of
>>>  >> directories (release, enforcer, etc.).
>>>  >>
>>>  >> If this is so, not totally sure what would be left?
>>>  >>
>>>  >> Thanks.
>>>  >>
>>>  >> 2012/9/12 Benson Margulies 
>>>  >>
>>>  >>> Who is going to open the initial negotiation with INFRA?
>>>  >>>
>>>  >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy

Re: Plan for git migration

[Benson Margulies]

I don't think we get control of this, but I think you'll be happy with
what we do get. Infra has a repeatable process for converting svn
repos to git.

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Kristian Rosenvold]

We still need some verification that the individual repos are ok.
(build an old tag,  just look at file trees to see nothing strange
happens)

You can post that here.

Kristian

Den 12. s. 2012 kl. 15:55 skrev Olivier Lamy :

> 2012/9/12 Baptiste MATHUS :
>> I can try and take care of enforcer & release to begin with if no-one
>> objects. But I cannot add myself to the wiki even logged in. I guess the
>> pages are protected to spammers.
> Thanks for the help.
> But the task will be "relatively easy" as we have already clones
> available for some parts of the svn tree.
>
> It's just a question of available time from ASF infra folks (normally
> already existed volunteers from the project will help too at least I
> hope :P )
>>
>> Cheers
>>
>> 2012/9/12 Olivier Lamy 
>>
>>> +1 for keep svn references.
>>>
>>> FYI I will start migration with moving the following repositories:
>>> * surefire
>>> * wagon
>>> * scm
>>>
>>> 2012/9/12 Baptiste MATHUS :
 2012/9/12 Kristian Rosenvold 

> Are you thinking about the svn references etched into each commit ?
>
> The current git-svn repos all have this information appended at the
> end of each commit:
> git-svn-id:
>>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> 13f79535-47bb-0310-9956-ffa450edef68
>
> Personally I think we should keep them, since they contain the
> historical reference to the SVN commit number. And technically we have
> a lot
> of jiras referencing "r990909" so removing them is not a good idea wrt
> traceability of changes.
>

 +1000. I was about to answer in the same vein.
 I really think that storing as much information of where a gives path
>>> comes
 from will be very valuable in the future.

 I cannot understand how one could want to get rid of that informations.
 Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
>>> some
 revisions and it's always very useful to be able to find that very
>>> revision
 in the Git history.

 Cheers

 --
 Baptiste  MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 nbsp;!
>>>
>>>
>>>
>>> --
>>> Olivier Lamy
>>> Talend: http://coders.talend.com
>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>> --
>>> Baptiste  MATHUS - http://batmat.net
>>> Sauvez un arbre,
>>> Mangez un castor !
>>> nbsp;!
>>> 
>>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Olivier Lamy]

2012/9/12 Baptiste MATHUS :
> I can try and take care of enforcer & release to begin with if no-one
> objects. But I cannot add myself to the wiki even logged in. I guess the
> pages are protected to spammers.
Thanks for the help.
But the task will be "relatively easy" as we have already clones
available for some parts of the svn tree.

It's just a question of available time from ASF infra folks (normally
already existed volunteers from the project will help too at least I
hope :P )
>
> Cheers
>
> 2012/9/12 Olivier Lamy 
>
>> +1 for keep svn references.
>>
>> FYI I will start migration with moving the following repositories:
>> * surefire
>> * wagon
>> * scm
>>
>> 2012/9/12 Baptiste MATHUS :
>> > 2012/9/12 Kristian Rosenvold 
>> >
>> >> Are you thinking about the svn references etched into each commit ?
>> >>
>> >> The current git-svn repos all have this information appended at the
>> >> end of each commit:
>> >> git-svn-id:
>> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>> >> 13f79535-47bb-0310-9956-ffa450edef68
>> >>
>> >> Personally I think we should keep them, since they contain the
>> >> historical reference to the SVN commit number. And technically we have
>> >> a lot
>> >> of jiras referencing "r990909" so removing them is not a good idea wrt
>> >> traceability of changes.
>> >>
>> >
>> > +1000. I was about to answer in the same vein.
>> > I really think that storing as much information of where a gives path
>> comes
>> > from will be very valuable in the future.
>> >
>> > I cannot understand how one could want to get rid of that informations.
>> > Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
>> some
>> > revisions and it's always very useful to be able to find that very
>> revision
>> > in the Git history.
>> >
>> > Cheers
>> >
>> > --
>> > Baptiste  MATHUS - http://batmat.net
>> > Sauvez un arbre,
>> > Mangez un castor !
>> > nbsp;!
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>>  
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Baptiste MATHUS]

I can try and take care of enforcer & release to begin with if no-one
objects. But I cannot add myself to the wiki even logged in. I guess the
pages are protected to spammers.

Cheers

2012/9/12 Olivier Lamy 

> +1 for keep svn references.
>
> FYI I will start migration with moving the following repositories:
> * surefire
> * wagon
> * scm
>
> 2012/9/12 Baptiste MATHUS :
> > 2012/9/12 Kristian Rosenvold 
> >
> >> Are you thinking about the svn references etched into each commit ?
> >>
> >> The current git-svn repos all have this information appended at the
> >> end of each commit:
> >> git-svn-id:
> https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> >> 13f79535-47bb-0310-9956-ffa450edef68
> >>
> >> Personally I think we should keep them, since they contain the
> >> historical reference to the SVN commit number. And technically we have
> >> a lot
> >> of jiras referencing "r990909" so removing them is not a good idea wrt
> >> traceability of changes.
> >>
> >
> > +1000. I was about to answer in the same vein.
> > I really think that storing as much information of where a gives path
> comes
> > from will be very valuable in the future.
> >
> > I cannot understand how one could want to get rid of that informations.
> > Exactly as Kristian said: you have JIRAs, mails, whatever pointing to
> some
> > revisions and it's always very useful to be able to find that very
> revision
> > in the Git history.
> >
> > Cheers
> >
> > --
> > Baptiste  MATHUS - http://batmat.net
> > Sauvez un arbre,
> > Mangez un castor !
> > nbsp;!
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
>  
>

Re: Plan for git migration

[Olivier Lamy]

+1 for keep svn references.

FYI I will start migration with moving the following repositories:
* surefire
* wagon
* scm

2012/9/12 Baptiste MATHUS :
> 2012/9/12 Kristian Rosenvold 
>
>> Are you thinking about the svn references etched into each commit ?
>>
>> The current git-svn repos all have this information appended at the
>> end of each commit:
>> git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
>> 13f79535-47bb-0310-9956-ffa450edef68
>>
>> Personally I think we should keep them, since they contain the
>> historical reference to the SVN commit number. And technically we have
>> a lot
>> of jiras referencing "r990909" so removing them is not a good idea wrt
>> traceability of changes.
>>
>
> +1000. I was about to answer in the same vein.
> I really think that storing as much information of where a gives path comes
> from will be very valuable in the future.
>
> I cannot understand how one could want to get rid of that informations.
> Exactly as Kristian said: you have JIRAs, mails, whatever pointing to some
> revisions and it's always very useful to be able to find that very revision
> in the Git history.
>
> Cheers
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: [VOTE] Release Maven Changes Plugin version 2.8

[Tony Chemit]

On Tue, 11 Sep 2012 21:55:16 +0200
Dennis Lundberg  wrote:

+1,

works fine to me,

thanks,

tony.

> Hi,
> 
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=18484
> 
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
> 
> Staging repo:
> https://repository.apache.org/content/repositories/maven-053/
> https://repository.apache.org/content/repositories/maven-053/org/apache/maven/plugins/maven-changes-plugin/2.8/maven-changes-plugin-2.8-source-release.zip
> 
> Staging site (wait for the sync):
> http://maven.apache.org/plugins/maven-changes-plugin-2.8/
> 
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
> 
> Vote open for 72 hours.
> 
> [ ] +1
> [ ] +0
> [ ] -1
> 



-- 
Tony Chemit

tél: +33 (0) 2 40 50 29 28
email: che...@codelutin.com
http://www.codelutin.com

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Baptiste MATHUS]

2012/9/12 Kristian Rosenvold 

> Are you thinking about the svn references etched into each commit ?
>
> The current git-svn repos all have this information appended at the
> end of each commit:
> git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
> 13f79535-47bb-0310-9956-ffa450edef68
>
> Personally I think we should keep them, since they contain the
> historical reference to the SVN commit number. And technically we have
> a lot
> of jiras referencing "r990909" so removing them is not a good idea wrt
> traceability of changes.
>

+1000. I was about to answer in the same vein.
I really think that storing as much information of where a gives path comes
from will be very valuable in the future.

I cannot understand how one could want to get rid of that informations.
Exactly as Kristian said: you have JIRAs, mails, whatever pointing to some
revisions and it's always very useful to be able to find that very revision
in the Git history.

Cheers

-- 
Baptiste  MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !
nbsp;!

Re: [VOTE] Release Maven Changes Plugin version 2.8

[Olivier Lamy]

+1

2012/9/11 Dennis Lundberg :
> Hi,
>
> We solved 6 issues:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11212&styleName=Html&version=18484
>
> There are still a couple of issues left in JIRA:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11212&status=1
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-053/
> https://repository.apache.org/content/repositories/maven-053/org/apache/maven/plugins/maven-changes-plugin/2.8/maven-changes-plugin-2.8-source-release.zip
>
> Staging site (wait for the sync):
> http://maven.apache.org/plugins/maven-changes-plugin-2.8/
>
> Guide to testing staged releases:
> http://maven.apache.org/guides/development/guide-testing-releases.html
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
> --
> Dennis Lundberg
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Kristian Rosenvold]

Are you thinking about the svn references etched into each commit ?

The current git-svn repos all have this information appended at the
end of each commit:
git-svn-id: https://svn.apache.org/repos/asf/maven/surefire/trunk@1374642
13f79535-47bb-0310-9956-ffa450edef68

Personally I think we should keep them, since they contain the
historical reference to the SVN commit number. And technically we have
a lot
of jiras referencing "r990909" so removing them is not a good idea wrt
traceability of changes.

I know some projects (spring-framework) removed them and others kept
them. But they have value for us; at least the revision number. We
could consider rewriting it to just "r900900" although personally I
think it's just uneccesary work.

Kristian






2012/9/12 Nord, James :
> The existing ones will likely have a lot of svn metadata which would tnhen be 
> broken / wrong and then could cause issues/confusion in the future
>
> I have migrated svn repos using the scrips at 
> https://github.com/nirvdrum/svn2git which tidies up this extra info and does 
> some extra housekeeping.
>
> Should you wish to split the svn structure then this allows you to do that.
>
> YMMV - but also something that you may not have been aware of.
>
> /James
>
>> -Original Message-
>> From: Olivier Lamy [mailto:ol...@apache.org]
>> Sent: 12 September 2012 13:26
>> To: Maven Developers List
>> Subject: Re: Plan for git migration
>>
>> 2012/9/12 Kristian Rosenvold :
>> > Just to clarify additionally: There are existing read-only clones of a
>> > lot of our projects (i'm sure infra can make the rest if they have
>> > value)
>> >
>> > Some of these are excellent and  of high quality (surefire, m3 + it's
>> > are the ones I know of) while at least maven-plugins is useless (due
>> > to a strange interpretation of tags - try checking out a tag in the
>> > current maven-plugins git clone !!!). So we need to collect the
>> > assessments of which repos are "migration ready" and which are not.
>> > Any community input on this would be great! (If you've used the clone
>> > and find that tags/branches etc work according to expectations we're
>> > cool)
>> >
>> > For those that are migration ready the process is is something like this:
>> >
>> > 1. Have infra make the existing read-only mirror the official master.
>> > 2. Change scm url in pom
>> > 3. Update github mirroring url (file issue with github)
>> that's something we maintain @asf infra.
>> I recommend you lurking on infra@ mailing list (if you don't already) as some
>> discussions will start here. (see
>> http://www.apache.org/dev/infra-mail.html)
>>
>> > 4. Celebrate
>> >
>> >
>> > For those that for /some/ reason are not ready, we need to resolve
>> > what needs to be done.
>> >
>> > Kristian
>> >
>> >
>> >
>> >
>> >
>> > 2012/9/12 Baptiste MATHUS :
>> >> Hi,
>> >>
>> >> +1.
>> >> Though I'm volunteering to help, as I'm not Maven committer, I don't
>> >> know if I'm really allowed to help.
>> >> I could help on some projects if needed (I can see maybe enforcer &
>> >> release for example).
>> >>
>> >> By the way, I'm not sure how this is supposed to work. After reading
>> >> Kristian comment, I discovered there's actually already many (if not
>> >> all) Maven projects that seem migrated (?).
>> >> http://git.apache.org/ Is this something that was done by someone
>> >> during the night? :-).
>> >>
>> >> Or maybe that repos are not correct in some way (Kristian's comment
>> >> say some are already usable as-is)?
>> >>
>> >> What makes a repo correct or not to be used as-is?
>> >>
>> >> Looking at the repo structure from the HTTP interface, I'm under the
>> >> impression this is a git repo created by git svn (or svn2git?), .
>> >> My naive first guess understanding is that there already may be a
>> >> batch of "maven git scripts" running on the infrastructure that would
>> >> git-svn the main repo, then filter-branch this repo for a bunch of
>> >> directories (release, enforcer, etc.).
>> >>
>> >> If this is so, not totally sure what would be left?
>> >>
>> >> Thanks.
>> >>
>> >> 2012/9/12 Benson Margulies 
>> >>
>> >>> Who is going to open the initial negotiation with INFRA?
>> >>>
>> >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy 
>> wrote:
>> >>> > Hi Folks,
>> >>> > So the vote passed, now it's time for volunteers to use their
>> >>> > fingers
>> >>> :-).
>> >>> > I have started a page [1] for ETA of migration (note the Volunteer
>> >>> > column :-) ) and for discussion on some stuff (plugins shared)
>> >>> >
>> >>> >
>> >>> > Thanks
>> >>> > --
>> >>> > Olivier Lamy
>> >>> > Talend: http://coders.talend.com
>> >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy [1]
>> >>> > https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>> >>>
>> >>> --
>> >>> Baptiste  MATHUS - http://batmat.net Sauvez un arbre, Mangez
>> >>> un castor !
>> >>> nbsp;!
>> >>>  
>> >>>
>> >
>> > ---

Re: Release of Maven Indexer 5.0

[Milos Kleint]

the usual operations like indexing local repo, downloding remote index
and searching appear all working properly.

I had to change a place or two to call aquire+release methods on the context.

Milos

On Wed, Sep 12, 2012 at 1:02 PM, Milos Kleint  wrote:
> On Wed, Sep 12, 2012 at 12:53 PM, Tamás Cservenák  wrote:
>> Milos,
>>
>> yes I think it is, since all of it is _removed_. See issue
>> https://jira.codehaus.org/browse/MINDEXER-57
>> and related commits.
>>
>> Only integration I tested is... Nexus. So, you could give it a spin in NB
>> for example...
>
> I'm right at it, however the issue reported is fairly random (and
> rarely occurring) so the most likely result of my testing will be just
> sanity check confirmation..
>
> Milos
>
>
>
>>
>> Thanks,
>> ~t~
>>
>> On Wed, Sep 12, 2012 at 12:35 PM, Milos Kleint  wrote:
>>
>>> hey,
>>>
>>> do you believe https://jira.codehaus.org/browse/MINDEXER-52 is fixed in
>>> 5.0?
>>>
>>> Milos
>>>
>>> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
>>> wrote:
>>> > Howdy,
>>> >
>>> > there are a notable changes in trunk of MI:
>>> >
>>> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>>> >
>>> > https://github.com/apache/maven-indexer/commits/trunk?page=1
>>> >
>>> >
>>> > So, I'd like to spin a release of it.
>>> >
>>> > Any objections to this? Any last minute wish?
>>> >
>>> >
>>> > Thanks,
>>> > ~t~
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

RE: Plan for git migration

[Nord, James]

The existing ones will likely have a lot of svn metadata which would tnhen be 
broken / wrong and then could cause issues/confusion in the future

I have migrated svn repos using the scrips at 
https://github.com/nirvdrum/svn2git which tidies up this extra info and does 
some extra housekeeping.

Should you wish to split the svn structure then this allows you to do that.

YMMV - but also something that you may not have been aware of.

/James

> -Original Message-
> From: Olivier Lamy [mailto:ol...@apache.org]
> Sent: 12 September 2012 13:26
> To: Maven Developers List
> Subject: Re: Plan for git migration
>
> 2012/9/12 Kristian Rosenvold :
> > Just to clarify additionally: There are existing read-only clones of a
> > lot of our projects (i'm sure infra can make the rest if they have
> > value)
> >
> > Some of these are excellent and  of high quality (surefire, m3 + it's
> > are the ones I know of) while at least maven-plugins is useless (due
> > to a strange interpretation of tags - try checking out a tag in the
> > current maven-plugins git clone !!!). So we need to collect the
> > assessments of which repos are "migration ready" and which are not.
> > Any community input on this would be great! (If you've used the clone
> > and find that tags/branches etc work according to expectations we're
> > cool)
> >
> > For those that are migration ready the process is is something like this:
> >
> > 1. Have infra make the existing read-only mirror the official master.
> > 2. Change scm url in pom
> > 3. Update github mirroring url (file issue with github)
> that's something we maintain @asf infra.
> I recommend you lurking on infra@ mailing list (if you don't already) as some
> discussions will start here. (see
> http://www.apache.org/dev/infra-mail.html)
>
> > 4. Celebrate
> >
> >
> > For those that for /some/ reason are not ready, we need to resolve
> > what needs to be done.
> >
> > Kristian
> >
> >
> >
> >
> >
> > 2012/9/12 Baptiste MATHUS :
> >> Hi,
> >>
> >> +1.
> >> Though I'm volunteering to help, as I'm not Maven committer, I don't
> >> know if I'm really allowed to help.
> >> I could help on some projects if needed (I can see maybe enforcer &
> >> release for example).
> >>
> >> By the way, I'm not sure how this is supposed to work. After reading
> >> Kristian comment, I discovered there's actually already many (if not
> >> all) Maven projects that seem migrated (?).
> >> http://git.apache.org/ Is this something that was done by someone
> >> during the night? :-).
> >>
> >> Or maybe that repos are not correct in some way (Kristian's comment
> >> say some are already usable as-is)?
> >>
> >> What makes a repo correct or not to be used as-is?
> >>
> >> Looking at the repo structure from the HTTP interface, I'm under the
> >> impression this is a git repo created by git svn (or svn2git?), .
> >> My naive first guess understanding is that there already may be a
> >> batch of "maven git scripts" running on the infrastructure that would
> >> git-svn the main repo, then filter-branch this repo for a bunch of
> >> directories (release, enforcer, etc.).
> >>
> >> If this is so, not totally sure what would be left?
> >>
> >> Thanks.
> >>
> >> 2012/9/12 Benson Margulies 
> >>
> >>> Who is going to open the initial negotiation with INFRA?
> >>>
> >>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy 
> wrote:
> >>> > Hi Folks,
> >>> > So the vote passed, now it's time for volunteers to use their
> >>> > fingers
> >>> :-).
> >>> > I have started a page [1] for ETA of migration (note the Volunteer
> >>> > column :-) ) and for discussion on some stuff (plugins shared)
> >>> >
> >>> >
> >>> > Thanks
> >>> > --
> >>> > Olivier Lamy
> >>> > Talend: http://coders.talend.com
> >>> > http://twitter.com/olamy | http://linkedin.com/in/olamy [1]
> >>> > https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
> >>>
> >>> --
> >>> Baptiste  MATHUS - http://batmat.net Sauvez un arbre, Mangez
> >>> un castor !
> >>> nbsp;!
> >>>  
> >>>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For
> > additional commands, e-mail: dev-h...@maven.apache.org
> >
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional
> commands, e-mail: dev-h...@maven.apache.org





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
em

Re: Plan for git migration

[Olivier Lamy]

2012/9/12 Kristian Rosenvold :
> I'm a long time lurker on infra and #asfinfra; are these the sole places for
> discussing this stuff ?
yup.
>
> Kristian
>
> 2012/9/12 Olivier Lamy :
>> 2012/9/12 Kristian Rosenvold :
>>> Just to clarify additionally: There are existing read-only clones of a
>>> lot of our projects (i'm sure infra can make the rest if they have
>>> value)
>>>
>>> Some of these are excellent and  of high quality (surefire, m3 + it's
>>> are the ones I know of) while at least maven-plugins is useless (due
>>> to a strange interpretation of tags - try checking out a tag in the
>>> current maven-plugins git clone !!!). So we need to collect the
>>> assessments of which repos are "migration ready" and which are not.
>>> Any community input on this would be great! (If you've used the clone
>>> and find that tags/branches etc work according to expectations we're
>>> cool)
>>>
>>> For those that are migration ready the process is is something like this:
>>>
>>> 1. Have infra make the existing read-only mirror the official master.
>>> 2. Change scm url in pom
>>> 3. Update github mirroring url (file issue with github)
>> that's something we maintain @asf infra.
>> I recommend you lurking on infra@ mailing list (if you don't already)
>> as some discussions will start here. (see
>> http://www.apache.org/dev/infra-mail.html)
>>
>>> 4. Celebrate
>>>
>>>
>>> For those that for /some/ reason are not ready, we need to resolve
>>> what needs to be done.
>>>
>>> Kristian
>>>
>>>
>>>
>>>
>>>
>>> 2012/9/12 Baptiste MATHUS :
 Hi,

 +1.
 Though I'm volunteering to help, as I'm not Maven committer, I don't know
 if I'm really allowed to help.
 I could help on some projects if needed (I can see maybe enforcer & release
 for example).

 By the way, I'm not sure how this is supposed to work. After reading
 Kristian comment, I discovered there's actually already many (if not all)
 Maven projects that seem migrated (?).
 http://git.apache.org/ Is this something that was done by someone during
 the night? :-).

 Or maybe that repos are not correct in some way (Kristian's comment say
 some are already usable as-is)?

 What makes a repo correct or not to be used as-is?

 Looking at the repo structure from the HTTP interface, I'm under the
 impression this is a git repo created by git svn (or svn2git?), .
 My naive first guess understanding is that there already may be a batch of
 "maven git scripts" running on the infrastructure that would git-svn the
 main repo, then filter-branch this repo for a bunch of directories
 (release, enforcer, etc.).

 If this is so, not totally sure what would be left?

 Thanks.

 2012/9/12 Benson Margulies 

> Who is going to open the initial negotiation with INFRA?
>
> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
> > Hi Folks,
> > So the vote passed, now it's time for volunteers to use their fingers
> :-).
> > I have started a page [1] for ETA of migration (note the Volunteer
> > column :-) ) and for discussion on some stuff (plugins shared)
> >
> >
> > Thanks
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
>  
>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Kristian Rosenvold]

I'm a long time lurker on infra and #asfinfra; are these the sole places for
discussing this stuff ?

Kristian

2012/9/12 Olivier Lamy :
> 2012/9/12 Kristian Rosenvold :
>> Just to clarify additionally: There are existing read-only clones of a
>> lot of our projects (i'm sure infra can make the rest if they have
>> value)
>>
>> Some of these are excellent and  of high quality (surefire, m3 + it's
>> are the ones I know of) while at least maven-plugins is useless (due
>> to a strange interpretation of tags - try checking out a tag in the
>> current maven-plugins git clone !!!). So we need to collect the
>> assessments of which repos are "migration ready" and which are not.
>> Any community input on this would be great! (If you've used the clone
>> and find that tags/branches etc work according to expectations we're
>> cool)
>>
>> For those that are migration ready the process is is something like this:
>>
>> 1. Have infra make the existing read-only mirror the official master.
>> 2. Change scm url in pom
>> 3. Update github mirroring url (file issue with github)
> that's something we maintain @asf infra.
> I recommend you lurking on infra@ mailing list (if you don't already)
> as some discussions will start here. (see
> http://www.apache.org/dev/infra-mail.html)
>
>> 4. Celebrate
>>
>>
>> For those that for /some/ reason are not ready, we need to resolve
>> what needs to be done.
>>
>> Kristian
>>
>>
>>
>>
>>
>> 2012/9/12 Baptiste MATHUS :
>>> Hi,
>>>
>>> +1.
>>> Though I'm volunteering to help, as I'm not Maven committer, I don't know
>>> if I'm really allowed to help.
>>> I could help on some projects if needed (I can see maybe enforcer & release
>>> for example).
>>>
>>> By the way, I'm not sure how this is supposed to work. After reading
>>> Kristian comment, I discovered there's actually already many (if not all)
>>> Maven projects that seem migrated (?).
>>> http://git.apache.org/ Is this something that was done by someone during
>>> the night? :-).
>>>
>>> Or maybe that repos are not correct in some way (Kristian's comment say
>>> some are already usable as-is)?
>>>
>>> What makes a repo correct or not to be used as-is?
>>>
>>> Looking at the repo structure from the HTTP interface, I'm under the
>>> impression this is a git repo created by git svn (or svn2git?), .
>>> My naive first guess understanding is that there already may be a batch of
>>> "maven git scripts" running on the infrastructure that would git-svn the
>>> main repo, then filter-branch this repo for a bunch of directories
>>> (release, enforcer, etc.).
>>>
>>> If this is so, not totally sure what would be left?
>>>
>>> Thanks.
>>>
>>> 2012/9/12 Benson Margulies 
>>>
 Who is going to open the initial negotiation with INFRA?

 On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
 > Hi Folks,
 > So the vote passed, now it's time for volunteers to use their fingers
 :-).
 > I have started a page [1] for ETA of migration (note the Volunteer
 > column :-) ) and for discussion on some stuff (plugins shared)
 >
 >
 > Thanks
 > --
 > Olivier Lamy
 > Talend: http://coders.talend.com
 > http://twitter.com/olamy | http://linkedin.com/in/olamy
 > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration

 --
 Baptiste  MATHUS - http://batmat.net
 Sauvez un arbre,
 Mangez un castor !
 nbsp;!
  

>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Olivier Lamy]

2012/9/12 Kristian Rosenvold :
> Just to clarify additionally: There are existing read-only clones of a
> lot of our projects (i'm sure infra can make the rest if they have
> value)
>
> Some of these are excellent and  of high quality (surefire, m3 + it's
> are the ones I know of) while at least maven-plugins is useless (due
> to a strange interpretation of tags - try checking out a tag in the
> current maven-plugins git clone !!!). So we need to collect the
> assessments of which repos are "migration ready" and which are not.
> Any community input on this would be great! (If you've used the clone
> and find that tags/branches etc work according to expectations we're
> cool)
>
> For those that are migration ready the process is is something like this:
>
> 1. Have infra make the existing read-only mirror the official master.
> 2. Change scm url in pom
> 3. Update github mirroring url (file issue with github)
that's something we maintain @asf infra.
I recommend you lurking on infra@ mailing list (if you don't already)
as some discussions will start here. (see
http://www.apache.org/dev/infra-mail.html)

> 4. Celebrate
>
>
> For those that for /some/ reason are not ready, we need to resolve
> what needs to be done.
>
> Kristian
>
>
>
>
>
> 2012/9/12 Baptiste MATHUS :
>> Hi,
>>
>> +1.
>> Though I'm volunteering to help, as I'm not Maven committer, I don't know
>> if I'm really allowed to help.
>> I could help on some projects if needed (I can see maybe enforcer & release
>> for example).
>>
>> By the way, I'm not sure how this is supposed to work. After reading
>> Kristian comment, I discovered there's actually already many (if not all)
>> Maven projects that seem migrated (?).
>> http://git.apache.org/ Is this something that was done by someone during
>> the night? :-).
>>
>> Or maybe that repos are not correct in some way (Kristian's comment say
>> some are already usable as-is)?
>>
>> What makes a repo correct or not to be used as-is?
>>
>> Looking at the repo structure from the HTTP interface, I'm under the
>> impression this is a git repo created by git svn (or svn2git?), .
>> My naive first guess understanding is that there already may be a batch of
>> "maven git scripts" running on the infrastructure that would git-svn the
>> main repo, then filter-branch this repo for a bunch of directories
>> (release, enforcer, etc.).
>>
>> If this is so, not totally sure what would be left?
>>
>> Thanks.
>>
>> 2012/9/12 Benson Margulies 
>>
>>> Who is going to open the initial negotiation with INFRA?
>>>
>>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
>>> > Hi Folks,
>>> > So the vote passed, now it's time for volunteers to use their fingers
>>> :-).
>>> > I have started a page [1] for ETA of migration (note the Volunteer
>>> > column :-) ) and for discussion on some stuff (plugins shared)
>>> >
>>> >
>>> > Thanks
>>> > --
>>> > Olivier Lamy
>>> > Talend: http://coders.talend.com
>>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>>
>>> --
>>> Baptiste  MATHUS - http://batmat.net
>>> Sauvez un arbre,
>>> Mangez un castor !
>>> nbsp;!
>>>  
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Kristian Rosenvold]

Just to clarify additionally: There are existing read-only clones of a
lot of our projects (i'm sure infra can make the rest if they have
value)

Some of these are excellent and  of high quality (surefire, m3 + it's
are the ones I know of) while at least maven-plugins is useless (due
to a strange interpretation of tags - try checking out a tag in the
current maven-plugins git clone !!!). So we need to collect the
assessments of which repos are "migration ready" and which are not.
Any community input on this would be great! (If you've used the clone
and find that tags/branches etc work according to expectations we're
cool)

For those that are migration ready the process is is something like this:

1. Have infra make the existing read-only mirror the official master.
2. Change scm url in pom
3. Update github mirroring url (file issue with github)
4. Celebrate


For those that for /some/ reason are not ready, we need to resolve
what needs to be done.

Kristian





2012/9/12 Baptiste MATHUS :
> Hi,
>
> +1.
> Though I'm volunteering to help, as I'm not Maven committer, I don't know
> if I'm really allowed to help.
> I could help on some projects if needed (I can see maybe enforcer & release
> for example).
>
> By the way, I'm not sure how this is supposed to work. After reading
> Kristian comment, I discovered there's actually already many (if not all)
> Maven projects that seem migrated (?).
> http://git.apache.org/ Is this something that was done by someone during
> the night? :-).
>
> Or maybe that repos are not correct in some way (Kristian's comment say
> some are already usable as-is)?
>
> What makes a repo correct or not to be used as-is?
>
> Looking at the repo structure from the HTTP interface, I'm under the
> impression this is a git repo created by git svn (or svn2git?), .
> My naive first guess understanding is that there already may be a batch of
> "maven git scripts" running on the infrastructure that would git-svn the
> main repo, then filter-branch this repo for a bunch of directories
> (release, enforcer, etc.).
>
> If this is so, not totally sure what would be left?
>
> Thanks.
>
> 2012/9/12 Benson Margulies 
>
>> Who is going to open the initial negotiation with INFRA?
>>
>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
>> > Hi Folks,
>> > So the vote passed, now it's time for volunteers to use their fingers
>> :-).
>> > I have started a page [1] for ETA of migration (note the Volunteer
>> > column :-) ) and for discussion on some stuff (plugins shared)
>> >
>> >
>> > Thanks
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>>  
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Olivier Lamy]

Yup IMHO most of Maven indexer "users" are ide and/or repository
managers (most are probably already 1.6 required)
So perso I don't have any issues regarding moving to 1.6 required.

2012/9/12 Milos Kleint :
> if it matters, netbeans (the user the library is on 1.6 for a while
> already), no problems whatsoever upgrading..
>
> Milos
>
> On Wed, Sep 12, 2012 at 1:04 PM, Tamás Cservenák  wrote:
>> Actually, my hope was to have someone here say "c'mon, not bumping to
>> Java6? Are you nuts?" and then continue with, "listen, you code _today_
>> something that will be hopefully used 3-4 years from today. But, you are
>> _prevented_ to leave something that is already dead _today_ for 3 years
>> (will be 6-7 years during hopeful use of this release), you are prevented
>> to bump the source to something that _will be dead_ in months from
>> _today_... it does not make sense, especially as this is a major 5.x
>> release". Also, someone else could chime in with "those locked to java
>> 5 and java 4 should seriously stop and think a bit". And another with "we
>> [ASF] are an open, non-profit OSS forge, doing development for our own sake
>> and love. so did the company [since it's not a natural person I hope]
>> making you wont-fix this Java6 bump at least a golden sponsor of next
>> upcoming ApacheCon?" and so on :D
>>
>> etc.
>>
>>
>> Thanks,
>> ~t~
>>
>>
>>
>>
>> On Wed, Sep 12, 2012 at 11:34 AM, Anders Hammar  wrote:
>>
>>> Should MINDEXER-60 really have a fix version as it is won't fix? It
>>> could trick people just browsing the list of tickets associated with
>>> this relaese to think this has been introduced.
>>>
>>> /Anders
>>>
>>> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
>>> wrote:
>>> > Howdy,
>>> >
>>> > there are a notable changes in trunk of MI:
>>> >
>>> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>>> >
>>> > https://github.com/apache/maven-indexer/commits/trunk?page=1
>>> >
>>> >
>>> > So, I'd like to spin a release of it.
>>> >
>>> > Any objections to this? Any last minute wish?
>>> >
>>> >
>>> > Thanks,
>>> > ~t~
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Milos Kleint]

if it matters, netbeans (the user the library is on 1.6 for a while
already), no problems whatsoever upgrading..

Milos

On Wed, Sep 12, 2012 at 1:04 PM, Tamás Cservenák  wrote:
> Actually, my hope was to have someone here say "c'mon, not bumping to
> Java6? Are you nuts?" and then continue with, "listen, you code _today_
> something that will be hopefully used 3-4 years from today. But, you are
> _prevented_ to leave something that is already dead _today_ for 3 years
> (will be 6-7 years during hopeful use of this release), you are prevented
> to bump the source to something that _will be dead_ in months from
> _today_... it does not make sense, especially as this is a major 5.x
> release". Also, someone else could chime in with "those locked to java
> 5 and java 4 should seriously stop and think a bit". And another with "we
> [ASF] are an open, non-profit OSS forge, doing development for our own sake
> and love. so did the company [since it's not a natural person I hope]
> making you wont-fix this Java6 bump at least a golden sponsor of next
> upcoming ApacheCon?" and so on :D
>
> etc.
>
>
> Thanks,
> ~t~
>
>
>
>
> On Wed, Sep 12, 2012 at 11:34 AM, Anders Hammar  wrote:
>
>> Should MINDEXER-60 really have a fix version as it is won't fix? It
>> could trick people just browsing the list of tickets associated with
>> this relaese to think this has been introduced.
>>
>> /Anders
>>
>> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
>> wrote:
>> > Howdy,
>> >
>> > there are a notable changes in trunk of MI:
>> >
>> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>> >
>> > https://github.com/apache/maven-indexer/commits/trunk?page=1
>> >
>> >
>> > So, I'd like to spin a release of it.
>> >
>> > Any objections to this? Any last minute wish?
>> >
>> >
>> > Thanks,
>> > ~t~
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Olivier Lamy]

2012/9/12 Benson Margulies :
> Who is going to open the initial negotiation with INFRA?
looks to be one of my task :-)
>
> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
>> Hi Folks,
>> So the vote passed, now it's time for volunteers to use their fingers :-).
>> I have started a page [1] for ETA of migration (note the Volunteer
>> column :-) ) and for discussion on some stuff (plugins shared)
>>
>>
>> Thanks
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Olivier Lamy]

2012/9/12 Baptiste MATHUS :
> Hi,
>
> +1.
> Though I'm volunteering to help, as I'm not Maven committer, I don't know
> if I'm really allowed to help.
> I could help on some projects if needed (I can see maybe enforcer & release
> for example).
>
> By the way, I'm not sure how this is supposed to work. After reading
> Kristian comment, I discovered there's actually already many (if not all)
> Maven projects that seem migrated (?).
> http://git.apache.org/ Is this something that was done by someone during
> the night? :-).
Apache Git mirror exists for long time (mirrored to github.apache.org/apache).
That's not new (just some communication missing imho).
Those are only for read and ease use of git-svn.
Write/cannonical asf git repos are here: https://git-wip-us.apache.org/repos/asf
>
> Or maybe that repos are not correct in some way (Kristian's comment say
> some are already usable as-is)?
>
> What makes a repo correct or not to be used as-is?
>
> Looking at the repo structure from the HTTP interface, I'm under the
> impression this is a git repo created by git svn (or svn2git?), .
> My naive first guess understanding is that there already may be a batch of
> "maven git scripts" running on the infrastructure that would git-svn the
> main repo, then filter-branch this repo for a bunch of directories
> (release, enforcer, etc.).
>
> If this is so, not totally sure what would be left?
moving to https://git-wip-us.apache.org (and various stuff) move some
svn paths to read only.
fix github mirroring.
etc..
>
> Thanks.
>
> 2012/9/12 Benson Margulies 
>
>> Who is going to open the initial negotiation with INFRA?
>>
>> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
>> > Hi Folks,
>> > So the vote passed, now it's time for volunteers to use their fingers
>> :-).
>> > I have started a page [1] for ETA of migration (note the Volunteer
>> > column :-) ) and for discussion on some stuff (plugins shared)
>> >
>> >
>> > Thanks
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>>
>> --
>> Baptiste  MATHUS - http://batmat.net
>> Sauvez un arbre,
>> Mangez un castor !
>> nbsp;!
>>  
>>



-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Baptiste MATHUS]

Hi,

+1.
Though I'm volunteering to help, as I'm not Maven committer, I don't know
if I'm really allowed to help.
I could help on some projects if needed (I can see maybe enforcer & release
for example).

By the way, I'm not sure how this is supposed to work. After reading
Kristian comment, I discovered there's actually already many (if not all)
Maven projects that seem migrated (?).
http://git.apache.org/ Is this something that was done by someone during
the night? :-).

Or maybe that repos are not correct in some way (Kristian's comment say
some are already usable as-is)?

What makes a repo correct or not to be used as-is?

Looking at the repo structure from the HTTP interface, I'm under the
impression this is a git repo created by git svn (or svn2git?), .
My naive first guess understanding is that there already may be a batch of
"maven git scripts" running on the infrastructure that would git-svn the
main repo, then filter-branch this repo for a bunch of directories
(release, enforcer, etc.).

If this is so, not totally sure what would be left?

Thanks.

2012/9/12 Benson Margulies 

> Who is going to open the initial negotiation with INFRA?
>
> On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
> > Hi Folks,
> > So the vote passed, now it's time for volunteers to use their fingers
> :-).
> > I have started a page [1] for ETA of migration (note the Volunteer
> > column :-) ) and for discussion on some stuff (plugins shared)
> >
> >
> > Thanks
> > --
> > Olivier Lamy
> > Talend: http://coders.talend.com
> > http://twitter.com/olamy | http://linkedin.com/in/olamy
> > [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !
> nbsp;!
>  
>

Re: Release of Maven Indexer 5.0

[Anders Hammar]

I fully agree with you and I'm actually of the opinion that the Java
community has a responsibility to provide enough reasons for those on
older Java platforms to upgrade. But as long as we provide libraries
etc that are Java 1.4 compatible, there might not be enough reasons.
I'm sure there are lots of developers out there trying to explain to
their managers that they need to upgrade, and if they could say "we
need this to use the new cool and wicket-fast Maven Indexer release"
(maybe they need something else as well) that might be what makes the
upgrade happen.

But, we did touch on this topic before and the consensus was to leave
it on Java 5 level. I'm fine with that although it might not be along
my aggressive thinking.

/Anders

PS. Care to create a Java 7 fork of it? ;-)

On Wed, Sep 12, 2012 at 1:04 PM, Tamás Cservenák  wrote:
> Actually, my hope was to have someone here say "c'mon, not bumping to
> Java6? Are you nuts?" and then continue with, "listen, you code _today_
> something that will be hopefully used 3-4 years from today. But, you are
> _prevented_ to leave something that is already dead _today_ for 3 years
> (will be 6-7 years during hopeful use of this release), you are prevented
> to bump the source to something that _will be dead_ in months from
> _today_... it does not make sense, especially as this is a major 5.x
> release". Also, someone else could chime in with "those locked to java
> 5 and java 4 should seriously stop and think a bit". And another with "we
> [ASF] are an open, non-profit OSS forge, doing development for our own sake
> and love. so did the company [since it's not a natural person I hope]
> making you wont-fix this Java6 bump at least a golden sponsor of next
> upcoming ApacheCon?" and so on :D
>
> etc.
>
>
> Thanks,
> ~t~
>
>
>
>
> On Wed, Sep 12, 2012 at 11:34 AM, Anders Hammar  wrote:
>
>> Should MINDEXER-60 really have a fix version as it is won't fix? It
>> could trick people just browsing the list of tickets associated with
>> this relaese to think this has been introduced.
>>
>> /Anders
>>
>> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
>> wrote:
>> > Howdy,
>> >
>> > there are a notable changes in trunk of MI:
>> >
>> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>> >
>> > https://github.com/apache/maven-indexer/commits/trunk?page=1
>> >
>> >
>> > So, I'd like to spin a release of it.
>> >
>> > Any objections to this? Any last minute wish?
>> >
>> >
>> > Thanks,
>> > ~t~
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Authorative lists of projects....

[Kristian Rosenvold]

As I was trying to correlate olamy's project list with my mind and the
maven site I discovered that they *are* already spread out, and
it's only indirectly doucmented. There is room for improvement even
before we migrate ;)

Kristian


2012/9/12 Anders Hammar :
> Yes, if we start having stuff spread out in different repos there
> should be some other way that Google to find things.
>
> /Anders
>
> On Wed, Sep 12, 2012 at 12:43 PM, Kristian Rosenvold
>  wrote:
>> In the "maven projects" menu heading on maven.apache.org we expose a
>> plugins page (http://maven.apache.org/plugins/index.html) and shared
>> components(http://maven.apache.org/shared/index.html), both of which
>> summarize the latest version and the scm url.
>>
>> We have quite a few projects that are NOT on any of these lists; would
>> this be a good time to create a third list for non-plugin, non-shared
>> stuff ? (poms, maven itself etc)
>>
>> I'm thinking 3 pages that all together describe the exact status of
>> ALL our projects, maybe a 4th for deprecated stuff...?
>>
>>
>> WDYT ?
>>
>> Kristian
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Plan for git migration

[Benson Margulies]

Who is going to open the initial negotiation with INFRA?

On Wed, Sep 12, 2012 at 4:44 AM, Olivier Lamy  wrote:
> Hi Folks,
> So the vote passed, now it's time for volunteers to use their fingers :-).
> I have started a page [1] for ETA of migration (note the Volunteer
> column :-) ) and for discussion on some stuff (plugins shared)
>
>
> Thanks
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
> [1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Tamás Cservenák]

Actually, my hope was to have someone here say "c'mon, not bumping to
Java6? Are you nuts?" and then continue with, "listen, you code _today_
something that will be hopefully used 3-4 years from today. But, you are
_prevented_ to leave something that is already dead _today_ for 3 years
(will be 6-7 years during hopeful use of this release), you are prevented
to bump the source to something that _will be dead_ in months from
_today_... it does not make sense, especially as this is a major 5.x
release". Also, someone else could chime in with "those locked to java
5 and java 4 should seriously stop and think a bit". And another with "we
[ASF] are an open, non-profit OSS forge, doing development for our own sake
and love. so did the company [since it's not a natural person I hope]
making you wont-fix this Java6 bump at least a golden sponsor of next
upcoming ApacheCon?" and so on :D

etc.


Thanks,
~t~




On Wed, Sep 12, 2012 at 11:34 AM, Anders Hammar  wrote:

> Should MINDEXER-60 really have a fix version as it is won't fix? It
> could trick people just browsing the list of tickets associated with
> this relaese to think this has been introduced.
>
> /Anders
>
> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
> wrote:
> > Howdy,
> >
> > there are a notable changes in trunk of MI:
> >
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
> >
> > https://github.com/apache/maven-indexer/commits/trunk?page=1
> >
> >
> > So, I'd like to spin a release of it.
> >
> > Any objections to this? Any last minute wish?
> >
> >
> > Thanks,
> > ~t~
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Release of Maven Indexer 5.0

[Milos Kleint]

On Wed, Sep 12, 2012 at 12:53 PM, Tamás Cservenák  wrote:
> Milos,
>
> yes I think it is, since all of it is _removed_. See issue
> https://jira.codehaus.org/browse/MINDEXER-57
> and related commits.
>
> Only integration I tested is... Nexus. So, you could give it a spin in NB
> for example...

I'm right at it, however the issue reported is fairly random (and
rarely occurring) so the most likely result of my testing will be just
sanity check confirmation..

Milos



>
> Thanks,
> ~t~
>
> On Wed, Sep 12, 2012 at 12:35 PM, Milos Kleint  wrote:
>
>> hey,
>>
>> do you believe https://jira.codehaus.org/browse/MINDEXER-52 is fixed in
>> 5.0?
>>
>> Milos
>>
>> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
>> wrote:
>> > Howdy,
>> >
>> > there are a notable changes in trunk of MI:
>> >
>> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>> >
>> > https://github.com/apache/maven-indexer/commits/trunk?page=1
>> >
>> >
>> > So, I'd like to spin a release of it.
>> >
>> > Any objections to this? Any last minute wish?
>> >
>> >
>> > Thanks,
>> > ~t~
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> For additional commands, e-mail: dev-h...@maven.apache.org
>>
>>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Authorative lists of projects....

[Anders Hammar]

Yes, if we start having stuff spread out in different repos there
should be some other way that Google to find things.

/Anders

On Wed, Sep 12, 2012 at 12:43 PM, Kristian Rosenvold
 wrote:
> In the "maven projects" menu heading on maven.apache.org we expose a
> plugins page (http://maven.apache.org/plugins/index.html) and shared
> components(http://maven.apache.org/shared/index.html), both of which
> summarize the latest version and the scm url.
>
> We have quite a few projects that are NOT on any of these lists; would
> this be a good time to create a third list for non-plugin, non-shared
> stuff ? (poms, maven itself etc)
>
> I'm thinking 3 pages that all together describe the exact status of
> ALL our projects, maybe a 4th for deprecated stuff...?
>
>
> WDYT ?
>
> Kristian
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Tamás Cservenák]

Thats' good :)

But seriously, there are two related commits (one doing it, and one undoing
it). All I wanted it to simply cover those and have a history for that
change in JIRA too


Thanks,
~t~

On Wed, Sep 12, 2012 at 11:34 AM, Anders Hammar  wrote:

> Should MINDEXER-60 really have a fix version as it is won't fix? It
> could trick people just browsing the list of tickets associated with
> this relaese to think this has been introduced.
>
> /Anders
>
> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
> wrote:
> > Howdy,
> >
> > there are a notable changes in trunk of MI:
> >
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
> >
> > https://github.com/apache/maven-indexer/commits/trunk?page=1
> >
> >
> > So, I'd like to spin a release of it.
> >
> > Any objections to this? Any last minute wish?
> >
> >
> > Thanks,
> > ~t~
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Release of Maven Indexer 5.0

[Tamás Cservenák]

Milos,

yes I think it is, since all of it is _removed_. See issue
https://jira.codehaus.org/browse/MINDEXER-57
and related commits.

Only integration I tested is... Nexus. So, you could give it a spin in NB
for example...

Thanks,
~t~

On Wed, Sep 12, 2012 at 12:35 PM, Milos Kleint  wrote:

> hey,
>
> do you believe https://jira.codehaus.org/browse/MINDEXER-52 is fixed in
> 5.0?
>
> Milos
>
> On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák 
> wrote:
> > Howdy,
> >
> > there are a notable changes in trunk of MI:
> >
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
> >
> > https://github.com/apache/maven-indexer/commits/trunk?page=1
> >
> >
> > So, I'd like to spin a release of it.
> >
> > Any objections to this? Any last minute wish?
> >
> >
> > Thanks,
> > ~t~
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Authorative lists of projects....

[Kristian Rosenvold]

In the "maven projects" menu heading on maven.apache.org we expose a
plugins page (http://maven.apache.org/plugins/index.html) and shared
components(http://maven.apache.org/shared/index.html), both of which
summarize the latest version and the scm url.

We have quite a few projects that are NOT on any of these lists; would
this be a good time to create a third list for non-plugin, non-shared
stuff ? (poms, maven itself etc)

I'm thinking 3 pages that all together describe the exact status of
ALL our projects, maybe a 4th for deprecated stuff...?


WDYT ?

Kristian

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Milos Kleint]

hey,

do you believe https://jira.codehaus.org/browse/MINDEXER-52 is fixed in 5.0?

Milos

On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák  wrote:
> Howdy,
>
> there are a notable changes in trunk of MI:
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>
> https://github.com/apache/maven-indexer/commits/trunk?page=1
>
>
> So, I'd like to spin a release of it.
>
> Any objections to this? Any last minute wish?
>
>
> Thanks,
> ~t~

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Release of Maven Indexer 5.0

[Anders Hammar]

Should MINDEXER-60 really have a fix version as it is won't fix? It
could trick people just browsing the list of tickets associated with
this relaese to think this has been introduced.

/Anders

On Wed, Sep 12, 2012 at 11:27 AM, Tamás Cservenák  wrote:
> Howdy,
>
> there are a notable changes in trunk of MI:
> https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC
>
> https://github.com/apache/maven-indexer/commits/trunk?page=1
>
>
> So, I'd like to spin a release of it.
>
> Any objections to this? Any last minute wish?
>
>
> Thanks,
> ~t~

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Release of Maven Indexer 5.0

[Tamás Cservenák]

Howdy,

there are a notable changes in trunk of MI:
https://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+MINDEXER+AND+fixVersion+%3D+%225.0.0%22+AND+status+%3D+Closed+ORDER+BY+priority+DESC

https://github.com/apache/maven-indexer/commits/trunk?page=1


So, I'd like to spin a release of it.

Any objections to this? Any last minute wish?


Thanks,
~t~

Plan for git migration

[Olivier Lamy]

Hi Folks,
So the vote passed, now it's time for volunteers to use their fingers :-).
I have started a page [1] for ETA of migration (note the Volunteer
column :-) ) and for discussion on some stuff (plugins shared)


Thanks
-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
[1] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

[RESULT] [VOTE] Move Maven projects sources to git

[Olivier Lamy]

Hi,
So it looks it was an interesting vote and topic with some
nice/various views. (seems people looks more interested than voting on
release :P )

The vote details are:

+1 (binding PMC)
krosenvold
sconnolly
aheritier
benson
milos
barrie
john casey
emmanuel venisse
herve boutemy
olamy
mark struberg
pgier
wayne fay
robert scholte
Brian fox

+0.5 (binding)
Dan Kulp
Brett porter


+0 (binding)
stephane nicoll
dennis lundberg
mark struberg

+1 (non pmc but committer)
tony chemit
anders
igor

+1 (non binding)
Raffaele
Jesse
garvin
manfred
jason peyron
baptiste mathus

-1 (non binding)
Chris

So I see 15 +1 PMC binding votes (and some more community +1 votes too !)
And 4 volunteers to help on various infra tasks!

As we are 26 PMC [1], the majority is here so we can declare: vote passed.

Regarding tasks for the migration, I will start an other email with
details (etc..)

Thanks
-- 
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy

[1] http://people.apache.org/committers-by-project.html#maven-pmc

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

maven-scm pull request: Fix for SCM-694 (renamed files not supported during...

[fcamblor]

Github user fcamblor closed the pull request at:

https://github.com/apache/maven-scm/pull/3


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org