> > If its a bunch of changes we might need to rollback tag it with > > Rel_3_0_0_5. > > Adds one file, modifies MainDeployer, and I think it may require a change > in the web stuff - it turns out to break the web integration tests, I > haven't looked why yet. > Not required to tag then. Not sure why the web integration test should break here.
> > The question here is will it work with the standard codebase syntax. What > > is the most nested url we allow for an ejb-jar and war? sar/ear/ejb? > > I'm working on security manager permission tests and I can add tests of > > the njar url codebase usage in permissions. > > I really have no clue about these permission things. There is no > theoretical limit to how deeply nested this stuff can get. sar/ear/rar/jar > is plausible: ear/rar/jar is required by spec. If I commit this can you > investigate the security stuff? Yes. > > > > A 'native' directory under the deployment package directory makes sense > > to me. > where? I'm thinking of for instance native libs in rars. I was thinking > tmp/native. > Fine. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
