2012/3/2 Eric Barboni <eric.barb...@irit.fr>:
> At least I have artifact after resetup everything at my home with no proxies 
> and thinks like that (without my 1.4M2 corporate archiva (I want to keep it 
> to test some issue not related to webappjs))
>
> I will try to look at browse repository navigation this week end, if not 
> already done :p (not net available friday and monday). (Will give all 
> feedback I can)
I have a look at your patch and take some points update your local wc :-)
>
>
>
>
> ####
> Idea (en vrac):D
>  - Have a nice warning if  no js enabled
>    >  minimal functionnality or
>    > get out flintstone and install a modern browser :D
>  - svg or vectorial image asap to have non blur archiva logo and apache 
> feather :D.
>  - make maven / continuum looking the same.  :D
it's an other story :-)
>  - menuitem should have rounded border like other link
like tab/pills ?
>  - login ok button valid for ever
??
>
>
>
> ## issue
>  - cache
>    sometime   browse search at bottom
>    sometime  login register disappears.
IE ?
>
> ## administration issue admin/admin*** not working
???
>
> After some investigation I think I'am missing lots of new features because I 
> am not able to login .
>
> It seems that auto-admin-creation.properties was not taken into account.
yup I see for that. I can add it again
> the only exception is java.lang.ClassNotFoundException: 
> org.jvnet.animal_sniffer.IgnoreJRERequirement

