> -Original Message-
> From: Rafal Krzewski [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 1:37 PM
> To: Maven Users List
> Subject: Re: Why no multiple locations of sources? ( was Re:
> inter-project dependencies for the Eclipse plugin )
>
>
> B
> -Original Message-
> From: Brian Ewins [mailto:[EMAIL PROTECTED]
> Sent: Friday, April 04, 2003 11:36 AM
> To: Maven Users List
> Subject: Re: Why no multiple locations of sources? ( was Re:
> inter-project dependencies for the Eclipse plugin )
>
>
> Micha
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, April 03, 2003 3:52 PM
> To: [EMAIL PROTECTED]
> Subject: RE: Why no multiple locations of sources? ( was Re:
> inter-project dependencies for the Eclipse plugin )
>
&g
> Suppose maven was designed so that we could say "goal A's
> input is the output of goals B, C, and D", instead of just "goal
> A depends on B, C, D". s would appear as input-less
> goals, and most plugins would require output path properties,
> not input path properties. Just a thought.
Make
I also like the idea listed in the email below.
As to Ben's email here are my answers:
Why do you have multiple source trees?
We are using two tools for our projects. One tool is a code generation tool
for our o/r mapping layer and we would like to keep it in it's own src
directory to alleviat
---
> From: Ben Walding [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 02, 2003 6:23 AM
> To: Maven Users List
> Subject: Re: Why no multiple locations of sources? ( was Re:
> inter-project dependencies for the Eclipse plugin )
>
>
> Maybe if we understood the "why
ers List
> Subject: Re: Why no multiple locations of sources? ( was Re:
> inter-project dependencies for the Eclipse plugin )
>
>
> Maybe if we understood the "why" of multiple trees, we would be better
> able to describe the "why not" and the "how to work
En réponse à Raphaël Piéroni <[EMAIL PROTECTED]>:
> Hello maven devs and users,
>
> i dunno why splitting a source tree but as said before maven at the
> moment as multiple trees : one for tests, one for java, one for
> aspects.
>
> but i'll see a new one that can be added : aspect-test because
Ben,
> So to Colin (I think)
I'm not Colin, but I will try to explain the situation I'm in.
> Why do you have multiple source trees?
> What is in them?
1) src/java: production source code
2) src/junit: unit test code: component white box tests
3) src/integration: integration unit test code: com
Hello maven devs and users,
i dunno why splitting a source tree but as said before maven at the
moment as multiple trees : one for tests, one for java, one for
aspects.
but i'll see a new one that can be added : aspect-test because some
aspects are for production execution and some others for tes
Jason van Zyl wrote:
On Tue, 2003-04-01 at 10:33, Colin Sampaleanu wrote:
Jason, can you clarify what the real issue with multiple source
directories is?
...
Given that Maven already does support
multiple source dirs in the only fashion I use them (to separate test
sources from non-test
On Tue, 2003-04-01 at 10:33, Colin Sampaleanu wrote:
> Jason, can you clarify what the real issue with multiple source
> directories is?
Separation of concerns. If you have gone to the trouble of separating
your sources into a separate tree then you probably did it for a reason.
When you have m
On Tue, 2003-04-01 at 15:22, Jason van Zyl wrote:
>
> So if we use, say, the Antlr plugin that generates sources you're
> talking about some non-maven compilation process knowing about the
> generated sources?
Yeah, that's basically it.
> The addPath tag allows any addition path of sources
> to
Jason van Zyl wrote:
On Mon, 2003-03-31 at 19:29, [EMAIL PROTECTED] wrote:
"Mark H. Wilkinson" <[EMAIL PROTECTED]> wrote on 01/04/2003
01:44:01 AM:
On Fri, 2003-03-28 at 20:57, Mark McBride wrote:
Ahh; see what you mean. I don't think it would be that difficult to add
support for that kind of
On Tue, 2003-04-01 at 04:33, Mark H. Wilkinson wrote:
>
> I think there's a bit of a problem with the model here, because plugins
> that would like to know about the various trees that contain Java source
> need to have explicit code in them to handle each source tree. The
> Eclipse plugin curren
On Tue, 2003-04-01 at 04:29, Jason van Zyl wrote:
> On Mon, 2003-03-31 at 19:29, [EMAIL PROTECTED] wrote:
> > "Mark H. Wilkinson" <[EMAIL PROTECTED]> wrote on 01/04/2003
> > 01:44:01 AM:
>
> > > At the moment the paths to the source trees are
> > > encoded in the jelly script, so
On Mon, 2003-03-31 at 19:29, [EMAIL PROTECTED] wrote:
> "Mark H. Wilkinson" <[EMAIL PROTECTED]> wrote on 01/04/2003
> 01:44:01 AM:
>
> > On Fri, 2003-03-28 at 20:57, Mark McBride wrote:
> > Ahh; see what you mean. I don't think it would be that difficult to add
> > support for that kind of thing,
> On 31 Mar 2003 16:32:09 +0100, "Mark H. Wilkinson" <[EMAIL PROTECTED]> said:
[SNIP]
>> > I don't know whether this kind of dependency information would be
>> of > use when building multiple projects under reactor - presumably
>> that > can work with jar file dependencies?
>>
>> The jar depe
"Mark H. Wilkinson" <[EMAIL PROTECTED]> wrote on 01/04/2003
01:44:01 AM:
> On Fri, 2003-03-28 at 20:57, Mark McBride wrote:
> Ahh; see what you mean. I don't think it would be that difficult to add
> support for that kind of thing, but it's not there now. You'd need to
> solve a couple of problem
On Fri, 2003-03-28 at 20:57, Mark McBride wrote:
> As for the multiple source:
> For moving the multiple source directories we've used a jelly script that
> copies the mulitple src with the pre-goal:prepare-filesystem goal. The
> problem I'm having is when I run the eclipse:generate-project I can
On Sat, 2003-03-29 at 03:50, Jeffrey D. Brekke wrote:
>
> Right, I understand that. I was wondering if you had a project
> dependency and a jar dependency to the same project defined if eclipse
> would use the project classes before going to the jar. It was a real
> quick and ugly way of maybe m
PM
> To: Maven Users List
> Subject: Re: inter-project dependencies for the Eclipse plugin
>
>
> On Fri, 2003-03-28 at 19:12, Jeffrey D. Brekke wrote:
> > This is very interesting. We have 36 projects, all with
> > interdependencies ( some build, some test, some runtime
> On 28 Mar 2003 19:37:02 +, "Mark H. Wilkinson" <[EMAIL PROTECTED]> said:
> In Eclipse if you have a number of separate projects open in your
> workspace you can specify dependencies between them, so you can say
> that project 'foo' depends on project 'bar' in the same
> workspace. This r
Thanks for the info on the maven.eclipse.output.dir property.
As for the multiple source:
For moving the multiple source directories we've used a jelly script that
copies the mulitple src with the pre-goal:prepare-filesystem goal. The
problem I'm having is when I run the eclipse:generate-project
On Fri, 2003-03-28 at 19:24, Mark McBride wrote:
> I'm new to the list
heh; me too!
> so I'm not sure if this has been covered, but has there
> been any thoughts to supporting multiple source entries so that when one
> runs eclipse:generate-project it will properly set up the src's in the
> .
On Fri, 2003-03-28 at 19:12, Jeffrey D. Brekke wrote:
> This is very interesting. We have 36 projects, all with
> interdependencies ( some build, some test, some runtime ) and to have
> the reactor/maven maintain the eclipse projects like this would be
> cool. Is there a dep heirarchy in eclipse
Good idea! This is one of the things that I was hoping would get addressed =)
I'm new to the list so I'm not sure if this has been covered, but has there
been any thoughts to supporting multiple source entries so that when one
runs eclipse:generate-project it will properly set up the src's in th
This is very interesting. We have 36 projects, all with
interdependencies ( some build, some test, some runtime ) and to have
the reactor/maven maintain the eclipse projects like this would be
cool. Is there a dep heirarchy in eclipse where like a project dep is
used if present before a jar dep?
28 matches
Mail list logo
