OK, thanks for the answer. And what about the plugins-section in
org/apache/maven/plugins/maven-metadata.xml? Deprecated as well?
Regards Mirko
--
Sent from my phone
http://illegalstateexception.blogspot.com
http://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/
On Jan 17, 2012 11:
On 12-01-17 07:24 PM, Jeff Trent wrote:
I am stuck on two things while writing a plugin: (1) configuration,
and (2) binding to the right goal/phase automatically. I am using
Maven 3.0.3, and trying to use the plugin for APK (android) packaged
modules.
(1) configuration.
/**
* @phase compile
I am stuck on two things while writing a plugin: (1) configuration,
and (2) binding to the right goal/phase automatically. I am using
Maven 3.0.3, and trying to use the plugin for APK (android) packaged
modules.
(1) configuration.
/**
* @phase compile
* @goal myGoal
* @requiresDependencyResol
Does anyone know how to change the working directory, that the prepare phase of
the release plugin uses, without also changing where it checkouts out the tag?
Basically, I want to run the top level pom, but from a different working
directory.
1. Both of these tags are deprecated because they are a load of crap
and useless.
2. Here is what they mean:
LATEST => The most recently deployed version
RELEASE => The most recently deployed non -SNAPSHOT version
Crappy aren't they!
3. Versions-maven-plugin does not pay any heed to those t
Hello,
what is the difference between these two tags?
Say I deploy two versions 1.1 and 1.2 in this order. What should I expect
for release and latest? My expectation would be to see 1.2 for both.
Say I deploy 1.2 and later on 1.1. Now my expectation would be 1.2 for
latest and 1.1 for release.
> I'm working on a large project that takes time to compile. I would like
Realistically I think you should be looking for LOCAL help (from
someone else in your project team, who knows Maven better than you do
-- who set these projects up originally?) rather than asking here on
Maven Users...
> i
Hi Max,
Don't confuse a mojo with a pojo.
The Mojo reflects the actual goal, supports injection, etc, etc.
A pojo is just that plain old java object: private fields with their
getters and setters
Only for mojo's the @parameters can be used.
Such field can be of a lot of types: String, primitiv
Hello,
I'm working on a large project that takes time to compile. I would like to
instruct Maven to only build the jar file, but after the build I have a tar,
tar.bz2, and a zip file. I am brand new to Maven, but have converted a
project to use Maven for the compilation of all component modules.
sorry yeah, completion goals is for after starting the next version.
you can do the same trick in preparation goals though
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 1
Thanks, I somehow missed completionGoals before.
However, it doesn't really seem to do what's necessary. Looking at my
build log, I can see that the source code is being tagged and
committed before completionGoals runs.
Not to mention that I'm not sure scm:add is the right command, since
my .prop
Thanks Benson !!!
This is what i was looking for. I made following entry and it's working all
right now... Thx again.
org.apache.maven.plugins
maven-site-plugin
3.0
Has anyone thought about how to get a google doc into a format usable
in a maven site? The download choices are rather lame: html, open
office, ms word, and then images.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
I'd move the 'special' tests to their own project.
On Tue, Jan 17, 2012 at 11:17 AM, Stevo Slavić wrote:
> OK, thanks for explaining! A module's tests are supposed to be run only by
> part of the team. For others not even test dependencies are accessible, so
> just disabling compiling and executi
OK, thanks for explaining! A module's tests are supposed to be run only by
part of the team. For others not even test dependencies are accessible, so
just disabling compiling and executing tests was not enough. Resolved this
with a profile and putting dependencies of those tests there.
Kind regard
Hello,
2012/1/17 Stevo Slavić :
> Hello Maven community,
>
> Why does Maven (3.0.3) resolve test scoped dependencies when tests
> compilation and execution is skipped via maven.test.skip system property?
That's something will happen with all maven 2.x or 3.x versions.
Why because maven use someth
> Why does Maven (3.0.3) resolve test scoped dependencies when tests
> compilation and execution is skipped via maven.test.skip system property?
The maven.test.skip system property is apparently not utilized by the
plugin(s) responsible for resolving dependencies early in the build.
Whether or not
in
http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#completionGoals
invoke scm:add
Though I am pretty sure all unmodified files which are already in SCM
get committed by default
On 17 January 2012 14:47, Andrew Todd wrote:
> I'm fairly certain the answer to the question b
I'm fairly certain the answer to the question below is "no," but I'm
wondering if anyone can definitively say either way. Thanks.
On Mon, Jan 9, 2012 at 3:02 PM, Andrew Todd wrote:
> Maven 2.2, release plugin.
>
> During the preparationGoals, I'm modifying a .properties file that
> references the
Thanxs Robert, but i still don't get it
i'm just replacing my String object (which works fine) by a Person object
so instead of having in my project's pom :
John
i have :
Jason
Doesn't it work this way ? :
plugin mojo.xml : declaring properties used in build.xml
plugin build.xml : executed part
Hello Maven community,
Why does Maven (3.0.3) resolve test scoped dependencies when tests
compilation and execution is skipped via maven.test.skip system property?
I'm trying to achieve this by defining a profile with all test scope
dependencies declared in it only. Profile is activated when mave
21 matches
Mail list logo
