nope, I upgraded to maven-b8 but the same problem happen again and again. I'll hopefully keep the list updated with my progress.
David Worms On Wednesday, October 16, 2002, at 03:53 PM, Scott Eade wrote: > I haven't tried plexus yet, so these are only suggestions: > > 1. Upgrade to maven-b7 > 2. Try running maven twice. The problem you describe sounds a little > like > the problem fulcrum has where some of the steps are in the wrong order > to > satisfy the dependency requirements - a second execution may be able to > build on the result of the first execution. > > HTH, > > Scott > -- > Scott Eade > Backstage Technologies Pty. Ltd. > http://www.backstagetech.com.au > > >> From: David Worms <[EMAIL PROTECTED]> >> Reply-To: "Turbine Users List" <[EMAIL PROTECTED]> >> Date: Wed, 16 Oct 2002 14:45:42 -0700 >> To: "Turbine Users List" <[EMAIL PROTECTED]> >> Subject: build Plexus with maven >> >> >> I kept trying to build plexus for the last two weeks, but the same >> compilation problem happen. On turbine dev today, Jason say Plexus is >> fully functional", so I tried again.. >> OK, here is what happen, I can't compile the scheduler component. Here >> is the first error message i get: >> >> [ERROR] /Users/wdavidw/www/temp/plexus/component-builds/quartz-jobs/ >> src/java/org/apache/plexus/job/JobSendMessages.java:74: cannot resolve >> symbol >> [ERROR] symbol : class Scheduler >> [ERROR] location: package scheduler >> [ERROR] import org.apache.plexus.scheduler.Scheduler; >> >> Looking at "plexus/component-builds/scheduler/maven.xml", there is a >> "preGoal" tag targeting >> "plexus/component-builds/quartz-jobs/maven.xml". From my >> understanding, >> this means that maven is trying to compile quarts-jobs before the >> scheduler, but in order to compile quarts-jobs, the scheduler is >> required to be compiled. For example, in my stack trace above, the >> class "JobSendMessages" import the class "Scheduler" which is actually >> compiled just after. >> >> Does anyone build plexus successfully? >> What am I missing, the maven install should be straightforward. >> I use maven v. 1.0-b5-dev. >> >> Thanks in advance, >> >> David Worms >> >> On Wednesday, October 16, 2002, at 09:02 AM, Chris K Chew wrote: >> >>> 1) You will access the template using commas instead of slashes: >>> >>> http://localhost/servlet/template/xyz,abc.vm >>> >>> NOTE: When calling link.setPage() you use commas, but use slashes >>> (/) >>> when >>> calling data.setXXXTemplate(). >>> >>> 2) In the Velocity Site howto in the Turbine-2 site, there is a >>> section "How >>> Templates Are Found". Use this search process to easily handle >>> security -- >>> Put a Default screen in each sub-package. The Default screen in the >>> auth >>> package should require security, the Default screen in the unauth >>> package >>> should not. You can read the source code for the SecureScreen to see >>> a good >>> example of how to determine if the user is valid >>> (http://jakarta.apache.org/turbine/turbine-2/xref/index.html). >>> >>> There is a lot of info in the above paragraph that I gained from >>> having made >>> mistakes on previous turbine apps. Let me know if you have any >>> specific >>> questions about it. >>> >>> Chris >>> >>>> On Tue, 15 Oct 2002, Akshay Kapur wrote: >>> >>>> I have 2 questions. Will really appreciate your suggestions - >>>> >>>> 1) >>>> I have created abc.vm under templates/screens/xyz >>>> and on accessing the URL >>>> http://localhost/servlet/template/xyz/abc.vm >>>> get routed to the default error.vm. What am I doing wrong? >>>> >>>> >>>> 2) >>>> I would like to create 2 directories under modules/screens ... >>>> modules/screens/auth >>>> modules/screens/unauth >>>> ... such that the auth directory is configured to be authenticated >>>> in >>>> web.xml and unauth is un-authenticated. Is this possible and how >>>> should I >>>> configure this? >>>> >>>> Regards >>>> Akshay >>>> >>>> >>>> -- >>>> To unsubscribe, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>>> For additional commands, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>>> >>>> >>> >>> >>> -- >>> To unsubscribe, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>> For additional commands, e-mail: >>> <mailto:[EMAIL PROTECTED]> >>> >> >> >> -- >> To unsubscribe, e-mail: >> <mailto:[EMAIL PROTECTED]> >> For additional commands, e-mail: >> <mailto:[EMAIL PROTECTED]> >> > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
