[aharvey]

I have a project that uses dependent projects within my webapp. When I deploy to an exploded ear, the class files are properly being merged into web-inf/classes.

When I deploy to a packaged ear, my dependent project gets built as a jar and dropped into web-inf/lib. However, the file is NOT getting a .jar extension and classloader appears to not inspect the file for my classes. My dependent project is named something like MyProject.common and thus gets dropped into the lib dir as WebProject.common w/o a .jar extension.

Is there a way I can keep the same naming convention and have some control over what the name of the .jar file turns out when deploying to a packaged ear?

Thanks

[Riyad Kalla]

You will need to rename the project OR add “.jar” to the name, the reason this behavior is happening is because we support custom named deployable files via your project name, this came about because JBoss supports SO many different kinds of module names (RAR, SAR, JAR, etc. etc.) so we decided to simply honor archived project names by keying off of the project name itself.

So either you can rename your project to MyProjectCommon or MyProject.common.jar. Sorry for the inconvenience.

[Author]

Posts