DO NOT REPLY [Bug 39872] - validate module descriptors (module.xml)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 39872] New: - validate module descriptors (module.xml)

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 39871] - Update module descriptors

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 39871] New: - Update module descriptors

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

Re: trunk does not compile [ was: [1.4] Modules are built separately ]

Hi Jörn, Give the build a try now. A fresh checkout allowed me to build w/o errors. --Doug Jörn Nettingsmeier wrote: it looks like the trunk got broken during this change: after a fresh checkout and rebuilding the compile-build-target classes (see other thread), i get this: compile-module

trunk does not compile [ was: [1.4] Modules are built separately ]

it looks like the trunk got broken during this change: after a fresh checkout and rebuilding the compile-build-target classes (see other thread), i get this: compile-module-org.apache.lenya.modules.webdav: Created dir: /build/lenya/build/lenya/modules/org.apache.lenya.modules.webdav Compilin

Re: [1.4] Modules are built separately

Andreas Hartmann wrote: http://apache.org/lenya/module/1.0";> org.apache.lenya.modules.jackrabbit org.apache.lenya.modules 0.1-dev Jackrabbit Repository Module @lenya.version@ Jackrabbit JCR Implementation (see org.apache.lenya.modules.jcr Module) how about adding a maintaine

Re: [1.4] Modules are built separately

Andreas Hartmann wrote: To have your modules compiled, you have to add a module descriptor file: /module.xml i'm not really sure about this myself, but have you considered /config/module.xml instead? -- "Open source takes the bullshit out of software." - Charles Ferguson on Te

Re: [1.4] Modules are built separately

Andreas Hartmann wrote: Jörn Nettingsmeier wrote: Andreas Hartmann wrote: [...] http://apache.org/lenya/module/1.0";> org.apache.lenya.modules.jackrabbit org.apache.lenya.modules 0.1-dev Jackrabbit Repository Module @lenya.version@ Jackrabbit JCR Implementation (see org.apa

Re: BUILD FAILED java.lang.UnsupportedClassVersionError (Unsupported major.minor version 49.0)

Oliver Schalch wrote: On Wednesday 21 June 2006 22:59, Renaud Richardet wrote: Andreas Hartmann wrote: Renaud Richardet wrote: I had an error while trying to build Lenya trunk today: [EMAIL PROTECTED]:~/src/lenya-1.4.x-purevirgin$ ./build.sh Buildfile: build.xml BUILD FAILED java.lang.Unsupp

Re: [1.4] Modules are built separately

Jörn Nettingsmeier wrote: Andreas Hartmann wrote: [...] http://apache.org/lenya/module/1.0";> org.apache.lenya.modules.jackrabbit org.apache.lenya.modules 0.1-dev Jackrabbit Repository Module @lenya.version@ Jackrabbit JCR Implementation (see org.apache.lenya.modules.jcr Mod

Re: [1.4] Changing profiles/passwords of other users

Josias Thöny wrote: [...] Maybe I'm misunderstanding you, but the example I described doesn't really require to have access control code in the checkPreconditions() method. The usecase which allows to edit the profile of the current user just wouldn't use a userId parameter. It assumes that the

Re: [1.4] protect admin usecases

Jörn Nettingsmeier wrote: Josias Thöny wrote: Hi, Currently most admin usecases can be executed by a normal (non-admin) user, because it's possible to call admin usecases in the authoring area. You just have to enter: http://localhost:/default/authoring/index.html?lenya.usecase=admin.users

Re: svn commit: r415977 - /lenya/trunk/src/webapp/lenya/xslt/util/introspection.xsl

Jörn Nettingsmeier wrote: Michael Wechner wrote: ok, let me try to put it into a module. I guess it won't hurt even if one might consider it a core functionality. yeah, i think making something a module does not imply that it's not core functionality. ultimately, everything should be a module.

Re: [1.4] Changing profiles/passwords of other users

On Wed, 2006-06-21 at 17:21 +0200, Andreas Hartmann wrote: > Josias Thöny wrote: > > [...] > > >> Not sure but the user needs to be part of the admin group, right? > >> > >> The user is contained in the session, right? > >> > >> Then we need to check in the precondition whether the current user i

Re: [1.4] [RFO] UUID discussion

Michael Wechner wrote: >> How much time do you think is needed to implement this? > Well, I could give you an answer, but your question will lead myself > into a conflict of interests, so I won't > really answer it, but it shouldn't take very long if somebody is > actually taking the time to do it

Re: svn commit: r415977 - /lenya/trunk/src/webapp/lenya/xslt/util/introspection.xsl

Michael Wechner wrote: > ok, let me try to put it into a module. I guess it won't hurt even if > one might consider > it a core functionality. yeah, i think making something a module does not imply that it's not core functionality. ultimately, everything should be a module. that is the only way to

Re: [1.4] change password usecase

Josias Thöny wrote: > Hi, > > Jörn's patch about the "change password" usecase (see [1]) looks quite > good. > It made me think about a further improvement: since there are two > different "change password" usecases now, one for admins and one for > users, it might make sense to use a differnt us

Re: [1.4] protect admin usecases

Josias Thöny wrote: > Hi, > > Currently most admin usecases can be executed by a normal (non-admin) > user, because it's possible to call admin usecases in the authoring > area. > > You just have to enter: > http://localhost:/default/authoring/index.html?lenya.usecase=admin.users > > And you

Re: [1.4] protect admin usecases

Andreas Hartmann wrote: > Josias Thöny wrote: >> Hi, >> >> Currently most admin usecases can be executed by a normal (non-admin) >> user, because it's possible to call admin usecases in the authoring >> area. > > BTW, do we still need the admin area? > IMO it's just a collection of usecases like t

Re: [1.4] Modules are built separately

Andreas Hartmann wrote: > Hi Lenya devs, > > I updated the build process slightly, now modules are not compiled > together but separately. > > The process is as follows: > > - an Ant task generates a list of available modules > - the modules are ordered by dependency > - each module is compiled

Re: [1.4] Changing profiles/passwords of other users

Andreas Hartmann wrote: > Josias Thöny wrote: > > [...] > >>> Not sure but the user needs to be part of the admin group, right? >>> >>> The user is contained in the session, right? >>> >>> Then we need to check in the precondition whether the current user is in >>> the admin group, if not add a e

Re: [1.4] Modules are built separately

Andreas Hartmann wrote: Hi Lenya devs, I updated the build process slightly, now modules are not compiled together but separately. The process is as follows: - an Ant task generates a list of available modules - the modules are ordered by dependency BTW, this is now handled using Ant target

Re: [1.4] protect admin usecases

Jann Forrer wrote: [...] Yes, it looks like we don't need it anymore. Maybe it wasn't very appropriate anyway to have an area for the admin usecases, because an area in Lenya is rather something which contains documents, IMHO. Yes, I share this point of view. Not sure though. Where should

Re: [1.4] protect admin usecases

Andreas Hartmann wrote: Thorsten Scherler wrote: El mié, 21-06-2006 a las 16:30 +0200, Andreas Hartmann escribió: Josias Thöny wrote: On Wed, 2006-06-21 at 15:07 +0200, Andreas Hartmann wrote: Josias Thöny wrote: Hi, Currently most admin usecases can be executed by a normal (non-admin) user