[pcable]

I am working on an application that I have added MyEclipse hibernate capabilities too. I am deploying to JBoss 4 and I have added the following to my log4j.xml JBoss configuration file:

<!– Vendor Extranet File Appender –>
<appender name=”VENDOREXTRANET_FILE” class=”org.apache.log4j.DailyRollingFileAppender”>
<param name=”File” value=”${jboss.server.log.dir}/VendorExtranet.log”/>
<param name=”Append” value=”true”/>

<layout class=”org.apache.log4j.PatternLayout”>
<param name=”ConversionPattern” value=”%d{dd MMM yyy HH:mm:ss}, %-6p %C:%M:%L %m %n”/>
</layout>
</appender>

<!– Vendor Extranet –>
<category name=”com.drhorton.ve”>
<priority value=”DEBUG”/>
<appender-ref ref=”VENDOREXTRANET_FILE”/>
</category>

When I go to startup the server, I get errors as described in the issue log found at the below website:
http://wiki.jboss.org/wiki/Wiki.jsp?page=Log4jConflictsInJBoss

If I manually take out the log4j-1.2.11.jar and commons-logging-1.0.4.jar from the deployed application, then the server starts up properly.

Is there a way to setup MyEclipse to not include certain files from the MyEclipse Library – Hibernate 3.1 Core Libraries?

Thanks for any help,
Pam

[Riyad Kalla]

Pam,
Unfortunately there isn’t a way to filter out individual files at this time but it’s an enhancement we have been looking at doing for a long time now and this is an excellent use-case reason for doing it.

What you *can* do however is navigate to Window > Prefs > MyEclipse > Project Capabilities > Hibernate > Hibernate 3.1 tab, select the Core set, and remove the log4j library directly from there. So it will no longer be included in the library and thusly not deployed with it.

[pcable]

Ok, after I removed them from the Hibernate core set I got compilation errors. So, then I used a variable that points to the library listing for JBoss and extended it to bring in the log4j and commons-logging jars for compile time. However, something is still putting it in the deployed ear.

Do you have any ideas?

[Riyad Kalla]

We will have a feature in 5.5 that will work around this issue. In the mean time if you can place the JAR back and work around it manually (sorry about that) hopefully we will have the solution deployed in 2 weeks.

[pcable]

Is the new feature that you discussed (hopefully in version 5.5) in the newest version of MyEclipse? If so, how do I access it?

[Riyad Kalla]

Pam,
Sorry about that, yes we got it in. They are customizable deployment exclusion rules for the MyEclipse libraries on a per-server basis.

You can access them from Windows > Prefs > MyEclipse > Project Capabilities, then selecting the caps you want to manage, then the libraries you want to change. From there when you expand the individual JARs, you have a lot of preferences for each JAR you can adjust, and there is a new deployment exclusion rule you can modify.

Please see the attached screenshot:

Attachments:

You must be logged in to view attached files.

[Author]

Posts