[forgotit]

Hi,
We have an ear project in ME with ejb and web modules. In the ear project, we have a bunch of files like build scripts and related junk that we need for the project. When we do a deploy using ME, it picks up everything in the ear project folder and deploys to the server. Is there any way of stopping this? It is not really a problem apart from bloating and messing up the ear but we are worried that at some point there will be some files that will actually stop the ear from working.
Just to clarify this is the structure we have:

earproject
-junkfile1
-junkfile2
-buildfile2
-META-INF
–application.xml
–MANIFEST.MF
-lib
–somejar.jar

ejbproject
-some folder structure here

weproject
-some folder structure here

Thanks!

[Riyad Kalla]

The devs got back to me about this and it seems you cannot stop these files from deploying unless they are moved into another project. The reason is that the EAP project represents the exploded form of the EAR archive, literally.

This will be addressed in the future when we introduce more flexible project constructs, sorry for the inconvenience.

[forgotit]

Cool,
Have moved these files to a seperate project. Thanks!

[Author]

Posts