Re: Can somebody (Hervé?) stage the Doxia 1.5 site

content staged here: http://maven.apache.org/doxia/doxia-archives/doxia-LATEST/ notice I had to tweak m-changes-p version (done in trunk too) and fix manually staging site siince the actual automatic location is wrong: I still need to fix trunk (see MSITE-687) I you can wait a little bit before

maven-wagon pull request: Code cleanup

Github user ebourg closed the pull request at: https://github.com/apache/maven-wagon/pull/8 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org

Re: Can somebody (Hervé?) stage the Doxia 1.5 site

I suppose you did "mvn site-deploy" but for such a multi-module project, you need to use "mvn scm-publish:publish- scm" [1] Notice actual Doxia 1.5 can't be injected into maven-site-plugin because of DOXIA-499 + DOXIASITETOOLS-85 perhaps the class should be readded for compatibility, but marked d

Re: svn commit: r1402867 - /maven/pom/trunk/maven/pom.xml

I'm a trifle swamped, so anyone else who wants to change the pom is welcome to lead this charge. On Wed, Nov 13, 2013 at 1:23 PM, Robert Scholte wrote: > Hi, > > I can confirm that I'm having the same issues as Stephen when releasing but > didn't took the time to figure out the cause: I knew the

Re: svn commit: r1402867 - /maven/pom/trunk/maven/pom.xml

Hi, I can confirm that I'm having the same issues as Stephen when releasing but didn't took the time to figure out the cause: I knew the workaround and thought it had to do with my settings.xml. The issue of the m-release-p for not picking up the profile was fixed in MRELEASE-459 [1], tog

Re: svn commit: r1402867 - /maven/pom/trunk/maven/pom.xml

On Wed, Nov 13, 2013 at 11:33 AM, Stephen Connolly wrote: > The profiles are not being activated... this is why in the asf pom we use > the -P... in the tag Why aren't the profiles activated? Does 'arguments' disable 'releaseProfiles'? > > > On 13 November 2013 16:01, Benson Margulies wrote: >

Re: svn commit: r1402867 - /maven/pom/trunk/maven/pom.xml

The profiles are not being activated... this is why in the asf pom we use the -P... in the tag On 13 November 2013 16:01, Benson Margulies wrote: > On Wed, Nov 13, 2013 at 10:54 AM, Stephen Connolly > wrote: > > On 27 October 2012 22:00, wrote: > > > >> Author: bimargulies > >> Date: Sat Oct

Can somebody (Hervé?) stage the Doxia 1.5 site

WARNING: Going to buffer response body of large or unknown size. Using getResponseBodyAsStream instead is recommended. [INFO] Downloading from JIRA at: http://jira.codehaus.org/secure/IssueNavigator.jspa?view=rss&pid=10780&statusIds=6&resolutionIds=1&sorter/field=issuekey&sorter/order=ASC&tempMax=

Re: Defective Nov 5 upload to Maven central of Eclipse artifacts broke our build

On 11/13/2013 10:21 AM, Arnaud Héritier wrote: > I had a similar issue but I solved it by removing some JBoss repositories > Are you sure that the problem is in central ? Not sure. It's found by this website: http://search.maven.org/remotecontent?filepath=org/eclipse/core/runtime/3.9.0-v20130326-

Re: svn commit: r1402867 - /maven/pom/trunk/maven/pom.xml

On Wed, Nov 13, 2013 at 10:54 AM, Stephen Connolly wrote: > On 27 October 2012 22:00, wrote: > >> Author: bimargulies >> Date: Sat Oct 27 21:00:24 2012 >> New Revision: 1402867 >> >> URL: http://svn.apache.org/viewvc?rev=1402867&view=rev >> Log: >> MPOM-38: Enable RAT to help us get maven release

Re: svn commit: r1402867 - /maven/pom/trunk/maven/pom.xml

On 27 October 2012 22:00, wrote: > Author: bimargulies > Date: Sat Oct 27 21:00:24 2012 > New Revision: 1402867 > > URL: http://svn.apache.org/viewvc?rev=1402867&view=rev > Log: > MPOM-38: Enable RAT to help us get maven releases to be license-header > compliant > o Also configure the release plu

