[Design of JBoss Build System] - Re: Request: htmlunit from sourceforge in thirdpary.
by chilin
Hi,
I'm taking over the task(s) Bob described at the beginning of this post.
I've identified that we need to add the following 4 new jars to the repository:
. commons-io.jar
. htmlunit.jar
. js.jar
. nekohtml.jar
And we also need to upgrade commons-collections.jar and commons-httpclient.jar from version 2.1 & 2.0.2 to version 3.1 & 3.0 respectively.
3.1 commons-collections.jar and 3.0.1 commons-httpclient.jar already exist in the repository, so I modified build/build-thirdparty.xml to include them. However, this caused compile errors in multiple testsuite modules.
Being new to this, I'd like to find out what is the standard procedure of handling this. Should I attempt to fix the testsuite to cope with the new version (not sure about the magnitude)? Or is it ok to include multiple versions of a jar file in the thirdparty directory (so only the admin-console's htmlunt test uses the new version, everything else remains the same)?
Any other suggestions?
Chi
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958630#3958630
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958630
19 years, 8 months
[Design of Kosmos] - serviceResultUpdaterJob not traversing repository
by sstuart4
Hi, I am currently trying to implement the scheduler functionality new to Version 0.2.0RC2. The problem I am having seems to be minor since I am not getting any errors, its just that the service is only taking a very short time to run when I know it should be 10+ mins or so... Here are the last few lines of my JBoss server log:
2006-07-17 15:41:50,272 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.0.3SP1 (build: CVSTag=JBoss_4_0_3_SP1 date=200510231054)] Started in 2m:18s:405ms
| 2006-07-17 15:41:53,004 DEBUG [org.quartz.simpl.SimpleJobFactory] Producing instance of Job 'DEFAULT.serviceResultUpdaterJob', class=hu.midori.kosmos.server.ServiceResultUpdaterJob
| 2006-07-17 15:41:53,005 DEBUG [org.quartz.core.JobRunShell] Calling execute on job DEFAULT.serviceResultUpdaterJob
| 2006-07-17 15:41:53,009 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Running scheduled update job...
| 2006-07-17 15:41:53,010 INFO [hu.midori.kosmos.server.ServiceResultUpdaterJob] Update job completed.
As you can see, this is taking less than a second for a rather large repository.
The portlet.xml should be hitting the trunk of my repo and the org.springframework.scheduling.quartz.SimpleTriggerBean configuration in the kosmos-services-servlet.xml is set like this:
<bean id="serviceResultUpdateTrigger" class="org.springframework.scheduling.quartz.SimpleTriggerBean">
| <property name="jobDetail" ref="serviceResultUpdaterJob"/>
| <property name="startDelay" value="10000"/>
| <property name="repeatInterval" value="7200000"/>
| </bean>
BTW, I am running the jboss-portal-2.2.0-bundled install. Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3958616#3958616
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3958616
19 years, 8 months