Hi Florian,
since testing your problem I've some trouble with my workspace ;-)
I'm not understanding the behavior (of my ws) yet!
I'm using m3, there your problem seems to be fixed.
So it looks more like a bug than a feature!
Fredy
http://stackoverflow.com/questions/4488237/how-does-the-default-annotation-processors-discovery-process-apply
In question
how-to-process-annotations-with-mavenhttp://stackoverflow.com/questions/4487338/how-to-process-annotations-with-mavenI
posted a link for a maven project that processes
I'm looking for a plugin or some tool that helps out encrypting the server
passwords in Maven. I know the manual command line way of doing this, but
I'm looking for any easier way of doing this. If you're having lots of devs,
a few are very likely not to get this right...
Anyone seen such a
Hi!
Have a look at versions-maven-plugin. It provides a goal for updating the
parent [0]. Maybe you can reuse code from it.
hth,
- martin
[0] http://mojo.codehaus.org/versions-maven-plugin/update-parent-mojo.html
On Friday 17 December 2010 Asmann, Roland wrote:
Currently I am not using this,
The Apache Archiva team would like to announce the release of Archiva 1.3.3.
All users are advised to upgrade.
Archiva is available for download from:
* http://archiva.apache.org/download.html
Archiva is an application for managing one or more remote artifact
repositories, including
I am trying to get the maven assembly working but I dont get it to work the
way I want.
I got a multi-project
I got a
root - under_root - project (pom.xml)
Now I want ALL my modules latest releases in a tar.gz package. How do I do
this the simplest way???
Where do I add the plugin in (in
I recommend creating a separate project to do this. In that project you
declare dependency to all artifacts you want to pack. Then create your
assembly xml (or use any one of the provided ones).
/Anders
On Mon, Dec 20, 2010 at 14:08, mickeys nero2...@hotmail.com wrote:
I am trying to get the
Hi all,
I've been trying to get some projects running on my Hudson server, abd
am running into problems. I've hunted down the problem to being the
version of Maven that I use!
On my Hudson I am running both 2.0.10 (for some older projects) and
2.2.1. On both these versions I have a project
Sorry, I got the location of the directories wrong... They were last but
are now first!
On 20.12.2010 14:47, Asmann, Roland wrote:
Hi all,
I've been trying to get some projects running on my Hudson server, abd
am running into problems. I've hunted down the problem to being the
version of
Hi,
I'm having problems using release:prepare plugin on a project that inherits
from a parent project. It seems that it cannot see the plugins from the
parent project and fails on compiling java vesion 1.6 classes claiming that
1.3 version does not support annotations. It works fine with clean
Check the project's effective pom.
mvn help:effective-pom
Most likely what you think should be inherited isn't. How is m-compiler-p
declared in the parent?
/Anders
On Mon, Dec 20, 2010 at 14:50, Piotr Skawinski
piotr.skawinski.ma...@gmail.com wrote:
Hi,
I'm having problems using
Hi list,
I've a multi module with differences between the prod and dev
environment. Threfor I've defined some profiles.
mvn clean install -P devContainerSettings,dependencies,!eclipse works
fine!
but mvn --batch-mode release:prepare -P
devContainerSettings,dependencies,!eclipse fails with
Hi again,
Actually when running mvn help:effective-pom I can see all plugins from the
parent as expected, but when running it after release:prepare (which
actually faills) they are not there anymore. It seems that release:prepare
ignores the parent's plugins for the project it runs the release
Found a workarround:
http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html
Fredy
-Ursprüngliche Nachricht-
Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de]
Gesendet: Montag, 20. Dezember 2010 15:23
An: Maven Users List
Betreff:
http://blog.artifact-software.com/tech/ includes a blog entry on using
JNDI to get environment stuff out of projects.
Got tired of writing it every week here.
Putting environmental stuff inside your modules is a recipe for long
frustrating Maven discussions and hours of fruitless screwing
Hi
I am trying to migrate to maven3. And I have a couple of custom
repository layouts registered that works all right in maven2.
But in maven3 I got this exception (when running with mvn -e)
Caused by:
On 20/12/2010 10:20 AM, Hauschel Fred Robert wrote:
Found a workarround:
http://www.tutorials.de/java/347377-maven-release-plugin-und-profile-activation.html
Fredy
You will be back.
Search this forum for discussions of profiles and environments.
The road to Maven hell is paved with profiles.
Where is the reference to 1.3 coming from?
I think that was what the effective-pom was for, not to see if the
plug-ins were there but to find out who is asking for 1.3.
Ron
On 20/12/2010 10:05 AM, Piotr Skawinski wrote:
Hi again,
Actually when running mvn help:effective-pom I can see all
Hello, i trying package my project with the plugin maven assembly. The
command that i use is mvn assembly:assembly
-DdescriptorId=jar-with-dependencies, but the following error is showed:
[ERROR] BUILD ERROR
[INFO]
Analyzing the debug and error output should also give a clue. Maybe focus on
that and ignore the effective pom for now.
/Anders (mobile)
Den 20 dec 2010 17.05 skrev Ron Wheeler rwhee...@artifact-software.com:
Where is the reference to 1.3 coming from?
I think that was what the effective-pom was
With a structure like the following:
umbrella-module
core-module
optional-module-1
optional-module-2
How can the maven pom files be configured so that a user can build:
1) either, core-module with configuration and jar files from
optional-module-1 as dependencies
2) or, core-module with
I'm guessing that some sort of condition will need to be put into
place in the core-module's pom.xml file to let it know which
dependency it needs? Based on what is specified in an env variable or
Whenever you are looking for this kind of conditional building of your
projects, you should
ok I have investigated this a bit more
It looks like that the WagonRepositoryConnectorFactory throws
exception if the repository layout is != "default".
So I guess that means that if you want your own layout you also
need to create your own
On 20/12/2010 1:11 PM, Wayne Fay wrote:
I'm guessing that some sort of condition will need to be put into
place in the core-module's pom.xml file to let it know which
dependency it needs? Based on what is specified in an env variable or
Whenever you are looking for this kind of conditional
I've already manually done the release:prepare because for some reason my
release:prepare didn't successfully push to github.
I'm using Maven 2.2.1.
-K
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
Hi,
I have long been a user of Maven, but disfavoured the xml verbosity. With Maven
3 I am aware of the polyglot capabilities of using Groovy or YAML for pom
files, but I would still prefer the xml syntax for a while.
A few years ago, a JIRA was raised [1], and an experimental branch created
Hi,
I have a question regarding the m2eclipse plugin. Let me know if this is
not the right place to ask.
I'm writing my own custom plugin, and I would like to execute the mvn
package command. Meaning: I want to run the m2eclipse builder, so that
it would run the Run As-Maven package. Anyone
27 matches
Mail list logo
