Hi Simon,
Good news: jms-binding build is now working (also) for me :-)
The problem was a failing test in the SCA Contribution Model Implementation.
This caused failing builds of all dependent modules (inclusive host-embedded
and jms-binding).
What I see from the Maven/Test-Output is that the test case has a problem if
the path to local repository folder contains whitespaces. After I removed
the whitespaces the build run through successfully. Though there were still
some other failing tests, jms-binding module could be built.
Can somebody confirm the bug? Should I create a JIRA-Entry?
I pasted the Maven/Test-Output below.
Now I'm facing the next problem: How should I proceed to be able to use
jms-binding in an application? I mean what would be the preferred way to
create the tuscany-sca package (the everything containing jar file)?
Thanks,
Philipp
Maven/Test-Output :
[INFO]
----------------------------------------------------------------------------
[INFO] Building Apache Tuscany SCA Contribution Model Implementation
[INFO] task-segment: [install]
[INFO]
----------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Compiling 19 source files to D:\Work\CodeLibrary\Java\Tuscany
Java\modules\contribution-impl\target\classes
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Compiling 10 source files to D:\Work\CodeLibrary\Java\Tuscany
Java\modules\contribution-impl\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory: D:\Work\CodeLibrary\Java\Tuscany
Java\modules\contribution-impl\target\surefire-reports
-------------------------------------------------------
T E S T S
-------------------------------------------------------
Running
org.apache.tuscany.sca.contribution.processor.URLartifactProcessorExtensionPointTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.063 sec
Running
org.apache.tuscany.sca.contribution.services.ContributionMetadataDocumentProcessorTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.234 sec
Running
org.apache.tuscany.sca.contribution.processor.FolderContributionPackageProcessorTestCase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.031 sec
<<< FAILURE!
testProcessPackageArtifacts(
org.apache.tuscany.sca.contribution.processor.FolderContributionPackageProcessorTestCase)
Time
elapsed: 0 sec <<< ERROR!
org.apache.tuscany.sca.contribution.processor.impl.InvalidFolderContributionURIException:
file:/D:/Work/CodeLibrary/Java/Tuscany Java/modules/contribution-impl/./
at
org.apache.tuscany.sca.contribution.processor.impl.FolderContributionProcessor.getArtifacts
(FolderContributionProcessor.java:117)
at
org.apache.tuscany.sca.contribution.processor.FolderContributionPackageProcessorTestCase.testProcessPackageArtifacts
(FolderContributionPackageProcessorTestCase.java:48)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at junit.framework.TestCase.runTest(TestCase.java:168)
at junit.framework.TestCase.runBare(TestCase.java:134)
at junit.framework.TestResult$1.protect(TestResult.java:110)
at junit.framework.TestResult.runProtected(TestResult.java:128)
at junit.framework.TestResult.run(TestResult.java:113)
at junit.framework.TestCase.run(TestCase.java:124)
at junit.framework.TestSuite.runTest(TestSuite.java:232)
at junit.framework.TestSuite.run(TestSuite.java:227)
at org.junit.internal.runners.OldTestClassRunner.run(
OldTestClassRunner.java:35)
at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(
JUnit4TestSet.java:62)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(
AbstractDirectoryTestSuite.java:138)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(
AbstractDirectoryTestSuite.java:125)
at org.apache.maven.surefire.Surefire.run(Surefire.java:132)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
SurefireBooter.java:299)
at org.apache.maven.surefire.booter.SurefireBooter.main(
SurefireBooter.java:837)
Caused by: java.net.URISyntaxException: Illegal character in path at index
38: file:/D:/Work/CodeLibrary/Java/Tuscany Java/modules/contribution-impl/./
at java.net.URI$Parser.fail(URI.java:2809)
at java.net.URI$Parser.checkChars(URI.java:2982)
at java.net.URI$Parser.parseHierarchical(URI.java:3066)
at java.net.URI$Parser.parse(URI.java:3014)
at java.net.URI.<init>(URI.java:578)
at java.net.URL.toURI(URL.java:918)
at
org.apache.tuscany.sca.contribution.processor.impl.FolderContributionProcessor.getArtifacts
(FolderContributionProcessor.java:107)
... 24 more
-----Ursprüngliche Nachricht-----
Von: Simon Laws [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 28. September 2007 16:04
An: [email protected]
Betreff: Re: Build and use of jms-binding
Hi Philipp
Comments in line....
Regards
Simon
On 9/28/07, Philipp Konradi <[EMAIL PROTECTED]> wrote:
>
> Hi Simon,
>
> Thank you very much your hints.
>
> The build is still failing for me.
> It seems that 1 artifact is missing for binding-jms module. Though that's
> already some progress, the day before there were 3 artifacts missing.
A step in the right direction at least :-)
My environment is:
> - Windows XP Pro SP2
> - Sun JDK 1.5.0_12
> - Maven 2.0.5 ( previously tried it with 2.0.7 but as you already
> mentioned
> this version of maven isn't supported yet. It would be really good if the
> "tuscany - get involved"-web site would mention that)
Done. Thanks for the suggestion. I've put a link into the java developer
guide on the getting involved page and added the explicit maven version
required to the java developer guide.
- My trunk is at revision 580013 (last change 11:45 Thursday 27.09.2007)
Am just updating to the very latest to make sure
The build is working for you...hmm... might it be the maven settings has to
be
> configured in some special way to make the build process work? After Maven
> installation, I've just set the settings for a proxy.
Shouldn't be. I don't have any active proxy settings. The build should be
able to get everything that it needs given the repo settings in the project
poms.
I've pasted here some maven output, maybe it will be of help
>
>
> Maven output for java/sca:
> ...
> [INFO] Apache Tuscany SCA JMS Binding Extension .............. SKIPPED
> (dependen
> cy build failed or was skipped)
> ...
> [INFO] Apache Tuscany SCA Web Services Void Args and Return Test SKIPPED
> (depen
> dency build failed or was skipped)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error for project: Apache Tuscany SCA Contribution Model
> Implementation (
> during install)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Error for project: Apache Tuscany SCA WSDL2Java Tool (during
> install)
> [INFO]
> ------------------------------------------------------------------------
> [INFO] There are test failures.
> [INFO]
> ------------------------------------------------------------------------
> [INFO] For more information, run Maven with the -e switch
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD ERRORS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 1 minute 42 seconds
> [INFO] Finished at: Thu Sep 27 16:17:49 CEST 2007
> [INFO] Final Memory: 28M/51M
> [INFO]
> ------------------------------------------------------------------------
>
>
>
> Maven output for java/sca/modules/binding-jms:
> ...
> Downloading:
>
>
http://people.apache.org/repo/m2-incubating-repository/org/apache/tuscany/sca/tuscany-host-embedded/1.1-incubating-SNAPSHOT/tuscany-host-embedded-1.1-incubating-SNAPSHOT.jar
> [WARNING] Unable to get resource '
> org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT '
> from repository apache.incubator (
> http://people.apache.org/repo/m2-incubating-repository)
> Downloading:
>
>
http://people.apache.org/repo/m2-snapshot-repository/org/apache/tuscany/sca/tuscany-host-embedded/1.1-incubating-SNAPSHOT/tuscany-host-embedded-1.1-incubating-SNAPSHOT.jar
> [WARNING] Unable to get resource '
> org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT '
> from repository apache.snapshots (
> http://people.apache.org/repo/m2-snapshot-repository)
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1)
> org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file
> -DgroupId=org.apache.tuscany.sca-DartifactId=tuscany-host-embedded \
> -Dversion=1.1-incubating-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
> Path to dependency:
> 1)
> org.apache.tuscany.sca:tuscany-binding-jms:jar:1.1-incubating-SNAPSHOT
> 2)
> org.apache.tuscany.sca:tuscany-host-embedded:jar:1.1-incubating-SNAPSHOT
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.apache.tuscany.sca:tuscany-binding-jms:jar:1.1-incubating-SNAPSHOT
>
> from the specified remote repositories:
> central ( http://repo1.maven.org/maven2),
> apache.ws.zone (http://ws.zones.apache.org/repository2),
> apache.incubator (
> http://people.apache.org/repo/m2-incubating-repository
> ),
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository)
>
>
> Thanks,
> Philipp
It's very strange that it's going off looking for prebuilt 1.1 tuscany
jars. Of course it won't find any as we haven't published any 1.1 snapshots.
These should all be created by the build when you build from the sca
directory as you have done. SO it looks like maven is getting the
dependencies confused for some reason.
If you go and build modules/host-embedded manually and then go and build
binding-jms does it solve the problem?
Another thing to try is cleaning down everything and starting again...
cd java/sca
mvn clean
remove any sca artefacts from you local repo
mvn -fae
-----Ursprüngliche Nachricht-----
> Von: Simon Laws [mailto:[EMAIL PROTECTED]
> Gesendet: Donnerstag, 27. September 2007 14:43
> An: [email protected]
> Betreff: Re: Build and use of jms-binding
>
> On 9/27/07, Philipp Konradi <[EMAIL PROTECTED]> wrote:
> >
> > Hi all,
> >
> > I'm new to Tuscany and very enthusiastic about the SCA concepts.
> > After I played a little with some samples, I would like to try out the
> jms
> > binding.
> > The problem I face now is that it's not part of the official release yet
> > (though some basic functionality is working already according to the
> > Tuscany
> > web site), so one has to build the module from the repository on his
> own.
> > I tried it on several trunk revisions but the build never succeed (some
> > artifacts where missing etc.).
> >
> > Has somebody done it before? Any hints on some stable
> revision/branch/tag
> > of
> > the source code, so one could build and use the jms binding module?
> > I'd appreciate any help on this issue.
> >
> > Thanks,
> > Philipp Konradi
> >
>
> Hi Philipp
>
> The trunk is working for me this morning with the exception of the das
> implementation extension and the osgi itest (not sure why at the moment).
> But the binding-jms tests build and run ok.
>
> My environment is
>
> Windows XP SP2 (other test on various linux distros also)
> IBM JDK 5 (others test on sun jdk also)
> maven 2.0.5
>
> Of these the maven version is the important one as people have been having
> build problems on maven versions other than 2.0.5
>
> What I actually did was check out all of the tuscany java code form svn (
> http://svn.apache.org/repos/asf/incubator/tuscany/java/ ) to a directory I
> called java-trunk. Then,
>
> cd java-trunk/sca
> mvn -fae
>
> The -fae just makes it ignore failures that occur during the build. As I
> said I saw two failures but the jms bits worked.
>
> As you already know the JMS binding is not finished yet. If you want to
> help
> finish it you are more than welcome.
>
> Hope this helps
>
> Simon
>
