[nranly]

When I deploy my J2EE project and it is using a shared output directory, it includes all the class files within the output directory instead of just the class files the project needs. It would be nice if it would only include the class files the project needs based on its java files within the project and dependent project. Is there a way to do this with the current release?

Thanks

[Riyad Kalla]

and it is using a shared output directory

Can you explain more clearly here what you mean by shared, what else is sharing it? Do you mean you have multiple source folders?

it includes all the class files within the output directory instead of just the class files the project needs.

How would the project be able to know which classes it needed and didn’t need? I think I don’t quite understand the “shared output directory”… why are there artifacts in here that your project doesn’t need?

Is there a way to do this with the current release?

Maybe, I’m just not entirely sure what you are doing here yet.

[nranly]

The shared output directory, is basically what is says, multiply projects within the workspace are building to the same folder.

This is done by using eclipse’s linked folder ability. (Create a linked folder called bin to a folder elsewhere in the filesystem. then change the default output directory to be that folder)

The projects are also sharing a linked source folder then using inclusion/exclusion rules to filter the java code a certain project uses.

Why is this being done? I have some common classes that need to be shared by a j2ee client and a j2ee app server.

For example, package com.x.server and com.x.common is included in the j2ee server project.

And package com.x.client and package com.x.common is included in the j2ee client project.

Creating a common project(s) is not a desired solution. I have many (Eclipse RCP) plug-in projects which are using just one common class that is shared with the server. I do not want to create a seperate common project for each plug-in project for this would cause ‘pollution’ of the workspace.

With the plug-ins projects, I just specify the classes to be included on the deployed (Eclipse Plug-in) jar but I can’t do this with MyEclipse J2ee project.

[Riyad Kalla]

nranly,
Thank you for the detailed description, there is currently no way to filter out what is deployed. Although you mentioned you don’t want to create common projects, are you able to extract ALL the common code into a single common Java project that can be added to the classpath of all those projects? In that case MyEclipse would be able to deploy/not deploy that common project depending on your settings.

[nranly]

@support-rkalla wrote:

nranly,
Thank you for the detailed description, there is currently no way to filter out what is deployed. Although you mentioned you don’t want to create common projects, are you able to extract ALL the common code into a single common Java project that can be added to the classpath of all those projects? In that case MyEclipse would be able to deploy/not deploy that common project depending on your settings.

Yes. I may end up going that route for the time being or do use a generic common project through eclipse and then create custom ant scripts to create the production jars. Thanks

[Author]

Posts