archiva-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Barboni" <sk...@apache.org>
Subject RE: Improvements to search [was: Performance issues after upgrading to 2.0.1]
Date Fri, 25 Apr 2014 16:08:01 GMT
Perso I use netbeans. But as oliver just said we are IDE free :p.

Tip:
No use autoformating too fast (or configure it to comply with archiva coding style) (sic).
OS tips:

If you are using Windows:
  --the filelock tests are failing. (native issue I process locking and so one)
  
  --some issue occurs because mismatch with md5 or filesize;
  the eol were wrong for jar, war and pom file
  you need to "refresh your local repository" 
  >git rm --cached -rf .
  >git reset --hard



-----Message d'origine-----
De : Olivier Lamy [mailto:olamy@apache.org] 
Envoyé : vendredi 25 avril 2014 13:07
À : dev@archiva.apache.org
Objet : Re: Improvements to search [was: Performance issues after upgrading to 2.0.1]

On 24 April 2014 19:15, Sascha Vogt <sascha.vogt@gmail.com> wrote:
> Hi,
>
>>> Am 23.04.2014 15:18, schrieb Sascha Vogt:
>>> Now in general a few things, which I think improve the situation:
>>> 1. The max count should be changeable (at least when using advanced
>>> parameters)
>>> 2. Don't duplicate the results for each version, instead do it like 
>>> search.maven.org -> Display the latest version only and give a link 
>>> to the artifact (which has all the versions listed) and telling only 
>>> the number of other versions available
>>>
>>> How do others feel about those changes? If everyone can aggree on 
>>> them, I'll open an issue and see, if I can work on it.
>
> I created
> https://jira.codehaus.org/browse/MRM-1835
> and
> https://jira.codehaus.org/browse/MRM-1836
>
> I'm a bit tight on time, as I'm moving flats this weekend. As soon as 
> I have set myself up there I'll try to address them. If you have any 
> more suggestions or additions - just post them to the issues.
>
> By the way, if some of the more experienced devs find time, please go 
> ahead ;) These issues are by no means "reserved" to me
>
> A few general dev questions:
> 1. would it be OK to change the .gitignore to also include the typical 
> Eclipse project files (.project, .classpath and .settings/*)
done.
>
> 2. What is the easiest for you to apply patches? Are these Github 
> Pull-Requests OK? Or is there something else which is easier for you?
github is nice and easy.
>
> 3. At least under Windows I have issues getting the tests to run, any 
> tips? Will try on my Mac, if this should work better
no real idea. What sort of issues?
>
> 4. What would you recommend as IDE? Does anybody of the core devs run 
> Eclipse?

Perso I use intellij. But you are free to use the IDE you prefer. We are IDE independant :-)


>
> Greetings
> -Sascha-



--
Olivier Lamy
Ecetera: http://ecetera.com.au
http://twitter.com/olamy | http://linkedin.com/in/olamy


Mime
View raw message