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
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
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 actua
+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:
+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 s
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/repositori
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
- Orig
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 comma
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 & re
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
ava
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 re
+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 thi
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.code
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-ff
+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
>
>
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 k
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 Cs
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.
S
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
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 res
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 ma
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 i
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 proble
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, "
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] fo
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 w
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 disco
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 lot
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 sprea
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 discus
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
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
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.or
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 ve
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,
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
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+MINDEX
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 tr
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
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
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 struber
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
42 matches
Mail list logo
