Re: Packaging status

Hi,
welcome back:)


> Having a separate module is a good idea. However, we can achieve the   same
> results storing assembly descriptor in the parent module and disabling
> recursion.
> So that it would create a package from the resources in children modules.
>

ok, it makes sense.

> >
> >
> > * Precompiling jsps: this is a well known one:)
>
> Yes. The only question is whether we compile them only for 'testbed' package
> or always?
>

For the time being I'd only do it for the testbed version. I don't
know if we might end up with compatibility implications doing that always.



> I don't quite get the problem, but I'll take a look at the code. AFAIR,
> working with resources
> works very good in Maven though.

Ok.
if you do mvn war:war (or package) maven will build a war archive,
copying everything it finds under target/classes in WEB-INF/classes.
By default also src/main/webapp gets copied into the war root.

The objective is to create a war without the configuration properties file
within it. and to resort to the classpath to access them.

Right now doing assembly:assembly will re-copy the config files under
a conf/ dir, adding it to the classpath. So there are two sets of properties,
one in the war and one outside, but it happens that the external ones
are picked up first so that works:)

My doubt is: can we rely on this mechanism? or is it better to try not
to include config files in the war?

Another approach would be to read the configuration at the application level,
for example trying to find files under "ext/config" within the
classpath, and otherwise
resorting to the default ones (that would be in the war).
This is what alfresco does AFAIK.

What do you say, our maven master?
:)

ciao
F

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Atalaya-developer mailing list
Atalaya-developer@...
https://lists.sourceforge.net/lists/listinfo/atalaya-developer