From: Larry Mills-G. <lm...@we...> - 2012-02-27 21:48:05
|
I used the curl setup line to move the job from my local (os x) machine to the linux machine. (I went into the job on the local machine and used that config.xml file to feed to the curl createItem command (e.g. curl -v --user youruser:yourpassword -H "Content-Type: text/xml" -s --data "@config.xml" http://remotemachine:8080/createItem?name=VAEO) So, I'm pretty sure the jobs started out identical. I did make some changes to -lib in the ant target to see if I could force it to find woproject.jar (to no effect) I added -diagnostics to the ant call and confirmed that the environment looks reasonable (and even that woproject was in $ANT_HOME/lib I am still confused (Ok, I'm generally confused, but specifically, I'm still confused about this error) Larry Mills-Gahl lm...@we... (Yes, I'm moving new projects to Git when they start, but I haven't moved the old projects to Git yet. One of the guys is lobbying for Mercurial so we're looking at that too.) On Feb 27, 2012, at 1:54 PM, Pascal Robert wrote: > I have run the scripts on both CentOS and Ubuntu without problems. woproject.jar is indeed in Root/lib of the project. The only difference for me is that on Linux, I only build Git projects (I would never want to go back to Subversion…), but I don't think it would make a difference. > > Did you change anything in the scripts? > > One thing you can try is to logging on the Linux box and to launch the Ant task by command-line to see if you get the same error. > >> I have Jenkins running as expected on an OS X machine and I have WO/Wonder jobs and local framework and application jobs building as expected. >> I have take the config files from those jobs and added them to the linux box running Jenkins and am having a woproject.jar problem. >> >> I have confirmed that the woproject link is made in the local job (and is present in the $JENKINS_HOME/WOFrameworkRepository/WOProject directory. >> I have tried copying the woproject.jar into the job workspace/Root/lib in case there is a linking problem or a problem traversing the link. >> I have copied woproject.jar into the ant lib directory for the machine. >> >> None of that has changed anything and those path related differences are what I can think of to try to isolate why this job works well on OS X but fails to find the woproject.jar on Linux. >> >> My next path is to look into the build file for Wonder to find out what is different between that setup that builds Wonder (pretty much unchanged from David Avendasora's WOJenkins_Job_InstallWOAndWOnder at https://github.com/avendasora/WOJenkins_Job_InstallWOAndWOnder.git) and the setup that builds my frameworks (which is also from David's github projects WOJenkins and WOJenkins_Job_WOProject_SVN) >> >> >> Here is the failure from the Jenkins console: >> [...] >> Look For: MySQLPlugIn >> Not found in WebObjects: /var/lib/jenkins/WOFrameworksRepository/WebObjects/5.4.3/Library/Frameworks/MySQLPlugIn.framework >> Found in Project WOnder. >> Linking: ln -sfn /var/lib/jenkins/WOFrameworksRepository/ProjectWOnder/master/5.4.3/Local/Library/Frameworks/MySQLPlugIn.framework >> /var/lib/jenkins/jobs/VAEO/workspace/Root/Local/Library/Frameworks >> Not found in other build job: /var/lib/jenkins/jobs/VAEO/workspace/../../MySQLPlugIn/lastSuccessful/archive/Projects/MySQLPlugIn/dist/MySQLPlugIn.tar.gz >> Link to woproject.jar so Ant can build the WO project. >> Setup /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties for Ant to use for building >> Create link for backward compatibility with old build.properties file name since old build jobs will still be pointing to it. >> ln -sfn /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties /var/lib/jenkins/jobs/VAEO/workspace/Root/build.properties >> [VAEO] $ ant -file build.xml -DPROJECT_SVN_REPOSITORY= >> svn+ssh://192.168.2.110/usr/local/svn/va/java/va6/trunk/VAEO >> -DDEPLOYED_APPLICATION_NAME= -DPROJECT_BRANCH_TAG= -DJAVA_COMPATIBILITY_VERSION=1.5 -DBUILD_TYPE=Deployment -DWONDER_GIT_REFERENCE=master -DWO_VERSION=5.4.3 -DPROJECT_BRANCHES_TAGS_TRUNK=trunk -DPROJECT_NAME=VAEO -DProjects/${PROJECT_NAME}/= build -propertyfile /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties -lib /var/lib/jenkins/jobs/VAEO/workspace/Root/lib/woproject.jar >> Buildfile: /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml >> >> >> init.properties >> : >> >> >> init.build >> : >> >> >> compile >> : >> >> >> BUILD FAILED >> >> /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml:87: taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found >> using the classloader AntClassLoader[] >> >> Total time: 0 seconds >> Build step 'Invoke Ant' marked build as failure >> Archiving artifacts >> Finished: FAILURE >> >> >> >> Does anybody have any ideas about where I can look for what would cause this job to fail this way on Linux (OpenSuSE 12.1 with JDK (not OpenJDK)) while the identical job configuration succeeds on OS X. >> >> >> >> >> >> Larry Mills-Gahl >> lm...@we... >> >> >> >> ------------------------------------------------------------------------------ >> Try before you buy = See our experts in action! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-dev2_______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc > |
From: David A. <web...@av...> - 2012-03-01 15:13:55
|
Hi Larry, Is the woproject.jar file located at: /var/lib/jenkins/jobs/VAEO/workspace/Root/lib/woproject.jar ? That's where the ant command is looking for it. If it is there, then it could be permissions that's keeping the file from being read, but since the job is the one that put it there in the first place by running the setupWonderProjectWorkspace.sh script, the permissions should be right. If it is not there, then something has gone wrong prior to ant trying to read it. If it's not at the above location, how about here: How about at : /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar ? If it is not there, are you using my Jenkins job that downloads and install WebObjects and WOProject?: https://github.com/avendasora/WOJenkins_Job_InstallWOAndWOnder If not, you'll need to because everything about my WOJenkins_Job_WOProject_SVN depends upon things being where the WOJenkins_Job_InstallWOAndWOnder installs things. If you are running both jobs and you're still getting errors, read both jobs' console output carefully. The shell script that does all the downloading and linking has a lot of echo statements in it that should all show both before and after the SVN checkout log entries. It should give you a pretty good idea where things went wrong… Maybe paste it or a zip of the output here. Dave On Feb 28, 2012, at 5:47 AM, Larry Mills-Gahl wrote: > I used the curl setup line to move the job from my local (os x) machine to the linux machine. (I went into the job on the local machine and used that config.xml file to feed to the curl createItem command (e.g. curl -v --user youruser:yourpassword -H "Content-Type: text/xml" -s --data "@config.xml" http://remotemachine:8080/createItem?name=VAEO) > > So, I'm pretty sure the jobs started out identical. I did make some changes to -lib in the ant target to see if I could force it to find woproject.jar (to no effect) > > I added -diagnostics to the ant call and confirmed that the environment looks reasonable (and even that woproject was in $ANT_HOME/lib > > I am still confused (Ok, I'm generally confused, but specifically, I'm still confused about this error) > > Larry Mills-Gahl > lm...@we... > > (Yes, I'm moving new projects to Git when they start, but I haven't moved the old projects to Git yet. One of the guys is lobbying for Mercurial so we're looking at that too.) > > On Feb 27, 2012, at 1:54 PM, Pascal Robert wrote: > >> I have run the scripts on both CentOS and Ubuntu without problems. woproject.jar is indeed in Root/lib of the project. The only difference for me is that on Linux, I only build Git projects (I would never want to go back to Subversion…), but I don't think it would make a difference. >> >> Did you change anything in the scripts? >> >> One thing you can try is to logging on the Linux box and to launch the Ant task by command-line to see if you get the same error. >> >>> I have Jenkins running as expected on an OS X machine and I have WO/Wonder jobs and local framework and application jobs building as expected. >>> I have take the config files from those jobs and added them to the linux box running Jenkins and am having a woproject.jar problem. >>> >>> I have confirmed that the woproject link is made in the local job (and is present in the $JENKINS_HOME/WOFrameworkRepository/WOProject directory. >>> I have tried copying the woproject.jar into the job workspace/Root/lib in case there is a linking problem or a problem traversing the link. >>> I have copied woproject.jar into the ant lib directory for the machine. >>> >>> None of that has changed anything and those path related differences are what I can think of to try to isolate why this job works well on OS X but fails to find the woproject.jar on Linux. >>> >>> My next path is to look into the build file for Wonder to find out what is different between that setup that builds Wonder (pretty much unchanged from David Avendasora's WOJenkins_Job_InstallWOAndWOnder at https://github.com/avendasora/WOJenkins_Job_InstallWOAndWOnder.git) and the setup that builds my frameworks (which is also from David's github projects WOJenkins and WOJenkins_Job_WOProject_SVN) >>> >>> >>> Here is the failure from the Jenkins console: >>> [...] >>> Look For: MySQLPlugIn >>> Not found in WebObjects: /var/lib/jenkins/WOFrameworksRepository/WebObjects/5.4.3/Library/Frameworks/MySQLPlugIn.framework >>> Found in Project WOnder. >>> Linking: ln -sfn /var/lib/jenkins/WOFrameworksRepository/ProjectWOnder/master/5.4.3/Local/Library/Frameworks/MySQLPlugIn.framework >>> /var/lib/jenkins/jobs/VAEO/workspace/Root/Local/Library/Frameworks >>> Not found in other build job: /var/lib/jenkins/jobs/VAEO/workspace/../../MySQLPlugIn/lastSuccessful/archive/Projects/MySQLPlugIn/dist/MySQLPlugIn.tar.gz >>> Link to woproject.jar so Ant can build the WO project. >>> Setup /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties for Ant to use for building >>> Create link for backward compatibility with old build.properties file name since old build jobs will still be pointing to it. >>> ln -sfn /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties /var/lib/jenkins/jobs/VAEO/workspace/Root/build.properties >>> [VAEO] $ ant -file build.xml -DPROJECT_SVN_REPOSITORY= >>> svn+ssh://192.168.2.110/usr/local/svn/va/java/va6/trunk/VAEO >>> -DDEPLOYED_APPLICATION_NAME= -DPROJECT_BRANCH_TAG= -DJAVA_COMPATIBILITY_VERSION=1.5 -DBUILD_TYPE=Deployment -DWONDER_GIT_REFERENCE=master -DWO_VERSION=5.4.3 -DPROJECT_BRANCHES_TAGS_TRUNK=trunk -DPROJECT_NAME=VAEO -DProjects/${PROJECT_NAME}/= build -propertyfile /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties -lib /var/lib/jenkins/jobs/VAEO/workspace/Root/lib/woproject.jar >>> Buildfile: /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml >>> >>> >>> init.properties >>> : >>> >>> >>> init.build >>> : >>> >>> >>> compile >>> : >>> >>> >>> BUILD FAILED >>> >>> /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml:87: taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found >>> using the classloader AntClassLoader[] >>> >>> Total time: 0 seconds >>> Build step 'Invoke Ant' marked build as failure >>> Archiving artifacts >>> Finished: FAILURE >>> >>> >>> >>> Does anybody have any ideas about where I can look for what would cause this job to fail this way on Linux (OpenSuSE 12.1 with JDK (not OpenJDK)) while the identical job configuration succeeds on OS X. >>> >>> >>> >>> >>> >>> Larry Mills-Gahl >>> lm...@we... >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Try before you buy = See our experts in action! >>> The most comprehensive online learning library for Microsoft developers >>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >>> Metro Style Apps, more. Free future releases when you subscribe now! >>> http://p.sf.net/sfu/learndevnow-dev2_______________________________________________ >>> Wonder-disc mailing list >>> Won...@li... >>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >> >> >> ------------------------------------------------------------------------------ >> Try before you buy = See our experts in action! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-dev2 >> _______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc >> > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2_______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |
From: Larry Mills-G. <lm...@we...> - 2012-03-01 19:44:09
|
On Mar 1, 2012, at 9:56 AM, David Avendasora wrote: > Hi Larry, > > Is the woproject.jar file located at: /var/lib/jenkins/jobs/VAEO/workspace/Root/lib/woproject.jar ? > > That's where the ant command is looking for it. If it is there, then it could be permissions that's keeping the file from being read, but since the job is the one that put it there in the first place by running the setupWonderProjectWorkspace.sh script, the permissions should be right. The woproject.jar is in those places and the permissions appear correct: lmg42@vadb-03:/var/lib/jenkins/jobs/VAEO/workspace/Root/lib> ls -l total 4 lrwxrwxrwx 1 jenkins jenkins 63 Feb 29 16:33 woproject.jar -> /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar lmg42@vadb-03:/var/lib/jenkins/jobs/VAEO/workspace/Root/lib> ls -l /var/lib/jenkins/WOFrameworksRepository/WOProject/ total 560 -rw-r--r-- 1 jenkins jenkins 570045 Feb 28 11:48 woproject.jar I am using your WOJenkins scripts for WO, Wonder and SVN jobs (thanks, by the way) All of my jobs build fine on OSX but it appears that those are using a different copy of woproject.jar One interesting difference between the WOnder setup and the framework job is that Root/lib/woproject.jar for WO and Wonder is different from Wonder/Build/lib/woproject.jar. It looks like WO_and_Wonder are using a local woproject.jar rather than the WOFrameworksRepository version. The following output shows ls -l and ls -lL to clarify what woproject.jar is being referenced in a job. The WO_and_Wonder Wonder/Build/lib/woproject.jar are the same across two builds (the projectwonder master and my fork) but the repository version is different (downloaded from http://webobjects.mdimension.com/hudson/job/WOLips37Current/lastSuccessfulBuild/artifact/woproject.jar is 570045, the one built locally is 524536) lrwxrwxrwx 1 jenkins jenkins 63 Mar 1 13:19 ./jobs/VAEO/workspace/Root/lib/woproject.jar -> /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar -rw-r--r-- 1 jenkins jenkins 570045 Feb 28 11:48 ./jobs/VAEO/workspace/Root/lib/woproject.jar lrwxrwxrwx 1 jenkins jenkins 63 Feb 29 16:32 ./jobs/Install_WO_and_Wonder/workspace/Root/lib/woproject.jar -> /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar -rw-r--r-- 1 jenkins jenkins 570045 Feb 28 11:48 ./jobs/Install_WO_and_Wonder/workspace/Root/lib/woproject.jar -rw-r--r-- 1 jenkins jenkins 524536 Feb 24 11:31 ./jobs/Install_WO_and_Wonder/workspace/Wonder/Build/lib/woproject.jar -rw-r--r-- 1 jenkins jenkins 524536 Feb 24 11:31 ./jobs/Install_WO_and_Wonder/workspace/Wonder/Build/lib/woproject.jar lrwxrwxrwx 1 jenkins jenkins 63 Mar 1 13:44 ./jobs/Install_WO_and_Wonder_elemegee/workspace/Root/lib/woproject.jar -> /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar -rw-r--r-- 1 jenkins jenkins 570045 Feb 28 11:48 ./jobs/Install_WO_and_Wonder_elemegee/workspace/Root/lib/woproject.jar -rw-r--r-- 1 jenkins jenkins 524536 Mar 1 13:15 ./jobs/Install_WO_and_Wonder_elemegee/workspace/Wonder/Build/lib/woproject.jar -rw-r--r-- 1 jenkins jenkins 524536 Mar 1 13:15 ./jobs/Install_WO_and_Wonder_elemegee/workspace/Wonder/Build/lib/woproject.jar lrwxrwxrwx 1 jenkins jenkins 63 Mar 1 13:19 ./jobs/VAEO/workspace/Root/lib/woproject.jar -> /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar -rw-r--r-- 1 jenkins jenkins 570045 Feb 28 11:48 ./jobs/VAEO/workspace/Root/lib/woproject.jar I'm thinking this may be a java loading difference rather than a configuration problem because the woproject.jar files on my OS X instance of Jenkins are the same. I think what I'm going to do is put together an ant project that just loads the wocompile taskdef and see if high debugging output sheds some light on this. > > If it's not at the above location, how about here: How about at : /var/lib/jenkins/WOFrameworksRepository/WOProject/woproject.jar ? > > If it is not there, are you using my Jenkins job that downloads and install WebObjects and WOProject?: https://github.com/avendasora/WOJenkins_Job_InstallWOAndWOnder > > If not, you'll need to because everything about my WOJenkins_Job_WOProject_SVN depends upon things being where the WOJenkins_Job_InstallWOAndWOnder installs things. > > If you are running both jobs and you're still getting errors, read both jobs' console output carefully. The shell script that does all the downloading and linking has a lot of echo statements in it that should all show both before and after the SVN checkout log entries. It should give you a pretty good idea where things went wrong… > > Maybe paste it or a zip of the output here. After the framework dependency checks, this is what the build shows: Link to woproject.jar so Ant can build the WO project. Setup /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties for Ant to use for building Create link for backward compatibility with old build.properties file name since old build jobs will still be pointing to it. ln -sfn /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties /var/lib/jenkins/jobs/VAEO/workspace/Root/build.properties [VAEO] $ ant -file build.xml -DPROJECT_SVN_REPOSITORY=svn+ssh://192.168.2.75:10451/usr/local/svn/va/java/va6/trunk/VAEO -DDEPLOYED_APPLICATION_NAME= -DPROJECT_BRANCH_TAG= -DJAVA_COMPATIBILITY_VERSION=1.5 "-DBUILD_TYPE=Test Build" -DWONDER_GIT_REFERENCE=master -DWO_VERSION=5.4.3 -DPROJECT_BRANCHES_TAGS_TRUNK=trunk -DPROJECT_NAME=VAEO -DProjects/${PROJECT_NAME}/= build -propertyfile /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties -lib /var/lib/jenkins/jobs/VAEO/workspace/Root/lib/woproject.jar Buildfile: /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml init.properties: init.build: compile: BUILD FAILED /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml:87: taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found using the classloader AntClassLoader[] I am using all of your (excellent and greatly appreciated) WOJenkins work and the setup appears to be working as expected. I'm betting this is either an over-zealous security configuration (they don't call me "Little Paranoid Larry" for nothing) or a java environment problem. Im will be surprised if it's a Java config thing because this should all run in a defined environment with Jenkins.... but we'll see. Thanks for your help. Larry > > Dave > > On Feb 28, 2012, at 5:47 AM, Larry Mills-Gahl wrote: > >> I used the curl setup line to move the job from my local (os x) machine to the linux machine. (I went into the job on the local machine and used that config.xml file to feed to the curl createItem command (e.g. curl -v --user youruser:yourpassword -H "Content-Type: text/xml" -s --data "@config.xml" http://remotemachine:8080/createItem?name=VAEO) >> >> So, I'm pretty sure the jobs started out identical. I did make some changes to -lib in the ant target to see if I could force it to find woproject.jar (to no effect) >> >> I added -diagnostics to the ant call and confirmed that the environment looks reasonable (and even that woproject was in $ANT_HOME/lib >> >> I am still confused (Ok, I'm generally confused, but specifically, I'm still confused about this error) >> >> Larry Mills-Gahl >> lm...@we... >> >> (Yes, I'm moving new projects to Git when they start, but I haven't moved the old projects to Git yet. One of the guys is lobbying for Mercurial so we're looking at that too.) >> >> On Feb 27, 2012, at 1:54 PM, Pascal Robert wrote: >> >>> I have run the scripts on both CentOS and Ubuntu without problems. woproject.jar is indeed in Root/lib of the project. The only difference for me is that on Linux, I only build Git projects (I would never want to go back to Subversion…), but I don't think it would make a difference. >>> >>> Did you change anything in the scripts? >>> >>> One thing you can try is to logging on the Linux box and to launch the Ant task by command-line to see if you get the same error. >>> >>>> I have Jenkins running as expected on an OS X machine and I have WO/Wonder jobs and local framework and application jobs building as expected. >>>> I have take the config files from those jobs and added them to the linux box running Jenkins and am having a woproject.jar problem. >>>> >>>> I have confirmed that the woproject link is made in the local job (and is present in the $JENKINS_HOME/WOFrameworkRepository/WOProject directory. >>>> I have tried copying the woproject.jar into the job workspace/Root/lib in case there is a linking problem or a problem traversing the link. >>>> I have copied woproject.jar into the ant lib directory for the machine. >>>> >>>> None of that has changed anything and those path related differences are what I can think of to try to isolate why this job works well on OS X but fails to find the woproject.jar on Linux. >>>> >>>> My next path is to look into the build file for Wonder to find out what is different between that setup that builds Wonder (pretty much unchanged from David Avendasora's WOJenkins_Job_InstallWOAndWOnder at https://github.com/avendasora/WOJenkins_Job_InstallWOAndWOnder.git) and the setup that builds my frameworks (which is also from David's github projects WOJenkins and WOJenkins_Job_WOProject_SVN) >>>> >>>> >>>> Here is the failure from the Jenkins console: >>>> [...] >>>> Look For: MySQLPlugIn >>>> Not found in WebObjects: /var/lib/jenkins/WOFrameworksRepository/WebObjects/5.4.3/Library/Frameworks/MySQLPlugIn.framework >>>> Found in Project WOnder. >>>> Linking: ln -sfn /var/lib/jenkins/WOFrameworksRepository/ProjectWOnder/master/5.4.3/Local/Library/Frameworks/MySQLPlugIn.framework >>>> /var/lib/jenkins/jobs/VAEO/workspace/Root/Local/Library/Frameworks >>>> Not found in other build job: /var/lib/jenkins/jobs/VAEO/workspace/../../MySQLPlugIn/lastSuccessful/archive/Projects/MySQLPlugIn/dist/MySQLPlugIn.tar.gz >>>> Link to woproject.jar so Ant can build the WO project. >>>> Setup /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties for Ant to use for building >>>> Create link for backward compatibility with old build.properties file name since old build jobs will still be pointing to it. >>>> ln -sfn /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties /var/lib/jenkins/jobs/VAEO/workspace/Root/build.properties >>>> [VAEO] $ ant -file build.xml -DPROJECT_SVN_REPOSITORY= >>>> svn+ssh://192.168.2.110/usr/local/svn/va/java/va6/trunk/VAEO >>>> -DDEPLOYED_APPLICATION_NAME= -DPROJECT_BRANCH_TAG= -DJAVA_COMPATIBILITY_VERSION=1.5 -DBUILD_TYPE=Deployment -DWONDER_GIT_REFERENCE=master -DWO_VERSION=5.4.3 -DPROJECT_BRANCHES_TAGS_TRUNK=trunk -DPROJECT_NAME=VAEO -DProjects/${PROJECT_NAME}/= build -propertyfile /var/lib/jenkins/jobs/VAEO/workspace/Root/jenkins.build.properties -lib /var/lib/jenkins/jobs/VAEO/workspace/Root/lib/woproject.jar >>>> Buildfile: /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml >>>> >>>> >>>> init.properties >>>> : >>>> >>>> >>>> init.build >>>> : >>>> >>>> >>>> compile >>>> : >>>> >>>> >>>> BUILD FAILED >>>> >>>> /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml:87: taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found >>>> using the classloader AntClassLoader[] >>>> >>>> Total time: 0 seconds >>>> Build step 'Invoke Ant' marked build as failure >>>> Archiving artifacts >>>> Finished: FAILURE >>>> >>>> >>>> >>>> Does anybody have any ideas about where I can look for what would cause this job to fail this way on Linux (OpenSuSE 12.1 with JDK (not OpenJDK)) while the identical job configuration succeeds on OS X. >>>> >>>> >>>> >>>> >>>> >>>> Larry Mills-Gahl >>>> lm...@we... >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Try before you buy = See our experts in action! >>>> The most comprehensive online learning library for Microsoft developers >>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >>>> Metro Style Apps, more. Free future releases when you subscribe now! >>>> http://p.sf.net/sfu/learndevnow-dev2_______________________________________________ >>>> Wonder-disc mailing list >>>> Won...@li... >>>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >>> >>> >>> ------------------------------------------------------------------------------ >>> Try before you buy = See our experts in action! >>> The most comprehensive online learning library for Microsoft developers >>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >>> Metro Style Apps, more. Free future releases when you subscribe now! >>> http://p.sf.net/sfu/learndevnow-dev2 >>> _______________________________________________ >>> Wonder-disc mailing list >>> Won...@li... >>> https://lists.sourceforge.net/lists/listinfo/wonder-disc >>> >> ------------------------------------------------------------------------------ >> Try before you buy = See our experts in action! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-dev2_______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/_______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |
From: Paul H. <pa...@lo...> - 2012-03-02 22:36:03
|
Hi Larry, On 02/03/2012, at 6:13 AM, Larry Mills-Gahl wrote: > I'm betting this is either an over-zealous security configuration (they don't call me "Little Paranoid Larry" for nothing) or a java environment problem. Im will be surprised if it's a Java config thing because this should all run in a defined environment with Jenkins.... but we'll see. Did you sort this out? I'm trying to get Jenkins up on an EC2 instance running Amazon Linux, and I seem to have hit exactly the same problem: no matter what I do, I cannot get Ant to see woproject.jar. I'm not using Dave's scripts, but the setup would be quite similar, based on some quite early versions of the setup scripts. I can't even get Ant to build from the command line from within the workspace. > ant -v -propertyfile Root/wolips.properties -lib Root/lib clean build or even: > ant -v -propertyfile Root/wolips.properties -lib Root/lib/woproject.jar clean build Both fail with: taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found Let me know if you made any progress with this. -- Paul. http://logicsquad.net/ |
From: <pr...@ma...> - 2012-03-02 23:41:42
|
Which version of Ant and Java? Envoyé de mon iPhone Le 2012-03-02 à 17:36, "Paul Hoadley" <pa...@lo...> a écrit : > Hi Larry, > > On 02/03/2012, at 6:13 AM, Larry Mills-Gahl wrote: > >> I'm betting this is either an over-zealous security configuration (they don't call me "Little Paranoid Larry" for nothing) or a java environment problem. Im will be surprised if it's a Java config thing because this should all run in a defined environment with Jenkins.... but we'll see. > > Did you sort this out? I'm trying to get Jenkins up on an EC2 instance running Amazon Linux, and I seem to have hit exactly the same problem: no matter what I do, I cannot get Ant to see woproject.jar. I'm not using Dave's scripts, but the setup would be quite similar, based on some quite early versions of the setup scripts. I can't even get Ant to build from the command line from within the workspace. > >> ant -v -propertyfile Root/wolips.properties -lib Root/lib clean build > > or even: > >> ant -v -propertyfile Root/wolips.properties -lib Root/lib/woproject.jar clean build > > Both fail with: > > taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found > > Let me know if you made any progress with this. > > > -- > Paul. > > http://logicsquad.net/ > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |
From: Paul H. <pa...@lo...> - 2012-03-03 02:29:50
|
Hi Pascal, On 03/03/2012, at 10:11 AM, pr...@ma... wrote: > Which version of Ant and Java? $ ant -version Apache Ant version 1.7.1 compiled on January 18 2011 $ java -version java version "1.6.0_22" OpenJDK Runtime Environment (IcedTea6 1.10.6) (amazon-52.1.10.6.41.amzn1-i386) OpenJDK Client VM (build 20.0-b11, mixed mode) Both just installed with yum (Amazon packages) on a brand new EC2 instance (32-bit Amazon Linux). -- Paul. http://logicsquad.net/ |
From: Paul H. <pa...@lo...> - 2012-03-03 03:42:31
|
On 03/03/2012, at 12:59 PM, Paul Hoadley wrote: > On 03/03/2012, at 10:11 AM, pr...@ma... wrote: > >> Which version of Ant and Java? > > $ ant -version > Apache Ant version 1.7.1 compiled on January 18 2011 > > $ java -version > java version "1.6.0_22" > OpenJDK Runtime Environment (IcedTea6 1.10.6) (amazon-52.1.10.6.41.amzn1-i386) > OpenJDK Client VM (build 20.0-b11, mixed mode) > > Both just installed with yum (Amazon packages) on a brand new EC2 instance (32-bit Amazon Linux). It looks like something like this is sufficient: <path id="lib-classpath"> <fileset dir="Root/lib"> <include name="*.jar"/> </fileset> </path> ... <taskdef name="wocompile" classname="org.objectstyle.woproject.ant.WOCompile" classpathref="lib-classpath" /> Is this a difference between Ant 1.7.1 and 1.8.x? (I'm not sure why Amazon Linux's Ant is lagging back at 1.7.1, or why they can't provide an update.) -- Paul. http://logicsquad.net/ |
From: Pascal R. <pr...@ma...> - 2012-03-03 07:51:58
|
Le 2012-03-02 à 22:42, Paul Hoadley a écrit : > On 03/03/2012, at 12:59 PM, Paul Hoadley wrote: > >> On 03/03/2012, at 10:11 AM, pr...@ma... wrote: >> >>> Which version of Ant and Java? >> >> $ ant -version >> Apache Ant version 1.7.1 compiled on January 18 2011 >> >> $ java -version >> java version "1.6.0_22" >> OpenJDK Runtime Environment (IcedTea6 1.10.6) (amazon-52.1.10.6.41.amzn1-i386) >> OpenJDK Client VM (build 20.0-b11, mixed mode) >> >> Both just installed with yum (Amazon packages) on a brand new EC2 instance (32-bit Amazon Linux). Try with Ant 1.8.2 (from ant.apache.org) and with the Oracle JVM. This is the setup I have and it's working fine without anything special to do. > It looks like something like this is sufficient: > > <path id="lib-classpath"> > <fileset dir="Root/lib"> > <include name="*.jar"/> > </fileset> > </path> > > ... > > <taskdef name="wocompile" classname="org.objectstyle.woproject.ant.WOCompile" classpathref="lib-classpath" /> > > Is this a difference between Ant 1.7.1 and 1.8.x? (I'm not sure why Amazon Linux's Ant is lagging back at 1.7.1, or why they can't provide an update.) > > > -- > Paul. > > http://logicsquad.net/ > > |
From: Paul H. <pa...@lo...> - 2012-03-03 09:53:18
|
On 03/03/2012, at 6:21 PM, Pascal Robert wrote: > Try with Ant 1.8.2 (from ant.apache.org) and with the Oracle JVM. This is the setup I have and it's working fine without anything special to do. Thanks Pascal. It turns out this was an issue, though I am still not 100% sure why. (Does Ant 1.7.1 _really_ ignore the -lib option on the command line, or is something else going on?) In any case, I discovered that Jenkins will auto-install Ant internally (who knew!?), and you can pick any version number you like. Using Ant 1.8.3 does, indeed, solve the problem with no further intervention. Larry—does this fix it for you? What version of Ant are you using? While we're at it, Amazon Linux provides packages for OpenJDK. I'm sure I could get a Sun/Oracle JDK installed if I tried, but it's a lot easier to just use a single "yum install" from the Amazon-supplied package repo. I know there was some aversion to OpenJDK for WebObjects projects at one point—are people still averse to it, and why? (I've never used it. I've been building with Hudson for over a year using OS X's JDK, but I'm interested in out-sourcing this to EC2.) -- Paul. http://logicsquad.net/ |
From: Aaron R. <aa...@ch...> - 2012-03-04 04:21:42
|
Hi WOrriors, Got a FreeBSD VPS up and nearing the final stages of completion to use as a WO app server. I've got wotaskd and JavaMonitor running. The Wonder versions of both of these of course! I'm stuck at the part where I try to add an App via JavaMonitor. I give the exact path to the app but when I try to flip on the frankenstein switch I get: "Path for FamilyCycleGroupOrder-1 does not exist" Funny, when I click the "path wizard" button (which now just says "Path...") I get a screen with no directories. If I click the ".. Back up one directory level" link I get: "Path null does not exist" However... If I kick it to get it going by typing /usr/ in the "Jump to" part and click submit I can navigate all the way to the executable which is: /usr/local/webobjects/Local/Library/WebObjects/Applications/ FamilyCycleGroupOrder.woa/FamilyCycleGroupOrder JavaMonitor is running as an "appserver" user I created. I was careful about making the directories accessible to this user. Out of desperation I added "appserver" to group "wheel" and even rebooted. No effect! I still get the same "path does not exist" error. Can anyone offer guidance? What did I miss? Many thanks, -- Aaron |
From: Chuck H. <ch...@gl...> - 2012-03-04 05:19:45
|
Is it a permissions issue for the use Javamonitor is running as? On Mar 3, 2012, at 7:50 PM, Aaron Rosenzweig <aa...@ch...> wrote: > Hi WOrriors, > > Got a FreeBSD VPS up and nearing the final stages of completion to use > as a WO app server. > > I've got wotaskd and JavaMonitor running. The Wonder versions of both > of these of course! > > I'm stuck at the part where I try to add an App via JavaMonitor. I > give the exact path to the app but when I try to flip on the > frankenstein switch I get: > > "Path for FamilyCycleGroupOrder-1 does not exist" > > Funny, when I click the "path wizard" button (which now just says > "Path...") I get a screen with no directories. If I click the ".. Back > up one directory level" link I get: > > "Path null does not exist" > > However... If I kick it to get it going by typing /usr/ in the "Jump > to" part and click submit I can navigate all the way to the executable > which is: > > /usr/local/webobjects/Local/Library/WebObjects/Applications/ > FamilyCycleGroupOrder.woa/FamilyCycleGroupOrder > > JavaMonitor is running as an "appserver" user I created. I was careful > about making the directories accessible to this user. Out of > desperation I added "appserver" to group "wheel" and even rebooted. No > effect! I still get the same "path does not exist" error. > > Can anyone offer guidance? What did I miss? > > Many thanks, > -- Aaron > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Wonder-disc mailing list > Won...@li... > https://lists.sourceforge.net/lists/listinfo/wonder-disc |
From: Aaron R. <aa...@ch...> - 2012-03-04 15:18:36
|
Hi Chuck, Could it be "NEXT_ROOT" - maybe I need to export that to the path somewhere? When I launch the .woa from the command line I get: > ./FamilyCycleGroupOrder FamilyCycleGroupOrder: NEXT_ROOT environment variable is not set! Reading UNIXClassPath.txt ... Launching FamilyCycleGroupOrder.woa ... I agree with you that not having the right permissions could cause something like this; however, the following had no effect: 1) double checked permissions with: sudo chown -R appserver:appserveradm <<the root of the directory tree>> 2) added "appserver" to group "wheel" out of desperation... Then later removed it. I could have made a goof somewhere with permissions but I'm 99% certain it's something else. Thanks, -- Aaron On Mar 4, 2012, at 12:19 AM, Chuck Hill wrote: > Is it a permissions issue for the use Javamonitor is running as? > > On Mar 3, 2012, at 7:50 PM, Aaron Rosenzweig <aa...@ch...> > wrote: > >> Hi WOrriors, >> >> Got a FreeBSD VPS up and nearing the final stages of completion to >> use >> as a WO app server. >> >> I've got wotaskd and JavaMonitor running. The Wonder versions of both >> of these of course! >> >> I'm stuck at the part where I try to add an App via JavaMonitor. I >> give the exact path to the app but when I try to flip on the >> frankenstein switch I get: >> >> "Path for FamilyCycleGroupOrder-1 does not exist" >> >> Funny, when I click the "path wizard" button (which now just says >> "Path...") I get a screen with no directories. If I click the ".. >> Back >> up one directory level" link I get: >> >> "Path null does not exist" >> >> However... If I kick it to get it going by typing /usr/ in the "Jump >> to" part and click submit I can navigate all the way to the >> executable >> which is: >> >> /usr/local/webobjects/Local/Library/WebObjects/Applications/ >> FamilyCycleGroupOrder.woa/FamilyCycleGroupOrder >> >> JavaMonitor is running as an "appserver" user I created. I was >> careful >> about making the directories accessible to this user. Out of >> desperation I added "appserver" to group "wheel" and even rebooted. >> No >> effect! I still get the same "path does not exist" error. >> >> Can anyone offer guidance? What did I miss? >> >> Many thanks, >> -- Aaron >> >> ------------------------------------------------------------------------------ >> Virtualization & Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> _______________________________________________ >> Wonder-disc mailing list >> Won...@li... >> https://lists.sourceforge.net/lists/listinfo/wonder-disc |
From: Henrique G. <li...@fa...> - 2012-02-28 10:13:38
|
On Feb 27, 2012, at 9:47 PM, Larry Mills-Gahl wrote: >>> >>> /var/lib/jenkins/jobs/VAEO/workspace/Projects/VAEO/build.xml:87: taskdef class org.objectstyle.woproject.ant.WOCompile cannot be found >>> using the classloader AntClassLoader[] >>> >>> (...) >>> >>> Does anybody have any ideas about where I can look for what would cause this job to fail this way on Linux (OpenSuSE 12.1 with JDK (not OpenJDK)) while the identical job configuration succeeds on OS X. >>> >>> >>> Larry Mills-Gahl >>> lm...@we... >>> >>> I always had to explicitly add the woproject.jat to the classpath on hudson/jenkins global settings: > From: Henrique Gomes <li...@fa...> > Subject: Re: [Wonder-disc] Hudson on linux > Date: May 5, 2010 4:26:44 PM GMT+01:00 > To: wonder Project <won...@li...> > > I knew there was something, and I found it on the hudson configure page: > > > Yes, lame. If I recall correctly, I tried to debug it and the -lib command line argument never made it into the classpath of the JVM running ant. Why? Life is just too short, the above configuration solved it without messing any of the build files and settings on my projects. > > HG > |