> I must say.. I think it's rather arrogant to assume to know what my
> prerequisites and goals are when all I've done is to ask how to set up my
Ron is just trying to be helpful. You are the one who is taking such
offense to his suggestions.
> I have not written any specs, or tests at this momen
good call ron
specifically
http://stackoverflow.com/questions/2334640/maven-how-to-test-two-modules-with-the-same-tests-in-a-third-module
so you'll wqant to create a base test-suite of abstract classes in the parent
then each of the child modules will extend the base test-suite (already defined
Ron Wheeler wrote:
> On 09/04/2011 1:19 PM, Ludwig Magnusson wrote:
>> The situation is this:
>> A depends on B
>> ... and I am working on B.
>> I want to be able to see how changes in B affects projects like A that
>> will be using B
> It is called testing.
No, it's called refactoring.
> You wa
I must say.. I think it's rather arrogant to assume to know what my
prerequisites and goals are when all I've done is to ask how to set up my
eclipse environment.
I wanted to do it to get an initial idea of how much work different
strategies would force upon the end users, and the project itself.
On 09/04/2011 1:19 PM, Ludwig Magnusson wrote:
The situation is this:
A depends on B
... and I am working on B.
I want to be able to see how changes in B affects projects like A that will
be using B
It is called testing.
You want to write B to a spec and test the API that A will use, in a
test
unsubscribe
On Sat, Apr 9, 2011 at 6:23 PM, Fadil wrote:
>
>
The situation is this:
A depends on B
... and I am working on B.
I want to be able to see how changes in B affects projects like A that will
be using B
With your strategy, I would have to install very often to see how the
changes to B effects A.
/Ludwig
-Ursprungligt meddelande-
Från: a
I always thing 'resolve workspace dependencies' is a bad idea. Better install
in local repo. But surely should work for single project. Then you would pick
everything up from project/lib. Can see why may want to do this
--Original Message--
From: Ludwig Magnusson
To: users@maven.apache.o
Thank you!
Worked fine.
-Ursprungligt meddelande-
Från: Jörg Schaible [mailto:joerg.schai...@gmx.de]
Skickat: den 9 april 2011 12:24
Till: users@maven.apache.org
Ämne: Re: [eclipse-plugin] Dependency to workspace projects
Ludwig Magnusson wrote:
> Hello!
>
> I know that the maven-eclip
Ludwig Magnusson wrote:
> Hello!
>
> I know that the maven-eclipse-plugin somehow can figure out that a
> dependency actually exists as a project in workspace and therefore add
> that project to the build path instead of trying to download a jar-file
> from a remote repository.
>
> My question i
Hello!
I know that the maven-eclipse-plugin somehow can figure out that a
dependency actually exists as a project in workspace and therefore add that
project to the build path instead of trying to download a jar-file from a
remote repository.
My question is:
Is this possible for any dependency o
11 matches
Mail list logo
