actually netbeans is also using a summer 2008 2.1-SNAPSHOT (heavily patched)
Milos
On Thu, Jun 10, 2010 at 2:41 AM, Jason van Zyl wrote:
> The embedder was phased out of the 2.x line years ago and is not supported.
> The only known client is Hudson. You might want to look in the Hudson source
>
Ah okay. Thanks. I'll take a look.
On 6/9/2010 8:41 PM, Jason van Zyl wrote:
The embedder was phased out of the 2.x line years ago and is not supported. The
only known client is Hudson. You might want to look in the Hudson source for
examples.
On Jun 9, 2010, at 5:39 PM, Michael Delaney wrote
While trying to debug some nexus-maven-plugin issues, I came across
some differences in the help:effective-settings output between 2.2.1
and 3.0-b1. Is this expected? Note that in both cases the properties I
have defined in my settings are not shown.
>From Maven 3:
http://maven.apache.org/POM/4.
The embedder was phased out of the 2.x line years ago and is not supported. The
only known client is Hudson. You might want to look in the Hudson source for
examples.
On Jun 9, 2010, at 5:39 PM, Michael Delaney wrote:
> Anyone?
>
> On 6/8/2010 10:05 AM, Michael Delaney wrote:
>> All,
>>
>> I'
Anyone?
On 6/8/2010 10:05 AM, Michael Delaney wrote:
All,
I'm trying to get Maven Embedder 2.0.4 working but I can't seem to get
around the error:
org.apache.maven.embedder.MavenEmbedderException: Cannot lookup required
component.
at
org.apache.maven.embedder.MavenEmbedder.start(Mave
relates more on how to initialise the operating environment for a
Multi-threaded framework such as what is seen here
http://gee.cs.oswego.edu/dl/papers/fj.pdf
if i were to incorporate the multi-thread framework routines into a plugin
which would then be used to either exec/yield/sleep/join
No, there's no need to "fork" for different unit tests. JUnit 4 will run the
old tests just fine, along with the new. All I have done is update my
dependency, like so:
junit
junit
4.8.1
test
Existing tests run, and I can also create and run unit tests using
On 9 June 2010 15:54, Olivier Lamy wrote:
> Hi,
> I have tested (
> http://code.google.com/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin
> )
> and it works nice !
> I have only changed a company plugin to made it works : so it was a
> bad maven usage !.
> regarding the cnfde there is t
I'll start with questions you should be asking yourself when suggesting merging
in a non-trivial change. There is no change to users, the change is non-trivial
from a development perspective.
Do you know what it means to merge in that code?
Did you have anything to do with the production of the
Dan and crew
i have seen junit configured as a Resource in the process phase by
maven-remote-resources-plugin as in:
org.apache.maven.plugins
maven-remote-resources-plugin
On 9 June 2010 18:08, nicolas de loof wrote:
> I built and used it also on few projects without any issue, including some
> custom plugins
>
> I'm +1 to switch to Guice,
>
> just a note : as Spice uses a modified Guice release, with patch proposed
> to
> Guice SVN, should we wait for a new Guice
I have similar experience. I upgraded a couple of projects to JUnit 4.8.1 (from
3.x) in the past few months. Leaving the old tests as-is has worked fine, while
allowing me to write new tests in the new style, just as you propose.
Seems like the best approach to me.
~Daniel Siegmann
-Origin
maybe more details ?
2010/6/9 Jason van Zyl :
>
> On Jun 9, 2010, at 12:54 AM, Olivier Lamy wrote:
>
>> Hi,
>> I have tested
>> (http://code.google.com/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin)
>> and it works nice !
>> I have only changed a company plugin to made it works : so it
On Jun 9, 2010, at 12:54 AM, Olivier Lamy wrote:
> Hi,
> I have tested
> (http://code.google.com/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin)
> and it works nice !
> I have only changed a company plugin to made it works : so it was a
> bad maven usage !.
> regarding the cnfde there
> JUnit 4 apparently runs JUnit 3 tests out of the box
I can confirm that (starting from JUnit 4.7 if I remember correctly). I usually
upgrade all my projects to JUnit 4. This way I can write new tests using JUnit
4 style and keep old tests with JUnit 3 style.
My 2 cts
++
Julien
- Mess
JUnit 4 apparently runs JUnit 3 tests out of the box, so one could feasibly
change the dependencies to JUnit 4 at least. I understand the reasons for
not physically changing old tests for the sake of change tho.
Mark
--
Pull me down under...
On Tue, Jun 8, 2010 at 6:29 AM, Jason Chaffee wrote
I built and used it also on few projects without any issue, including some
custom plugins
I'm +1 to switch to Guice,
just a note : as Spice uses a modified Guice release, with patch proposed to
Guice SVN, should we wait for a new Guice release with those changes
included ?
2010/6/9 Olivier Lamy
Hi,
I have tested
(http://code.google.com/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin)
and it works nice !
I have only changed a company plugin to made it works : so it was a
bad maven usage !.
regarding the cnfde there is the issue :
https://issues.sonatype.org/browse/SPICE-26 (do yo
18 matches
Mail list logo
