you could use the exec plugin to call login and add exec:exec to preparation
goals. voodoo economics
- 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 15 Apr 2011 17:58, "Hugh
The benefits are things like if one ci job does
mvn install and fails for some modules (say unit test failures) - you will end
up with these broken modules being in the repository for other jobs to consume.
You can completely wipe it for each full build (if you distinguish between
commit/smoke
Did some experiment :
For some reason -Dmaven.repo.remote=file:/// doesnt have any effect at all (
in maven 3.0 )
However the same can be given in settings.xml
However, it wont result in a read-only local repository, as the artifact
gets copied from teh file:/// location to teh location designated
Thanks a real lot James :
I was not aware of maven.repo.local ( although I was aware of teh
setting.xml optio to specify the local repository ). We have decided to use
this.
1. "which gives other benefits other than just its safe"
Do you mind explaining some of the other benefits we might reap wit
Hi all guys,
I have a parent pom[1] I use to play with small components that, after
upgrading few plugins[2], introduced a strange behavior: the parent
brings the site descriptor that is correctly included before the
plugins upgrade, but after the upgrade (the parent has version 3),
maven looks for
Hi Sony,
You can just configure a separate local repo for each CI job (which gives other
benefits other than just its safe).
Hudson/Jenkins can do this for you (use private repository option)
Otherwise use "mvn -Dmaven.repo.local=/path/to/job/specific/repo
"
Or set it in your settings file (w
I think the idea was to set a "maven property" - means not set it to a
file, but to the maven properties in runtime.
Maven should provide an API for that and you can check the source of
"build-helper-maven-plugin" project as an example ;)
Regards
Žilvinas Vilutis
Mobile: (+370) 652 38353
E-ma
You are correct. My interest is in knowing if I can use maven under a
CI/hudson environment ( with multiple seperate instances of maven running
).
If there is a patch for this, can somebody please post its reference here
--sony
On Fri, Apr 15, 2011 at 3:23 PM, Mirko Friedenhagen wrote:
> On Fr
On Fri, Apr 15, 2011 at 19:39, Kristian Rosenvold
wrote:
>
> fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
>> Thank you Jason :
>> If 3.x local repository is not safe for concurrent access, how does maven3
>> implement parallel builds ( -T switch )
>> ( maybe they decide on teh parallelism
Justin reads my mind.
/Anders
On Fri, Apr 15, 2011 at 17:49, Justin Edelson wrote:
> I don't think that's what Anders is suggesting specifically. He's
> suggesting that you look at how a plugin which already does this
> works. That's the beauty of an ecosystem of open source plugins.
>
> On Fri,
fr., 15.04.2011 kl. 11.54 -0400, skrev Sony Antony:
> Thank you Jason :
> If 3.x local repository is not safe for concurrent access, how does maven3
> implement parallel builds ( -T switch )
> ( maybe they decide on teh parallelism by making sure that there is no
> concurrent read/write access on
if a requires c then c is a dependency of a no matter what. so you
need to add c as a dep of a. relying on b having a transitive is
asking for trouble as b might change to not depend on c and then you
are borked
On 15 April 2011 16:02, Phillip Hellewell wrote:
> Apologies if this has been asked
add a dependency
2011/4/15 Igor Petruk :
> One artifact when passes package phase produces a file that is required to
> test another artifact. Maven produces the wrong build order because it does
> not know about this detail. How do it tell Maven "please build this artifact
> before this one".
Wayne,
Is my domain hidden? I think you can imagine how possible is at an org this
size.
And while I love svn for smaller projects, it is quirky as h***. Frankly, I'd
have chosen ClearCase. ;->
So, anyone? Bueller?
Thanks,
Will
206.799.1589 (cell)
-Original Message-
From: Wayne
> Thoughts to keep me from wasting my time GREATLY appreciated.
Move to Subversion? ;-)
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Okay,
There is a post here (http://jira.codehaus.org/browse/SCM-415) about this exact
issue, particularly the comments by Jeff Jensen, where one is running at level
3 in Perforce, but the maven release plugin is trying to use the -u -P
arguments to login.
As I'm running all of this within Quic
Thank you Jason :
If 3.x local repository is not safe for concurrent access, how does maven3
implement parallel builds ( -T switch )
( maybe they decide on teh parallelism by making sure that there is no
concurrent read/write access on teh repository *for the same* artifacts ? )
--sony
On Fri, A
I don't think that's what Anders is suggesting specifically. He's
suggesting that you look at how a plugin which already does this
works. That's the beauty of an ecosystem of open source plugins.
On Fri, Apr 15, 2011 at 7:44 AM, laredotornado-3
wrote:
> Ah, so I understand your idea, you're sayin
Apache Maven 3.x does not have a local repository implementation that is safe
for concurrent access.
Maven 3.x is intended to be compatible with Maven 2.x in all respects. A Maven
2.x build should just work in Maven 3.x
On Apr 15, 2011, at 11:13 AM, Sony Antony wrote:
> I read somewhere that
I read somewhere that during maven 2, teh repository was not safe for
concurrent access.
( If multiple maven builds access teh same repository, it might end up being
corrupt )
However, Im not sure if this unsafety arose because of teh way maven2
accessed teh repository or if the repository layout
Apologies if this has been asked before. Suppose I have A -> B -> C.
Is there any way to make A depend on B as optional, without making C
optional?
I know I can add an explicit dependency of A -> C, but I'm wondering
if there's a "shortcut" / "easier way".
The scenario at my work is A is a dll,
Ah, so I understand your idea, you're saying that my plugin should output its
value to a/the maven.proeprties file and then I can just read that in from
my other task?
- Dave
--
View this message in context:
http://maven.40175.n5.nabble.com/Mojo-How-do-I-write-a-plugin-to-interact-with-another-t
Hi,
We are struck with the same issue.
Were you able to solve this?
As a temporary fix, i deleted the maven-metadata-local.xml file and the
build runs fine but fails (as expected) during the subsequent builds.
Any help would be appreciated :)
Thanks,
Gayathri
--
View this message in context:
We set up *sequencing* in our CI tool.
Curt Yanko | Continuous Integration Services | UnitedHealth Group IT
Making IT Happen, one build at a time, 600 times a day
> -Original Message-
> From: Igor Petruk [mailto:igor_pet...@epam.com]
> Sent: Friday, A
One artifact when passes package phase produces a file that is required to test
another artifact. Maven produces the wrong build order because it does not know
about this detail. How do it tell Maven "please build this artifact before this
one". It is better to accomplish this with single comman
1. yes.
2. it's still ./m2 with Maven 3.0
/Anders
On Fri, Apr 15, 2011 at 15:16, Sony Antony wrote:
> Thank you for clarifying Anders :
> 1. "No, you should specify a version for all plugins "
> When I ran a sample project, it automatically downloaded a bunch of plugins
> ( like maven-clean-plu
Thank you for clarifying Anders :
1. "No, you should specify a version for all plugins "
When I ran a sample project, it automatically downloaded a bunch of plugins
( like maven-clean-plugin ) as specified in teh superpom version ( I didnt
specify ).
Are you saying that I should have specified the
> 1. Does that mean that the poms we write would look exactly same as how
> they
> would have looked during maven 2.x days ?
>
There are no changes to the pom. A pom that works with Maven 3.0.x should
work with Maven 2.x (with the possible exception that some specific plugin
might not work with so
1. Does that mean that the poms we write would look exactly same as how they
would have looked during maven 2.x days ?
2. "3 will complain if you did not specify versions in the plugins"
I guess, this applies only to the plugins that ate *not* specified in teh
superpom ( core plugins ) ?
--sony
Anders,
What other suggestion do you have for testing that a something works
with multiple versions of something else?
I completely agree that running 'install' let alone 'deploy' with a
profile that changes a version is a really bad idea. But it's an
effective mechanism for compatibility testing
Subj. They don't get transformed? Am I doing something wrong, or it is not a
feature of a plugin?
Thanks
Well, I just saw in another thread a reference to
http://jira.codehaus.org/browse/MSITE-171 which seems to be what I'm seeing
when using release, but obviously I'm not using site in this case.
On Wed, Apr 13, 2011 at 3:58 AM, Karl Heinz Marbaise wrote:
> Hi,
>
>
> John Ament wrote:
> >
> > I hav
Yes, but I still don't think this is a good idea for dependencies. What will
happen is that the dependency declared in the pom being deploy is not what
was used during build. Can lead to strange things IMO.
/Anders
On Fri, Apr 15, 2011 at 12:14, Kristian Rosenvold <
kristian.rosenv...@gmail.com>
The trick is to give the artifact a *default* version in properties so
you can override from the command line but still build without any
command line options;
1.1
Then you can build with -Dmygroup-myartifact.version=1.2-SNAPSHOT
Kristian
Den 15.04.2011 11:16, skrev Anders Hammar:
Ye
Yes, it is. "-Dmygroup-myartifact.version=xxx"
However, for your example it would be a very bad thing as your pom will not
be consumable by any client.
/Anders
On Fri, Apr 15, 2011 at 10:37, Geir Gullestad Pettersen wrote:
> Hi,
>
> Is it possible to inject properties into pom.xml from the comm
Hi Guillaume ,
I think it would be good to create separate mail thread as the thread in which
u have appended is related to maven-release-plugin :)
Thanks,
Gayathri
--- On Fri, 15/4/11, Helle, Guillaume [via Maven]
wrote:
From: Helle, Guillaume [via Maven]
Subject: How to skip a specific m
Hi,
Is it possible to inject properties into pom.xml from the command line at
runtime?
consider this dependency:
mygroup
myartifact
${mygroup-myartifact.version}
war
${mygroup-myartifact.version} can of course be set in
Hello,
I have a parent pom with a list of module and I want skip the last module.
It packages my delivery with ant and the build fail on Hudson because it needs
some specifics execs which are not installed.
But I need this module to package the produt on development platform.
So is there a way t
Am 13.04.11 00:10, schrieb Justin Edelson:
> On Tue, Apr 12, 2011 at 2:50 PM, Jason van Zyl wrote:
>>
>> On Apr 12, 2011, at 5:38 PM, Justin Edelson wrote:
>>
>>> On Tue, Apr 12, 2011 at 2:25 PM, Jason van Zyl wrote:
On Apr 12, 2011, at 3:49 PM, Carsten Ziegeler wrote:
> We're
Hi,
We are using maven release plugin to automate our release process. We
decided to have a pre-commit hook to avoid modification to svn tags once
they are created.
But, maven release plugin fails if the hook is enabled as it tags the trunk
and then modifies the version no in pom files ( in tags
It works here. You are probably using an incompatible plugin, eg try
disabling the reports. If you can't get it to work, attach a small test
project at http://jira.codehaus.org/browse/MPDF
HTH,
-Lukas
Stephen Cresswell wrote:
Has anyone got the PDF plugin working with Maven 2.2.1?
41 matches
Mail list logo
