Bug 534273 (RHQ-1085)

Summary: decide what to do with the bluetooth plugin
Product: [Other] RHQ Project Reporter: John Mazzitelli <mazz>
Component: PluginsAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: low    
Version: unspecifiedKeywords: Task
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
URL: http://jira.rhq-project.org/browse/RHQ-1085
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description John Mazzitelli 2008-11-07 23:18:00 UTC
Decide what to do with the bluetooth plugin - do we clean it up enough so we can put it back into the main mvn build reactor or do we delete it or do we..... what??

Right now, new Eclipse developers will not be able to follow the standard procedures to get up and running because they would "mvn install" from trunk, import the project into Eclipse and get an Eclipse build error because a dependency of the bluetooth plugin will not have been pulled down.

The dev will have to manually go to the bluetooth module and explicitly "mvn install" from there to pull down the dependency. That is annoying.

Comment 1 John Mazzitelli 2008-11-07 23:19:59 UTC
one other alternative is to take out the dependency and the bluetooth source dir out of the eclipse .classpath.

Comment 2 John Mazzitelli 2008-12-13 03:37:30 UTC
bluetooth taken out of svn

svn rev 2353

(svn rev 2355 removed the deps from the eclipse .classpath file)

Comment 3 John Mazzitelli 2008-12-13 03:37:53 UTC
removed bluetooth from svn

Comment 4 John Mazzitelli 2008-12-13 03:40:15 UTC
svn rev2354 is the rev that deleted the plugins/bluetooth directory (looks like eclipse performed two commits to do this)

Comment 5 Red Hat Bugzilla 2009-11-10 20:23:34 UTC
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1085
This bug incorporates RHQ-993
This bug incorporates RHQ-994