...@gmail.com wrote:
Hi everybody,
I have a build problem when I was trying to run dayTrader, can some one
please take a look and give me some suggestions on how to get a successful
build? Any reply will be very appreciated.
-- Forwarded message --
From: Jing Xu johnrob
The recent wink integration changes appear to have broken trunk. The
wink plugin is not built by default, but the javaee6 plugin has
dependencies on wink components. Unfortunately, I'm getting build
errors if I try to build the wink plugin:
The slf4j package reslove problem is a typical symptom in old wink snapshot.
It should have been fixed after wink project pushed the latest snapshot
to repo.
I can build plugins/wink after I clean up the wink artifacts in local
repository. will make sure everything works fine then re-enable
Hi,
Does anyone see this problem?
When build trunk from root these days, it always stops at
plugins/j2ee/geronimo-j2ee-builder module with exceptions like these:
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
(default-compile) on project
the Servicemix bundlized 3.7.GA version. The build failure was a
ClassNotFoundException attempting to load one of the javassist utility
classes that is not included in the 3.7.GA version. I did a quick experiment
and created a 3.12.0.GA version of the servicemix bundle, and the build
problem went
was a ClassNotFoundException attempting to load one of the
javassist utility classes that is not included in the 3.7.GA version. I
did a quick experiment and created a 3.12.0.GA version of the servicemix
bundle, and the build problem went away.
Unfortunately, the servicemix project does not have
I met a similar issue when built with ibm jdk sr8. Seems there is a memory
leak in java\util\ResourceBundle.class when build the 3.0 trunk.
I got a work around from harmony community, and uploaded the new jar
provided by them in the https://issues.apache.org/jira/browse/GERONIMO-5650
-Rex
Thanks Kevan. I did try the build with JRE 1.6.0 IBM Windows 32 build
pwi3260sr8fp1-20100624_01 (SR8 FP1), and think I got past this
problem. I got out of memory:
[INFO]
[INFO] Building Geronimo Plugins, Connector 1.6 ::
On Oct 15, 2010, at 12:48 PM, Ted Kirby wrote:
Thanks Kevan. I did try the build with JRE 1.6.0 IBM Windows 32 build
pwi3260sr8fp1-20100624_01 (SR8 FP1), and think I got past this
problem. I got out of memory:
[INFO]
I successfully built trunk on windows XP SP3 with JDK 1.6.0_20 this Turesday
(on Revision: 1021600).
--
Best regards,
Han Hong Fang
Revision: 1022182
Sun JDK
[INFO]
[INFO] Building Geronimo Build Support :: Plugin
[INFO]task-segment: [clean, install]
[INFO]
[INFO]
I've seen this issue myself when building on Windows. I was able to
make it go away by setting MAVEN_OPTS to
-Xmx1024m -Xms256m -XX:PermSize=64m -XX:MaxPermSize=256m
-XX:ReservedCodeCacheSize=64m
The error was somewhat intermittent for me and would sometimes go away
with a reboot. I've
from plugins\connector-1_6
[INFO]
[INFO] Building Geronimo Plugins, Connector 1.6 :: Connector wrappers
[INFO]task-segment: [clean, install]
[INFO]
I retried the build about an hour later, and it ran. I am happy to
have a succesful g3 build now!
On Thu, Oct 14, 2010 at 2:26 PM, Ted Kirby ted.ki...@gmail.com wrote:
from plugins\connector-1_6
[INFO]
[INFO] Building
Thanks Shawn and Janet. I switched to Sun JDK, and not only got by
this problem, but, after a couple others, I got a successful build!
WooHoo!
I was getting the error with JRE 1.6.0 IBM Windows 32 build
pwi3260sr7-20091217_01 (SR7). Do we support building only with Sun
JDK?
On Thu, Oct 14,
On Oct 14, 2010, at 7:48 PM, Ted Kirby wrote:
Thanks Shawn and Janet. I switched to Sun JDK, and not only got by
this problem, but, after a couple others, I got a successful build!
WooHoo!
I was getting the error with JRE 1.6.0 IBM Windows 32 build
pwi3260sr7-20091217_01 (SR7). Do we
On Thu, Oct 14, 2010 at 11:14 PM, Kevan Miller kevan.mil...@gmail.com wrote:
On Oct 14, 2010, at 7:48 PM, Ted Kirby wrote:
Thanks Shawn and Janet. I switched to Sun JDK, and not only got by
this problem, but, after a couple others, I got a successful build!
WooHoo!
I was getting the error
It's SUN JDK version 1.6.0_20 on my windows.
--
Best regards,
Han Hong Fang
my trunk build is fine on the mac, but I keep getting this failure on windows:
[INFO]
[INFO] Building Geronimo Plugins, BVal :: Core
[INFO]task-segment: [clean, install]
[INFO]
What's your JDK version ? IIRC, I met a similar problem but resolved it
after upgrading to the latest JDK 1.6.0_21.
On Thu, Oct 14, 2010 at 8:22 AM, Ted Kirby ted.ki...@gmail.com wrote:
my trunk build is fine on the mac, but I keep getting this failure on
windows:
[INFO]
I'm doing some work on the 3.0-M1 release branch to get things switched
over to the M1 version number, and mvn install -Dstage=bootstrap is
having problems because the car-maven-plugin has a dependency on
geronimo-transformer. Things are not getting built in the correct order
so the build
Looking at JasperListener I think we don't need it. We can add a
gbean to the jasper module to do the same thing. Hopefully this will
eliminate the dependency of tomcat on jasper.
thanks
david jencks
On Dec 15, 2009, at 5:28 AM, Ivan wrote:
I worked around this by adding
David Jencks wrote:
I updated jetty with the api fixes and made our jetty8 build against
the latest trunk. Stuff seems to work for me
I've asked the jetty folks to push a new snapshot but I'm not sure if
they have yet.
The new snapshot has not been pushed yet, so I had to build jetty
In case anyone else tries this to build jetty itself (not our
integration) you need
mvn clean install -Pgeronimo-spec
I'll try to find out what's going on with this too.
thanks
david jencks
On Dec 16, 2009, at 5:39 AM, Rick McGuire wrote:
David Jencks wrote:
I updated jetty with the
Finally, I could built the plugin folder (Jetty releated are commented out,
as I just wish to try Tomcat).
When starting the welcome server, I got a class not found exception in
JasperListener class, it tries to load a class in jasper modules, certainly
it failed. I remembered that Jarek or
I worked around this by adding DynamicImport-Package: org.apache.jasper.* to
the catalina bundle. Could not see whether they are other ways to solve it.
While after that, I got other issues. Will continue to investigate it.
2009/12/15 Ivan xhh...@gmail.com
Finally, I could built the plugin
David Jencks wrote:
I finally got trunk to build for me
there were a few more tomcat6 refeences that I think were confusing
feilix and preventing it from figuring out which tomcat bundle to wire
to.
Mark Thomas has fixed the jspc issue in tomcat trunk so I'll out
regenerating
I'll look into this. Ivan identified some api errors in our servlet 3
jar and it's possible that jetty has not picked up the fixes (I'm not
sure where jetty got their spec jar from).
thanks
david jencks
On Dec 15, 2009, at 6:24 AM, Rick McGuire wrote:
David Jencks wrote:
I finally got
I updated jetty with the api fixes and made our jetty8 build against
the latest trunk. Stuff seems to work for me
I've asked the jetty folks to push a new snapshot but I'm not sure if
they have yet.
thanks
david jencks
On Dec 15, 2009, at 9:16 AM, David Jencks wrote:
I'll look into
Jarek Gawor wrote:
I see it when building plugins/activemq/activemq-portlets when the
jspc-maven-plugin kicks in.
It looks like this occurs on all of the portlet subprojects.
Rick
Jarek
On Fri, Dec 11, 2009 at 10:03 PM, Ivan xhh...@gmail.com wrote:
Do you only get this error while
I fixed it in my copy of tomcat (external/trunk/tomcat-parent-7.0.0)
and deployed a snapshot so I'm wondering why you are still seeing this.
On the other hand I am seeing some of the portlet projects pull in
tomcat6 and hang during the car plugin phase on puglins/console/plugin-
I finally got trunk to build for me
there were a few more tomcat6 refeences that I think were confusing
feilix and preventing it from figuring out which tomcat bundle to wire
to.
Mark Thomas has fixed the jspc issue in tomcat trunk so I'll out
regenerating
I'm seeing this kind of error in building console bits... anyone else
seeing it or know how to fix it? Maybe I need to build something
locally??? Haven't looked far yet.
[INFO] snapshot org.apache.geronimo.ext.tomcat:jasper-el:7.0.0.0-
SNAPSHOT: checking for updates from ops4j.snapshots
On Dec 11, 2009, at 2:09 PM, David Jencks wrote:
I'm seeing this kind of error in building console bits... anyone else seeing
it or know how to fix it? Maybe I need to build something locally???
Haven't looked far yet.
[INFO] snapshot
I'm getting the same error.
Jarek
On Fri, Dec 11, 2009 at 2:09 PM, David Jencks david_jen...@yahoo.com wrote:
I'm seeing this kind of error in building console bits... anyone else seeing
it or know how to fix it? Maybe I need to build something locally???
Haven't looked far yet.
[INFO]
Do you only get this error while using Tomcat 7 ? It seems that we get the
runtime resource issue again.
2009/12/12 Jarek Gawor jga...@gmail.com
I'm getting the same error.
Jarek
On Fri, Dec 11, 2009 at 2:09 PM, David Jencks david_jen...@yahoo.com
wrote:
I'm seeing this kind of error in
I see it when building plugins/activemq/activemq-portlets when the
jspc-maven-plugin kicks in.
Jarek
On Fri, Dec 11, 2009 at 10:03 PM, Ivan xhh...@gmail.com wrote:
Do you only get this error while using Tomcat 7 ? It seems that we get the
runtime resource issue again.
2009/12/12 Jarek Gawor
Hit an exception when building woden-impl-dom bundle like this, any hints?
thanks!
[INFO] [bundle:bundle {execution: default-bundle}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
Hi, Forrest:
The cause for this error should be that some jar files downloaded are
corrupted. I am not sure which one, you could check the dependency tree of
the woden-impl-dom.
Wish it helps :-)
2009/12/8 Forrest Xia forres...@gmail.com
Hit an exception when building woden-impl-dom
yep, after debugging a while, finally I found the corrupted jar. The
corruption might be caused by the bad network these two days.
However, the exception thrown by the bndlib is not very helpful, it does not
indicate which jar is corrupted. So I write a patch and send it to the
maintainer Peter
Forrest Xia wrote:
Thank you Ivan for your quick response. After manually update that
bundle, another package can not be resolved for this project.
It's org.w3.xml.x1998.namespace.impl, which bundle includes it?
Forrest
That's in the geronimo-schema-j2ee_1.4 jar, which you'll also need to
Hi,
I update to the latest G 3.0 code, and try to build through its OSGi-ready
modules. However, I encounter a problem when building
geronimo-j2ee-schema. The debug info indicates like this:
unresolved constraint in bundle
org.apache.geronimo.modules.geronimo-j2ee-schema [63]: package;
Actually the export setting has already updated in svn, but the latest jar
files are not published to the snapshot site, so now, I think that you could
manually update the files in the local repo.
2009/11/10 Forrest Xia forres...@gmail.com
Hi,
I update to the latest G 3.0 code, and try to
Thank you Ivan for your quick response. After manually update that bundle,
another package can not be resolved for this project.
It's org.w3.xml.x1998.namespace.impl, which bundle includes it?
Forrest
Guillaume,
It looks like the Geronimo build has been messed up by a recent Karaf
change. Do you have any suggestions on what needs updating this time?
Rick
[INFO]
[ERROR] BUILD ERROR
[INFO]
Those artifacts are available in the following private maven repo:
http://svn.apache.org/repos/asf/servicemix/m2-repo/org/eclipse/osgi/3.5.1.v20090827/
which is referenced in the karaf parent pom, so it should be available
from maven, but given you use the car maven plugin, that may be the
Jason Warner wrote:
Talking with Dan Becker in IRC, he came across a daytrader build problem.
I also saw a minor problem when using Jason's fix and building the
DayTrader EAR 2.0 to a Geronimo 2.1 server with the given
daytrader-g-2.0-SNAPSHOT-plan.xml Tomcat plugin. Namely, I got an error
Hi all,
Talking with Dan Becker in IRC, he came across a daytrader build problem.
The issue is with the version of geronimo-jaxrpc_1.1_spec available. When
building, maven is looking for 2.0.0 while the daytrader pom specifies a
dependency on [1.0, 2.0). This can be fixed by modifying
I created Daytrader-58 for the build issue. I also attached a patch
implementing my proposed solution to the build problem.
Thanks
On Feb 18, 2008 12:42 PM, Dan Becker [EMAIL PROTECTED] wrote:
Jason Warner wrote:
Talking with Dan Becker in IRC, he came across a daytrader build
problem.
I
Hello,
is there any fix or bypass available to get rid of
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1)
On 10/28/07, Heinz Drews [EMAIL PROTECTED] wrote:
Hello,
is there any fix or bypass available to get rid of
[INFO]
[ERROR] BUILD ERROR
[INFO]
On Oct 28, 2007, at 4:30 AM, Heinz Drews wrote:
Hello,
is there any fix or bypass available to get rid of
[INFO]
[ERROR] BUILD ERROR
[INFO]
Kevan,
that was the cure, thanks.
On 10/28/07, Kevan Miller [EMAIL PROTECTED] wrote:
On Oct 28, 2007, at 4:30 AM, Heinz Drews wrote:
Hello,
is there any fix or bypass available to get rid of
[INFO]
[ERROR]
Sounds like your build is still looking for axis2 1.3-r562247, but I
think we moved recently to the released version of axis2 1.3.
Lin
Ted Kirby wrote:
anyone else seeing this?
Missing:
1) org.apache.axis2:axis2-jaxws-api:jar:1.3-r562247
2) org.apache.axis2:axis2-saaj-api:jar:1.3-r562247
2
I am able to build now, thanks.
On 10/1/07, Lin Sun [EMAIL PROTECTED] wrote:
Sounds like your build is still looking for axis2 1.3-r562247, but I
think we moved recently to the released version of axis2 1.3.
Lin
Ted Kirby wrote:
anyone else seeing this?
Missing:
1)
Hi Joe, I've built with and without a clean m2 repo today, and in both cases GEP
trunk builds fine for me. In my M2 repo after the build are these artifacts,
which differ than what you're looking for:
C:\M2\org\apache\axis2\axis2-saaj-api\1.3\axis2-saaj-api-1.3.jar
anyone else seeing this?
Missing:
1) org.apache.axis2:axis2-jaxws-api:jar:1.3-r562247
2) org.apache.axis2:axis2-saaj-api:jar:1.3-r562247
2 required artifacts are missing.
for artifact:
org.apache.geronimo.devtools:org.apache.geronimo.runtime.v20:jar:2.0.1
Ted Kirby
From trunk, rev 578938, with a clean build tree and repo, I get:
[INFO] Compiling 20 source files to D:\gdvtls\j2g\trunk\plugins\org.apache.geron
imo.j2g.sources\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
Ted,
I just checked out the j2g trunk myself, and I am getting the same errors
you mentioned.
I am going to attempt to play with it a bit to see if I can't figure out the
cause, however if you beat me to it, let me know what you found
On 9/25/07, Ted Kirby [EMAIL PROTECTED] wrote:
From trunk,
After jarek said he was able to build using 1.5.0_10, I tried using that but
ran into the same error :(
Vamsi
On 9/17/07, Vamsavardhana Reddy [EMAIL PROTECTED] wrote:
I guess I am the only one for now hitting this build error. Anyone else
seeing this error? Output from command window posted
I guess I am the only one for now hitting this build error. Anyone else
seeing this error? Output from command window posted below..
I am using Sun JDK 1.5.0_12 on WinXP SP2.
[INFO]
-
---
[INFO] Building Geronimo ::
On Sep 17, 2007, at 1:35 PM, Vamsavardhana Reddy wrote:
I guess I am the only one for now hitting this build error. Anyone
else seeing this error? Output from command window posted below..
I just rebuilt trunk and didn't see an error using sun javac 1.5.0_07
on osx.
Best wishes,
Paul
This is the error I got from today's trunk on win xp and java
1.5.0_08-b03 -
[INFO] [compiler:testCompile]
Compiling 16 source files to
C:\anita\geronimo\g2.0\modules\geronimo-system\targ
et\test-classes
[INFO]
[ERROR]
I updated and built earlier today without any problems. I built rev.
576541 with Sun JDK 1.5.0_11 on OSX 10.4.10
Joe
Vamsavardhana Reddy wrote:
I guess I am the only one for now hitting this build error. Anyone else
seeing this error? Output from command window posted below..
I am using
Rebuilding trunk from a fresh checkout with a clean M2 repository, I get
the following errors:
|/home/rick/Geronimo/builds/g/2.0/modules/geronimo-cxf/src/main/java/org/apache/geronimo/cxf/GeronimoDestinationFactory.java:[23,37]
cannot find symbol|
|symbol : class AbstractHTTPTransportFactory|
They just pushed some snaps so I think we need to make a few fixes.
Jeff
Rick McGuire wrote:
Rebuilding trunk from a fresh checkout with a clean M2 repository, I get
the following errors:
I fixed it AFAICT so you should update now. Hopefully I didn't break
anything ;-)
Jeff
Rick McGuire wrote:
Rebuilding trunk from a fresh checkout with a clean M2 repository, I get
the following errors:
I removed the legacy java.net repo from the root pom Friday PM. Are
there others?
Joe
Jason Dillon wrote:
Strange dependency muck like this often happens when a legacy repo is
in the mix.
--jason
On Dec 10, 2006, at 8:55 PM, anita kulshreshtha wrote:
When I build cxf-builder from
Not sure... might be getting picked up as a dependency too.
You removed it? Where are you getting jstl 2.0 from now?
--jason
On Dec 11, 2006, at 1:49 AM, Joe Bohn wrote:
I removed the legacy java.net repo from the root pom Friday PM.
Are there others?
Joe
Jason Dillon wrote:
Strange
I wish I could say I removed it without any additional qualification.
:-P However, what I actually said was that I removed it *from the root
pom*. I still have references to the java.net as a legacy repo in
modules/geronimo-web-2.5-builder, configs/tomcat6 and configs/jetty6 to
pick up jstl
,
configs/tomcat6 and configs/jetty6 to pick up jstl 1.2.
AFAIK this shouldn't cause a problem for modules/geronimo-cxf-
builder or generally anything other than children of the poms I
changed ... right?
Joe
Ya, that is what I had thought. I believe this is why the strange
build problem
When I build cxf-builder from modules directory, I get this error:
Missing:
--
1) wsdl4j:wsdl4j:jar:1.6.1
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=wsdl4j -DartifactId=wsdl4j \
Strange dependency muck like this often happens when a legacy repo is
in the mix.
--jason
On Dec 10, 2006, at 8:55 PM, anita kulshreshtha wrote:
When I build cxf-builder from modules directory, I get this error:
Missing:
--
1) wsdl4j:wsdl4j:jar:1.6.1
Try downloading the file
Something in that artifact id doesn't seem right. There is a missing piece here
org.apache.geronimo.missing_piece.javamail:geronimo-javamail_1.3.1_provider:jar:1.0-SNAPSHOT
Can you please post the entire error message ?
Cheers
Prasad
On 12/1/06, Apparao Kalimireddy [EMAIL PROTECTED] wrote:
I
Here is the entire message:
[INFO]
[INFO]Building Geronimo :: Mail
[INFO] task-segment: [install]
[INFO]
project-execute
There is indeed a
org.apache.geronimo.javamail:geronimo-javamail_1.3.1_provider:jar:1.0-SNAPSHOT
artifact
I just did an svn update and built the geronimo-mail module. It
downloaded the above artifact successfully from the apache-snapshots
repository.
Unless you have disabled snapshots, then you
That got me through the problem. Thanks for help.
On 12/4/06, Prasad Kashyap [EMAIL PROTECTED] wrote:
There is indeed a
org.apache.geronimo.javamail:geronimo-javamail_1.3.1_provider:jar:1.0-SNAPSHOT
artifact
I just did an svn update and built the geronimo-mail module. It
downloaded the above
I am trying to build latest code and I get a problem with javamail
dependency.
Here is what I see, any help is appreciated:
[INFO]Failed to resolve artifact.
Missing:
--
1)
org.apache.geronimo.javamail:geronimo-javamail_1.3.1_provider:jar:1.0-SNAPSHOT
Anyone know why this error (um set of errors?) might happen in rmi-
naming when running car:package?
This only happens when you run a `mvn site` build. You can `cd
configs/rmi-naming; mvn site` to quickly reproduce (assuming you have
a bootstrap/build before).
snip
Packaging
John,
On Fri, May 26, 2006 at 09:51:25AM +1000, John Sisson wrote:
I built Geronimo rev 409303 ok yesterday (with OpenEJB checked out at
rev 2658 via maven m:fresh-checkout command)
BUILD SUCCESSFUL
Total time : 117 minutes 44 seconds
Finished at : Friday, May 26, 2006 2:06:10 AM EDT
On Tue, May 23, 2006 at 05:49:34PM -0400, toby cabot wrote:
Hi folks,
I checked out a fresh copy of the 1.1 branch and tried to build. It
gets as far as:
Based on suggestions (thanks!) from several folks on the list I
updated from subversion, blew away my .maven directory, and lept back
Hi Tony,
So we can replicate the problem, are you building Geronimo and OpenEJB
or just building Geronimo and downloading OpenEJB dependencies.
I built Geronimo rev 409303 ok yesterday (with OpenEJB checked out at
rev 2658 via maven m:fresh-checkout command)
Thanks,
John
toby cabot
John,
Thanks for your help.
On Fri, May 26, 2006 at 09:51:25AM +1000, John Sisson wrote:
So we can replicate the problem, are you building Geronimo and OpenEJB
or just building Geronimo and downloading OpenEJB dependencies.
I built Geronimo rev 409303 ok yesterday (with OpenEJB checked out
Hi folks,
I checked out a fresh copy of the 1.1 branch and tried to build. It
gets as far as:
+
| configurations Geronimo Configuration for performing service deployments
| Memory: 40M/50M
+
DEPRECATED: the
Toby, I have been hitting that problem too on debian with a fresh
checkout or after running the clean target. I don't know what the
underlying problem is, but compiling a second time seems to work past
it (just type maven -o new4 new5 to complete the build). This
problem may be related to the
Ahh, so I wasn't the only one having the problem :-)
Ensure all the geronimo plugins in your local repo are deleted. That
seemed to fix it for me in GERONIMO-2037. I didn't have the time to
spend working out which plugin and change introduced the problem.
John
Paul McMahan wrote:
Toby, I
Paul,
Thanks for the tip. Looks like I need to do an online build, and
people.apache.org has been bouncy for the past few hours, but I'll try
a maven new4 new5 again tomorrow morning. Appreciate the help!
Toby
Hi:
When I tried to complie the latest source code from
incubator-activemq-4.0-SNAPSHOT, I get the following error
Missing:
--
1) org.apache.geronimo.specs:geronimo-servlet_2.4_spec:jar:1.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using
We officially don't support using maven 2 to build yet (we are still
working on it). Please use maven 1.
On 4/20/06, Li, Fan [EMAIL PROTECTED] wrote:
Hi:
When I tried to complie the latest source code from
incubator-activemq-4.0-SNAPSHOT, I get the following error
Missing:
--
1)
On Apr 3, 2006, at 2:25 AM, John Sisson wrote:
I tried building 1.1 on Solaris and got the following error (note
the FileNotFoundException at the bottom):
I read on IRC that DayTrader was working on 1.1, are there changes
that haven't been committed?
Hi John,
The problem isn't specific
Should be fixed now.
-dain
On Apr 3, 2006, at 5:38 AM, Kevan Miller wrote:
On Apr 3, 2006, at 2:25 AM, John Sisson wrote:
I tried building 1.1 on Solaris and got the following error (note
the FileNotFoundException at the bottom):
I read on IRC that DayTrader was working on 1.1, are
I tried building 1.1 on Solaris and got the following error (note the
FileNotFoundException at the bottom):
I read on IRC that DayTrader was working on 1.1, are there changes that
haven't been committed?
John
+
| configurations Daytrader using derby
can be created by adding additional statement in the
build command. e.g maven build.log.
Hope this helps,
Fritz
- Original Message -
From: Li, Fan [EMAIL PROTECTED]
To: activemq-dev@geronimo.apache.org
Sent: Friday, February 17, 2006 5:08 AM
Subject: RE: Build Problem
I did not find any
I have been trying to build the latest source code with maven 1.0.2 and kept
getting build failure. This is the build for the latest SNAPSHOT. I am not sure
if anyone had similar problem.
BUILD FAILED
File.. /home/fanli/.maven/cache/maven-multiproject-plugin-1.3.1/plugin.jelly
Element...
That indicates there were some JUnit test failures. We have some tests that
fail on some platforms with timing issues; its amazingly hard to write
highly asynchronous concurrent message based unit test cases that always
work on every platform.
If you seach for [ERROR] you'll find the actual
With a fresh checkout this morning I'm getting the following compile error:
default:
java:prepare-filesystem:
[mkdir] Created dir:
C:\Geronimo\geronimo\openejb\modules\core\target\classe
s
java:compile:
[depend] Deleted 0 out of date files in 0 seconds
[echo] Compiling to
oops
I'm hoping to have a more complete fix for the problems introduced by
the new principal wrapping ready very shortly. If I run into problems
I'll try to fix just this error.
thanks
david jencks
On Oct 14, 2005, at 6:09 AM, Rick McGuire wrote:
With a fresh checkout this morning I'm
David,
I'm already half into the configuration/builder for the new wrapped
principals.
Regards,
Alan
David Jencks wrote, On 10/14/2005 8:47 AM:
oops
I'm hoping to have a more complete fix for the problems introduced by
the new principal wrapping ready very shortly. If I run into
Can we get the interim fix in for this for now? I am S.O.L. on the
build and need it to continue with some of my development.
Thanks,
Jeff
David Jencks wrote:
oops
I'm hoping to have a more complete fix for the problems introduced by
the new principal wrapping ready very shortly. If I
When I do a rebuild-all on HEAD, I get (eventually):
+
| Executing default The Magic G Ball
| Memory: 67M/83M
+
You are working offline so the build will continue, but
geronimo-common-1.0-SNAPSHOT.jar may be out of
1 - 100 of 112 matches
Mail list logo
