On 23 Apr 07, at 10:11 PM 23 Apr 07, Brett Porter wrote:
Does it now have a prerequisite on 2.0.6?
No, in pre-2.0.6 that will get blocked with the artifact filter and
1.1 will be used from the core.
For post-2.0.6 the stated version will be used.
Jason.
On 23/04/2007, at 12:06 AM, [EMA
On 23 Apr 07, at 10:14 PM 23 Apr 07, Brett Porter wrote:
I'm a bit concerned about the implications of this for consumers of
the artifact-manager - aren't we going to see a lot of things
possibly getting two versions of classes now?
I doubt there are any users apart from us and simply ch
I'm a bit concerned about the implications of this for consumers of
the artifact-manager - aren't we going to see a lot of things
possibly getting two versions of classes now?
I definitely think we need the separate API (and that it needs to be
massively cleaned up), I'm just not sure how t
Does it now have a prerequisite on 2.0.6?
On 23/04/2007, at 12:06 AM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Sun Apr 22 15:06:16 2007
New Revision: 531288
URL: http://svn.apache.org/viewvc?view=rev&rev=531288
Log:
o p-u is safe to use now
Modified:
maven/plugins/trunk/maven-site-p
Looks like a typo?
On 22/04/2007, at 11:36 PM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Sun Apr 22 14:36:17 2007
New Revision: 531280
URL: http://svn.apache.org/viewvc?view=rev&rev=531280
Log:
o lock down the version
...
+
+ org.apache.maven.wagon
+ wagon-
+ 1.0-b
On 22/04/2007, at 9:58 PM, [EMAIL PROTECTED] wrote:
Author: jvanzyl
Date: Sun Apr 22 12:58:09 2007
New Revision: 531259
URL: http://svn.apache.org/viewvc?view=rev&rev=531259
Log:
o remove maven-artifact-test, not used anywhere
Actually, it is externally. It should probably be in shared, alon
An extension should still work there, as long as the things are
instantiated in the extension itself - sounds like doing it in the
plugin is the problem. Is there a reason it must be there, or can you
use the plexus component lifecycle to do the instantiation?
Other than extensions, you can
On 24/04/2007, at 2:18 AM, Jason van Zyl wrote:
On 23 Apr 07, at 8:06 PM 23 Apr 07, Brett Porter wrote:
This sounds reasonable to me, but I think there's lots of things
that work on the assumption of one pom per g/a/v. So the attached
artifact should also get a new artifact ID
A new id
On 23 Apr 07, at 8:06 PM 23 Apr 07, Brett Porter wrote:
This sounds reasonable to me, but I think there's lots of things
that work on the assumption of one pom per g/a/v. So the attached
artifact should also get a new artifact ID
A new id if you are going to deploy separate artifacts, or t
On 22/04/2007, at 7:47 PM, Wendy Smoak wrote:
Agreed. Assembly may be a special case, because it changed so much
from 2.1 to 2.2 -- my 2.1 descriptors didn't work with 2.2 last time I
tried it (which could have been with a snapshot.)
Should no longer be the case, but if it is - file a bug. J
This sounds reasonable to me, but I think there's lots of things that
work on the assumption of one pom per g/a/v. So the attached artifact
should also get a new artifact ID - which also seems reasonable to
me. It's just a whole new artifact coming out of a single build, the
POM for which i
On 23 Apr 07, at 5:40 PM 23 Apr 07, Dennis Lundberg wrote:
I thought that I'd give this plugin a workout, but I ran into a
couple of things that has prevented me from testing it completely.
1. The tests seem to require that there's an scp-server available
on localhost. That's not the case
On Apr 23, 2007, at 2:14 AM, Jerome Lacoste wrote:
On 4/23/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
I have no idea how to apply PLXUTILS-25 to try it :-(
Do you mean you need detailed instructions to:
* create a new plexus utils jar based on the proposed change ?
* or make sure this new pl
I thought that I'd give this plugin a workout, but I ran into a couple
of things that has prevented me from testing it completely.
1. The tests seem to require that there's an scp-server available on
localhost. That's not the case on Windows, so no joy running the tests
for me.
2. After inst
Shane Isbell wrote:
> The project is going well and as such, should not be archived.
> I have not reported for April since the NMaven schedule occurs
> on the February, May, August, November schedule.
This is one of those problems with maintaining consistency in redundant sets
of meta-data. Accor
+1
On 4/21/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
+1
Vincent
2007/4/21, Brian E. Fox <[EMAIL PROTECTED]>:
> +1
>
> -Original Message-
> From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 20, 2007 10:49 PM
> To: Maven Developers List
> Subject: [vote] release
Here is the result of this vote:
+1 Binding: Dennis Lundberg, Vincent Siveton, Brian Fox
I will proceed with the release.
Dennis Lundberg wrote:
Hi,
I'd like to release maven-stylus-skin 1.0.1. The only existing issue for
this skin has been fixed. The fix is needed by the upcoming version of
On 23 Apr 07, at 3:12 PM 23 Apr 07, Hervé BOUTEMY wrote:
Le lundi 23 avril 2007 21:00, Jason van Zyl a écrit :
I checked them today: they seem fine to me
Time for a second take ?
Yup, I guess I just wanted to see if anyone thought it wise to
include the libraries necessary for SSH deployment
Le lundi 23 avril 2007 21:00, Jason van Zyl a écrit :
> > I checked them today: they seem fine to me
> > Time for a second take ?
>
> Yup, I guess I just wanted to see if anyone thought it wise to
> include the libraries necessary for SSH deployment. Currently you
> could not deploy via SSH without
On 23 Apr 07, at 2:55 PM 23 Apr 07, Hervé BOUTEMY wrote:
Le dimanche 22 avril 2007 17:32, Jason van Zyl a écrit :
I staged the Ant Tasks to the same place and
they look fine now.
I checked them today: they seem fine to me
Time for a second take ?
Yup, I guess I just wanted to see if anyon
Le dimanche 22 avril 2007 17:32, Jason van Zyl a écrit :
> I staged the Ant Tasks to the same place and
> they look fine now.
I checked them today: they seem fine to me
Time for a second take ?
Hervé
-
To unsubscribe, e-mail: [E
Hi there,
I've had an initial stab at implementing ConflictResolvers and
attached a patch to MNG-612. If people wouldn't mind taking a peek,
I'd appreciate some feedback on the following:
1) ConflictResolver API - is the negative/positive/zero return type
sufficient, or would a boolean return t
Wayne Fay wrote:
>
> On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
>> So if I say BETA then no alpha bundle (a bundle
>> containing alpha software) will be selected.
>
> Who exactly decides what the quality is for a given release? Outside
> of a handful (literally) of major ap
Hi Noel,
The project is going well and as such, should not be archived. I have not
reported for April since the NMaven schedule occurs on the February, May,
August, November schedule.
Thanks,
Shane
On 4/23/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
Is this project going, or should it be
Here is a new list of plugins to release for maven 1.x.
--
IDEA 1.7
--
Changes in this version include :
New Features:
o Autodetect which version control system to use Fixes MPIDEA-43.
Download :
maven plugin:download
-Dmaven.repo.remote=http://people.apache.org/repo/m1-snapsh
I thought one of the main arguments in all this discussion is to make things
simple and easy for users. At least those were the comments against forcing
everyone to explicitly set versions for everything. The bundle will free
every single user of having to go finding out what version of what to us
Is this project going, or should it be archived?
--- Noel
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Friday, November 17, 2006 2:25
To: [EMAIL PROTECTED]
Cc: Shane Isbell
Subject: [PROPOSAL] NMaven podling
Hi,
The Maven PMC has voted to accept NMaven
Brian E. Fox wrote:
>
> Everyone keeps referring to bundles that "are known to work together."
> Come someone produce an example of plugins that are incompatible with
> each other? I haven't seen this and I'm not even sure it's possible
> given that plugins can't communicate or even know about e
"Can't you have a plug-in that generates some file to be consumed by
another plugin? It may not be the most orthodox usage but definitely a
possibility.
Just because you do not have one now, it does not mean it cannot happen.
The plug-in may not talk to each other but they may use different
versi
>> I haven't seen this and I'm not even sure it's possible given that
>> plugins can't communicate or even know about each other.
>XDoclet plugin depends on Antrun plugin 1.0. And the dep is declared as
*jar* dependency
>(relying on the fact, that M2 cannot distinguish it). This is the real
cu
Hi,
we use several plugins that need to share data. This as done by
creating an extension containing some "container" classes, and adding
an extension to the project's pom. These container classes are
instantiated in a plugin using Plexus. However, since 2.0.5, this
stopped working, because e
On 23 Apr 07, at 8:57 AM 23 Apr 07, Jörg Schaible wrote:
Hi Brian,
Brian E. Fox wrote on Monday, April 23, 2007 2:42 PM:
Everyone keeps referring to bundles that "are known to work
together."
Come someone produce an example of plugins that are incompatible with
each other?
Annoying: http
On 23 Apr 07, at 8:42 AM 23 Apr 07, Brian E. Fox wrote:
Everyone keeps referring to bundles that "are known to work together."
Come someone produce an example of plugins that are incompatible with
each other? I haven't seen this and I'm not even sure it's possible
given that plugins can't commu
I will go and specify the versions.
But isn't maven suppose to look for and upgrade to the latest version,
unless I say otherwise, every time I run maven?
Or is this something done on a random basis? I get more and more confuse by
the minute on how maven is suppose to behave.
Jose A.
Brian
Hi Brian,
Brian E. Fox wrote on Monday, April 23, 2007 2:42 PM:
> Everyone keeps referring to bundles that "are known to work together."
> Come someone produce an example of plugins that are incompatible with
> each other?
Annoying: http://jira.codehaus.org/browse/MOJO-641
> I haven't seen this
Agreed. Putting the "release management" hat on, "betas", "RCs", etc. are
not much of a beta/RC when they keep adding new functionalitythey are
continued development releases. :-)
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Monday, April 23, 2007 5:43 A
If you haven't specified the version of the plugin in your pom, then the
version each developer has can be different. See the other threads on
this list for more info.
-Original Message-
From: Jose Alberto Fernandez [mailto:[EMAIL PROTECTED]
Sent: Monday, April 23, 2007 8:36 AM
To: dev@ma
Everyone keeps referring to bundles that "are known to work together."
Come someone produce an example of plugins that are incompatible with
each other? I haven't seen this and I'm not even sure it's possible
given that plugins can't communicate or even know about each other.
I personally think a
We are quite simple maven users here. We all installed maven 2.0.5, our
project code and POMs are on SVN. We do not build any maven component from
source and using the same settings. And we all run maven from the same
recipe of commands that we more or less cut and paste like:
mvn install assembl
Hi,
yes i know that , but my problem is , it's not me which decide the
hibernate configuration.
i have these 5 properties to configure Hibernate
org.hibernate.dialect.DerbyDialect
${org.hibernate.connection.driverclass}
${org.hibernate.connection.connectionurl}
$
On 23 Apr 07, at 7:25 AM 23 Apr 07, Jose Alberto Fernandez wrote:
Hi Jason,
When was 2.2-beta-1 released? This problem has been happening for
several
days on one of my co-workers machine. However it does not occurs on
some
other machines. Since maven should have upgraded all machines or
On 22 Apr 07, at 11:09 PM 22 Apr 07, Wayne Fay wrote:
On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
So if I say BETA then no alpha bundle (a bundle
containing alpha software) will be selected.
Who exactly decides what the quality is for a given release?
Dead on. All this wi
Wayne Fay wrote:
>
> On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
>> So if I say BETA then no alpha bundle (a bundle
>> containing alpha software) will be selected.
>
> Who exactly decides what the quality is for a given release? Outside
> of a handful (literally) of major apps
You can set the configuration in your plexus/components.xml :)
Thanks,
Deng
dvicente wrote:
Hi,
I try to create a Plexus component for Maven 2 allowing to manage my factory
Hibernate in order to use it in one or more plugins.
How to configure this plexus component from the pom.xml without s
Hi Jason,
When was 2.2-beta-1 released? This problem has been happening for several
days on one of my co-workers machine. However it does not occurs on some
other machines. Since maven should have upgraded all machines or none, I do
not see how this can be a version issue.
As per a reproducible
Hi,
I try to create a Plexus component for Maven 2 allowing to manage my factory
Hibernate in order to use it in one or more plugins.
How to configure this plexus component from the pom.xml without setting the
values from my Mojo?
thank you in advance for your assistance
--
View this message
Wendy Smoak-3 wrote:
>
> On 4/21/07, Jose Alberto Fernandez <[EMAIL PROTECTED]> wrote:
>
>> Well, having the documentation not reflecting the released plugins but
>> SNAPSHOTs is not helpful to any user.
>
> We're discussing this now in a different thread. Please add your
> comments there if
Ok, I agree. I don't know if Jeff's change in the javadoc is dangerous, but
It's certainly a better idea to postpone its integration in the
distribution.
I'll in some minutes the vote for all the plugins I mentioned but it's not a
vote to incorporate them in the RC1 distribution.
I think to releas
We have talked about it in private already: I think we have made the
error far too often now, that we waited for 'small' releases in order to
get the big one out. I also don't like adding new features in the last
minute, eg I haven't had time to really test Jeff's last changes to the
javadoc pl
+1
Thanks! Let's get ready for m11 now...
-Lukas
Arnaud HERITIER wrote:
Hi team,
We finalized the new version of maven-model 3.0.2 for maven 1.1.
You can find the new web site in [1] and the model documentation [2] will
replace the one actually in the maven 1 site [3].
I deployed a Snapsho
On 4/23/07, Jason Dillon <[EMAIL PROTECTED]> wrote:
I have no idea how to apply PLXUTILS-25 to try it :-(
Do you mean you need detailed instructions to:
* create a new plexus utils jar based on the proposed change ?
* or make sure this new plexus-utils jar is used when you run maven ?
* both ?
Thanks Vincent. This has been long awaited...
On 4/23/07, Vincent Massol <[EMAIL PROTECTED]> wrote:
The Maven team is pleased to announce the release of the Maven Clover
plugin, version 2.4.
You can run mvn -up to get the latest version of the plugin, or
specify the version in your project's p
The Maven team is pleased to announce the release of the Maven Clover
plugin, version 2.4.
You can run mvn -up to get the latest version of the plugin, or
specify the version in your project's plugin configuration:
org.apache.maven.plugins
maven-clover-plugin
2.4
Here are the release
+1
Emmanuel
Arnaud HERITIER a écrit :
Hi team,
We finalized the new version of maven-model 3.0.2 for maven 1.1.
You can find the new web site in [1] and the model documentation [2] will
replace the one actually in the maven 1 site [3].
I deployed a Snapshot of the library.
In this new vers
54 matches
Mail list logo