History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: RHQ-1085
Type: Task Task
Status: Closed Closed
Resolution: Not An Issue
Priority: Minor Minor
Assignee: Unassigned
Reporter: John Mazzitelli
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project

decide what to do with the bluetooth plugin

Created: 07/Nov/08 05:18 PM   Updated: 12/Dec/08 09:40 PM
Component/s: Plugins
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Incorporate
 

Resolution Date: 12/Dec/08 09:37 PM


 Description  « Hide
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.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
John Mazzitelli - 07/Nov/08 05:19 PM
one other alternative is to take out the dependency and the bluetooth source dir out of the eclipse .classpath.

John Mazzitelli - 12/Dec/08 09:37 PM
bluetooth taken out of svn

svn rev 2353

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

John Mazzitelli - 12/Dec/08 09:37 PM
removed bluetooth from svn

John Mazzitelli - 12/Dec/08 09:40 PM
svn rev2354 is the rev that deleted the plugins/bluetooth directory (looks like eclipse performed two commits to do this)