This content has been marked as final.
Show 3 replies
-
1. Re: Controlling the installation of components at deploy time
cbredesen Oct 8, 2009 4:55 PM (in response to cbredesen)I got around this by modifying the Module Assembly in Eclipse. I removed src/test/java and src/test/resources which were, by default, deployed to WEB-INF/classes during publishing. It works!
Now, the question becomes how to make an imported project begin life this way. It's a tooling concern so I'll ping those folks.
-Chris
-
2. Re: Controlling the installation of components at deploy time
gavin.king Oct 9, 2009 2:09 AM (in response to cbredesen)Hrrrm there is no good way to programmatically control the bean discovery process at this time. But I guess it is something we should schedule for a maintenance release...
-
3. Re: Controlling the installation of components at deploy time
gavin.king Oct 9, 2009 2:10 AM (in response to cbredesen)
Gavin King wrote on Oct 09, 2009 02:09:
Hrrrm there is no good way to programmatically control the bean discovery process at this time. But I guess it is something we should schedule for a maintenance release...Oh, you were talking about Seam2. I was thinking about 299.