The problem is javassit is not installed into deps folder by maven. I fixed this issue by adding a dependence on it instead of add javassit jar file in deps rpm.
Sent from my iPhone On Oct 9, 2012, at 11:22 PM, "Rohit Yadav" <[email protected]> wrote: > > On 10-Oct-2012, at 8:25 AM, Edison Su <[email protected]> wrote: > >> Hi Rohit, >> I don't understand how the javassist*.jar been added into our build >> system. If I run "mvn -P deps" on a clean system, there is no javassist*.jar >> downloaded into deps folder. > > This is what happens when you touch the build system without getting review > or let people know about it. > > @Chip, please see the following commits that were made, these dependencies > are added to the build packages and not the source code. > > The following commits added deps in the awsapi rpm package: > 543305367962cf1a57c10d0f1e6c16011bbca92c > 2f9941d85f8277f1fb2cbf958e41afb3fcd6960b > > I just fixed those with CLOUDSTACK-292. > > The following commit removed javassist in awsapi/pom: > 850433240401cd318f1d8d8b0fa2032a60d52c1f > > Regards. > >> >>> -----Original Message----- >>> From: Chip Childers [mailto:[email protected]] >>> Sent: Tuesday, October 09, 2012 7:30 PM >>> To: [email protected] >>> Subject: Please, please, please... please don't add dependencies >>> without the appropriate legal documentation. >>> >>> Hi all, >>> >>> As the subject line says, we all need to be VERY aware of adding a >>> dependency to the project. When we add one, we need to (1) discuss it >>> on the list, (2) if agreed ensure that it's compatible, (3) update the >>> legal documentation for the project. >>> >>> We found issues today, that would have been avoided if everyone >>> followed those steps correctly. >>> >>> Thanks. >>> >>> -chip >