Re: Defective Nov 5 upload to Maven central of Eclipse artifacts broke our build

I had a similar issue but I solved it by removing some JBoss repositories Are you sure that the problem is in central ? On Wed, Nov 13, 2013 at 3:57 PM, Marshall Schor wrote: > Hi, > > First, apologies if this is not the right mailing list for Maven Central > issues... > > On Nov 5, someone up

Defective Nov 5 upload to Maven central of Eclipse artifacts broke our build

Hi, First, apologies if this is not the right mailing list for Maven Central issues... On Nov 5, someone uploaded to Maven Central some new versions of Eclipse artifacts. In particular, they uploaded: org.eclipse.core : runtime : 3.9.0-v20130326-1255 and org.eclipse.equinox: app : 1.3.100-v

Re: Anyone object to a Doxia 1.5 release being cut?

OK, I'm fed up waiting *Gold Leader:* Red Leader, This is Gold Leader. We're starting our attack run. On 13 November 2013 09:47, Stephen Connolly wrote: > I'd really like to get the DOXIA-472 support out so that we can actually > use markdown for documentation that has the set... > > If a

maven-plugin-testing pull request: Upgrade the dependency on Easymock to 3....

GitHub user ebourg opened a pull request: https://github.com/apache/maven-plugin-testing/pull/2 Upgrade the dependency on Easymock to 3.2 The `MockControl` class used by `MockManager` in the maven-test-tools artifact has been removed from EasyMock starting with version 3.0. This pat

maven-wagon pull request: Code cleanup

GitHub user ebourg opened a pull request: https://github.com/apache/maven-wagon/pull/8 Code cleanup Here is a patch performing minor code improvements (foreach loops, generics, unused imports, StringBuilders, etc) You can merge this pull request into a Git repository by running:

Re: Anyone know why Doxia treats H1 as an "unknown" event and H2 as "section_level_1"?

No I think that it is that Doxia is kind of expecting that you only have one H1 in your document and that is for the title... of course it doesn't actually use it for the title The H1 gets generated by the output sinks... but it just does not get the hyperlinking targets set... On 13 November 20

Re: Anyone know why Doxia treats H1 as an "unknown" event and H2 as "section_level_1"?

On 13 November 2013 19:56, Lukas Theussl wrote: > > Hi Stephen, > > The Sink API only knows 5 section levels, which in html are mapped to - > : http://jira.codehaus.org/browse/DOXIA-203 Probably from a typography point of view H1 is junk (http://practicaltypography.com/point-size.html) and every

Anyone object to a Doxia 1.5 release being cut?

I'd really like to get the DOXIA-472 support out so that we can actually use markdown for documentation that has the set... If anyone has anything they feel really needs to be added... shout out... likely I'll pull the trigger in a couple of hours anyway... but as most of the doxia committers are

Re: Anyone know why Doxia treats H1 as an "unknown" event and H2 as "section_level_1"?

Hi Stephen, The Sink API only knows 5 section levels, which in html are mapped to - : http://jira.codehaus.org/browse/DOXIA-203 HTH, -Lukas Am 13.11.2013 10:13, schrieb Stephen Connolly: http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-core/src/main/java/org/apache/maven/doxia/p

Re: [ANN] Maven Jarsigner 1.1 Released

On Tue, 12 Nov 2013 23:59:06 +0100 Tony Chemit wrote: > The Maven team is pleased to announce the release of the Maven JArsigner, > version 1.1 > > This component provides some utilities to sign/verify jars/files in your > Mojos. > > http://maven.apache.org/shared/maven-jarsigner/ > > To us

Anyone know why Doxia treats H1 as an "unknown" event and H2 as "section_level_1"?

http://svn.apache.org/viewvc/maven/doxia/doxia/trunk/doxia-core/src/main/java/org/apache/maven/doxia/parser/XhtmlBaseParser.java?view=markup#l413 Seems strange to me... but perhaps there is a good reason...