I am absolutely agree with your opinion that unreproducability of build is a
bad feature, but ...
1. Maven has a built-in mechanism of dependency version range
I don't like to use version ranges and I agree that it is evil.
This is just example that it is possible.
I just want to use the latest version from full dependency tree. This is
absolutely reproducable. Do you agree with that?
Now I set version of A in D each time some middle artifact is
I don't need to make maven use A version that is inherited from C exactly.
I want Maven to define the latest version automatically, without explicit
definition.
And I don't want to release new version of B only to fix it's A version.
A:1.0 is suitable for B, so there's no need to change it.
In
Suppose I have the following artifacts. I will omit groups for simplicity.
A:1.0
A:2.0
A:3.0
B:1.0 depends on A:1.0
C:1.0 depends on A:2.0
D:1.0 depends on B:1.0, C:1.0
I want D to use the latest version of A that is inherited from it's
dependencies (not from repository). In this case it is 2.0.
I can create configuration parameter for my plugin and annotate it with
/**
* The greeting to display.
*
* @parameter expression=${sayhi.greeting} default-value=Hello
World!
*/
private String greeting;
This is said here
Please tell about all known ways. I will choose then.
nicolas de loof-2 wrote:
Do you want to use current project artifact or a project dependency ?
2010/2/28 boraldo bora...@hotbox.ru
I want to develop plugin that will do something with jar files in a local
repository.
Example
I tried to use glassfish-plugin but it has very simple goals whereas I need
to implement a huge and complex workflow.
Wendy Smoak-3 wrote:
On Mon, Mar 1, 2010 at 6:02 AM, boraldo bora...@hotbox.ru wrote:
Please tell about all known ways. I will choose then.
You already said that existing
I want to develop plugin that will do something with jar files in a local
repository.
Example: deploy application ear file to server. Please, don't propose to use
existing plugins for this. They don't satisfy my requirements. I want to
develop my plugin.
How can I do it?
--
View this message
I have the same problem and I'd like to explain it.
I want to have an ability to add some web-modules to my ear in some profile.
And I don't want to redefine other modules, only my module. If I only add
dependency on my module in profile, it's context root will be equal to war
name, but I want to
a bug since the order of plugins should be respected.
Have you checked the ticket list of 2.2.2 or 3.0-alpha-3 to see if it
is already fixed?
And are you running 2.2.1?
Paul
On Tue, Nov 10, 2009 at 11:48 AM, boraldo bora...@hotbox.ru wrote:
Suppose I have to execute some actions after some
Suppose I have to execute some actions after some phase.
These actions are made plugins X and Y.
1st action - executed by plugin X
2nd action - executed by plugin Y
3rd action - executed by plugin X
I wrote the following pom:
build
plugins
plugin
Please tell me which plugin is able to do it ?
--
View this message in context:
http://www.nabble.com/How-to-send-email-with-enclosed-files---tp26074704p26074704.html
Sent from the Maven - Users mailing list archive at Nabble.com.
October 2009 14:45, boraldo wrote:
deploy:deploy implies to
The packaging for this project did not assign a file to the build
artifact
MALICE wrote:
If the artifact still exists, try deploy:deploy.
On Monday 12 October 2009 12:54, boraldo wrote:
I want to build in 2 steps.
1. install
I want to build in 2 steps.
1. install
2. deploy
But if I execute mvn deploy, it executes install phase again.
If I execute mvn deploy:mvn deploy, error occurs:
The packaging for this project did not assign a file to the build artifact
How can I fix it ?
--
View this message in context:
deploy:deploy implies to
The packaging for this project did not assign a file to the build artifact
MALICE wrote:
If the artifact still exists, try deploy:deploy.
On Monday 12 October 2009 12:54, boraldo wrote:
I want to build in 2 steps.
1. install
2. deploy
But if I execute mvn
15 matches
Mail list logo
