You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-dev@jakarta.apache.org by Vincent Massol <vm...@pivolis.com> on 2003/09/16 13:50:54 UTC
Maven build patches accepted!
Hi Julien,
The 3 active committers have voted +1 to commit the patches you send us
related to the Maven build! Let's do this. Can you modify the scripts
according to the comments I sent and tell me when you're done. I'll then
commit them to CVS.
Also, I think we should work with Maven HEAD for the time being so that
we are ready when the final 1.0 comes out.
Thanks
-Vincent
Re: Maven build patches accepted!
Posted by Julien Dubois <ju...@julien-dubois.com>.
> Cool. I'm sure we can succeed in some way or other.
>
> -Vincent
I sure hope we will succeed!!!
I'm going to spend a few days working on xdocs. I think it could be useful in
my work too, so I can have a look at it during daylight.
And I'll create our own Maven goal for generating the site, as Vincent
recommanded.
I'll get back to you next week on those matters, I need some time to learn
more about those tools, and I need a week end!
Vincent > Thanx thanx thanx for telling me how to handle dependencies between
projects with Maven. I'll use this for Cactus (of course), and this might
also trigger the move from Ant to Maven at my work (lots of projects, lots of
dependencies, lots of Ant files everywhere).
Julien.
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Maven build patches accepted!
Posted by Julien Dubois <ju...@julien-dubois.com>.
> Cool. I'm sure we can succeed in some way or other.
>
> -Vincent
I sure hope we will succeed!!!
I'm going to spend a few days working on xdocs. I think it could be useful in
my work too, so I can have a look at it during daylight.
And I'll create our own Maven goal for generating the site, as Vincent
recommanded.
I'll get back to you next week on those matters, I need some time to learn
more about those tools, and I need a week end!
Vincent > Thanx thanx thanx for telling me how to handle dependencies between
projects with Maven. I'll use this for Cactus (of course), and this might
also trigger the move from Ant to Maven at my work (lots of projects, lots of
dependencies, lots of Ant files everywhere).
Julien.
RE: Maven build patches accepted!
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 18 September 2003 00:04
> To: Cactus Developers List
> Subject: Re: Maven build patches accepted!
[snip]
> > No it won't. Or at least it won't give what we want. The xdocs DTDs
are
> > different.
>
> So now there's a DTD (or some kind of formalized schema) for the Maven
> xdocs? ;-)
Nope, but there is a known format... :-) I was using DTD to loosely mean
a format!
>
> I think a change to the Maven "DTTD" wouldn't be very hard, and I
> wouldn't oppose, even though I'm not very fond of the schema and would
> prefer using forrest's documentv12 (or whatever) DTD.
Cool. Another option is to keep our DTD and simply pass our own
stylesheet (JSL...) to the Maven xdoc plugin.
[snip]
> >
> > I can't find navigation.xml on your web site. I'm still not sure why
you
> > need the link to that DTD! Simply remove it. In all my
navigation.xml, I
> > never use any reference to any DTD.
>
> Hmm, a misunderstanding I suppose:
>
> http://cvs.apache.org/viewcvs.cgi/jakarta-
> cactus/documentation/docs/xdocs/navigation.xml?rev=1.14&content-
> type=text/vnd.viewcvs-markup
Ah yes. I was referring to Maven's navigation.xml! Whereas Julien was
referring to Cactus's navigation.xml file (which I had forgotten about).
BTW, this is the reason I named it navigation.xml in the first place...
(to be more "compatible" with the Maven equivalent... ;-)
>
> There *is* a "link" to the DTD, and it's relative. It's relative for
the
> simple reason so that XML editors can find it. The Ant build uses a
> catalog to resolve the DTD reference, so it isn't even using the
> relative path specified.
>
> IMHO, the current documentation story with the sitemap and the
> navigation files is a bit messy. If the Maven documentation module
> offers the functionality to generate a navigation with nested menus
> based on sub-directories *and* we can style the result so it looks
like
> Jakarta/Cactus and not SourceCast/Tigris/java.net/Maven/you-name-it,
> that'd be the way to go.
Cool. I'm sure we can succeed in some way or other.
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: Maven build patches accepted!
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 18 September 2003 00:04
> To: Cactus Developers List
> Subject: Re: Maven build patches accepted!
[snip]
> > No it won't. Or at least it won't give what we want. The xdocs DTDs
are
> > different.
>
> So now there's a DTD (or some kind of formalized schema) for the Maven
> xdocs? ;-)
Nope, but there is a known format... :-) I was using DTD to loosely mean
a format!
>
> I think a change to the Maven "DTTD" wouldn't be very hard, and I
> wouldn't oppose, even though I'm not very fond of the schema and would
> prefer using forrest's documentv12 (or whatever) DTD.
Cool. Another option is to keep our DTD and simply pass our own
stylesheet (JSL...) to the Maven xdoc plugin.
[snip]
> >
> > I can't find navigation.xml on your web site. I'm still not sure why
you
> > need the link to that DTD! Simply remove it. In all my
navigation.xml, I
> > never use any reference to any DTD.
>
> Hmm, a misunderstanding I suppose:
>
> http://cvs.apache.org/viewcvs.cgi/jakarta-
> cactus/documentation/docs/xdocs/navigation.xml?rev=1.14&content-
> type=text/vnd.viewcvs-markup
Ah yes. I was referring to Maven's navigation.xml! Whereas Julien was
referring to Cactus's navigation.xml file (which I had forgotten about).
BTW, this is the reason I named it navigation.xml in the first place...
(to be more "compatible" with the Maven equivalent... ;-)
>
> There *is* a "link" to the DTD, and it's relative. It's relative for
the
> simple reason so that XML editors can find it. The Ant build uses a
> catalog to resolve the DTD reference, so it isn't even using the
> relative path specified.
>
> IMHO, the current documentation story with the sitemap and the
> navigation files is a bit messy. If the Maven documentation module
> offers the functionality to generate a navigation with nested menus
> based on sub-directories *and* we can style the result so it looks
like
> Jakarta/Cactus and not SourceCast/Tigris/java.net/Maven/you-name-it,
> that'd be the way to go.
Cool. I'm sure we can succeed in some way or other.
-Vincent
Re: Maven build patches accepted!
Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
> Hi Julien,
>
>>-----Original Message-----
>>From: Julien Dubois [mailto:julien@julien-dubois.com]
>>Sent: 17 September 2003 22:52
>>To: Cactus Developers List
>>Subject: Re: Maven build patches accepted!
>>
>>Hi Vincent,
>>
>>Some quick replies and one big question:
>>
>>
>>>2 things:
>>>- what is your strategy for xdocs? Do you plan to convert every
> single
>>>xdoc file to the maven format?
>>I'm just trying to keep the xdocs the way it is for the moment. For
> that I
>>have two options
>>1. Trying to generate the site from Maven, as normal.
>>Just use my documentation/project.xml with "maven site". It's very
> basic,
>>and
>>I don't know xdocs/maven enough to know if it's totally stupid or not.
> But
>>it
>>might work.
>
> No it won't. Or at least it won't give what we want. The xdocs DTDs are
> different.
So now there's a DTD (or some kind of formalized schema) for the Maven
xdocs? ;-)
I think a change to the Maven "DTTD" wouldn't be very hard, and I
wouldn't oppose, even though I'm not very fond of the schema and would
prefer using forrest's documentv12 (or whatever) DTD.
>>2. Do my own Maven goal. This would be a lot like what's Ant doing I
>>guess.
>>It's more work, and it would require some maintenance, so I'll leave
> that
>>as
>>option B.
>
> That will work and I believe this is what we should do for now. The goal
> should simply do the same as is currently in the Ant build file for
> generating the web site. Easy to do.
>
> The tricky part will be to link the Maven reports but we can leave that
> for later.
>
>>>- why do you need to have navigation.xml pointing to ../dtds ?
>>
>>I don't need it. But in the current navigation.xml, there's a link to
> that
>>DTD. So when Maven is working on that file, it fails to find the DTD,
> and
>>the
>>build fails miserably.
>
> I can't find navigation.xml on your web site. I'm still not sure why you
> need the link to that DTD! Simply remove it. In all my navigation.xml, I
> never use any reference to any DTD.
Hmm, a misunderstanding I suppose:
http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/documentation/docs/xdocs/navigation.xml?rev=1.14&content-type=text/vnd.viewcvs-markup
There *is* a "link" to the DTD, and it's relative. It's relative for the
simple reason so that XML editors can find it. The Ant build uses a
catalog to resolve the DTD reference, so it isn't even using the
relative path specified.
IMHO, the current documentation story with the sitemap and the
navigation files is a bit messy. If the Maven documentation module
offers the functionality to generate a navigation with nested menus
based on sub-directories *and* we can style the result so it looks like
Jakarta/Cactus and not SourceCast/Tigris/java.net/Maven/you-name-it,
that'd be the way to go.
-chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Maven build patches accepted!
Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
> Hi Julien,
>
>>-----Original Message-----
>>From: Julien Dubois [mailto:julien@julien-dubois.com]
>>Sent: 17 September 2003 22:52
>>To: Cactus Developers List
>>Subject: Re: Maven build patches accepted!
>>
>>Hi Vincent,
>>
>>Some quick replies and one big question:
>>
>>
>>>2 things:
>>>- what is your strategy for xdocs? Do you plan to convert every
> single
>>>xdoc file to the maven format?
>>I'm just trying to keep the xdocs the way it is for the moment. For
> that I
>>have two options
>>1. Trying to generate the site from Maven, as normal.
>>Just use my documentation/project.xml with "maven site". It's very
> basic,
>>and
>>I don't know xdocs/maven enough to know if it's totally stupid or not.
> But
>>it
>>might work.
>
> No it won't. Or at least it won't give what we want. The xdocs DTDs are
> different.
So now there's a DTD (or some kind of formalized schema) for the Maven
xdocs? ;-)
I think a change to the Maven "DTTD" wouldn't be very hard, and I
wouldn't oppose, even though I'm not very fond of the schema and would
prefer using forrest's documentv12 (or whatever) DTD.
>>2. Do my own Maven goal. This would be a lot like what's Ant doing I
>>guess.
>>It's more work, and it would require some maintenance, so I'll leave
> that
>>as
>>option B.
>
> That will work and I believe this is what we should do for now. The goal
> should simply do the same as is currently in the Ant build file for
> generating the web site. Easy to do.
>
> The tricky part will be to link the Maven reports but we can leave that
> for later.
>
>>>- why do you need to have navigation.xml pointing to ../dtds ?
>>
>>I don't need it. But in the current navigation.xml, there's a link to
> that
>>DTD. So when Maven is working on that file, it fails to find the DTD,
> and
>>the
>>build fails miserably.
>
> I can't find navigation.xml on your web site. I'm still not sure why you
> need the link to that DTD! Simply remove it. In all my navigation.xml, I
> never use any reference to any DTD.
Hmm, a misunderstanding I suppose:
http://cvs.apache.org/viewcvs.cgi/jakarta-cactus/documentation/docs/xdocs/navigation.xml?rev=1.14&content-type=text/vnd.viewcvs-markup
There *is* a "link" to the DTD, and it's relative. It's relative for the
simple reason so that XML editors can find it. The Ant build uses a
catalog to resolve the DTD reference, so it isn't even using the
relative path specified.
IMHO, the current documentation story with the sitemap and the
navigation files is a bit messy. If the Maven documentation module
offers the functionality to generate a navigation with nested menus
based on sub-directories *and* we can style the result so it looks like
Jakarta/Cactus and not SourceCast/Tigris/java.net/Maven/you-name-it,
that'd be the way to go.
-chris
--
Christopher Lenz
/=/ cmlenz at gmx.de
RE: Maven build patches accepted!
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Julien,
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 17 September 2003 22:52
> To: Cactus Developers List
> Subject: Re: Maven build patches accepted!
>
> Hi Vincent,
>
> Some quick replies and one big question:
>
> > 2 things:
> > - what is your strategy for xdocs? Do you plan to convert every
single
> > xdoc file to the maven format?
>
> I'm just trying to keep the xdocs the way it is for the moment. For
that I
> have two options
> 1. Trying to generate the site from Maven, as normal.
> Just use my documentation/project.xml with "maven site". It's very
basic,
> and
> I don't know xdocs/maven enough to know if it's totally stupid or not.
But
> it
> might work.
No it won't. Or at least it won't give what we want. The xdocs DTDs are
different.
> 2. Do my own Maven goal. This would be a lot like what's Ant doing I
> guess.
> It's more work, and it would require some maintenance, so I'll leave
that
> as
> option B.
That will work and I believe this is what we should do for now. The goal
should simply do the same as is currently in the Ant build file for
generating the web site. Easy to do.
The tricky part will be to link the Maven reports but we can leave that
for later.
>
> > - why do you need to have navigation.xml pointing to ../dtds ?
>
> I don't need it. But in the current navigation.xml, there's a link to
that
> DTD. So when Maven is working on that file, it fails to find the DTD,
and
> the
> build fails miserably.
I can't find navigation.xml on your web site. I'm still not sure why you
need the link to that DTD! Simply remove it. In all my navigation.xml, I
never use any reference to any DTD.
>
> *And now for the big question*
> I've got two projects (framework and samples/servlet for example).
Project
> B
> depends on project A, because it uses classes compiled or packaged by
> project
> A.
> Well, how on earth do I make this link?
> If you're using Eclipse, it's the same thing as in the project
properties
> >
> Java build path > projects (projects required on the build path).
Ok, That's easy! Simply call jar:install on project A. This will put
project's A jar in the local repository. Then in project B, declare a
dependency on project's A jar artifact.
You can do that for any artifact type (not just jar). For example if
you're doing this for a zip, simply use the <artifact:install> tag, etc.
-Vincent
RE: Maven build patches accepted!
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Julien,
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 17 September 2003 22:52
> To: Cactus Developers List
> Subject: Re: Maven build patches accepted!
>
> Hi Vincent,
>
> Some quick replies and one big question:
>
> > 2 things:
> > - what is your strategy for xdocs? Do you plan to convert every
single
> > xdoc file to the maven format?
>
> I'm just trying to keep the xdocs the way it is for the moment. For
that I
> have two options
> 1. Trying to generate the site from Maven, as normal.
> Just use my documentation/project.xml with "maven site". It's very
basic,
> and
> I don't know xdocs/maven enough to know if it's totally stupid or not.
But
> it
> might work.
No it won't. Or at least it won't give what we want. The xdocs DTDs are
different.
> 2. Do my own Maven goal. This would be a lot like what's Ant doing I
> guess.
> It's more work, and it would require some maintenance, so I'll leave
that
> as
> option B.
That will work and I believe this is what we should do for now. The goal
should simply do the same as is currently in the Ant build file for
generating the web site. Easy to do.
The tricky part will be to link the Maven reports but we can leave that
for later.
>
> > - why do you need to have navigation.xml pointing to ../dtds ?
>
> I don't need it. But in the current navigation.xml, there's a link to
that
> DTD. So when Maven is working on that file, it fails to find the DTD,
and
> the
> build fails miserably.
I can't find navigation.xml on your web site. I'm still not sure why you
need the link to that DTD! Simply remove it. In all my navigation.xml, I
never use any reference to any DTD.
>
> *And now for the big question*
> I've got two projects (framework and samples/servlet for example).
Project
> B
> depends on project A, because it uses classes compiled or packaged by
> project
> A.
> Well, how on earth do I make this link?
> If you're using Eclipse, it's the same thing as in the project
properties
> >
> Java build path > projects (projects required on the build path).
Ok, That's easy! Simply call jar:install on project A. This will put
project's A jar in the local repository. Then in project B, declare a
dependency on project's A jar artifact.
You can do that for any artifact type (not just jar). For example if
you're doing this for a zip, simply use the <artifact:install> tag, etc.
-Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Maven build patches accepted!
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent,
Some quick replies and one big question:
> 2 things:
> - what is your strategy for xdocs? Do you plan to convert every single
> xdoc file to the maven format?
I'm just trying to keep the xdocs the way it is for the moment. For that I
have two options
1. Trying to generate the site from Maven, as normal.
Just use my documentation/project.xml with "maven site". It's very basic, and
I don't know xdocs/maven enough to know if it's totally stupid or not. But it
might work.
2. Do my own Maven goal. This would be a lot like what's Ant doing I guess.
It's more work, and it would require some maintenance, so I'll leave that as
option B.
> - why do you need to have navigation.xml pointing to ../dtds ?
I don't need it. But in the current navigation.xml, there's a link to that
DTD. So when Maven is working on that file, it fails to find the DTD, and the
build fails miserably.
*And now for the big question*
I've got two projects (framework and samples/servlet for example). Project B
depends on project A, because it uses classes compiled or packaged by project
A.
Well, how on earth do I make this link?
If you're using Eclipse, it's the same thing as in the project properties >
Java build path > projects (projects required on the build path).
Ant still rulez,
Julien.
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Maven build patches accepted!
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent,
Some quick replies and one big question:
> 2 things:
> - what is your strategy for xdocs? Do you plan to convert every single
> xdoc file to the maven format?
I'm just trying to keep the xdocs the way it is for the moment. For that I
have two options
1. Trying to generate the site from Maven, as normal.
Just use my documentation/project.xml with "maven site". It's very basic, and
I don't know xdocs/maven enough to know if it's totally stupid or not. But it
might work.
2. Do my own Maven goal. This would be a lot like what's Ant doing I guess.
It's more work, and it would require some maintenance, so I'll leave that as
option B.
> - why do you need to have navigation.xml pointing to ../dtds ?
I don't need it. But in the current navigation.xml, there's a link to that
DTD. So when Maven is working on that file, it fails to find the DTD, and the
build fails miserably.
*And now for the big question*
I've got two projects (framework and samples/servlet for example). Project B
depends on project A, because it uses classes compiled or packaged by project
A.
Well, how on earth do I make this link?
If you're using Eclipse, it's the same thing as in the project properties >
Java build path > projects (projects required on the build path).
Ant still rulez,
Julien.
RE: Maven build patches accepted!
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 17 September 2003 01:43
> To: Cactus Developers List
> Subject: Re: Maven build patches accepted!
>
> Hi Vincent, hi everybody,
>
> I'm happy to have everybody's +1. I'll try to do my best.
>
> First of all, I took care of Vincent's comments and updated my site :
> http://www.julien-dubois.com/jakarta-cactus/
>
> It's still very basic, but at least it will compile the framework, and
the
> reactor will work a little bit.
>
> 2 questions :
>
You'll see this is where it becomes interesting... ;-)
> 1. Concerning the documentation : the build is going to fail because
of
> DTDs.
> Maven matches the DTD according to its current working directory, so
when
> navigation.xml points to "../dtds/", it fails. I don't think I can
correct
> this without changing the documentation itself.
2 things:
- what is your strategy for xdocs? Do you plan to convert every single
xdoc file to the maven format?
- why do you need to have navigation.xml pointing to ../dtds ?
>
> 2. I'd like to have one master project.properties file, to avoid
having
> all
> those project.properties (with cactus.j2ee.version=13) everywhere. Can
> anyone
> tell me how to do that?
This is not currently possible with Maven. It's a known limitation that
properties cannot be inherited between projects
(http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-37).
Project.xml and maven.xml are inherited properly but not properties.
The only solution that currently exists is to define all the properties
in a top level maven.xml file (using the <j:set> tag).
Thanks
-Vincent
>
> Thanx,
>
> Julien Dubois.
>
> Le Mardi 16 Septembre 2003 13:50, Vincent Massol a écrit :
> > Hi Julien,
> >
> > The 3 active committers have voted +1 to commit the patches you send
us
> > related to the Maven build! Let's do this. Can you modify the
scripts
> > according to the comments I sent and tell me when you're done. I'll
then
> > commit them to CVS.
> >
> > Also, I think we should work with Maven HEAD for the time being so
that
> > we are ready when the final 1.0 comes out.
> >
> > Thanks
> > -Vincent
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
RE: Maven build patches accepted!
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 17 September 2003 01:43
> To: Cactus Developers List
> Subject: Re: Maven build patches accepted!
>
> Hi Vincent, hi everybody,
>
> I'm happy to have everybody's +1. I'll try to do my best.
>
> First of all, I took care of Vincent's comments and updated my site :
> http://www.julien-dubois.com/jakarta-cactus/
>
> It's still very basic, but at least it will compile the framework, and
the
> reactor will work a little bit.
>
> 2 questions :
>
You'll see this is where it becomes interesting... ;-)
> 1. Concerning the documentation : the build is going to fail because
of
> DTDs.
> Maven matches the DTD according to its current working directory, so
when
> navigation.xml points to "../dtds/", it fails. I don't think I can
correct
> this without changing the documentation itself.
2 things:
- what is your strategy for xdocs? Do you plan to convert every single
xdoc file to the maven format?
- why do you need to have navigation.xml pointing to ../dtds ?
>
> 2. I'd like to have one master project.properties file, to avoid
having
> all
> those project.properties (with cactus.j2ee.version=13) everywhere. Can
> anyone
> tell me how to do that?
This is not currently possible with Maven. It's a known limitation that
properties cannot be inherited between projects
(http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-37).
Project.xml and maven.xml are inherited properly but not properties.
The only solution that currently exists is to define all the properties
in a top level maven.xml file (using the <j:set> tag).
Thanks
-Vincent
>
> Thanx,
>
> Julien Dubois.
>
> Le Mardi 16 Septembre 2003 13:50, Vincent Massol a écrit :
> > Hi Julien,
> >
> > The 3 active committers have voted +1 to commit the patches you send
us
> > related to the Maven build! Let's do this. Can you modify the
scripts
> > according to the comments I sent and tell me when you're done. I'll
then
> > commit them to CVS.
> >
> > Also, I think we should work with Maven HEAD for the time being so
that
> > we are ready when the final 1.0 comes out.
> >
> > Thanks
> > -Vincent
Re: Maven build patches accepted!
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent, hi everybody,
I'm happy to have everybody's +1. I'll try to do my best.
First of all, I took care of Vincent's comments and updated my site :
http://www.julien-dubois.com/jakarta-cactus/
It's still very basic, but at least it will compile the framework, and the
reactor will work a little bit.
2 questions :
1. Concerning the documentation : the build is going to fail because of DTDs.
Maven matches the DTD according to its current working directory, so when
navigation.xml points to "../dtds/", it fails. I don't think I can correct
this without changing the documentation itself.
2. I'd like to have one master project.properties file, to avoid having all
those project.properties (with cactus.j2ee.version=13) everywhere. Can anyone
tell me how to do that?
Thanx,
Julien Dubois.
Le Mardi 16 Septembre 2003 13:50, Vincent Massol a écrit :
> Hi Julien,
>
> The 3 active committers have voted +1 to commit the patches you send us
> related to the Maven build! Let's do this. Can you modify the scripts
> according to the comments I sent and tell me when you're done. I'll then
> commit them to CVS.
>
> Also, I think we should work with Maven HEAD for the time being so that
> we are ready when the final 1.0 comes out.
>
> Thanks
> -Vincent
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-dev-help@jakarta.apache.org
Re: Maven build patches accepted!
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent, hi everybody,
I'm happy to have everybody's +1. I'll try to do my best.
First of all, I took care of Vincent's comments and updated my site :
http://www.julien-dubois.com/jakarta-cactus/
It's still very basic, but at least it will compile the framework, and the
reactor will work a little bit.
2 questions :
1. Concerning the documentation : the build is going to fail because of DTDs.
Maven matches the DTD according to its current working directory, so when
navigation.xml points to "../dtds/", it fails. I don't think I can correct
this without changing the documentation itself.
2. I'd like to have one master project.properties file, to avoid having all
those project.properties (with cactus.j2ee.version=13) everywhere. Can anyone
tell me how to do that?
Thanx,
Julien Dubois.
Le Mardi 16 Septembre 2003 13:50, Vincent Massol a écrit :
> Hi Julien,
>
> The 3 active committers have voted +1 to commit the patches you send us
> related to the Maven build! Let's do this. Can you modify the scripts
> according to the comments I sent and tell me when you're done. I'll then
> commit them to CVS.
>
> Also, I think we should work with Maven HEAD for the time being so that
> we are ready when the final 1.0 comes out.
>
> Thanks
> -Vincent
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-dev-help@jakarta.apache.org