look spring-asm in 3.1.x is doing more check for this animal sniffer annotation
>
> Too long I know :p
>
> Will help now
>
> Eric
>
>
>
>> something you can do to have more results in the search: go to remote
>> repositories mngt screen and schedule a remote index download. (can
>> take long :-) )
>>
>> 2012/3/1 Olivier Lamy <ol...@apache.org>:
>> > Use your local archiva as a mirror of central :-).
>> > Start archiva.
>> >
>> > In ~/.m2/settings.xml
>> >  <mirrors>
>> >    <mirror>
>> >      <name>archiva</name>
>> >      <mirrorOf>central</mirrorOf>
>> >      <id>archiva-mirror</id>
>> >      <url>http://localhost:9091/archiva/repository/internal/</url>
>> >    </mirror>
>> >  </mirrors>
>> >
>> > and build a project using an empty repo: add -Dmaven.repo.local=path
>> > to an empty repo
>> >
>> > this will populate your archiva instance.
>> >
>> > 2012/3/1 Eric Barboni <barb...@irit.fr>:
>> >> Just a question how to have some artifact inside  the new UI to test?
>> >>
>> >> -----Message d'origine-----
>> >> De : Olivier Lamy [mailto:ol...@apache.org]
>> >> Envoyé : jeudi 1 mars 2012 12:47
>> >> À : dev@archiva.apache.org
>> >> Objet : Re: Random unit test fail during build
>> >>
>> >> 2012/3/1 Eric Barboni <barb...@irit.fr>:
>> >>> Yep not so much failure.
>> >> Cool :-)
>> >> I have implemented some filtering on search. Have a look :-) Don't miss 
>> >> -U I
>> >> have changed few things in redback too.
>> >>
>> >>>
>> >>> I move from jdk7.0 to jdk7.3 but they are still random test failure.
>> >>>
>> >>> Is Jenkins able to build only one artifact for example
>> >>> archiva-scheduler-repository (which fail random) and do a lots of
>> >>> clean build to see if at least on fail :p ?
>> >>> Something like checkout + 100 * mvn clean install
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> -----Message d'origine-----
>> >>> De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mercredi 29
>> >>> février 2012 18:26 À : dev@archiva.apache.org Objet : Re: Random unit
>> >>> test fail during build
>> >>>
>> >>> 2012/2/29 Eric Barboni <barb...@irit.fr>:
>> >>>> Well I think I found one more difficult to investigate in
>> >>>> ArchivaRepositoryScanningTaskExecutor :p.
>> >>>> I will take a look.
>> >>> Weird you have so much unit failures.
>> >>>>
>> >>>> Is there a web site where "current svn trunk"  reports (surefire,...)
>> >>>> are generated ?
>> >>> nope :-)
>> >>> You have Jenkins which execute builds on various os/jdk here:
>> >>> https://builds.apache.org/view/A-F/view/Archiva/ and not so much 
>> >>> failures.
>> >>>>
>> >>>>
>> >>>> -----Message d'origine-----
>> >>>> De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mercredi 29
>> >>>> février 2012 16:17 À : dev@archiva.apache.org Objet : Re: Random unit
>> >>>> test fail during build
>> >>>>
>> >>>> 2012/2/29 Eric Barboni <barb...@irit.fr>:
>> >>>>> Sorry for the too local patch but was not capable of doing that for
>> >>>>> unknown reason. Unclear what the top repo is.
>> >>>>> Seems to work in all/archiva will do that for next one.
>> >>>>>
>> >>>>> As I will have other  test failing cause ordering I want to know if
>> >>>>> issue
>> >>>>> https://jira.codehaus.org/browse/MRM-1609 can be reopen a rename as
>> >>>>> something more generic to store the "faulty" tests ?
>> >>>>
>> >>>> reopened.
>> >>>>
>> >>>>> I can open another issue otherwise.
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> -----Message d'origine-----
>> >>>>> De : Eric Barboni [mailto:barb...@irit.fr] Envoyé : mercredi 29
>> >>>>> février 2012 12:11 À : dev@archiva.apache.org Objet : RE: Random
>> >>>>> unit test fail during build
>> >>>>>
>> >>>>> For the one of the test see issue
>> >>>>> https://jira.codehaus.org/browse/MRM-1609
>> >>>>>
>> >>>>> -----Message d'origine-----
>> >>>>> De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mardi 28
>> >>>>> février
>> >>>>> 2012
>> >>>>> 19:23 À : dev@archiva.apache.org Objet : Re: Random unit test fail
>> >>>>> during build
>> >>>>>
>> >>>>> 2012/2/28 Eric Barboni <barb...@irit.fr>:
>> >>>>>> I have limited knowledge of surefire so not sure if I am right
>> >>>>>> Seems to me that runOrder=alphabetical is only for class ordering
>> >>>>>> and not for method ordering.
>> >>>>>> org.apache.maven.surefire.util.DefaultRunOrderCalcultator.java in
>> >>>>>> surefire-api
>> >>>>> correct !
>> >>>>> So I'm puzzled with your issue. :-(
>> >>>>>>
>> >>>>>> I try to run new UI with modifying template to see if it works even
>> >>>>>> with test unit not working.
>> >>>>> Yup no problem you can still run the webapp
>> >>>>>
>> >>>>>> Seems I can try to propose the patch for browser part (in a close
>> >>>> future).
>> >>>>>> (will write an enhancement issue to keep trace)
>> >>>>>
>> >>>>> Good !!! and Thanks !
>> >>>>>
>> >>>>>>
>> >>>>>
>> >>>>>> Eric
>> >>>>>>
>> >>>>>>
>> >>>>>> -----Message d'origine-----
>> >>>>>> De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : mardi 28
>> >>>>>> février
>> >>>>>> 2012 15:00 À : dev@archiva.apache.org Objet : Re: Random unit test
>> >>>>>> fail during build
>> >>>>>>
>> >>>>>> 2012/2/28 Eric Barboni <barb...@irit.fr>:
>> >>>>>>> I log some info during test on Archiva Base :: Repository
>> >>>>>>> Interface Layer
>> >>>>>>>
>> >>>>>>> It seems that the two following tests are executed in random order.
>> >>>>>>>
>> >>>>>>> public void testGatherSnapshotVersionsA() public void
>> >>>>>>> testGatherSnapshotVersionsAWithProxies()
>> >>>>>>>
>> >>>>>>> If testGatherSnapshotVersionsA before
>> >>>>>>> testGatherSnapshotVersionsAWithProxies
>> >>>>>>> Test run OK
>> >>>>>>> But testGatherSnapshotVersionsAWithProxies before
>> >>>>>>> testGatherSnapshotVersionsA leads to
>> >>>>>>> 1.0-alpha-11-20070315.033030-10 present on the test repository and
>> >>> messing the test.
>> >>>>>> weird as surefire is configured to runOrder=alphabetical
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> -- On the UI (Long and not easy to explain only by text) Cannot
>> >>>>>>> yet help in coding. Not fluent in the framework yet.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>>>I like the idea about separate browsing vs search with query
>> >>>>>>>>>parameters
>> >>>>>>> (I'm currently working on the search I hope to have finish this
>> >>>>>>> week)
>> >>>>>>>
>> >>>>>>>>>BTW the autocomplete/filtering on browsing looks to be a nice
>> >>>>>>>>>idea
>> >>>>>>> (something like http://www.screencast.com/t/01FIwaVTr ? ) (I have
>> >>>>>>> just committed that) Looks cool
>> >>>>>>>
>> >>>>>>> Some other idea to have in the new UI
>> >>>>>>>
>> >>>>>>> --> browser with more complete list (list of full path group +
>> >>>>>>> --> artifact +
>> >>>>>>> version) with filtering according to current search quick search.
>> >>>>>>> With nice color cycle to make reading reading easy.
>> >>>>>>>  --> possibility remove in browser (according to user permission,
>> >>>>>>> and maybe
>> >>>>>>> upload) less error in filling the delete or upload form. (because
>> >>>>>>> input can be pre filled)
>> >>>>>>
>> >>>>>> yup agree on the delete too :-) (but with selection on which
>> >>>>>> repository(ies) to delete)
>> >>>>>>
>> >>>>>>>        .....                                        |  repository
>> >>>>>>> | Manage
>> >>>>>>>
>> >>>>>>>  / ant / ant / 1.6.5                  | internal
>> >>>>>>> | remove
>> >>>>>>>  / ant / ant / 1.6                      | internal
>> >>>>>>> | remove
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>   --> right side view  (1/2 to 1/3 % of width of page) for details
>> >>>>>>> info with tab like is now when you got the artifact.
>> >>>>>>
>> >>>>>> patch welcome :-)
>> >>>>>>
>> >>>>>>>
>> >>>>>>> Alternative menu item center on artifact / repo / report / user /
>> >>>>>>> system vs find / manage / administration Somehow restricted menu
>> >>>>>>> should be not displayed or in different color
>> >>>>>>>
>> >>>>>>> Artifacts  (public with exception)
>> >>>>>>>  Browse
>> >>>>>>>  Search
>> >>>>>>>  Upload  (restricted)
>> >>>>>>>  Delete  (restricted)
>> >>>>>>>
>> >>>>>>> Repository (restricted)
>> >>>>>>>  Repository Group
>> >>>>>>>  Repository
>> >>>>>>>  Proxy connectors
>> >>>>>>>  Network Proxies
>> >>>>>>>  Legacy Support
>> >>>>>>>
>> >>>>>>> Reports  (public with exception)
>> >>>>>>>  Report
>> >>>>>>>  Audit Log (restricted)
>> >>>>>>>  System Status (restricted)
>> >>>>>>>
>> >>>>>>> System (restricted)
>> >>>>>>>  Customize appearance
>> >>>>>>>  Network configuration
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> //
>> >>>>>>> Users (restricted) seems to be done in top tool bar
>> >>>>>>>   Management
>> >>>>>>>   Roles
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> -----Message d'origine-----
>> >>>>>>> De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : lundi 27
>> >>>>>>> février
>> >>>>>>> 2012 22:24 À : dev@archiva.apache.org Objet : Re: Random unit test
>> >>>>>>> fail during build
>> >>>>>>>
>> >>>>>>> 2012/2/27 Eric Barboni <barb...@irit.fr>:
>> >>>>>>>> Hello,
>> >>>>>>>> Thanks for your answer
>> >>>>>>>>
>> >>>>>>>> To cite a new world famous French actor ("P...., genial, mercy")
>> >>>>>>> :-)
>> >>>>>>>> It works archiva get started on my localhost with new UI.
>> >>>>>>>>
>> >>>>>>>> The tomcat7 seems working good but not sure what is doing :p.
>> >>>>>>>> I like the permanent banner on top.
>> >>>>>>>> My 2 cents on current "Find menu item" in UI Work in Progress :
>> >>>>>>>>  Is it possible to merge search and browse page? If now using
>> >>>>>>>> javascript it may be cool to have a dynamic filtering allowing
>> >>>>>>>> incomplete
>> >>>>>>> search.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>> If doing a clean / build on archiva folder I still have test
>> >>>>>>>> failure (I am working on windows 7)
>> >>>>>>>
>> >>>>>>> no luck :-)
>> >>>>>>>
>> >>>>>>>>>> with - Dsurefire.useFile=false and "clean and build" on archiva
>> >>>>>>>>>> folder
>> >>>>>>>>
>> >>>>>>>> Then Archiva Base :: Repository Interface Layer ........ FAILURE
>> >>>>>>>> [12.329s]
>> >>>>>>>>
>> >>>>>>>> testGatherSnapshotVersionsA(org.apache.archiva.repository.metadata.
>> >>>>>>>> M
>> >>>>>>>> e
>> >>>>>>>> t
>> >>>>>>>> adataT
>> >>>>>>>> oolsTest)  Time elapsed: 0.022 sec  <<< FAILURE!
>> >>>>>>>> java.lang.AssertionError: Assert Snapshot Versions: length/size
>> >>>>>>>> expected:<8> but was:<9>
>> >>>>>>>>        at org.junit.Assert.fail(Assert.java:91)
>> >>>>>>>>        at org.junit.Assert.failNotEquals(Assert.java:645)
>> >>>>>>>>        at org.junit.Assert.assertEquals(Assert.java:126)
>> >>>>>>>>        at org.junit.Assert.assertEquals(Assert.java:470)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.archiva.repository.metadata.MetadataToolsTest.assertSn
>> >>>>>>>> a
>> >>>>>>>> p
>> >>>>>>>> s
>> >>>>>>>> h
>> >>>>>>>> o
>> >>>>>>>> tVersi
>> >>>>>>>> ons(MetadataToolsTest.java:372)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.archiva.repository.metadata.MetadataToolsTest.testGath
>> >>>>>>>> e
>> >>>>>>>> r
>> >>>>>>>> S
>> >>>>>>>> n
>> >>>>>>>> a
>> >>>>>>>> pshotV
>> >>>>>>>> ersionsA(MetadataToolsTest.java:76)
>> >>>>>>>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >>>>>>>> Method)
>> >>>>>>>>        at
>> >>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >>>>>>>> j
>> >>>>>>>> ava:57
>> >>>>>>>> )
>> >>>>>>>>        at
>> >>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA
>> >>>>>>>> c
>> >>>>>>>> c
>> >>>>>>>> e
>> >>>>>>>> s
>> >>>>>>>> s
>> >>>>>>>> orImpl
>> >>>>>>>> .java:43)
>> >>>>>>>>        at java.lang.reflect.Method.invoke(Method.java:601)
>> >>>>>>>>        at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >> org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.
>> >>>>>>>> java:44)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.internal.runners.model.ReflectiveCallable.run(Reflectiv
>> >>>>>>>> e
>> >>>>>>>> C
>> >>>>>>>> a
>> >>>>>>>> l
>> >>>>>>>> l
>> >>>>>>>> able.j
>> >>>>>>>> ava:15)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.model.FrameworkMethod.invokeExplosively(Framewo
>> >>>>>>>> r
>> >>>>>>>> k
>> >>>>>>>> M
>> >>>>>>>> e
>> >>>>>>>> t
>> >>>>>>>> hod.ja
>> >>>>>>>> va:41)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.internal.runners.statements.InvokeMethod.evaluate(Invok
>> >>>>>>>> e
>> >>>>>>>> M
>> >>>>>>>> e
>> >>>>>>>> t
>> >>>>>>>> h
>> >>>>>>>> od.jav
>> >>>>>>>> a:20)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.statements.RunBeforeTestM
>> >>>>>>>> e
>> >>>>>>>> t
>> >>>>>>>> h
>> >>>>>>>> o
>> >>>>>>>> d
>> >>>>>>>> Callba
>> >>>>>>>> cks.evaluate(RunBeforeTestMethodCallbacks.java:74)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.statements.RunAfterTestMe
>> >>>>>>>> t
>> >>>>>>>> h
>> >>>>>>>> o
>> >>>>>>>> d
>> >>>>>>>> C
>> >>>>>>>> allbac
>> >>>>>>>> ks.evaluate(RunAfterTestMethodCallbacks.java:83)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.rules.TestWatchman$1.evaluate(TestWatchman.java:48)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.statements.SpringRepeat.e
>> >>>>>>>> v
>> >>>>>>>> a
>> >>>>>>>> l
>> >>>>>>>> u
>> >>>>>>>> a
>> >>>>>>>> te(Spr
>> >>>>>>>> ingRepeat.java:72)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.r
>> >>>>>>>> u
>> >>>>>>>> n
>> >>>>>>>> C
>> >>>>>>>> h
>> >>>>>>>> i
>> >>>>>>>> ld(Spr
>> >>>>>>>> ingJUnit4ClassRunner.java:231)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4Clas
>> >>>>>>>> s
>> >>>>>>>> R
>> >>>>>>>> u
>> >>>>>>>> n
>> >>>>>>>> n
>> >>>>>>>> er.jav
>> >>>>>>>> a:49)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
>
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.statements.RunBeforeTestC
>> >>>>>>>> l
>> >>>>>>>> a
>> >>>>>>>> s
>> >>>>>>>> s
>> >>>>>>>> C
>> >>>>>>>> allbac
>> >>>>>>>> ks.evaluate(RunBeforeTestClassCallbacks.java:61)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.statements.RunAfterTestCl
>> >>>>>>>> a
>> >>>>>>>> s
>> >>>>>>>> s
>> >>>>>>>> C
>> >>>>>>>> a
>> >>>>>>>> llback
>> >>>>>>>> s.evaluate(RunAfterTestClassCallbacks.java:71)
>> >>>>>>>>        at
>> >>>>>>>> org.junit.runners.ParentRunner.run(ParentRunner.java:236)
>> >>>>>>>>        at
>> >>>>>>>> org.springframework.test.context.junit4.SpringJUnit4ClassRunner.r
>> >>>>>>>> u
>> >>>>>>>> n
>> >>>>>>>> (
>> >>>>>>>> S
>> >>>>>>>> p
>> >>>>>>>> ringJU
>> >>>>>>>> nit4ClassRunner.java:174)
>> >>>>>>>>        at
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>
>> >>>
>> >> org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:
>> >>>>>>>> 236)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JU
>> >>>>>>>> n
>> >>>>>>>> i
>> >>>>>>>> t
>> >>>>>>>> 4
>> >>>>>>>> P
>> >>>>>>>> rovide
>> >>>>>>>> r.java:134)
>> >>>>>>>>        at
>> >>>>>>>>
>> >> org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.
>> >>>>>>>> java:1
>> >>>>>>>> 13)
>> >>>>>>>>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
>> >>>>>>>> Method)
>> >>>>>>>>        at
>> >>>>>>>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
>> >>>>>>>> j
>> >>>>>>>> ava:57
>> >>>>>>>> )
>> >>>>>>>>        at
>> >>>>>>>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodA
>> >>>>>>>> c
>> >>>>>>>> c
>> >>>>>>>> e
>> >>>>>>>> s
>> >>>>>>>> s
>> >>>>>>>> orImpl
>> >>>>>>>> .java:43)
>> >>>>>>>>        at java.lang.reflect.Method.invoke(Method.java:601)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithAr
>> >>>>>>>> r
>> >>>>>>>> a
>> >>>>>>>> y
>> >>>>>>>> (
>> >>>>>>>> R
>> >>>>>>>> eflect
>> >>>>>>>> ionUtils.java:189)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.in
>> >>>>>>>> v
>> >>>>>>>> o
>> >>>>>>>> k
>> >>>>>>>> e
>> >>>>>>>> (
>> >>>>>>>> Provid
>> >>>>>>>> erFactory.java:165)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(P
>> >>>>>>>> r
>> >>>>>>>> o
>> >>>>>>>> v
>> >>>>>>>> i
>> >>>>>>>> d
>> >>>>>>>> erFact
>> >>>>>>>> ory.java:85)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(
>> >>>>>>>> F
>> >>>>>>>> o
>> >>>>>>>> r
>> >>>>>>>> k
>> >>>>>>>> e
>> >>>>>>>> dBoote
>> >>>>>>>> r.java:103)
>> >>>>>>>>        at
>> >>>>>>>> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:
>> >>>>>>>> 7
>> >>>>>>>> 4)
>> >>>>>>>>
>> >>>>>>>> -----Message d'origine-----
>> >>>>>>>> De : Olivier Lamy [mailto:ol...@apache.org] Envoyé : lundi 27
>> >>>>>>>> février
>> >>>>>>>> 2012 18:08 À : dev@archiva.apache.org Objet : Re: Random unit
>> >>>>>>>> test fail during build
>> >>>>>>>>
>> >>>>>>>> Hello,
>> >>>>>>>>
>> >>>>>>>> 2012/2/27 Eric Barboni <barb...@irit.fr>:
>> >>>>>>>>> Hi archiva dev team,
>> >>>>>>>>>
>> >>>>>>>>>  I tried to build archiva to see how the new UI looks and also
>> >>>>>>>>> be able to give better feedback on an issue I have with metadata
>> >>>>>>>>> (already
>> >>>>>>>> reported).
>> >>>>>>>>>
>> >>>>>>>>> I follow the steps here
>> >>>>>>>>> http://archiva.apache.org/developers/building.html
>> >>>>>>>>> step 1 and 2 works fine.
>> >>>>>>>> Oups my bad is not up2date :-) (I will fix that) Follow
>> >>>>>>>> instruction from README.txt file.
>> >>>>>>>> to run the new ui: mvn tomcat7:run -pl :archiva-webapp-js -Pjs
>> >>>>>>>> -am -Pdev then hit http://localhost:9091/archiva/index.html
>
>> >>>>>>>> (optionally force en with ?request_lang=en as other i18n are not
>> >>>>>>>> here)
>> >>>>>>>>
>> >>>>>>>> Those tests always failed ? (weird as I don't see failure on ASF
>> >>>>>> Jenkins).
>> >>>>>>>> Can you give more output with -Dsurefire.useFile=false
>> >>>>>>>>
>> >>>>>>>> Merci :-)
>> >>>>>>>> --
>> >>>>>>>> Olivier Lamy
>> >>>>>>>> Talend: http://coders.talend.com
>> >>>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> But while trying to build step 3 unit test fail in two ways [1]
>> >>>>>>>>> and [2] (output).
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> I would be happy to help archiva.  I have some hci background
>> >>>>>>>>> and web design skill (not logo or image design).
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Best Regards
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> Eric Barboni
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> [1]---
>> >>>>>>>>>
>> >>>>>>>>> In Archiva Base :: Repository Interface Layer
>> >>>>>>>>>
>> >>>>>>>>> ----------------------------------------------------------------
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> ------
>> >>>>>>>>> ---
>> >>>>>>>>>
>> >>>>>>>>> Test set:
>> >>>>>>>>> org.apache.archiva.repository.metadata.MetadataToolsTest
>> >>>>>>>>>
>> >>>>>>>>> ----------------------------------------------------------------
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> ------
>> >>>>>>>>> ---
>> >>>>>>>>>
>> >>>>>>>>> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Time elapsed:
>> >>>>>>>>> 3.076 sec <<< FAILURE!
>> >>>>>>>>>
>> >>>>>>>>> testGatherSnapshotVersionsA(org.apache.archiva.repository.metadata.
>> >>>>>>>>> M
>> >>>>>>>>> e
>> >>>>>>>>> t
>> >>>>>>>>> adataT
>> >>>>>>>>> oolsTest)  Time elapsed: 0.029 sec  <<< FAILURE!
>
>> >>>>>>>>>
>> >>>>>>>>> java.lang.AssertionError: Assert Snapshot Versions: length/size
>> >>>>>>>>> expected:<8> but was:<9>
>> >>>>>>>>>
>> >>>>>>>>> at org.junit.Assert.fail(Assert.java:91)
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>> [2]---
>> >>>>>>>>>
>> >>>>>>>>> In Archiva Base :: Policies
>> >>>>>>>>>
>> >>>>>>>>> ----------------------------------------------------------------
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> ------
>> >>>>>>>>> ---
>> >>>>>>>>>
>> >>>>>>>>> Test set: org.apache.archiva.policies.CachedFailuresPolicyTest
>> >>>>>>>>>
>> >>>>>>>>> ----------------------------------------------------------------
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> -
>> >>>>>>>>> ------
>> >>>>>>>>> ---
>> >>>>>>>>>
>> >>>>>>>>> Tests run: 3, Failures: 0, Errors: 1, Skipped: 0, Time elapsed:
>> >>>>>>>>> 0.934 sec <<< FAILURE!
>> >>>>>>>>>
>> >>>>>>>>> testPolicyYesNotInCache(org.apache.archiva.policies.CachedFailur
>> >>>>>>>>> e
>> >>>>>>>>> s
>> >>>>>>>>> P
>> >>>>>>>>> o
>> >>>>>>>>> l
>> >>>>>>>>> i
>> >>>>>>>>> cyTest
>> >>>>>>>>> )  Time elapsed: 0.005 sec  <<< ERROR!
>> >>>>>>>>>
>> >>>>>>>>> org.apache.archiva.policies.PolicyViolationException: NO to
>> >>>>>>>>> fetch, check-failures detected previous failure on url:
>> >>>>>>>>> http://a.bad.hostname.maven.org/path/to/resource.txt
>> >>>>>>>>>
>> >>>>>>>>> at
>> >>>>>>>>> org.apache.archiva.policies.CachedFailuresPolicy.applyPolicy(Cac
>> >>>>>>>>> h
>> >>>>>>>>> e
>> >>>>>>>>> d
>> >>>>>>>>> F
>> >>>>>>>>> a
>> >>>>>>>>> i
>> >>>>>>>>> luresP
>> >>>>>>>>> olicy.java:95)
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> --
>> >>>>>>> Olivier Lamy
>> >>>>>>> Talend: http://coders.talend.com
>> >>>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Olivier Lamy
>> >>>>>> Talend: http://coders.talend.com
>> >>>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>> Olivier Lamy
>> >>>>> Talend: http://coders.talend.com
>> >>>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Olivier Lamy
>> >>>> Talend: http://coders.talend.com
>> >>>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>>
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> Olivier Lamy
>> >>> Talend: http://coders.talend.com
>> >>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Olivier Lamy
>> >> Talend: http://coders.talend.com
>> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
>> >>
>> >
>> >
>> >
>> > --
>> > Olivier Lamy
>> > Talend: http://coders.talend.com
>> > http://twitter.com/olamy | http://linkedin.com/in/olamy
>>
>>
>>
>> --
>> Olivier Lamy
>> Talend: http://coders.talend.com
>> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
>
>
>



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

Reply via email to