Issue Subscription
Filter: Design & Best Practices (37 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
htt
Good day to you, Matt,
Thanks for the additional info.
Yes, plexus-utils Os.java is the one handling the comparison in the os
activation. Also, it is the reference that I use for [1] ( I placed it
under maven user since I don't have write access to the PLEXUS wiki ).
Furthermore, yes, the os.xx
On Feb 6, 2007, at 1:58 PM, Graham Leggett wrote:
Hi all,
I've been trying to use profile activation based on OS to work
around maven's lack of support for exposing the OS family (you can
test against the current OS family, you just cannot find out what
the current OS family is using ${m
yes.
On 09/02/2007, at 11:14 AM, Edwin Punzalan wrote:
Brett Porter wrote:
On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote:
AFAIK the reason the poms are excluded is because they're
modified by the
release process; if the check for local modifications is run
after the pom
is modified, i
Brett Porter wrote:
On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote:
AFAIK the reason the poms are excluded is because they're modified
by the
release process; if the check for local modifications is run after
the pom
is modified, it's impossible to do a release. So this could probably
be f
On 09/02/2007, at 6:44 AM, Edwin Punzalan wrote:
AFAIK the reason the poms are excluded is because they're modified
by the
release process; if the check for local modifications is run after
the pom
is modified, it's impossible to do a release. So this could
probably be fixed.
That's correct
I just submitted the following:
http://jira.codehaus.org/browse/CONTINUUM-1156
I have a project that builds the first time, but is unable to build
after that because the directory it is in doesn't get cleaned up
properly by Continuum. The project contains symbolic links, and the
Plexus Fi
Hi,
That (Plexus component list) is on the todo list for docs, but I haven't
been able to get to it.
Do you want to take this discussion to the Plexus list? I know there are
a some gaps and would be interested in hearing what (else) you are
looking for on the Plexus site.
Cheers,
Rahul
n
Kenney Westerhof wrote:
Edwin Punzalan wrote:
Hi,
I've seen that **/pom.xml is being ignored for local modifications
during a release... Although that doesn't seem right because when the
release is committed, the changes will become part of the release
process, I have found a use for it
Edwin Punzalan wrote:
Hi,
I've seen that **/pom.xml is being ignored for local modifications
during a release... Although that doesn't seem right because when the
release is committed, the changes will become part of the release
process, I have found a use for it when dryRun=true... that i
only org.springframework is synced from you, any other group needs to
be added. i'll do it for springmodules
On 2/8/07, Ben Hale <[EMAIL PROTECTED]> wrote:
We recently added the org/springmodules path to our repository for
syncing and it doesn't appear to be picked up by the regular maven
repo s
We recently added the org/springmodules path to our repository for
syncing and it doesn't appear to be picked up by the regular maven
repo sync. Is it possible to get this path added? Thanks.
-Ben
smime.p7s
Description: S/MIME cryptographic signature
On 2/8/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
Actually, one little minor caveat: (not something that would warrant a -1)
The key that was used to sign this is not available in the public key servers.
Yes. I don't know why but the stupid server does not want my key. I'll
chat later on #ma
Actually, one little minor caveat: (not something that would warrant a -1)
The key that was used to sign this is not available in the public key servers.
Not a huge deal. It's available in the Apache SVN. However, that was an
extra step I had to take to verify the jars.
Dan
On Thursda
On 8 Feb 07, at 10:26 AM 8 Feb 07, Daniel Kulp wrote:
I'll give it a +1 (non-binding) as well. :-)
Caveat being I don't use the ejb plugin at all so I don't know if
it works or
not. From a simple audit, it looks like all the apache stuff is OK.
But we know that you opened every JAR
I'll give it a +1 (non-binding) as well. :-)
Caveat being I don't use the ejb plugin at all so I don't know if it works or
not. From a simple audit, it looks like all the apache stuff is OK.
Dan
On Wednesday 07 February 2007 19:09, Joakim Erdfelt wrote:
> +1 (this is sorely needed)
>
> -
I think it is clear now - Ralph, you jumped into a thread about the Maven 2
Cobertura plugin, and began asking about the Maven 1 plugin. This confused
subsequent replies!
If you have Cobertura questions or issues, please start a new thread as
Lukas suggested.
-Original Message-
From: Ra
Hi,
I've seen that **/pom.xml is being ignored for local modifications
during a release... Although that doesn't seem right because when the
release is committed, the changes will become part of the release
process, I have found a use for it when dryRun=true... that is, to test
a release of
I didn't talk abou lifecycle and phases and a surefire plugin. My first
response to this thread was to simply ask what the "well known problem"
was in the hopes I could figure out how to get the cobertura plugin for
maven 1 working better. (I did by the way). You must have confused me
with the
Just to make things clear, I now about the (nice) plexus documentation about
HOW to write components. What I'm looking for is doc about available
components
(http://plexus.codehaus.org/ref/available-components.html) that may be
really usefull
2007/2/7, nicolas de loof <[EMAIL PROTECTED]>:
Hi g
Your mail is very confusing: you talk about lifecycle and phases and a
surefire plugin, all of which do not exist in Maven 1. If you are indeed
using the m1 plugin, then your question should go to the plugins-user
list at sourceforge (see [1] for links). (Btw, did you check your
maven.compile.d
21 matches
Mail list logo
