...@gmail.com
Date: 2012/5/31
Subject: Re: Build problem of dayTrader
To: Matt Hogstrom hogst...@apache.org
Cc: cjbly...@apache.org, jgenen...@apache.org, vmas...@apache.org
Hi Matt,
This seems a common problem, I also see at
http://apache-geronimo.328035.n3.nabble.com/Daytrader-application-does
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
On Nov 1, 2010, at 12:20 PM, Rick McGuire wrote:
I was having problems building trunk this morning, and it looks like the root
cause of the problem is a javassist version mismatch. The openwebbeans
project is using the javassist 3.12.0.GA version to build and Geronimo is
using the
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
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
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]
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
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
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
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
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)
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
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
For some reason you have to refresh and build openejb, then go back to
building Geronimo.
-Original Message-
From: toby cabot [mailto:[EMAIL PROTECTED]
Sent: Saturday, November 06, 2004 10:39 PM
To: [EMAIL PROTECTED]
Subject: build problem?
Hi folks,
Friday I could build OK
18, 2004 10:59 AM
To: [EMAIL PROTECTED]
Subject: Re: Build problem with latest Codeline
Is there a reason why maven doesn't just do that for us?
-dain
On Aug 18, 2004, at 4:16 AM, Alan D. Cabrera wrote:
This is a known issue with the Axis module. The way that you can
get
around
This is a known issue with the Axis module. The way that you can get
around it is to copy the Geronimo axis jar into your local repository by
hand.
You can track the resolution of this issue via
http://nagoya.apache.org/jira/browse/AXIS-1517.
Regards,
Alan
-Original Message-
From:
Is there a reason why maven doesn't just do that for us?
-dain
On Aug 18, 2004, at 4:16 AM, Alan D. Cabrera wrote:
This is a known issue with the Axis module. The way that you can get
around it is to copy the Geronimo axis jar into your local repository
by
hand.
You can track the resolution of
39 matches
Mail list logo
