-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Sunday, January 11, 2004 10:54 PM
To: Maven Users List
Subject: RE: Mutliple source directories in project.xml
On Sat, 2004-01-10 at 18:34, John Casey wrote:
It seems to me that the POM is the wrong place
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Subject: RE: Mutliple source directories in project.xml
It seems to me that the POM is the wrong place to put anything related
to artifacts created during maven execution.
I tend to agree with this, but in my case
On Sun, 2004-01-11 at 14:30, Brian Topping wrote:
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Subject: RE: Mutliple source directories in project.xml
It seems to me that the POM is the wrong place to put anything related
to artifacts created during maven
On Fri, 2004-01-09 at 15:19, Michal Maczka wrote:
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 6:28 PM
To: Maven Users List
Subject: RE: Mutliple source directories in project.xml
On Fri, 2004-01-09 at 11:33, Maczka
wrote:
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 6:28 PM
To: Maven Users List
Subject: RE: Mutliple source directories in project.xml
On Fri, 2004-01-09 at 11:33, Maczka Michal wrote
-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 6:28 PM
To: Maven Users List
Subject: RE: Mutliple source directories in project.xml
On Fri, 2004-01-09 at 11:33, Maczka Michal wrote:
Because it is not necessary to have this aspect configurable
There will always be some hairy cases where something Maven does isn't
compatible with a given method but the
generatedSourceDirectory/ would
go a long way to making things better. In the cases where things are
hairy, as John said, you can always whip something together in your
maven.xml
Why is it a bad idea? How is it any different than having /target/docs a
property that all plugins CAN use? It's not hardcoded and can be changed
by users that want to change the location of the files. I'm not seeing how
this is any different. The target directory is not a free-for-all where
-Original Message-
From: Sonnek, Ryan [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 4:59 PM
To: 'Maven Users List'
Subject: RE: Mutliple source directories in project.xml
Why is it a bad idea? How is it any different than having
/target/docs a
property that all
On Fri, 2004-01-09 at 03:06, Maczka Michal wrote:
There will always be some hairy cases where something Maven does isn't
compatible with a given method but the
generatedSourceDirectory/ would
go a long way to making things better. In the cases where things are
hairy, as John said, you
On Fri, 2004-01-09 at 11:33, Maczka Michal wrote:
Because it is not necessary to have this aspect configurable
How do you know this for certain? The answer is you can't without
feedback from users over time.
There is many plugin which are generating reports and which have hardcoded
the
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, January 09, 2004 6:28 PM
To: Maven Users List
Subject: RE: Mutliple source directories in project.xml
On Fri, 2004-01-09 at 11:33, Maczka Michal wrote:
Because it is not necessary to have
Hi all
I've seen that there has been a discussion regarding this before (at least
on the mailing list).
I gather one can circumvent this by modifying the appropriate
property/variable in a preGoal
(like maven.compile.src.set), but that would add to the maintenance
workload and really
it'd
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 9:43 AM
To: 'Maven Users List'
Subject: Mutliple source directories in project.xml
Hi all
I've seen that there has been a discussion regarding this before
(at least
PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 9:43 AM
To: 'Maven Users List'
Subject: Mutliple source directories in project.xml
Hi all
I've seen that there has been a discussion regarding this before
(at least
on the mailing list).
I gather one can
:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 9:43 AM
To: 'Maven Users List'
Subject: Mutliple source directories in project.xml
Hi all
I've seen that there has been a discussion regarding this before
(at least
on the mailing list).
I gather one can
at 14:32, Michal Maczka wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Thursday, January 08, 2004 9:43 AM
To: 'Maven Users List'
Subject: Mutliple source directories in project.xml
Hi all
I've seen that there has
PROTECTED]
Sent: Thursday, January 08, 2004 9:43 AM
To: 'Maven Users List'
Subject: Mutliple source directories in project.xml
Hi all
I've seen that there has been a discussion regarding this before
(at least
on the mailing list).
I gather one
On Thu, 2004-01-08 at 16:57, Steve Garcia wrote:
What about specifying sourceDirectory as a fileset? This would add a lot
more work to retrofit plugins but it really would give developers good
flexibility.
sourceDirectory
include name=dir1 /
include name=dir2 /
include name=dir3
On 2004-01-08 22:38, Jason van Zyl wrote:
On Thu, 2004-01-08 at 16:25, John Casey wrote:
2cents
One easy way to get around this duality between single-source and
multiple source directories would be to stage out the java sources to
some temporary location under ${basedir}/target for subsequent
What about specifying sourceDirectory as a fileset? This
would add
a lot more work to retrofit plugins but it really would give
developers good flexibility.
sourceDirectory
include name=dir1 /
include name=dir2 /
include name=dir3 /
/sourceDirectory
Absolutely
I believe it would only compile sourceDirectory if
generatedSourceDirectory didn't exist...
As for the serial generator execution, the only real problem I see is
_what_ a particular generator would attach to as a preGoal. I mean, it
might depend upon whether xDoclet, javaCC, antlr, etc. was
On Thu, 2004-01-08 at 17:16, Steve Garcia wrote:
What about specifying sourceDirectory as a fileset? This
would add
a lot more work to retrofit plugins but it really would give
developers good flexibility.
sourceDirectory
include name=dir1 /
include name=dir2 /
On Thu, 2004-01-08 at 17:14, Tomasz Pik wrote:
On 2004-01-08 22:38, Jason van Zyl wrote:
On Thu, 2004-01-08 at 16:25, John Casey wrote:
2cents
One easy way to get around this duality between single-source and
multiple source directories would be to stage out the java sources to
some
On Thu, 2004-01-08 at 17:16, Steve Garcia wrote:
[ snip ]
Would the java plugin compile sourceDirectory first then
generatesSourceDirectory second? Well it would
presumably occur at
the same time. Other plugins that require access to a source
directory would need to be tweaked to
On Thu, 2004-01-08 at 00:43, [EMAIL PROTECTED] wrote:
I gather one can circumvent this by modifying the appropriate
property/variable in a preGoal
(like maven.compile.src.set), but that would add to the maintenance
workload and really
it'd just be a hack.
For those of us who haven't been
On Thu, 2004-01-08 at 18:17, Keith Irwin wrote:
On Thu, 2004-01-08 at 00:43, [EMAIL PROTECTED] wrote:
I gather one can circumvent this by modifying the appropriate
property/variable in a preGoal
(like maven.compile.src.set), but that would add to the maintenance
workload and really
It may be better to use maven:addPath rather than override
maven.compile.src.set - not too sure of the implications, but have a
look at the plugin.jelly for plugins that generate java source - eg.
antlr, castor or xdoclet. They all have something like
ant:path id=some.reference.id
28 matches
Mail list logo
