Hi,
Out of curiosity, why don't you use the seemingly equivalent mojo
buildnumber maven plugin? May not be your issue, but may be the plugin
you're using doesn't create properties in the right way (no offense, just
trying to guess)?
My 2 cents
Le 23 mars 2014 22:37, Henrik Østerlund Gram
Couldn't you set up a tailored release job in your CI server. Then you
would had handle authorizations there?
This is somehow what we do. And developers all have the same settings.xml
file.
HTH
Le 24 mars 2014 00:34, ghostwolf59 martin.cederv...@commerce.wa.gov.au
a écrit :
Hi,
I am a strong
The Apache Maven team is pleased to announce the release of the
maven-shared-utils, version 0.6
This project aims to be a functional replacement for
{{{http://plexus.codehaus.org/plexus-utils}plexus-utils}} in Maven.
It is not a 100% API compatible replacement though but a replacement
with
The Maven team is pleased to announce the release of the Apache Maven
Jarsigner,
version 1.3.2
This component provides some utilities to sign/verify jars/files in your Mojos.
http://maven.apache.org/shared/maven-jarsigner/
To use the Maven Jarsigner, add the following dependency to your
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.3.2.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant
The one at
http://mojo.codehaus.org/buildnumber-maven-plugin/create-mojo.html ? It
states in the first couple of lines that it only works with subversion and
I'm using git.
Aside from that, I can't really see why it would make a difference; how
many ways are there to set properties? I did
It doesn't matter which plugin you use to set the property. What does
matter is when the property substitution takes place. It normally happens
in the very beginning of the Maven build when the pom is read, before the
build lifecycle is executed and way before your plugin is executed. So you
need
We started using multi-module project for the first time and notice strange
behaviour. We hope that some experienced user can tell us how to proceed.
There is one multi-module project where module 1 is dependend on module 2.
Module 1 uses assembly plugin in the package phase to produce the final
On Mon, Mar 24, 2014 at 9:40 AM, mkarg k...@quipsy.de wrote:
We started using multi-module project for the first time and notice strange
behaviour. We hope that some experienced user can tell us how to proceed.
There is one multi-module project where module 1 is dependend on module 2.
Module
Hi,
the vote has passed with the following results:
+1 (binding):
Hervé Boutemy,
Olivier Lamy,
Kristian Rosenvold,
Stephen Connolly,
Stephane Nicoll,
+1 (non binding):
Mirko Friedenhagen,
Jason van Zyl,
Toni Chemit,
Anders Hammar,
Dominik
Hi,
There is one multi-module project where module 1 is dependend on module 2.
Module 1 uses assembly plugin in the package phase to produce the final
artifact (zip file). Modul 2 uses dependency plugin in the generate-source
phase to unpack that artifact (zip file).
Using dependency plugin
Ok, I see.
Any chance of such a change making it into the official ear-plugin? I
think it would be generally useful to be able to reference properties in
the env-entry values. Could post a pull request if desired, but judging by
the months old ones at
The multi-module project is for a PowerBuilder project.
Module 1 is building a ZIP file containing lots of resources (GIFs etc.)
taken from somewhere (e. g. from a CIFS drive, a Maven repo, whatever
place the designers store them) which are used by other modules (sibling
modules but also stand
Hi Henrik,
FYI, my projects use buildnumber-maven-plugin with git and it works great.
Probably the docs are just out of date.
Regards,
Curtis
On Mar 24, 2014 3:05 AM, Henrik Østerlund Gram henrik.g...@gmail.com
wrote:
The one at
I use the dependency plugin this way constantly. I also have to tell
people to give on 'mvn test', at least in 3.0.4, and stick to 'mvn
install'.
Maven builds do many more things than put java classes into jar files.
Frequently, they bundle up archives of various other things, and then
unbundle
Hi,
sorry i missed Robert Scholte +1 (binding)...
Kind regards
Karl-Heinz Marbaise
On 3/24/14 12:11 PM, Karl Heinz Marbaise wrote:
Hi,
the vote has passed with the following results:
+1 (binding):
Hervé Boutemy,
Olivier Lamy,
Kristian Rosenvold,
Stephen Connolly,
Hi,
Hi Henrik,
FYI, my projects use buildnumber-maven-plugin with git and it works great.
Probably the docs are just out of date.
That looks like. I have created the following JIRA ticket for this.
https://jira.codehaus.org/browse/MBUILDNUM-119
If you have supplementals/infos etc. don't
Le 24 mars 2014 12:19, Karl Heinz Marbaise khmarba...@gmx.de a écrit :
Hi,
There is one multi-module project where module 1 is dependend on module
2.
Module 1 uses assembly plugin in the package phase to produce the final
artifact (zip file). Modul 2 uses dependency plugin in the
Please read my answer to a similar question on Stack Overflow:
http://stackoverflow.com/questions/14725197/reading-properties-file-from-pom-file-in-maven/14727072#14727072
On 23 March 2014 21:36, Henrik Østerlund Gram henrik.g...@gmail.com wrote:
I stumbled over some rather strange behaviour
Herve,
I'm looking at trying to add this functionality to maven-dependency-tree
but I want to start with a unit test showing the failure. But there doesn't
seem to be any unit tests for the DependencyGraphBuilder (for any
environment).
What's the best way to create a unit test that sets up the
Thanks for the link. It was quite informative, but I'm again a little
confused because it is stated in your explanation,
the configuration sections will have mojo-injected properties evaluated,
but that isn't the case in my example. I was trying to have such
properties evaluated in a envEntries
you hit the problem I faced when doing magic for multi-Maven versions
compatibility: I didn't figure out how to have tests inside the component
itself
or it would need ITs (through m-invoker-p), but requires to write a plugin
that uses the API then a pom that uses the plugin: too much
the way
22 matches
Mail list logo
