On 12/05/2015 07:34, Mark Struberg wrote:
I am currently migrating a much bigger app I have been working on for 4 years.
With this significant code base, I found no issues in my test appart from this
beans.xml / bean annotated mode issue.
Wow, thanks a lot Ludovic! That’s great news!
I’ve (hopefully) already fixed this bug in trunk yesterday night. Could you
please be so kind and test this as well?
A note of caution: If you debug your application with IDEA, Eclipse or the
tomcat7-maven-plugin, then you might end up having your classes NOT in
WEB-INF/classes but somewhere in target/classes. That way we cannot detect that
this is the class folder which belongs to WEB-INF/beans.xml. Thus I personally
prefer to have the beans.xml info in src/main/resources. That way it also works
if you decide to package your web classes into a jar (maven-war-plugin option
‚archiveClasses‘).
The only reason I have a WEB-INF/beans.xml is when I know that the project
_also_ needs to run on WebSphere. WAS _only_ activates CDI if you have the
marker file in WEB-INF.
ok, thanks for your highlight.
I have been using netbeans for a couple of years precisely to avoid the
(IMHO unneeded) complexities added by eclipse with maven-based problems.
I do not know if it got better in latest release, but the way you had to
specify lifecycle elements in your pom.xml and the difficulty to work
with multiple artefacts / maven reactor are a stopper for me.
In the opposite, netbeans just calls maven. I like it this way. :-) For
JSF focused dev, it is a great IDE.
I am using "stock" Tomcat 8 for the time being.
Ludovic
|
| AVANT D'IMPRIMER, PENSEZ A L'ENVIRONNEMENT.
|
