Build failed in Jenkins: doxia-sitetools » JDK 1.5 (latest),osx #64

See https://builds.apache.org/hudson/job/doxia-sitetools/./jdk=JDK%201.5%20(latest),label=osx/64/changes Changes: [dennisl] [maven-release-plugin] prepare for next development iteration [dennisl] [maven-release-plugin] prepare release doxia-sitetools-1.2 [dennisl] o Use released (staged)

Build failed in Jenkins: doxia-sitetools » JDK 1.5 (latest),Solaris #64

See https://builds.apache.org/hudson/job/doxia-sitetools/./jdk=JDK%201.5%20(latest),label=Solaris/64/changes Changes: [dennisl] [maven-release-plugin] prepare for next development iteration [dennisl] [maven-release-plugin] prepare release doxia-sitetools-1.2 [dennisl] o Use released (staged)

Build failed in Jenkins: doxia-sitetools » JDK 1.5 (latest),Ubuntu #64

See https://builds.apache.org/hudson/job/doxia-sitetools/./jdk=JDK%201.5%20(latest),label=Ubuntu/64/changes Changes: [dennisl] [maven-release-plugin] prepare for next development iteration [dennisl] [maven-release-plugin] prepare release doxia-sitetools-1.2 [dennisl] o Use released (staged)

Re: Need help getting our plugins to build successfully in Jenkins

Benson Margulies skrev 2011-04-25 22:48: fix the tests to have a catalog to point to local copies Yes, it is always best to use local copies of DTDs and XSDs for tests, but in this case that would be difficult to do. We are testing to see that the generated deployment descriptor matches the

CI for the Maven project

Hi Over the last weeks I've been adding and configuring our various sub projects on the ASF Jenkins instance in the Maven view [1]. I've also renamed a couple of the jobs that was already there, trying to establish a common naming convention for the jobs. For a normal project job the name of the

Re: CI for the Maven project

+1 LieGrue, strub --- On Tue, 4/26/11, Dennis Lundberg denn...@apache.org wrote: From: Dennis Lundberg denn...@apache.org Subject: CI for the Maven project To: Maven Developers List dev@maven.apache.org Date: Tuesday, April 26, 2011, 6:02 PM Hi Over the last weeks I've been adding and

Re: CI for the Maven project

+1 -- Olivier Le 26 avr. 2011 20:02, Dennis Lundberg denn...@apache.org a écrit : Hi Over the last weeks I've been adding and configuring our various sub projects on the ASF Jenkins instance in the Maven view [1]. I've also renamed a couple of the jobs that was already there, trying to

Re: CI for the Maven project

Dennis Lundberg wrote: Hi Over the last weeks I've been adding and configuring our various sub projects on the ASF Jenkins instance in the Maven view [1]. I've also renamed a couple of the jobs that was already there, trying to establish a common naming convention for the jobs. For a normal

Re: Need help getting our plugins to build successfully in Jenkins

Then use a resolver to do the check instead of actually fetching? On Tue, Apr 26, 2011 at 1:30 PM, Dennis Lundberg denn...@apache.org wrote: Benson Margulies skrev 2011-04-25 22:48: fix the tests to have a catalog to point to local copies Yes, it is always best to use local copies of DTDs and

Re: Need help getting our plugins to build successfully in Jenkins

Hi, The problem here is that the actual fetching is done inside XmlUnit, which is only a tool we use to assert that the generated deployment descriptor is equal to the expected one. Do you know if it's possible to tell XmlUnit to *not* fetch the DTDs? I haven't used XmlUnit myself, I'm only

Re: CI for the Maven project

+1 Arnaud Le 26 avr. 2011 à 20:02, Dennis Lundberg denn...@apache.org a écrit : Hi Over the last weeks I've been adding and configuring our various sub projects on the ASF Jenkins instance in the Maven view [1]. I've also renamed a couple of the jobs that was already there, trying to

Re: Need help getting our plugins to build successfully in Jenkins

