On Wed, Jun 25, 2008 at 3:13 PM, Scott Kurz <[EMAIL PROTECTED]> wrote:
> Simon, > > No there is more missing. All I have in my lib in the trunk build is: > > XmlSchema-1.3.2.jar commons-logging-1.1.jar > jsr181-api-1.0-MR1.jar tuscany-sca-manifest.jar > activation-1.1.jar ecore-2.2.3.jar > jsr250-api-1.0.jar tuscany-sdo-api-r2.1-1.1-incubating.jar > activeio-core-3.0.0-incubator.jar ecore-change-2.2.3.jar > log4j-1.2.12.jar tuscany-sdo-impl-1.1-incubating.jar > apache-activemq-4.1.1.jar ecore-xmi-2.2.3.jar > logkit-1.0.1.jar tuscany-sdo-lib-1.1-incubating.jar > asm-all-3.1.jar geronimo-commonj_1.1_spec-1.0.jar > neethi-2.0.2.jar wstx-asl-3.2.1.jar > avalon-framework-4.1.3.jar jaxb-api-2.1.jar > servlet-api-2.3.jar xml-apis-1.3.03.jar > backport-util-concurrent-3.0.jar jaxb-impl-2.1.7.jar > stax-api-1.0-2.jar xsd-2.2.3.jar > cglib-nodep-2.1_3.jar jaxb2-reflection-2.1.4.jar > stax-api-1.0.1.jar > common-2.2.3.jar jaxws-api-2.1.jar > tuscany-sca-all-1.4-SNAPSHOT.jar > > > whereas there is much more in the branch build. > > Is there a special build command to issue in the trunk or some prereq I may > have failed to build?? But I"m not doing anything different.... > > Thanks, Scott > > On Wed, Jun 25, 2008 at 9:38 AM, Simon Laws <[EMAIL PROTECTED]> > wrote: > > > On Wed, Jun 25, 2008 at 2:33 PM, Scott Kurz <[EMAIL PROTECTED]> wrote: > > > > > I was wondering.. how come this zip: > > > > > > .../distribution/target/apache-tuscany-sca-1.3-SNAPSHOT.zip > > > > > > gets things like the wsdl4j jar built into its .../lib directory when I > > > build it from the branches/sca-java-1.3 directory but not from the > trunk? > > > > > > The binary download available at the website has the wsdl4j.jar in the > > > ../lib directory too... just wondering why the build-from-trunk build > > > does not. > > > > > > Is this by design? temporarily not working? > > > > > > Just curious, thanks, > > > Scott > > > > > > > I'm surprised that you don't see that when building from trunk. Is it > just > > wsdl4j.jar that is missing. > > > > Simon > > > Nope, no special commands. Just run mvn in the distribution directory. We do of course edit the distribution build in each release branch to ensure that the dependencies are correct. I'm doing this right now in 1.3. Maybe the trunk distribution build dependencies are not correct but I haven't had to make big changes yet so I'd be surprised if that were the case. Did you do a full build in trunk before running the distribution build Simon
