> You have some test classes that extends something else than TestCase and you
> want to share these intermediate classes between projects ?
Or perhaps he has some utility classes that are used only by his
tests, or he wants to re-use some test classes for some other reasons.
There are many good r
Hi
I'm not 100 pct sure I get this right.
You have some test classes that extends something else than TestCase
and you want to share these intermediate classes between projects ?
If this is the case.
I re comment to re-engineer your test cases so they only extends
TestCase
/Anders
On 12/
Great, thanks.
Dennis Lundberg wrote:
Rusty Wright wrote:
Where is this documented on the maven site?
It's not yet live, but is included in the next version of the Assembly
Plugin. Until that is released you can view the apt source file for the
document here:
http://svn.eu.apache.org/repos/
Rusty Wright wrote:
> Where is this documented on the maven site?
It's not yet live, but is included in the next version of the Assembly
Plugin. Until that is released you can view the apt source file for the
document here:
http://svn.eu.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plu
mvn help:effective-pom shows that there is no version declared. So,
somehow, it should be possible to check this. Is it possible to parse
the output of help:effective-pom to create an extra rule to check on
the reporting plugins?
With regards,
Nick Stolwijk
~Java Developer~
Iprofs BV.
Claus Slut
Wendy Smoak-3 wrote:
>
> I still tend to favor communication and a quiet period when a release
> is going on, as well as keeping a close eye on the commits list to
> make sure nothing slips in (or slips _by_, as in this case.)
>
We have a distributed team, and we release "often" and "small". M
On 13 Dec 2008, at 13:04, Olivier Dehon wrote:
On Fri, 2008-12-12 at 19:52 -0800, CheapLisa wrote:
yea, I already googled. I already to that before posting. Nothing
came up.
What does "modicum" mean?
This is hilarious. Did you google the definition for it ?
-Olivier
I wonder if lisa i
On Fri, 2008-12-12 at 19:52 -0800, CheapLisa wrote:
> yea, I already googled. I already to that before posting. Nothing came up.
> What does "modicum" mean?
This is hilarious. Did you google the definition for it ?
-Olivier
http://letmegooglethatforyou.com/?q=modicum
On Fri, Dec 12, 2008 at 10:52 PM, CheapLisa wrote:
>
> yea, I already googled. I already to that before posting. Nothing came
> up.
> What does "modicum" mean?
>
> thanks
>
>
>
> Wayne Fay wrote:
> >
> >> Somebody made me discover that recently: http
What I'm saying is that the surefire plugin is responsible for bootstrapping
Junit4, but does not follow all of its conventions. It has its own
conventions. If you want to use Junit4 in maven, that means you use
surefire to call into Junit4. If you don't like the default configuration
for the s
And to add a small thing about Justing just said:
Maven determines which version to use looking at the "closeness".
So, if you want a particular version, the best way is to specify it in the
wanted artefact (say in the war, for you).
Btw, mvn dependency:list will also show you what is finally sel
Well, as you might have seen if you just clicked on the link I provided, I
only copied then pasted the very sentence you were answering to... So if you
really googled, I don't understand why you didn't find anything.
And about your question for "modicum", I'm no native speaker, and I didn't
know t
It appears that when you unpack things, then you can not change their names.
And for whatever reasons, what I had was overly complex.
This works:
zip
false
${artifact.artifactId}.${artifact.extension}
On Sat, Dec 13, 2008 at 8:05 PM, Linghua Wang wrote:
> Correct typo.
>
> 2008/12/13 Linghua Wang
>
>> Hi,
>>
>> I am really puzzled about how 'Build in life-cycle bindings' works in
>> Maven.
>>
>> For example, 'jar' packaging, the default life-cycle bindings contains nine
>> phases - *process-re
Correct typo.
2008/12/13 Linghua Wang
> Hi,
>
> I am really puzzled about how 'Build in life-cycle bindings' works in
> Maven.
>
> For example, 'jar' packaging, the default life-cycle bindings contains nine
> phases - *process-resources,compile,process-test-resources,test-compile, test,
> packag
Hi,
This need an scm release too not only a release-plugin release.
So no really plan.
--
Olivier
2008/12/13 Laurent Perez :
> Thanks !
>
> Olivier, do you have any plans regarding
> http://jira.codehaus.org/browse/MRELEASE-385 ? Of course I know the
> blog hack works for the release plugin too, j
Hi,
No. We load properties (and it's look difficult to load properties
from an xml file).
--
Olivier
2008/12/8 Wim Deblauwe :
> Hi,
>
> is it possible to filter external web resources as explained here:
> http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html,
Hi All.
I am attempting to build a zip file of all listed dependencies of a project.
I am sucessfully creating the zip file with all deps included in it.
However, I need to strip the version numbers from the jar files.
This is the assembly file, it is packaged as a jar file.
Hi,
I am really puzzled about how 'Build in life-cycle bindings' works in Maven.
For example, 'jar' packaging, the default life-cycle bindings contains nine
phases - *process-resources,compile,process-test-resources,test-compile, test,
package, **install, deploy*. Actually, each phases 'build-in
Thanks !
Olivier, do you have any plans regarding
http://jira.codehaus.org/browse/MRELEASE-385 ? Of course I know the
blog hack works for the release plugin too, just asking :).
laurent
2008/12/12 Olivier Lamy :
> Maybe :
> http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactiv
google is your friend
look up cyclic reference
when you understand what one of them is, have a look at your project
and see if you have a cyclic reference
here is a hint for you: the parent section of a pom does not have to
be referencing the parent folders pom
Sent from my iPod
On 13 D
21 matches
Mail list logo
