Sorry this was by a mistake. The maven build costs too long so I comment tools out as it's rarely used by developer build. later on I found there is a profile called 'impatient' which does exactly the same thing. before bring it back, I wonder if it's right to put 'tools' in developer profile? I am sure 90% developer won't use it. Why not move it to a profile only used by RPM build?
> -----Original Message----- > From: Santhosh Edukulla [mailto:santhosh.eduku...@citrix.com] > Sent: Tuesday, December 31, 2013 7:25 AM > To: dev@cloudstack.apache.org > Subject: 4.3 : Developer Profile, tools module commented > > Team, > > For branch 4,3, the below commit appears to have commented the tools > module under developer profile. Any specific reason? > > commit fb1f3f0865c254abebfa5a43f66cef116fe36165 > Author: Frank.Zhang <frank.zh...@citrix.com> > Date: Mon Oct 7 18:03:12 2013 -0700 > > Add missing Baremetal security_group_agent java part > Change security_group_agent python side in line with default security > group rules change in 4.2 > > Conflicts: > > > plugins/hypervisors/baremetal/src/com/cloud/baremetal/networkservice/Bare > MetalResourceBase.java > > diff --git a/pom.xml b/pom.xml > index 2cee084..31946d8 100644 > --- a/pom.xml > +++ b/pom.xml > @@ -747,7 +747,9 @@ > </properties> > <modules> > <module>developer</module> > + <!-- > <module>tools</module> > +--> > </modules> > </profile> > <profile> > > Thanks! > Santhosh
