The commons-proxy snapshots will be in the repository on the build server, because it's also running in the build server.
On Wed, Mar 25, 2009 at 11:53 AM, Ryan McKinley <ryan...@gmail.com> wrote: > Hymm. I'm not sure what it could be... I did copy the inmethod-grid pom to > cuild the ki-secuity pom, but I think i got rid of any conflicts. > > What is the error the Continuum server spits out? Perhaps it has something > to do with syringe? (committed about the same time as ki-security) When I > try to build wicketstuff-core now, I get the following error: > > > [INFO] > ------------------------------------------------------------------------ > [ERROR] BUILD ERROR > [INFO] > ------------------------------------------------------------------------ > [INFO] Failed to resolve artifact. > > Missing: > ---------- > 1) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.apache.commons > -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar > -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > mvn deploy:deploy-file -DgroupId=org.apache.commons > -DartifactId=commons-proxy -Dversion=1.1-SNAPSHOT -Dpackaging=jar > -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > Path to dependency: > 1) org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT > 2) org.apache.commons:commons-proxy:jar:1.1-SNAPSHOT > > ---------- > 1 required artifact is missing. > > for artifact: > org.wicketstuff:wicket-syringe:jar:1.4-SNAPSHOT > > from the specified remote repositories: > wicket-snaps (http://wicketstuff.org/maven/repository), > central (http://repo1.maven.org/maven2) > > > > On Mar 25, 2009, at 11:21 AM, Jeremy Thomerson wrote: > >> I run Continuum on my server and just started receiving notifications two >> days ago that inmethod grid was not compiling. It showed up right after >> the >> commit of this ki security stuff. >> >> I haven't looked at it yet, hoping that someone who was working with ki >> security or inmethod would do so. >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> >> >> On Wed, Mar 25, 2009 at 5:48 AM, Martin Funk >> <mafulaf...@googlemail.com>wrote: >> >>> >>> Am 25.03.2009 um 10:17 schrieb nino martinez wael: >>> >>> The problem with wicket stuff have been cleared up a bit, the part about >>>> >>>> which projects are dead and not.. Those in wicketstuff-core are alive, >>>> and >>>> if they become incompatible with the current version of wicket they will >>>> be >>>> kicked.. >>>> >>> are they? I mean alive. >>> Locking here: >>> >>> >>> http://wicketstuff.org/teamcity/viewLog.html?buildId=3486&tab=buildResultsDiv&buildTypeId=bt35 >>> I'd say it's at least not compiling no more. >>> >>> Could someone please fix that? >>> >>> mf >>> >>> >>> >>>> >>>> 2009/3/25 Maarten Bosteels <mbosteels....@gmail.com> >>>> >>>> Hi Ryan, >>>>> >>>>> I added you to the Project Members, so feel free to commit your >>>>> examples. >>>>> Unfortunately, until now I haven't had time to work on it myself >>>>> >>>>> The idea was to let the code mature in >>>>> http://code.google.com/p/wicket-jsecurity/ >>>>> and maybe move it to wicket-stuff later on. >>>>> >>>>> Maybe we should move it to wicket-stuff already. >>>>> My main problem with wicket-stuff is/was that it's not always very >>>>> clear >>>>> which projects are still alive and maintained and which are practically >>>>> dead. And at the time, wicket-stuff had some problems with continuous >>>>> integration, IIRC. >>>>> >>>>> Les, what do you think ? >>>>> We should change the project name to wicket-ki anyway. >>>>> >>>>> regards, >>>>> Maarten >>>>> >>>>> On Wed, Mar 25, 2009 at 7:47 AM, nino martinez wael < >>>>> nino.martinez.w...@gmail.com> wrote: >>>>> >>>>> Yeah I've for one always been very pro for wicketstuff.. It's nice >>>>>> >>>>> keeping >>>>> >>>>>> things in one place.. Plus as you write if we share a somewhat similar >>>>>> structure it's potentially easier to maintain.. >>>>>> >>>>>> 2009/3/24 Ryan McKinley <ryan...@gmail.com> >>>>>> >>>>>> Hi- >>>>>>> >>>>>>> I've been looking to integrate a complex security model with wicket >>>>>>> -- >>>>>>> jsecurity seems really good. I tried messing with: >>>>>>> http://code.google.com/p/wicket-jsecurity/ >>>>>>> >>>>>>> This appears to be a starting place, but does not have any running >>>>>>> >>>>>> example. >>>>>> >>>>>>> >>>>>>> In an effort to get things running (and learn JSecurity) i took that >>>>>>> + >>>>>>> wicket-auth-roles and tried to make a functioning core + example. >>>>>>> I've >>>>>>> >>>>>> got >>>>>> >>>>>>> something running and would love to share it... >>>>>>> >>>>>>> Should I post this to the google code site? >>>>>>> >>>>>>> It makes more sense (to me) if we keep it in the wicketstuff repos -- >>>>>>> >>>>>> that >>>>>> >>>>>>> way we get the benefit of Jeremy's work to make wickettuff-core much >>>>>>> cleaner. >>>>>>> >>>>>>> Thoughts? >>>>>>> >>>>>>> Ryan >>>>>>> >>>>>>> >>>>>>> >>>>>>> --------------------------------------------------------------------- >>>>>>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>>>>>> For additional commands, e-mail: users-h...@wicket.apache.org >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org >>> For additional commands, e-mail: users-h...@wicket.apache.org >>> >>> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
