-----Original Message----- From: jboss-development-bounces(a)lists.jboss.org

bounces(a)lists.jboss.org] On Behalf Of Scott M Stark Sent: Tuesday, July 25, 2006 10:26 AM To: JBoss.org development list Subject: RE: [JBoss-dev] Invalid custom license There already was a jbpm-bpel.txt in licenses and the current bpel component info was referring to it. My local copy was out of date. > -----Original Message----- > From: jboss-development-bounces(a)lists.jboss.org > [mailto:jboss-development-bounces@lists.jboss.org] On Behalf > Of Scott M Stark > Sent: Tuesday, July 25, 2006 8:13 AM > To: JBoss.org development list > Subject: [JBoss-dev] Invalid custom license > > jboss-head will not build for me due to this invalid custom > license reference by jbpm-bpel: > > <project name="jbpm-component-info"> > > <component id="jbpm-bpel" > licenseType="custom" > version="1.0.0.alpha4" > projectHome="http://jbpm.org/" > description="Powerful orchestration platform"> > > <artifact id="jbpm-bpel.jar"/> > > <import componentref="jbpm"> > <compatible version="3.0.2"/> > </import> > > <export> > <include input="jbpm-bpel.jar"/> > </export> > > </component> > > </project> > > You cannot add libraries to the repository that do not have a > corresponding txt file in the > http://repository.jboss.com/licenses/ directory. This license > type should also be named bpel-lgpl or the like as well. > > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > VP Architecture & Technology > JBoss, a division of Red Hat > xxxxxxxxxxxxxxxxxxxxxxxxxxxx > > > _______________________________________________ > jboss-development mailing list > jboss-development(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development