Hi Bryan,
1. I just checked out the 3.0.0 tag on a clean machine with the
following enviroment:
mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0
Java home: /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.18-128.1.10.el5xen" arch: "amd64" Family:
"unix"
Note that I have*
export MAVEN_OPTS='-Xmx512m'
*to give maven some more memory.
and ran a successful build:
mvn clean install
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [clean, install]
[INFO] --------------------------------
.........
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] jUDDI_v3 Parent ....................................... SUCCESS
[4:36.199s]
[INFO] UDDI_v3 WS Stubs and Schema Bindings Generated from WSDL SUCCESS
[4:10.919s]
[INFO] UDDI Technical Compatibility Kit (TCK) Base ........... SUCCESS
[14.392s]
[INFO] jUDDI Client side Code ................................ SUCCESS
[33.746s]
[INFO] jUDDI Core ............................................ SUCCESS
[3:35.382s]
[INFO] jUDDI Axis2 Deployment ................................ SUCCESS
[3:09.165s]
[INFO] jUDDI CXF Deployment .................................. SUCCESS
[1:47.150s]
[INFO] jUDDI Service Registration Examples ................... SUCCESS
[4.148s]
[INFO] jUDDI Tomcat Packaging ................................ SUCCESS
[31.068s]
[INFO] UDDI TCK Tests ........................................ SUCCESS
[4:25.793s]
[INFO] jUDDI Document Packaging .............................. SUCCESS
[5.758s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 23 minutes 14 seconds
[INFO] Finished at: Tue Nov 10 14:28:36 EST 2009
[INFO] Final Memory: 110M/265M
[INFO]
------------------------------------------------------------------------
[WARNING] [talledLocalContainer] Java Result: 143
[WARNING] [talledLocalContainer] Java Result: 143
The build takes a while b/c it's downloading all the maven build
artifacts (Subsequent builds take 3 min).
So I'm starting to think there is something wrong in your environment.
2. That said, the fix is in the juddi-core.jar, and I think you already
have that building? Just take that jar and replace the one in
your distribution.
--Kurt
Bryan Pendleton wrote:
Hi Kurt,
Editing the word SNAPSHOT out of juddi-tomcat/bootstrap/pom.xml didn't
seem to help; I still get the error about being unable to access
org.apache.juddi:juddi-parent:pom:3.0.0.SNAPSHOT during the Tomcat
packaging.
I also found the word SNAPSHOT in
juddi-console/uddi-portlets/uddi-portlets.launch,
but editing it out of that file didn't help, either.
However, I *was* able to build just the juddi-core POM using Maven, so
for
the purposes of verifying that I can use the fix for JUDDI-306, I
should be
able to make progress that way.
But it would be really nice to figure out if I just have some sort of
configuration
error in my environment, or if it's just not possible to build the 3.0
tag
from subversion.
I suppose the next thing I should try is to checkout the trunk, and
see if I
can successfully build it using my Maven installation?
Are there Maven "debug" settings that I can configure which would give me
more information about where the SNAPSHOT reference is coming from?
thanks,
bryan
Kurt T Stam wrote:
Bryan Pendleton wrote:
Can you do a find to see if any pom is referencing 3.0.0.SNAPSHOT?
It really should be referencing 3.0.0.
Hi Kurt,
The SNAPSHOT reference appears to be in juddi-tomcat/bootstrap/pom.xml
(http://svn.apache.org/viewvc/webservices/juddi/tags/juddi-3.0.0/juddi-tomcat/bootstrap/pom.xml?view=markup)
Should I try editing out the word "SNAPSHOT" from this file and see
if that resolves my build problem?
thanks,
bryan
Yes please, that target is only used to get tomcat-6 into our repos,
so that we can use it for our builds.
There is not need to run this target itself.
