I had this problem, solved it by making my user have read/write access to
the application directory. This on OS/X BTW.
On 5/16/06, David LeBer <dlebe..odeferous.com> wrote:
>
> On 16-May-06, at 10:13 AM, Watkins, Garry wrote:
>
> > I had to use the expanded directory of the plugin
> > org.objectstyle.wolips.templateengine_2.0.0.124 instead of the jar.
> >
> > WOLips must not be able to get the resources out of the jar.
>
> Hmm,
>
> Thanks Gary, but thats not it, that jar is already expanded into a
> directory on my machine.
>
> --
> ;david
>
> --
> David LeBer
> Codeferous Software
> 'co-defer-ous' adj. producing or containing code
> site: http://www.codeferous.com
> blog: http://david.codeferous.com
>
> >
> > Garry
> >
> >
> > On 5/16/06 10:07 AM, "David LeBer" <dlebe..odeferous.com> wrote:
> >
> >> Hey all,
> >>
> >> Anyone else seeing this?
> >>
> >> I cannot create a viable WOFramework or WOApplication using the
> >> contextual menu in the Package Explorer or from the tool bar by
> >> selecting:
> >>
> >> New -> WOFramework or New -> WOApplication.
> >>
> >> I end up with the project directories, but no Libraries are added and
> >> Eclipse doesn't see it as a Java project.
> >>
> >> Selecting New -> Project -> WOLips WO 5.1 and 5.2 -> WOFramework (or
> >> WOApplication) does work however.
> >>
> >> I just upgraded from Eclipse 3.2 M6 to 3.2 RC4 using the new wiki
> >> instructions (thanks for that Mike!).
>
>
>
>
>
>
>
>
This archive was generated by hypermail 2.0.0 : Tue May 16 2006 - 13:09:40 EDT