Re: maven release-plugin 2.5 bug - releasing snapshots...

> So if I understand correctly you want to use SNAPSHOTs because: > - you don't want the artifact to end up in the "releases"-repository yes, correct > because QA needs to be done first Not quite - occasionally projects (still in development state but nearing its end) engage formal internal te

Re: doxia-module-markdown 1.5 mixing html and markdown in one file

Just a quick follow up on that: Are there already plans to release a bugfix version (or maybe 1.6) of the module? Thanks! Raphael On Thu, Feb 27, 2014 at 1:40 PM, Raphael André Bauer wrote: > kk. You already fixed the issue. Awesome. Thanks a lot! > > Cheers, > > > Raphael > > On Thu, Feb 27, 2

Any workaround for SCM-530

Hi, I'm importing external test resources as a git submodule (in src/test/resources) and that makes release:perform fail because my test doesn't find its data. This is because the git clone doesn't check the submodules out. Anyone would know (or imagine) a workaround? (as a last resort, I'll copy

Re: Javadoc plugin with Javadoc 8: error fetching URLs

On Fri, Mar 28, 2014 at 2:32 PM, Laird Nelson wrote: > Thanks; already got the -Xdoclint:none bit; will keep looking when I'm > back at my computer. > > On Friday, March 28, 2014, Baptiste Mathus wrote: > >> Just a guess: Maven basically only delegates to the javadoc tool provided >> by the JDK.

Re: Javadoc plugin with Javadoc 8: error fetching URLs

Thanks; already got the -Xdoclint:none bit; will keep looking when I'm back at my computer. On Friday, March 28, 2014, Baptiste Mathus wrote: > Just a guess: Maven basically only delegates to the javadoc tool provided > by the JDK. Did you try without Maven? > Java 8's javadoc has been added a m

Re: OutOfMemoryError with maven-javadoc-plugin

On 28 Mär 2014, Justin Georgeson wrote: > The maven-javadoc-plugin has a maxmemory configuration parameter. In my > parent POM I set a default property docs.maxMemory and then configure > maven-javadoc-plugin with > > ${docs.maxMemory} > > So each team can override that default setting in thei

Re: OutOfMemoryError with maven-javadoc-plugin

Hi Ron! On 28 Mär 2014, Ron Wheeler wrote: > Have you tried increasing the JVM memory past > > MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" > MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m" > > You could try something extreme (-Xmx8g ) and see if that changes anything. Well, I sho

Re: Javadoc plugin with Javadoc 8: error fetching URLs

Just a guess: Maven basically only delegates to the javadoc tool provided by the JDK. Did you try without Maven? Java 8's javadoc has been added a much more stringent parser, so you might be encountering http://blog.joda.org/2014/02/turning-off-doclint-in-jdk-8-javadoc.html ? 2014-03-28 22:15 GMT

Javadoc plugin with Javadoc 8: error fetching URLs

Running a few of my projects under Java 8, I found that the maven-javadoc-plugin won't accept configuration items that work under Javadoc 6. For example, I have this: http://mvel.codehaus.org/javadoc/2.0 With Javadoc 8 installed, whatever the maven-javadoc-plugin is doing to feed this URL to j

Re: maven release-plugin 2.5 bug - releasing snapshots...

> Let me join this thread, because that "someone" is me. As said by Stephen: > the version handling prior to 2.4 contained several issues, so you were > relying on a bug. Reminds me of this classic XKCD... :) https://xkcd.com/1172/ Wayne --

Re: multi-module phases sequence

I actually do not disagree, as I in fact do not see a "fault" here (in the sense of "someone did it wrong"). Maven simply seems to be designed in a way that simply cannot do what I need. So I would certainly love to see a declarative solution. But I won't say it is a "fault". More a "missing featur

Re: maven release-plugin 2.5 bug - releasing snapshots...

Hi, Let me join this thread, because that "someone" is me. As said by Stephen: the version handling prior to 2.4 contained several issues, so you were relying on a bug. This has all been done as part of MRELEASE-511[1] and related issues. There is no such thing as a "formal SNAPSHOT": it's a

