[
http://jira.codehaus.org/browse/MAVENUPLOAD-726?page=comments#action_58974 ]
Matt Raible commented on MAVENUPLOAD-726:
-
HtmlUnit 1.8 has been released.
http://sourceforge.net/project/showfiles.php?group_id=47038
Please upload the following bundl
[ http://jira.codehaus.org/browse/MAVEN-1628?page=all ]
Lukas Theussl closed MAVEN-1628:
Resolution: Fixed
> Deprecate plugin maven-j2ee-plugin in Maven 1.1 as well?
>
>
> Key: MAVEN-
We have too much corba tie-in to the Sun ORB which makes it so we
can't compile a few chunks of the code or test it on anything other
than strict 1.4 vm (no 1.5 with 1.4 flags).
-David
On Feb 8, 2006, at 11:08 PM, Emmanuel Venisse wrote:
An other option is to set source and target argument
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060219.030002.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060219.030002.txt
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060219.020001.txt
[ http://jira.codehaus.org/browse/MAVEN-1747?page=all ]
Lukas Theussl closed MAVEN-1747:
Resolution: Won't Fix
This has been fixed in ear plugin 1.7, please upgrade and check. See the links
given at MPEAR-37, in particular MPEAR-36.
> ear:ear does
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060219.01.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060219.01.txt
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060219.003001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060219.003001.txt
-
To unsubscribe, e-mai
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060219.01.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060219.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Yes but It seems that JUnit 4 works only with Java 5 ??
Arnaud
On 2/18/06, Grzegorz Słowikowski <[EMAIL PROTECTED]> wrote:
> Hi All
>
> JUnit 4.0 has just be released.
>
> http://sourceforge.net/projects/junit
>
> What I see is that it uses Java 5 annotations, and it's
> not backward compatible w
Vincent Massol wrote:
> I think what you're describing is a stub but not a mock. The advantage of a
> dynamic mock is that you don't need to code any method. It's the user of the
> mock which says what behavior it should have for the methods it calls on the
> mock.
You're right, I've always refer
wow, great feedback guys :)
vmassol: I'll read up on mocks tonight, I really need to learn more about
them before I talk about them at any lvl beyond what i have...if I am going
to try and build something out it ought to be useful :P Hopefully you and I
can chat a bit this week about all this onc
Hi Carlos,
Just wanted to say that I'm not against providing some stubs. I think this
is very useful. I guess the only thing I'm saying is that unit testing of
plugins is possible right now using mocks. If I find some time in the
future, I'll document it.
Thanks
-Vincent
> -Original Message-
Vote result
5 Bindings: (John, Jason, Emmanuel, Arnaud, Lukas)
3 Non Binding: (Nicolas, Fabrizio, Stephane)
The plugin will be moved to the core plugins and release 1.0 is on its way.
Thanks,
Stéphane
On 2/14/06, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I would like to move the mav
On 2/18/06, Vincent Massol <[EMAIL PROTECTED]> wrote:
>
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
> > Sanchez
> > Sent: samedi 18 février 2006 20:14
> > To: Maven Developers List
> > Subject: Re: plugin testing
> >
> > I thought more
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Carlos
> Sanchez
> Sent: samedi 18 février 2006 20:14
> To: Maven Developers List
> Subject: Re: plugin testing
>
> I thought more about static mocks vs. dinamic mocks, i think this is
> what you call s
[ http://jira.codehaus.org/browse/MEV-338?page=all ]
Carlos Sanchez closed MEV-338:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Deleted until we know who was playing with this one
> JPOX 1.1.0 Beta 6 has a POM, but it's invalid and no JAR exists
I don't know where it comes from and has m2 poms, while in their
sources they are still m1.
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
-
T
[ http://jira.codehaus.org/browse/MAVENUPLOAD-741?page=all ]
Carlos Sanchez closed MAVENUPLOAD-741:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Upload rmock to maven download sites
>
>
> Key
[ http://jira.codehaus.org/browse/MAVENUPLOAD-744?page=all ]
Carlos Sanchez closed MAVENUPLOAD-744:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> please upload webdav-servlet-1.2
>
>
> Key: MAVENU
[ http://jira.codehaus.org/browse/MAVENUPLOAD-746?page=all ]
Carlos Sanchez closed MAVENUPLOAD-746:
--
Assign To: Carlos Sanchez
Resolution: Fixed
Bundle URL: is the url of the bundle, not the jar
> DWR 1.1 Beta 3
> --
>
>
JPOX 1.1.0 Beta 6 has a POM, but it's invalid and no JAR exists on ibiblio
--
Key: MEV-338
URL: http://jira.codehaus.org/browse/MEV-338
Project: Maven Evangelism
Type: Bug
Components: Invalid
[
http://jira.codehaus.org/browse/MAVENUPLOAD-742?page=comments#action_58968 ]
Carlos Sanchez commented on MAVENUPLOAD-742:
Add this to your pom, and run "mvn deploy", in the folder repository you'll get
exactly what should be in ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-745?page=all ]
Carlos Sanchez closed MAVENUPLOAD-745:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> xpp3 pull parser
>
>
> Key: MAVENUPLOAD-745
> URL: http:/
OJB 1.0.4 has a number of dependencies that should be optional
--
Key: MEV-337
URL: http://jira.codehaus.org/browse/MEV-337
Project: Maven Evangelism
Type: Bug
Reporter: Matt Raible
Compare the 1.0.3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-747?page=all ]
Carlos Sanchez closed MAVENUPLOAD-747:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> HtmlUnit 1.8 upload request
> ---
>
> Key: MAVENUPLOAD-747
I thought more about static mocks vs. dinamic mocks, i think this is
what you call stubs vs. mocks.
What I found is that while jmock is great for certain cases, like
throwing an exception as you say, for other common tasks static mocks
are easier and require less test code.
On 2/18/06, Vincent Ma
I'd like to bump this back into current discussion. I'm nearing an
almost complete rewrite of dependency-maven-plugin complete with unit
tests etc. Before I go through the motions of updating everything on
mojo, I'd like to know where it will eventually end up. Now is a real
convienient time for me
What goes into:
Is there a sample working project that I can look at?
Regards,
Alan
On 2/16/2006 1:34 AM, Michael Böckling wrote:
Hi Alan ,
Next time, please write to users@maven.apache.org, this list is for
maven development!
To use Jar signing, you have to checkout the l
Brett Porter a écrit :
Raphaël Piéroni wrote:
- allow the adding of resource post compilation (to have the wsdl in the
jar)
You can do that by directly copying to target/classes in
process-classes. What you are doing is really processing classes as much
as generating resources. The onl
[ http://jira.codehaus.org/browse/MPIR-21?page=comments#action_58963 ]
Vincent Siveton commented on MPIR-21:
-
The problem seems to come from commons-validator in Maven Reporting project
(maven-reporting-impl).
Upgrade commons-validator dependency from 1.
[ http://jira.codehaus.org/browse/MEV-326?page=comments#action_58962 ]
Julien Dubois commented on MEV-326:
---
Hi Carlos,
I badly need this pom to be released. Can I help you? Is there an official
"Spring on Maven 2" relese manager? Do you know who I can con
[ http://jira.codehaus.org/browse/MASSEMBLY-71?page=all ]
Gary Murphy updated MASSEMBLY-71:
-
Attachment: MASSEMBLY-71-maven-assembly-plugin.patch
> Allow an archive base directory that accepts variables
> -
Allow an archive base directory that accepts variables
--
Key: MASSEMBLY-71
URL: http://jira.codehaus.org/browse/MASSEMBLY-71
Project: Maven 2.x Assembly Plugin
Type: New Feature
Versions: 2.0.1, 2.0
Re
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: vendredi 17 février 2006 23:59
> To: Maven Developers List
> Subject: Re: plugin testing
>
>
> I think this is the right separation. Unit test to get coverage, add and
> use setters like Vincent suggested. Integ
35 matches
Mail list logo
