Re: .asc.asc files

Hi Jochen, On 04/12/16 15:14, Jochen Wiedmann wrote: Hi, trying to deploy a release to Nexus, I end up with files commons-fileupload-1.3.3-bin.tar.gz.asc.asc.asc.asc. What I did: cd target/checkout (Directory created by mvn release:perform) mvn -Prealease -Papache-release clean site

Re: .asc.asc files

On Sun, Dec 4, 2016 at 3:29 PM, Karl Heinz Marbaise wrote: > mvn -Prelease -Papache-release clean site deploy > > is sufficient... Thanks very much, Karl-Heinz. I certainly hope to keep that in mind. Nevertheless, I do think that the plugin (which?) should be clever enough

Download & Caching Text Artifacts (XML schema) with Maven

Hi, In the Apache ODF Toolkit (incubating) project we are generating Java classes from the ODF XML schema. For this reason, we need to download the OASIS ODF XML schema, as Apache does not allow to have unchangeable artifacts within the source repository. On the other hand, I would love to build

Re: Download & Caching Text Artifacts (XML schema) with Maven

Svante, I bet that problem isn't 'unchangeable', but rather the license. Anyway, it's easy to do what you want. Read http://central.sonatype.org/pages/ossrh-guide.html. You will probably want to put the schema into a zip or tar file, though you can leave it 'naked'. You set up a github.com

.asc.asc files

Hi, trying to deploy a release to Nexus, I end up with files commons-fileupload-1.3.3-bin.tar.gz.asc.asc.asc.asc. What I did: cd target/checkout (Directory created by mvn release:perform) mvn -Prealease -Papache-release clean site install deploy Any ideas, what's wrong? And (so I can

Re: ${project.parent.parent.version} does not work

Hello, For now, you can make that property a constant in the grandparent like "1.0.0-SNAPSHOT" and use that property itself in the grandparent like "${grandparent.version}". Should not override that property in modules, of course. But that would require me to always update that property

Re: ${project.parent.parent.version} does not work

versions:update-property seems like a good choice. Sent from my iDevice > On Dec 4, 2016, at 8:22 AM, Florian Schätz wrote: > > Hello, > >> For now, you can make that property a constant in the grandparent like >> "1.0.0-SNAPSHOT" and use that >> property itself in

Re: Need to fully understand bad implications of combined aggregator and parent pom

Indeed, combining the parent and aggregator concerns in one POM is not a good idea. I would go so far as to call it an anti-pattern. A very common one, unfortunately. First, you get a cycle per module. Cycles are never a good thing, though sometimes they are unavoidable. Maven seems to be fine