Re: maven release-plugin 2.5 bug - releasing snapshots...

release:branch -> yes, release:prepare -> no On 28 March 2014 13:49, James Nord (jnord) wrote: > shouldn't release:branch still support this still though? > > If not that's bad as you will end up with a release version on the head of > either the source branch or the new branch (and both should

Re: maven release-plugin 2.5 bug - releasing snapshots...

So if I understand correctly you want to use SNAPSHOTs because: - you don't want the artifact to end up in the "releases"-repository yes, because QA needs to be done first - SNAPSHOTs are cleaned up automatically, so if QA doesn't accept a release, it's cleaned up for you. The SNAPSHOT usage

Re: maven release-plugin 2.5 bug - releasing snapshots...

Fully agree but with a snapshot not should be treated an release. The concept of "official snapshots" along with full site info and branch tagging don't seem wrong where I come from. If a project going through some stringent QA where formal test teams want to keep track of what they testing agains

Re: Overriding dependency scope

IIUC, you have a unique parent pom (likely a "corporate pom"), let's can him P. P says scope is test for groovy-all. You have modules m1, m2... who all inherits P. In some module mN, you need groovy-all with scope compile. But m1 actually depends on mN and will crash since the dependency onto gr

Re: Overriding dependency scope

Alexander, AFAIK you may override the scope in the inheriting poms. If I remember correctly I did this with junit as I needed it for an selenium test project, where I had put base tests beneath src/main (to recite Brecht: oh, don't ask why). Regards Mirko -- Sent from my mobile On Mar 28, 2014 2

RE: OutOfMemoryError with maven-javadoc-plugin

The maven-javadoc-plugin has a maxmemory configuration parameter. In my parent POM I set a default property docs.maxMemory and then configure maven-javadoc-plugin with ${docs.maxMemory} So each team can override that default setting in their pom.xml if they have an unusually large codebase, or

RE: maven release-plugin 2.5 bug - releasing snapshots...

shouldn't release:branch still support this still though? If not that's bad as you will end up with a release version on the head of either the source branch or the new branch (and both should be used for ongoing development so should be snapshots...) /James > -Original Message- > From

Re: maven release-plugin 2.5 bug - releasing snapshots...

Doing it as I explained did NOT allow you to do a release or refer to it within other resources during a legic release phase What you triggered was a release (as if legit) to go into the snapshot repo - cant see any issues with that kind of behavior and have turned out to be very useful when imple

Overriding dependency scope

I have a situation as follows: - Multi-module project (~30 modules) - Certain test dependencies (e.g. groovy-all) needed by nearly all sub-modules are declared directly with test scope in the parent POM (not just dependencyManagement, but also dependency). I know this is considere

Re: maven release-plugin 2.5 bug - releasing snapshots...

Let me rephrase. The release plugin is designed to make release versions. It is not designed to make -SNAPSHOT versions. It was a bug that it let you specify a -SNAPSHOT version as the release version. The bug has been fixed. On 28 March 2014 13:18, ghostwolf59 wrote: > That's a way to general s

Re: OutOfMemoryError with maven-javadoc-plugin

Yes I did. If I tried without "-J" I got some error. On 28 Mär 2014, Baptiste Mathus wrote: > Did you make sure you put -J-Xmx and not only -Xmx ? > > > 2014-03-28 12:24 GMT+01:00 Martin Hoeller : > > > Hi Baptiste! > > > > I tried it but it didn't change anything. Still OutOfMemoryError :( >

Re: OutOfMemoryError with maven-javadoc-plugin

Did you make sure you put -J-Xmx and not only -Xmx ? 2014-03-28 12:24 GMT+01:00 Martin Hoeller : > Hi Baptiste! > > I tried it but it didn't change anything. Still OutOfMemoryError :( > > -martin > > On 28 Mär 2014, Baptiste Mathus wrote: > > > Sorry, I haven't used javadoc for years now, but as

Re: maven release-plugin 2.5 bug - releasing snapshots...

That's a way to general statement to be made - that also is incorrect ! A snapshot is not allowed for final release - but could still be released into a shapshot repo for test purposes ! The question really bogs down to how much control you'd like to have against a release snapshot. Anyone can

Re: OutOfMemoryError with maven-javadoc-plugin

Have you tried increasing the JVM memory past MAVEN_OPTS="-Xmx1536m -Xms512m -XX:MaxPermSize=512m" MAVEN_OPTS="-Xmx1280m -Xms256m -XX:MaxPermSize=768m" You could try something extreme (-Xmx8g ) and see if that changes anything. -Xms512m is not very useful in this case and you can omit it or mak

Re: maven release-plugin 2.5 bug - releasing snapshots...

You do know you are not allowed to release a version containing a -SNAPSHOT don't you? On 28 March 2014 12:23, ghostwolf59 wrote: > Sorry for that - I was just in the process of updating this a simple > copy/paste mistake > > I am using 2.5 when the problem occur - as illustrated on the imag

Re: maven release-plugin 2.5 bug - releasing snapshots...

Sorry for that - I was just in the process of updating this a simple copy/paste mistake I am using 2.5 when the problem occur - as illustrated on the image below As you can see the prompt "What is

Re: maven release-plugin 2.5 bug - releasing snapshots...

On 28 March 2014 11:12, ghostwolf59 wrote: > 2.2.2 Then you are not using version 2.5

Re: OutOfMemoryError with maven-javadoc-plugin

Hi Baptiste! I tried it but it didn't change anything. Still OutOfMemoryError :( -martin On 28 Mär 2014, Baptiste Mathus wrote: > Sorry, I haven't used javadoc for years now, but as javadoc is an external > tool, I guess you should specify additionalJOption? > http://maven.apache.org/plugins/ma

Re: maven release-plugin 2.5 bug - releasing snapshots...

I don't think this issue have been rectified. The maven release plugin I use (downloaded from maven central via my plugin) is as follows... This fail: org.apache.maven.plugins maven-release-plugin

Re: maven release-plugin 2.5 bug - releasing snapshots...

Weird, many users reported the 2.5 had fixed their issues. What (version) are you actually using for: * maven * maven-release-plugin (triple-check you hadn't redefined maven-scm-* dependency somewhere) * svn ? Git ? Something else ? On a unrelated subject : issuing a "mvn clean install deploy" co

Re: OutOfMemoryError with maven-javadoc-plugin

Sorry, I haven't used javadoc for years now, but as javadoc is an external tool, I guess you should specify additionalJOption? http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalJOption Cheers 2014-03-28 10:36 GMT+01:00 Martin Hoeller : > Hi! > > I have a quite lar

maven release-plugin 2.5 bug - releasing snapshots...

Hi,Occasionally we have a need to perform a formal release on unfinished work so it can be tracked.These snapshot releases would in effect be releases identical to a formal release with the exception that the snapshot for a set release is tagged with a time stamp when released into archiva's snapsh

OutOfMemoryError with maven-javadoc-plugin

Hi! I have a quite large multimodule project with >150 modules. When executing "mvn site" the maven-javadoc-plugin is executed with default configuration. After some time of execution it fails in "aggregate" goal and I get a Exception in thread "main" java.lang.OutOfMemoryError: GC overhead lim

Re: multi-module phases sequence

Well, we clearly disagree on whose "fault" it is at least. Declarative inputs and outputs also help with incremental builds (exactly what Takari built, but only serves within a plugin to know whether it should do real work or just be a no-op). Le 28 mars 2014 08:35, "mkarg" a écrit : > Now I unde

Re: multi-module phases sequence

Now I understand. The problem is that Maven does not know upfront that a plugin *might* possibly produce an artifact. That is correct, obviously, and thank you for pointing me to that fact. So actually the only "correct" solution would be to write a set of plugins and a workflow, e. g. a "PowerBui