Hi guys,
I was wondering if anyone is coming at Javapolis [1] this year. I'll
be there so if you're around ...
Cheers,
Stéphane
[1] http://www.javapolis.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
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
Same thing for me. It's working fine.
Thanks a lot.
Arnaud
On 11/16/06, Nicolas DE LOOF <[EMAIL PROTECTED]> wrote:
Works fine for me
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT
What is the artifactId of the p
On 16 Nov 06, at 12:08 PM 16 Nov 06, Daniel Kulp wrote:
On Thursday November 16 2006 10:08 am, Brian E. Fox wrote:
Is the plugin parent version 4 ready for a vote? This will need to be
done before the new plugin releases can occur.
The pom.xml doesn't have the apache license header. Should
Hi folks... having a small problem getting uniqueVersion false to
function well in a profile.
I have this in my parent pom:
output
deploy
output-releases
file://${output.dir}/release
false
ou
It's coming soon. We need to get the parent released and deployed first.
-Original Message-
From: Sebastien Brunot [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 16, 2006 5:35 AM
To: dev@maven.apache.org
Subject: maven-dependency-plugin release plan
Hi all,
is there any release pl
On Thursday November 16 2006 10:08 am, Brian E. Fox wrote:
> Is the plugin parent version 4 ready for a vote? This will need to be
> done before the new plugin releases can occur.
The pom.xml doesn't have the apache license header. Should be easy for
you to fix. :-)
Also, will Jason's licens
Works fine for me
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT
What is the artifactId of the plugin to download (e.g. maven-java-plugin)?
maven-changelog-plugin
build:start:
plugin:download-artifact:
What is the
On 16 Nov 06, at 3:21 AM 16 Nov 06, Nicolas DE LOOF wrote:
You're right. I've created MRM-224 for this.
There we go:
http://repo1.maven.org/maven2/maven/maven-changelog-plugin/1.9.1/
There are now JAR files there for the plugins.
Jason.
Thanks !
Carlos Sanchez a écrit :
I think the c
Why the exec-maven-plugin has its property requiresProject to true?
Grégory
--
View this message in context:
http://www.nabble.com/exec-maven-plugin-requires-a-project-tf2644165s177.html#a7381422
Sent from the Maven Developers mailing list archive at Nabble.com.
---
On 16 Nov 06, at 10:56 AM 16 Nov 06, Wendy Smoak wrote:
On 11/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
URL: http://svn.apache.org/viewvc?view=rev&rev=475777
Log:
o fix the url to the apache snapshot repo
- * apache snapshots = {{http://people.apache.org/maven-snapshot-
reposito
On 16 Nov 06, at 8:15 AM 16 Nov 06, Nicolas DE LOOF wrote:
The default is not to overwrite existing artifacts so I can turn
on the conversion for plugins. I will also do a quick check as if
there is a Maven 1.x plugin where there exists a Maven 2.x plugin
with the same overall id then
On 11/16/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
URL: http://svn.apache.org/viewvc?view=rev&rev=475777
Log:
o fix the url to the apache snapshot repo
- * apache snapshots = {{http://people.apache.org/maven-snapshot-repository}}
+ * apache snapshots = {{http://people.apache.org/m2-s
Is the plugin parent version 4 ready for a vote? This will need to be
done before the new plugin releases can occur.
The default is not to overwrite existing artifacts so I can turn on
the conversion for plugins. I will also do a quick check as if there
is a Maven 1.x plugin where there exists a Maven 2.x plugin with the
same overall id then the Maven 1.x user is going to be messed up. Off
the top of my
One more question, are you using only a Maven 2.x repository? For both
your m1 and m2 clients?
Jason.
That's the case.
I've converted my corporate repository to Maven2 layout and use archiva
as a proxy from both M1 and M2.
Archiva detects maven1 requests (based on legacy format) and find t
Hi Jason,
Yes, I'm doing like Nicolas and I have the same problem for m1 plugins
$ maven oaf:install
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT
Trying to get missing dependencies and to update snapshots requ
On 16 Nov 06, at 7:27 AM 16 Nov 06, Nicolas DE LOOF wrote:
I don't agree with this :
I'm using archiva as a Maven proxy for BOTH maven1 and maven2, so I
expect to find maven1 plugins in maven2 public repository.
IMHO maven2 & maven1 repo must have the same content (but != layout).
AFAIK, t
On 16 Nov 06, at 7:27 AM 16 Nov 06, Nicolas DE LOOF wrote:
I don't agree with this :
I'm using archiva as a Maven proxy for BOTH maven1 and maven2, so I
expect to find maven1 plugins in maven2 public repository.
IMHO maven2 & maven1 repo must have the same content (but != layout).
AFAIK, th
On 16 Nov 06, at 7:27 AM 16 Nov 06, Nicolas DE LOOF wrote:
I don't agree with this :
I'm using archiva as a Maven proxy for BOTH maven1 and maven2,
How are you doing that? You are using the same rewrite rules that we
are?
so I expect to find maven1 plugins in maven2 public repository.
I
I don't agree with this :
I'm using archiva as a Maven proxy for BOTH maven1 and maven2, so I
expect to find maven1 plugins in maven2 public repository.
IMHO maven2 & maven1 repo must have the same content (but != layout).
AFAIK, there's no project that have both m1 and m2 plugins AND that use
Brett Porter wrote [and Dennis Lundberg said similar things]:
Given this, I don't see any need to change the way we use the closed
state or reintroduce the resolved workflow step.
Hrm, yes, fair enough, you're probably right. It was just a thought...
--
Richard van der Hoff <[EMAIL PROTECTED
On 16 Nov 06, at 3:21 AM 16 Nov 06, Nicolas DE LOOF wrote:
You're right. I've created MRM-224 for this.
Upon a little reflection we probably shouldn't convert plugins
because they're not going to run. We can't convert m1 plugins and
expect them to run so we should just block them from t
On 16 Nov 06, at 3:21 AM 16 Nov 06, Nicolas DE LOOF wrote:
You're right. I've created MRM-224 for this.
Yup, I switch it over to using Archiva so I'll track that one down. I
just got back from India so bear with me.
Jason.
Thanks !
Carlos Sanchez a écrit :
I think the code that does
Hi all,
is there any release plan for a first stable version (non SNAPSHOT) of
the maven-dependency-plugin ?
Thanks for your help,
Sebastien
Hello,
On maven2 public repo, M1 plugins have a wrong ".plugin" extension.
This looks like a repo converter bug, and I've created MRM-224 for it.
This seems to be related to MRM-211 : there is no M1 plugin
ArtifactHandler in default Maven2 plexus configuration. But this also
requires to run a
You're right. I've created MRM-224 for this.
Thanks !
Carlos Sanchez a écrit :
I think the code that does the conversion is now from archiva. Jason
can confirm this
On 11/16/06, Nicolas DE LOOF <[EMAIL PROTECTED]> wrote:
I'd like to create an MPA issue for this, but there's no MPA choice on
27 matches
Mail list logo
