IIUC your findings are summed up here:
http://maven.apache.org/plugins/maven-site-plugin/faq.html#Use_of_url
HTH,
-Lukas
On 05/23/2013 04:24 AM, Dan Rollo wrote:
Well, I never saw a response to this, and finally got tired of the missing
'parent' links in maven generated sites.
At some
Thanks Roger,
I'll give it a go and let you know.
Andy.
On 22.05.2013 17:47, Roger Brechbühl wrote:
Hi Andy
Have a look here:
https://github.com/rotscher/emerging
On the branches there is the latest version. Should work but is not yet
released.
Let me know when you need support.
Cheers,
[Note: this entire post deals with project layouts where it is
undesired for modules to know in what filesystem directory their
parent module resides. This rules out relying on Maven parent
found in parent directory or through the relativePath element.]
Maven 3 will throw a Non-resolvable
On Wed, May 22, 2013 at 2:39 AM, Baptiste MATHUS m...@batmat.net wrote:
Hi,
From the usage page, though not perfectly thoroughly definitely clearly
stated ;) and.from my understanding it's said only this property is to go
in this file.
Actually, this plugin is more designed to create
OK, So it's along the lines of what I'd like to do, but for the one drawback mentioned in the blog
http://diplingfh.blogspot.ch/2013/02/how-has-our-release-process-matured.html that is *the *drawback.
Our project uses several of the dependent modules, and so the version override has to be
I'd think this would be better suited for the maven developers list…
But it seems to me that in the case where modules are not supposed to know
where their parents are located, the working assumption is that the parent is
already in the repo and built separately.
That is, there are two cases:
OK, never mind - I found it. I needed to add the maven-plugin-plugin.
Thanks,
Russ
On May 23, 2013, at 12:10 PM, Russell Gold r...@gold-family.us wrote:
Hi,
I saw a previous discussion of this that seemed to be debian-specific. I am
building now on MacOS X and deliberately trying to
The Android Maven Plugin team is pleased to announce the release of
version 3.6.0 of the plugin.
This is another LARGE release with new support for the latest Android SDK
Version 22.0 released last week at Google IO as well as a number of new
features and bug fixes:
CI builds are now running on
Have you seen the two additional branches apart from master? There I
resolved the mentioned drawback (and added another version number
generation strategy) but not yet released them. I'd be interested if it
works.
Cheers,
Roger
Am 23.05.2013 17:39 schrieb Andy andy.gumbre...@orprovision.com:
Have you seen the two additional branches apart from master? There I
resolved the mentioned drawback (and added another version number
generation strategy) but not yet released them. I'd be interested if it
works.
Cheers,
Roger
Am 23.05.2013 17:39 schrieb Andy andy.gumbre...@orprovision.com:
Was on my mobile phone before, so here some more information and links:
Check
https://github.com/rotscher/emerging/tree/version.override-with_maven_install-2.4where
the overridden version is replaced in a copy of the pom.xml which
then gets installed to the local maven repo. I never checked how
I'm trying to make the point that Maven 2 had the expected
behaviour, and Maven 3 changed that into something less
good. As far as I can read the motivation, it seems to have
been done for the wrong reason.
But it's quite likely I'm missing something, and that a
better motivation may be found
Only the developers could say for sure, but I would guess that it was done as
part of code cleanup - that it's not so much that they wanted to remove the
feature as it was that cleaning up the code might have made it hard to support
the feature - and there was no particular reason to keep it.
You're missing my point. You should specify hte version as 5.9-OV.1 (notice
the dash and not a dot). OV.1 being a qualifier. This is best practice as
it will work much better with Maven-related tools sorting the different
versions.
On Thu, May 23, 2013 at 5:39 PM, Andy
14 matches
Mail list logo
