This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 227958 - jboss-client.jar from JBoss AS 7.1.3 interfering with Messages Annotation Processor
Summary: jboss-client.jar from JBoss AS 7.1.3 interfering with Messages Annotation Pro...
Status: RESOLVED WORKSFORME
Alias: None
Product: apisupport
Classification: Unclassified
Component: Project (show other bugs)
Version: 7.2.1
Hardware: PC Windows 7 x64
: P3 normal (vote)
Assignee: Martin Kozeny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-26 16:27 UTC by cappicard
Modified: 2013-07-17 12:40 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Working nbm project with TopComponent and jboss-client.jar from 7.1.3.Final (6.88 MB, application/zip)
2013-05-07 11:43 UTC, Martin Kozeny 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description cappicard 2013-03-26 16:27:18 UTC 
As of JBoss 7.1.3, 

I am having to manually edit jboss-client.jar to rip out JBoss's command processor when using that jar in a wrapper module.

Its command processor will cause any NetBeans module to fail to build due to interference from JBoss's command processor.

org.jboss.logging.processor.apt.LoggingToolsProcessor is the culprit. Thus, I remove /META-INF/services/javax.annotation.processing.Processor from jboss-client.jar.
Comment 1 cappicard 2013-03-26 16:36:14 UTC 
The failure comes when adding said jar or wrapper to any module with annotated TopComponents.
Comment 2 cappicard 2013-03-26 16:44:32 UTC 
Looks like Redhat/Apache fixed JBoss' command processor with their latest patch to 7.1.3.

So, more correctly, we need a way of preventing specific command processors from running when building NB modules.

It seems that -proc:none is not the proper way to to go. 

Listing each and every NB command processor in the build script is not the best way either as this would involve listing about 20 command processors.
Comment 3 Petr Hejl 2013-03-26 21:41:24 UTC 
I guess by command processor you mean annotation processor. Does not seem to be jboss plugin issue after all.
Comment 4 cappicard 2013-03-26 21:52:28 UTC 
Petr, my apologies.

Yes, I meant the annotation processor.
Comment 5 cappicard 2013-03-26 21:54:29 UTC 
You are correct. It is not the jBoss plugin, but rather how annotation processors are handled, and how conflicting processors are handled.
Comment 6 Petr Hejl 2013-03-26 22:04:32 UTC 
I'm not sure whether and how this should be handled. Reassigning to proper component.
Comment 7 Martin Kozeny 2013-05-07 09:03:05 UTC 
Please attach sample project whether it is possible. You can try to explicitly enumerate annotation processors you want to use during compilation by using -processor class1[,class2,class3…].
Comment 8 Martin Kozeny 2013-05-07 11:43:14 UTC 
Created attachment 134180 [details]
Working nbm project with TopComponent and jboss-client.jar from 7.1.3.Final

Product Version: NetBeans IDE Dev (Build 201304282301)
Java: 1.7.0_13; Java HotSpot(TM) 64-Bit Server VM 23.7-b01
Runtime: Java(TM) SE Runtime Environment 1.7.0_13-b20
System: Linux version 3.5.0-28-generic running on amd64; UTF-8; en_US (nb)


I've downloaded and built JBoss 7.1.3.Final and using its jboss-client.jar (with javax.annotation.processing.Processor located in META-INF/services) in nbm project with TopComponent and building works fine for me. See attachment.