Do you have tests that pull down multiple dependencies? If yes, you
do have test coverage. Tests are a good way to define a set of
expectations, so that if you reimplement the functionality, you can
ensure the functionality continues to work as expected. I'm not
saying more test coverage isn't
Don Brown wrote:
Do you have tests that pull down multiple dependencies?
Yes, but AFAICT only dependencies from the same group id.
If yes, you do have test coverage. [...] I'm not
saying more test coverage isn't a good thing, just that this
functionality probably does have coverage.
The
And can't we have an option to deactivate it in 2.1 ?
If it works like expected we'll remove it in 3.0
(I continue to be in favor to have tests, but it's really difficult to have
a good coverage it can be a cheap solution)
Arnaud
On Sun, Feb 8, 2009 at 2:14 PM, Benjamin Bentmann
+1000 to having it on by default but can be disabled from a CLI option
+1 to having it off by default but can be turned on from a CLI option
-1000 to not having // downloading
just my €0.02
-Stephen
2009/2/8 Arnaud HERITIER aherit...@gmail.com:
And can't we have an option to deactivate it in
Don Brown wrote:
Do you have tests that pull down multiple dependencies?
I just added a test that pulls down 16 dependencies, using 4 different
group ids and 4 dependencies per group id. The test uses the checksum
policy fail to check that the artifacts are intact. What remains to
check is
Hi John,
Author: jdcasey
Date: Sat Feb 7 02:51:21 2009
New Revision: 741834
URL: http://svn.apache.org/viewvc?rev=741834view=rev
Log:
[MNG-2720] Adding integration test.
Added:
Results:
+9 Brian, John, Shane, Jason, Oleg, Arnaud, Brett, Jesse, Ralph
+0 : None
-1 : None
This vote has passed.
Syncing of the Artifacts to central from the new location
(http://repository.apache.org) is already completed. I will now move the
artifacts from p.a.o and finish the rest of the
From my point of view (and the point of view of many colleagues), the most
important feature about 2.1 release is to be able to use the same stable
Maven version in m2eclipse and command line.
Actually, the only way to have good performances and control on Maven
integration in Eclipse is to use
Umm
m2eclipse is using the 3.x branch, not the 2.1 branch.
On Sun, Feb 8, 2009 at 4:52 PM, Bouiaw bou...@gmail.com wrote:
From my point of view (and the point of view of many colleagues), the most
important feature about 2.1 release is to be able to use the same stable
Maven version in
This is not the same 2.1 that was used for embedders last summer. That
version is now called 3.x and the alphas are moving forward so hopefully
you can have a common version soon.
See here for more details:
http://www.sonatype.com/people/2008/11/a-visual-history-of-maven-2/
-Original
On Thu, Feb 5, 2009 at 10:19 PM, Brett Porter br...@apache.org wrote:
You also need another step - either rsync to people so that one is kept up
to date, or provide a replacement for Henk's scripts (or just block
deploy/promotion with messed up sigs).
Any news on this bit?
The reposit...@a.o
While I prefer 2.1 to be released soon, I am more interested in bug
fixes from 2.0.10 and 2.0.11 than the new features.
What do you guys think about moving all of the 2.0.11 tickets to
2.1-M4? I am pretty sure you guys said only show stoppers would go
into 2.0.x once it's EOL.
Paul
OK, Thanks for the explanation.
On Sun, Feb 8, 2009 at 6:24 PM, Brian E. Fox bri...@reply.infinity.nuwrote:
This is not the same 2.1 that was used for embedders last summer. That
version is now called 3.x and the alphas are moving forward so hopefully
you can have a common version soon.
See
Picking up the doxia thread:
I have the feeling Doxia is never going to get out of it's vicious circle: we are
hesitant to release 1.1 because without the site plugin using it, it doesn't get
any hard-core testing, and for maven you guys don't want to use it because it
hasn't been released
Thanks for reminding me. We'll implement a custom plugin to validate
the sigs and send a notification. If the sigs don't match, we can stop
the promotion.
--Brian (mobile)
On Feb 8, 2009, at 12:32 PM, Wendy Smoak wsm...@gmail.com wrote:
On Thu, Feb 5, 2009 at 10:19 PM, Brett Porter
Any thing fixed in 2.0.10/11 will be in 2.1+
--Brian (mobile)
On Feb 8, 2009, at 12:42 PM, Paul Benedict pbened...@apache.org wrote:
While I prefer 2.1 to be released soon, I am more interested in bug
fixes from 2.0.10 and 2.0.11 than the new features.
What do you guys think about moving
Is it released yet? The reason it didn't make the previous releases is
that it wasn't ready. I think it should be in 2.1 but not 2.0 at this
point
--Brian (mobile)
On Feb 8, 2009, at 1:03 PM, Lukas Theussl ltheu...@apache.org wrote:
Picking up the doxia thread:
I have the feeling Doxia
Hi Ringo,
You will need to set the properties on the project object.
To get a project injected into your MOJO:
/**
* The Maven project instance for the executing project.
*
* pNote: This is passed by Maven and must not be configured by
the user./p
*
* @parameter
Since 2.1.x will support encryption for server password elements (as
detailed
http://www.sonatype.com//people/2009/02/new-feature-maven-settings-password-encryption/
here ) it should be fairly straight forward to add support for encrypting
properties in general.
In our settings.xml files we set
On 8-Feb-09, at 6:37 PM, jmaxwell wrote:
Since 2.1.x will support encryption for server password elements (as
detailed
http://www.sonatype.com//people/2009/02/new-feature-maven-settings-password-encryption/
here ) it should be fairly straight forward to add support for
encrypting
On 08/02/2009, at 10:12 PM, Benjamin Bentmann wrote:
Don Brown wrote:
Do you have tests that pull down multiple dependencies?
I just added a test that pulls down 16 dependencies, using 4
different group ids and 4 dependencies per group id. The test uses
the checksum policy fail to check
Your reply should be directed at Oleg, he is the one that stated
http://www.sonatype.com/people/2009/02/new-feature-maven-settings-password-encryption/#IDComment14858391
here that the implementation would be straight forward! :)
And, for the recorded, I have contributed a patch in the
I'm trying to implement a fix for http://jira.codehaus.org/browse/MDEPLOY-94
but I'm having trouble overriding 'org.apache.maven:maven-artifact-manager'
because it's packaged inside the maven-2.0.x-uber.jar. Am I missing
something simple for testing and deploying changes to
The easiest way is to put it in your maven install in /lib and then edit
the m2.conf file to put your jar in the list before uberjar.
-Original Message-
From: jaxzin [mailto:brian.r.jack...@espn3.com]
Sent: Sunday, February 08, 2009 9:13 PM
To: dev@maven.apache.org
Subject: How do I test
Thanks Brian! I was just stumbling into that so I appreciate you clarifying
it.
Regards,
Brian
Brian E Fox wrote:
The easiest way is to put it in your maven install in /lib and then edit
the m2.conf file to put your jar in the list before uberjar.
-Original Message-
From:
You'll probably find it easier to simply rebuild Maven :)
In some ways, the patch should look similar to this:
http://svn.apache.org/viewvc?view=revrevision=682589
Cheers,
Brett
On 09/02/2009, at 11:00 AM, jaxzin wrote:
Thanks Brian! I was just stumbling into that so I appreciate you
where is m2.conf file?
-D
On Sun, Feb 8, 2009 at 8:18 PM, Brett Porter br...@apache.org wrote:
You'll probably find it easier to simply rebuild Maven :)
In some ways, the patch should look similar to this:
http://svn.apache.org/viewvc?view=revrevision=682589
Cheers,
Brett
On
Right next to the mvn.bat/mvn.sh etc
-Original Message-
From: Dan Tran [mailto:dant...@gmail.com]
Sent: Sunday, February 08, 2009 11:49 PM
To: Maven Developers List
Subject: Re: How do I test patches to maven-artifact-manager?
where is m2.conf file?
-D
On Sun, Feb 8, 2009 at 8:18 PM,
Hi Arnaud,
Arnaud HERITIER wrote at Sonntag, 8. Februar 2009 14:33:
And can't we have an option to deactivate it in 2.1 ?
That would be a really good idea.
If it works like expected we'll remove it in 3.0
(I continue to be in favor to have tests, but it's really difficult to
have a good
29 matches
Mail list logo