Tell me an svn url and I'll see what I can patch. On Tue, Apr 26, 2011 at 3:24 PM, Dennis Lundberg denn...@apache.org wrote: Hi, The problem here is that the actual fetching is done inside XmlUnit, which is only a tool we use to assert that the generated deployment descriptor is equal to the

[JIRA] Request for new JIRA project for Doxia Tools

Hi Can someone with JIRA karma please create a new project for Doxia Tools with the key DOXIATOOLS. The URL to Doxia Tools is http://maven.apache.org/doxia/doxia-tools/index.html -- Dennis Lundberg - To unsubscribe, e-mail:

Re: Need help getting our plugins to build successfully in Jenkins

job done in r1096914 - http://svn.apache.org/viewvc?rev=1096914view=rev you can build the document yourself instead of letting XmlUnit build it from the InputStream Regards, Hervé Le mardi 26 avril 2011, Benson Margulies a écrit : Tell me an svn url and I'll see what I can patch. On Tue,

Re: [JIRA] Request for new JIRA project for Doxia Tools

Do we continue to create them @ codehaus ? I remember we discussed about Apache's Jira usage but I don't remember if we decided something ? On Tue, Apr 26, 2011 at 11:06 PM, Dennis Lundberg denn...@apache.orgwrote: Hi Can someone with JIRA karma please create a new project for Doxia Tools

[VOTE] Release Doxia 1.2 and Doxia Sitetools 1.2

Hi, We solved 5 + 15 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10780version=14082styleName=Html http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11624version=16990styleName=Html Note: 3 issues about the Link Checker in the Doxia Release Notes really belong to

Re: [JIRA] Request for new JIRA project for Doxia Tools

aherit...@gmail.com skrev 2011-04-26 23:21: Do we continue to create them @ codehaus ? Good question. I remember we discussed about Apache's Jira usage but I don't remember if we decided something ? Yes there were some discussions, but IIRC people didn't want to move to ASF JIRA because it

Re: [JIRA] Request for new JIRA project for Doxia Tools

Thus for short term and doxia tools you want it @ codehaus ? Le 27 avr. 2011 à 00:11, Dennis Lundberg denn...@apache.org a écrit : aherit...@gmail.com skrev 2011-04-26 23:21: Do we continue to create them @ codehaus ? Good question. I remember we discussed about Apache's Jira usage but I

Re: [JIRA] Request for new JIRA project for Doxia Tools

Arnaud Héritier skrev 2011-04-27 00:46: Thus for short term and doxia tools you want it @ codehaus ? Yes please. Le 27 avr. 2011 à 00:11, Dennis Lundberg denn...@apache.org a écrit : aherit...@gmail.com skrev 2011-04-26 23:21: Do we continue to create them @ codehaus ? Good question.

Re: Article proposed for Maven Article Page

On Tue, Apr 26, 2011 at 3:42 AM, xanadu72 surs...@gmail.com wrote: Barrie, I know that Eclipse is able to import a hierarchical structure but i have a concern with Subversion. The recommended structure for Subversion is using trunk,tags,branches subfolders. Is it compatible with the following

Re: [JIRA] Request for new JIRA project for Doxia Tools

http://jira.codehaus.org/browse/DOXIATOOLS Sorry for the delay Arnaud On Wed, Apr 27, 2011 at 1:11 AM, Dennis Lundberg denn...@apache.org wrote: Arnaud Héritier skrev 2011-04-27 00:46: Thus for short term and doxia tools you want it @ codehaus ? Yes please. Le 27 avr. 2011 à 00:11,

Re: [JIRA] Request for new JIRA project for Doxia Tools

Thanks Arnaud! I just moved 3 issues from DOXIA to DOXIATOOLS but I don't see how to create versions or components for DOXIATOOLS. Am I missing something? -Lukas aherit...@gmail.com wrote: http://jira.codehaus.org/browse/DOXIATOOLS Sorry for the delay Arnaud On Wed, Apr 27, 2011 at