You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Julien Dubois <ju...@julien-dubois.com> on 2003/06/23 21:26:08 UTC
Building Cactus with Maven -> I'd like to volonteer
Hi,
I'm trying to compile Cactus from CVS HEAD, and it's quite difficult because
you need to grab several libraries (and I'm not the only one, see
http://www.mail-archive.com/cactus-user@jakarta.apache.org/msg03273.html).
Besides, the "building cactus" page
(http://jakarta.apache.org/cactus/participating/howto_build.html) seems to
lack some information. For example, there's nothing concerning the HttpClient
library, which is needed (for example for compiling the WebResponse class).
I don't want to spend too much time downloading stuff/configuring eclipse, so
I'd like to volonteer for porting Cactus to Maven. I see that you plan to do
so, and I've already worked with Maven before, so I think I should be able to
help.
Waiting for your response,
--
Julien Dubois
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Julien,
Excellent! +1 from me to move the discussion to the dev mailing list.
Let's ask the other committers what they think there.
Thanks
-Vincent
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 15 September 2003 22:55
> To: Cactus Users List; Vincent Massol
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
>
> Hi Vincent,
>
> There seems to be a lot to learn for me in that area, and I think this
> would
> be interesting.
> I'm no novice : at work I made a CruiseControl + Ant + XDoclet system
that
> provides continuous integration to the half dozen projects I work on.
> So I think I could handle it, but I will need time and help.
> Concerning my commitement, I guess it will depend on my daily job, but
I'd
> like to give back to the Apache community for all they have done for
me.
> So
> I'll do it.
> If you give me your +1, I'll switch to the dev mailing list...
>
> Julien Dubois.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent,
There seems to be a lot to learn for me in that area, and I think this would
be interesting.
I'm no novice : at work I made a CruiseControl + Ant + XDoclet system that
provides continuous integration to the half dozen projects I work on.
So I think I could handle it, but I will need time and help.
Concerning my commitement, I guess it will depend on my daily job, but I'd
like to give back to the Apache community for all they have done for me. So
I'll do it.
If you give me your +1, I'll switch to the dev mailing list...
Julien Dubois.
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Julien,
First many thanks for that! I'd like to know what is your intention with
regards to Cactus and Maven. What we are looking for is someone who
would take the ownership of the Cactus Maven build, i.e.:
- would replace the current Ant build with a Maven one (for *all*
subprojects and with *at least* the same functionality). Of course this
would be done in several steps as it quite a big achievement (the 2
builds would have to live next to each other for some time. The main
pain with this is that we will have to port any build change to both
build systems...).
- would maintain it over time, fixing bugs, improving it, etc.
Is that what you have in mind? If the answer is yes, then we can
certainly make that a reality and we can commit your changes. If
however, you give Cactus a half-finished Maven build (or even a fully
working one) and go away after that, it will be much less interesting...
What we need to know at this stage is your long-term involvement. Do you
plan to contribute on a long-run basis? Hey, no problem if you can't for
any reason (that's normal).
Here are a few comments on your Maven files:
1/ We should use a different namespace than maven.* for properties name
(this is reserved for maven). Thus, I would recommend to name all our
properties: cactus.*
2/ Make the framework/project.xml inherit from the top level
project.xml. You can then remove all the stuff about developers, common
dependencies, mailing lists, etc.
3/ Do not use existing goal names for our custom goals (jar:jar, etc) in
the top level maven.xml file. I was going to recommend goals starting
with "cactus:" but this namespace is already used by the Maven Cactus
plugin... hmmm.... I don't have any bright idea ATM.
4/ There no "build" goal in maven.xml (this is the default you have set)
5/ pomVersion is 3!!!
6/ Version is 1.6dev not 1.5-beta1
I'm using the reactor daily on my project at work and it works just
fine. Are you using Maven b10 or later? Maybe using non-existing goals
will help?
The 2 big challenges facing us:
1/ Make the Maven web site generation generate our look and feel.
Probably require some changes in Maven itself.
2/ Integrate our Maven build in a continuous build with email sending on
build error. However, that one will become a reality in not too long as
Continuum is currently being tested on codehaus and should be made
visible within about 2 months I'd say.
There are several other intermediaries challenges that will also require
"fixing" Maven such as clover reports for the whole end to end stuff.
Thanks
-Vincent
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 15 September 2003 20:35
> To: Cactus Users List; Vincent Massol
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
>
> Hi Vincent, hi everybody,
>
> So here are my Maven build files :
> http://www.julien-dubois.com/jakarta-cactus/
>
> The directory layout is obvious.
>
> - At the root directory : (WARNING : it does not work!)
> I tried to use the Maven Reactor, without any success, so it's not
working
> at
> all. If you know a website with some clear explanation about this,
please
> send me URL.
>
> - In the framework directory (WARNING : it works :-)) )
> Just run "maven jar" or "maven site:generate" to see it in action.
> I'm using the latest Maven (1.0beta10), with the JDK 1.4.
>
> I know what I've done is pretty basic, but this was enough for my
needs,
> and
> IMHO it really eases the Cactus build process.
>
> Please send me your comments, I will have some free time this week to
> improve
> those files.
>
> Regards,
>
> Julien Dubois.
>
>
> Le Dimanche 14 Septembre 2003 00:56, Julien Dubois a écrit :
> > Hi Vincent, hi everybody,
> >
> > Sorry but I didn't work at all during summer (you know how much we
> French
> > people work during the summer...).
> > I had a working Maven file, which was ok for my needs, but which
clearly
> > wasn't good enough for the project. So I've been using it at work,
but I
> > didn't sent it to you.
> > I'll have a look at it on Monday - I'm Cc:ing this message to my
> business
> > email.
> >
> > Julien.
> >
> > Le Samedi 13 Septembre 2003 21:23, Vincent Massol a écrit :
> > > Hi Julien,
> > >
> > > Just curious. How is it going? Do you need help?
> > >
> > > Thanks
> > > -Vincent
> > >
> > > > -----Original Message-----
> > > > From: Julien Dubois [mailto:julien@julien-dubois.com]
> > > > Sent: 26 June 2003 21:50
> > > > To: Cactus Users List; Vincent Massol
> > > > Subject: Re: Building Cactus with Maven -> I'd like to volonteer
> > > >
> > > > > <preGoal name="java:compile">
> > > > > <ant:path id="maven.j2ee.compile.src.set"
> > > > >
location="${pom.build.sourceDirectory}/../${j2ee.version}"/>
> > > > > <maven:addPath id="maven.compile.src.set"
> > > > > refid="maven.j2ee.compile.src.set"/>
> > > > > </preGoal>
> > > >
> > > > Thanx Vincent, I've got it /nearly/ working now.
> > > > I hope that next week I'll be able to send you my project.xml
and
> > > > maven.xml
> > > > files.
> > > >
> > > > --
> > > >
> > > > Julien Dubois
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: cactus-user-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent, hi everybody,
So here are my Maven build files :
http://www.julien-dubois.com/jakarta-cactus/
The directory layout is obvious.
- At the root directory : (WARNING : it does not work!)
I tried to use the Maven Reactor, without any success, so it's not working at
all. If you know a website with some clear explanation about this, please
send me URL.
- In the framework directory (WARNING : it works :-)) )
Just run "maven jar" or "maven site:generate" to see it in action.
I'm using the latest Maven (1.0beta10), with the JDK 1.4.
I know what I've done is pretty basic, but this was enough for my needs, and
IMHO it really eases the Cactus build process.
Please send me your comments, I will have some free time this week to improve
those files.
Regards,
Julien Dubois.
Le Dimanche 14 Septembre 2003 00:56, Julien Dubois a écrit :
> Hi Vincent, hi everybody,
>
> Sorry but I didn't work at all during summer (you know how much we French
> people work during the summer...).
> I had a working Maven file, which was ok for my needs, but which clearly
> wasn't good enough for the project. So I've been using it at work, but I
> didn't sent it to you.
> I'll have a look at it on Monday - I'm Cc:ing this message to my business
> email.
>
> Julien.
>
> Le Samedi 13 Septembre 2003 21:23, Vincent Massol a écrit :
> > Hi Julien,
> >
> > Just curious. How is it going? Do you need help?
> >
> > Thanks
> > -Vincent
> >
> > > -----Original Message-----
> > > From: Julien Dubois [mailto:julien@julien-dubois.com]
> > > Sent: 26 June 2003 21:50
> > > To: Cactus Users List; Vincent Massol
> > > Subject: Re: Building Cactus with Maven -> I'd like to volonteer
> > >
> > > > <preGoal name="java:compile">
> > > > <ant:path id="maven.j2ee.compile.src.set"
> > > > location="${pom.build.sourceDirectory}/../${j2ee.version}"/>
> > > > <maven:addPath id="maven.compile.src.set"
> > > > refid="maven.j2ee.compile.src.set"/>
> > > > </preGoal>
> > >
> > > Thanx Vincent, I've got it /nearly/ working now.
> > > I hope that next week I'll be able to send you my project.xml and
> > > maven.xml
> > > files.
> > >
> > > --
> > >
> > > Julien Dubois
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi Vincent, hi everybody,
Sorry but I didn't work at all during summer (you know how much we French
people work during the summer...).
I had a working Maven file, which was ok for my needs, but which clearly
wasn't good enough for the project. So I've been using it at work, but I
didn't sent it to you.
I'll have a look at it on Monday - I'm Cc:ing this message to my business
email.
Julien.
Le Samedi 13 Septembre 2003 21:23, Vincent Massol a écrit :
> Hi Julien,
>
> Just curious. How is it going? Do you need help?
>
> Thanks
> -Vincent
>
> > -----Original Message-----
> > From: Julien Dubois [mailto:julien@julien-dubois.com]
> > Sent: 26 June 2003 21:50
> > To: Cactus Users List; Vincent Massol
> > Subject: Re: Building Cactus with Maven -> I'd like to volonteer
> >
> > > <preGoal name="java:compile">
> > > <ant:path id="maven.j2ee.compile.src.set"
> > > location="${pom.build.sourceDirectory}/../${j2ee.version}"/>
> > > <maven:addPath id="maven.compile.src.set"
> > > refid="maven.j2ee.compile.src.set"/>
> > > </preGoal>
> >
> > Thanx Vincent, I've got it /nearly/ working now.
> > I hope that next week I'll be able to send you my project.xml and
> > maven.xml
> > files.
> >
> > --
> >
> > Julien Dubois
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Julien,
Just curious. How is it going? Do you need help?
Thanks
-Vincent
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 26 June 2003 21:50
> To: Cactus Users List; Vincent Massol
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
>
> > <preGoal name="java:compile">
> > <ant:path id="maven.j2ee.compile.src.set"
> > location="${pom.build.sourceDirectory}/../${j2ee.version}"/>
> > <maven:addPath id="maven.compile.src.set"
> > refid="maven.j2ee.compile.src.set"/>
> > </preGoal>
>
> Thanx Vincent, I've got it /nearly/ working now.
> I hope that next week I'll be able to send you my project.xml and
> maven.xml
> files.
>
> --
>
> Julien Dubois
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Julien Dubois <ju...@julien-dubois.com>.
> <preGoal name="java:compile">
> <ant:path id="maven.j2ee.compile.src.set"
> location="${pom.build.sourceDirectory}/../${j2ee.version}"/>
> <maven:addPath id="maven.compile.src.set"
> refid="maven.j2ee.compile.src.set"/>
> </preGoal>
Thanx Vincent, I've got it /nearly/ working now.
I hope that next week I'll be able to send you my project.xml and maven.xml
files.
--
Julien Dubois
RE: Cactus coverage in "Java extreme Programming Cookbook"
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Karthik,
A bit late... No, I haven't read it and thus I can't comment on it.
<advertising>
However, I'm just finishing a book on unit testing java applications
(JUnit in Action, http://manning.com/massol/) which has a special focus
of unit testing J2EE applications. I can tell you that the Cactus
coverage is excellent and it covers Cactus 1.5 ;-)
</advertising>
Thanks
-Vincent
-----Original Message-----
From: karthik Guru [mailto:karthik_guru2000@yahoo.com]
Sent: 26 June 2003 14:41
To: Cactus Users List
Subject: Cactus coverage in "Java extreme Programming Cookbook"
Hi Vincent/ All,
Did anyone get a chance to read this book from oreilly. How is the
cactus coverage and in general the book? Does it teach you nice tricks ?
Thought i w'd grab this one if it's good. I liked the available Junit
chapter. Did'nt get a chance to read other chapters.
thanks,karthik
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
Cactus coverage in "Java extreme Programming Cookbook"
Posted by karthik Guru <ka...@yahoo.com>.
Hi Vincent/ All,
Did anyone get a chance to read this book from oreilly. How is the cactus coverage and in general the book? Does it teach you nice tricks ? Thought i w'd grab this one if it's good. I liked the available Junit chapter. Did'nt get a chance to read other chapters.
thanks,karthik
---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
Re: Error when using machine name instead of "localhost" with FormAuthentication
Posted by Christopher Lenz <cm...@gmx.de>.
karthik Guru wrote:
> Thanks Jason!
>
> The machines that run automated builds @ our place are different from
> the ones that host the application. Does that mean that i cannot
> automate unit testing along with our builds for now? / until the next
> cactus release is available? Can someone suggest a work around?
> Is downloading cactus source, modifying the source, and building
> cactus an option?
Sure it's an option. I'd recommend you play with the latest from CVS,
and provide a patch, so that it can be incorporated into the main trunk.
> Not sure what i s'd be modifying though. Automating unit testing is one
> of the prime objectives for me in this quarter :-(
>
> thanks,
> karthik.
>
> */Jason Arndt <ja...@yahoo.com>/* wrote:
>
> Hi Karthik,
>
> There is already an open bug on this problem. It can
> be viewed at:
> http://issues.apache.org/bugzilla/show_bug.cgi?id=17933
>
> Jason
--
Christopher Lenz
/=/ cmlenz at gmx.de
Re: Error when using machine name instead of "localhost" with FormAuthentication
Posted by karthik Guru <ka...@yahoo.com>.
Thanks Jason!
The machines that run automated builds @ our place are different from the ones that host the application. Does that mean that i cannot automate unit testing along with our builds for now? / until the next cactus release is available? Can someone suggest a work around?
Is downloading cactus source, modifying the source, and building cactus an option?
Not sure what i s'd be modifying though. Automating unit testing is one of the prime objectives for me in this quarter :-(
thanks,
karthik.
Jason Arndt <ja...@yahoo.com> wrote:
Hi Karthik,
There is already an open bug on this problem. It can
be viewed at:
http://issues.apache.org/bugzilla/show_bug.cgi?id=17933
Jason
--- karthik Guru wrote:
> I changed localhost to machine name in the code and
> ran into this error.
>
> "hostName" and "port" are 2 properties defined in
> the cactus.properties file.
> Moment i change hostName --> machine name i have a
> problem.
> As long as it remains "locahost" it is fine.
>
> Any idea as to what is going wrong? am able to
> access the application from another machine.
>
> If I do
>
:7001/ppo/home.jsp">http://:7001/ppo/home.jsp
> it works fine and am able to login.
>
> thanks
> karthik.
>
> public void login(WebRequest webRequest){
> String userName = getTestParameter(USERNAME_KEY);
> String password = getTestParameter(PASSWORD_KEY);
> FormAuthentication fa = new
> FormAuthentication(userName, password);
>
> webRequest.setRedirectorName("ServletRedirector");
> webRequest.setAuthentication(fa);
> String hostname=System.getProperty("hostName");
> String port=System.getProperty("port");
> String firstPart = hostname+":"+port;
> String secondPart = "/ppo";
> String thirdPart = "/home.jsp";
> System.out.println("Url: " + firstPart +
> secondPart + thirdPart);
> webRequest.setURL(firstPart, secondPart,
> thirdPart, null, null);
> }
>
>
> [junit] ------------- Standard Output
> ---------------
>
> [junit] user: mdoadmin, password: mdoadmin
>
> [junit] Created FormAuthentication
>
> [junit] Hostname:port got=sjain:7001
>
> [junit] Url: sjain:7001/ppo/home.jsp
>
> [junit] ------------- ----------------
> ---------------
>
> [junit] ------------- Standard Error
> -----------------
>
> [junit] log4j:ERROR No appenders could be found for
> category (org.apache.cac
>
> tus.client.initialization.ClientInitializer).
>
> [junit] log4j:ERROR Please initialize the log4j
> system properly.
>
> [junit] ------------- ----------------
> ---------------
>
> [junit] Testcase:
>
testMarkdownSearch(com.i2.mdo.unittest.MarkdownSearchTest)
>
> : Caused an ERROR
>
> [junit] Failed to authenticate the principal
>
> [junit]
> org.apache.cactus.util.ChainedRuntimeException:
> Failed to authentica
>
> te the principal
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.au
>
>
thenticate$ajcPostAround24(FormAuthentication.java;org/apache/cactus/util/log/Lo
>
> gAspect.aj(1k):314)
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.au
>
>
thenticate$ajcPostAround24$ajcVoidWrapper(FormAuthentication.java;org/apache/cac
>
> tus/util/log/LogAspect.aj(1k))
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.au
>
>
thenticate(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1
>
> 151)
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.co
>
>
nfigure$ajcPostAround15(FormAuthentication.java;org/apache/cactus/util/log/LogAs
>
> pect.aj(1k):155)
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.co
>
>
nfigure$ajcPostAround15$ajcVoidWrapper(FormAuthentication.java;org/apache/cactus
>
> /util/log/LogAspect.aj(1k))
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.co
>
>
nfigure(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1151
>
> )
>
> [junit] at
>
org.apache.cactus.client.connector.http.HttpClientConnectionH
>
>
elper.connect$ajcPostAround9(HttpClientConnectionHelper.java;org/apache/cactus/u
>
> til/log/LogAspect.aj(1k):123)
>
> [junit] at
>
org.apache.cactus.client.connector.http.HttpClientConnectionH
>
>
elper.connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspe
>
> ct.aj(1k):1222)
>
> [junit] at
>
org.apache.cactus.client.connector.http.DefaultHttpClient.cal
>
>
lRunTest(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):202)
>
> [junit] at
>
org.apache.cactus.client.connector.http.DefaultHttpClient.doT
>
>
est$ajcPostAround7(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.a
>
> j(1k):119)
>
> [junit] at
>
org.apache.cactus.client.connector.http.DefaultHttpClient.doT
>
>
est(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1222)
>
> [junit] at
>
org.apache.cactus.AbstractWebServerTestCase.runWebTest(Abstra
>
> ctWebServerTestCase.java:272)
>
> [junit] at
>
org.apache.cactus.AbstractWebServerTestCase.runGenericTest(Ab
>
> stractWebServerTestCase.java:214)
>
> [junit] at
>
org.apache.cactus.AbstractWebServerTestCase.runTest(AbstractW
>
> ebServerTestCase.java:287)
>
> [junit] at
>
org.apache.cactus.AbstractClientTestCase.runBare(AbstractClie
>
> ntTestCase.java:289)
>
> [junit] org.apache.cactus.client.ClientException:
> Failed to create Cookie he
>
> ader for [domain = [sjain, path =
> [/ppo/j_security_check, cookies = [[Lorg.apach
>
> e.commons.httpclient.Cookie;@69cb75]]. Turn on
> HttpClient logging for more infor
>
> mation about the error
>
> [junit] at
>
org.apache.cactus.client.connector.http.AbstractConnectionHel
>
>
per.createCookieHeader(AbstractConnectionHelper.java;org/apache/cactus/util/log/
>
> LogAspect.aj(1k):270)
>
> [junit] at
>
org.apache.cactus.client.connector.http.AbstractConnectionHel
>
>
per.getCookieString$ajcPostAround6(AbstractConnectionHelper.java;org/apache/cact
>
> us/util/log/LogAspect.aj(1k):221)
>
> [junit] at
>
org.apache.cactus.client.connector.http.AbstractConnectionHel
>
>
=== message truncated ===
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: cactus-user-help@jakarta.apache.org
---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
Re: Error when using machine name instead of "localhost" with FormAuthentication
Posted by Jason Arndt <ja...@yahoo.com>.
Hi Karthik,
There is already an open bug on this problem. It can
be viewed at:
http://issues.apache.org/bugzilla/show_bug.cgi?id=17933
Jason
--- karthik Guru <ka...@yahoo.com> wrote:
> I changed localhost to machine name in the code and
> ran into this error.
>
> "hostName" and "port" are 2 properties defined in
> the cactus.properties file.
> Moment i change hostName --> machine name i have a
> problem.
> As long as it remains "locahost" it is fine.
>
> Any idea as to what is going wrong? am able to
> access the application from another machine.
>
> If I do
>
:7001/ppo/home.jsp">http://<machine-name>:7001/ppo/home.jsp
> it works fine and am able to login.
>
> thanks
> karthik.
>
> public void login(WebRequest webRequest){
> String userName = getTestParameter(USERNAME_KEY);
> String password = getTestParameter(PASSWORD_KEY);
> FormAuthentication fa = new
> FormAuthentication(userName, password);
>
> webRequest.setRedirectorName("ServletRedirector");
> webRequest.setAuthentication(fa);
> String hostname=System.getProperty("hostName");
> String port=System.getProperty("port");
> String firstPart = hostname+":"+port;
> String secondPart = "/ppo";
> String thirdPart = "/home.jsp";
> System.out.println("Url: " + firstPart +
> secondPart + thirdPart);
> webRequest.setURL(firstPart, secondPart,
> thirdPart, null, null);
> }
>
>
> [junit] ------------- Standard Output
> ---------------
>
> [junit] user: mdoadmin, password: mdoadmin
>
> [junit] Created FormAuthentication
>
> [junit] Hostname:port got=sjain:7001
>
> [junit] Url: sjain:7001/ppo/home.jsp
>
> [junit] ------------- ----------------
> ---------------
>
> [junit] ------------- Standard Error
> -----------------
>
> [junit] log4j:ERROR No appenders could be found for
> category (org.apache.cac
>
> tus.client.initialization.ClientInitializer).
>
> [junit] log4j:ERROR Please initialize the log4j
> system properly.
>
> [junit] ------------- ----------------
> ---------------
>
> [junit] Testcase:
>
testMarkdownSearch(com.i2.mdo.unittest.MarkdownSearchTest)
>
> : Caused an ERROR
>
> [junit] Failed to authenticate the principal
>
> [junit]
> org.apache.cactus.util.ChainedRuntimeException:
> Failed to authentica
>
> te the principal
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.au
>
>
thenticate$ajcPostAround24(FormAuthentication.java;org/apache/cactus/util/log/Lo
>
> gAspect.aj(1k):314)
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.au
>
>
thenticate$ajcPostAround24$ajcVoidWrapper(FormAuthentication.java;org/apache/cac
>
> tus/util/log/LogAspect.aj(1k))
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.au
>
>
thenticate(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1
>
> 151)
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.co
>
>
nfigure$ajcPostAround15(FormAuthentication.java;org/apache/cactus/util/log/LogAs
>
> pect.aj(1k):155)
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.co
>
>
nfigure$ajcPostAround15$ajcVoidWrapper(FormAuthentication.java;org/apache/cactus
>
> /util/log/LogAspect.aj(1k))
>
> [junit] at
>
org.apache.cactus.client.authentication.FormAuthentication.co
>
>
nfigure(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1151
>
> )
>
> [junit] at
>
org.apache.cactus.client.connector.http.HttpClientConnectionH
>
>
elper.connect$ajcPostAround9(HttpClientConnectionHelper.java;org/apache/cactus/u
>
> til/log/LogAspect.aj(1k):123)
>
> [junit] at
>
org.apache.cactus.client.connector.http.HttpClientConnectionH
>
>
elper.connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspe
>
> ct.aj(1k):1222)
>
> [junit] at
>
org.apache.cactus.client.connector.http.DefaultHttpClient.cal
>
>
lRunTest(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):202)
>
> [junit] at
>
org.apache.cactus.client.connector.http.DefaultHttpClient.doT
>
>
est$ajcPostAround7(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.a
>
> j(1k):119)
>
> [junit] at
>
org.apache.cactus.client.connector.http.DefaultHttpClient.doT
>
>
est(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1222)
>
> [junit] at
>
org.apache.cactus.AbstractWebServerTestCase.runWebTest(Abstra
>
> ctWebServerTestCase.java:272)
>
> [junit] at
>
org.apache.cactus.AbstractWebServerTestCase.runGenericTest(Ab
>
> stractWebServerTestCase.java:214)
>
> [junit] at
>
org.apache.cactus.AbstractWebServerTestCase.runTest(AbstractW
>
> ebServerTestCase.java:287)
>
> [junit] at
>
org.apache.cactus.AbstractClientTestCase.runBare(AbstractClie
>
> ntTestCase.java:289)
>
> [junit] org.apache.cactus.client.ClientException:
> Failed to create Cookie he
>
> ader for [domain = [sjain, path =
> [/ppo/j_security_check, cookies = [[Lorg.apach
>
> e.commons.httpclient.Cookie;@69cb75]]. Turn on
> HttpClient logging for more infor
>
> mation about the error
>
> [junit] at
>
org.apache.cactus.client.connector.http.AbstractConnectionHel
>
>
per.createCookieHeader(AbstractConnectionHelper.java;org/apache/cactus/util/log/
>
> LogAspect.aj(1k):270)
>
> [junit] at
>
org.apache.cactus.client.connector.http.AbstractConnectionHel
>
>
per.getCookieString$ajcPostAround6(AbstractConnectionHelper.java;org/apache/cact
>
> us/util/log/LogAspect.aj(1k):221)
>
> [junit] at
>
org.apache.cactus.client.connector.http.AbstractConnectionHel
>
>
=== message truncated ===
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
Error when using machine name instead of "localhost" with FormAuthentication
Posted by karthik Guru <ka...@yahoo.com>.
I changed localhost to machine name in the code and ran into this error.
"hostName" and "port" are 2 properties defined in the cactus.properties file.
Moment i change hostName --> machine name i have a problem.
As long as it remains "locahost" it is fine.
Any idea as to what is going wrong? am able to access the application from another machine.
If I do :7001/ppo/home.jsp">http://<machine-name>:7001/ppo/home.jsp it works fine and am able to login.
thanks
karthik.
public void login(WebRequest webRequest){
String userName = getTestParameter(USERNAME_KEY);
String password = getTestParameter(PASSWORD_KEY);
FormAuthentication fa = new FormAuthentication(userName, password);
webRequest.setRedirectorName("ServletRedirector");
webRequest.setAuthentication(fa);
String hostname=System.getProperty("hostName");
String port=System.getProperty("port");
String firstPart = hostname+":"+port;
String secondPart = "/ppo";
String thirdPart = "/home.jsp";
System.out.println("Url: " + firstPart + secondPart + thirdPart);
webRequest.setURL(firstPart, secondPart, thirdPart, null, null);
}
[junit] ------------- Standard Output ---------------
[junit] user: mdoadmin, password: mdoadmin
[junit] Created FormAuthentication
[junit] Hostname:port got=sjain:7001
[junit] Url: sjain:7001/ppo/home.jsp
[junit] ------------- ---------------- ---------------
[junit] ------------- Standard Error -----------------
[junit] log4j:ERROR No appenders could be found for category (org.apache.cac
tus.client.initialization.ClientInitializer).
[junit] log4j:ERROR Please initialize the log4j system properly.
[junit] ------------- ---------------- ---------------
[junit] Testcase: testMarkdownSearch(com.i2.mdo.unittest.MarkdownSearchTest)
: Caused an ERROR
[junit] Failed to authenticate the principal
[junit] org.apache.cactus.util.ChainedRuntimeException: Failed to authentica
te the principal
[junit] at org.apache.cactus.client.authentication.FormAuthentication.au
thenticate$ajcPostAround24(FormAuthentication.java;org/apache/cactus/util/log/Lo
gAspect.aj(1k):314)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.au
thenticate$ajcPostAround24$ajcVoidWrapper(FormAuthentication.java;org/apache/cac
tus/util/log/LogAspect.aj(1k))
[junit] at org.apache.cactus.client.authentication.FormAuthentication.au
thenticate(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1
151)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.co
nfigure$ajcPostAround15(FormAuthentication.java;org/apache/cactus/util/log/LogAs
pect.aj(1k):155)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.co
nfigure$ajcPostAround15$ajcVoidWrapper(FormAuthentication.java;org/apache/cactus
/util/log/LogAspect.aj(1k))
[junit] at org.apache.cactus.client.authentication.FormAuthentication.co
nfigure(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1151
)
[junit] at org.apache.cactus.client.connector.http.HttpClientConnectionH
elper.connect$ajcPostAround9(HttpClientConnectionHelper.java;org/apache/cactus/u
til/log/LogAspect.aj(1k):123)
[junit] at org.apache.cactus.client.connector.http.HttpClientConnectionH
elper.connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspe
ct.aj(1k):1222)
[junit] at org.apache.cactus.client.connector.http.DefaultHttpClient.cal
lRunTest(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):202)
[junit] at org.apache.cactus.client.connector.http.DefaultHttpClient.doT
est$ajcPostAround7(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.a
j(1k):119)
[junit] at org.apache.cactus.client.connector.http.DefaultHttpClient.doT
est(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1222)
[junit] at org.apache.cactus.AbstractWebServerTestCase.runWebTest(Abstra
ctWebServerTestCase.java:272)
[junit] at org.apache.cactus.AbstractWebServerTestCase.runGenericTest(Ab
stractWebServerTestCase.java:214)
[junit] at org.apache.cactus.AbstractWebServerTestCase.runTest(AbstractW
ebServerTestCase.java:287)
[junit] at org.apache.cactus.AbstractClientTestCase.runBare(AbstractClie
ntTestCase.java:289)
[junit] org.apache.cactus.client.ClientException: Failed to create Cookie he
ader for [domain = [sjain, path = [/ppo/j_security_check, cookies = [[Lorg.apach
e.commons.httpclient.Cookie;@69cb75]]. Turn on HttpClient logging for more infor
mation about the error
[junit] at org.apache.cactus.client.connector.http.AbstractConnectionHel
per.createCookieHeader(AbstractConnectionHelper.java;org/apache/cactus/util/log/
LogAspect.aj(1k):270)
[junit] at org.apache.cactus.client.connector.http.AbstractConnectionHel
per.getCookieString$ajcPostAround6(AbstractConnectionHelper.java;org/apache/cact
us/util/log/LogAspect.aj(1k):221)
[junit] at org.apache.cactus.client.connector.http.AbstractConnectionHel
per.getCookieString(AbstractConnectionHelper.java;org/apache/cactus/util/log/Log
Aspect.aj(1k):1222)
[junit] at org.apache.cactus.client.connector.http.HttpClientConnectionH
elper.connect$ajcPostAround9(HttpClientConnectionHelper.java;org/apache/cactus/u
til/log/LogAspect.aj(1k):155)
[junit] at org.apache.cactus.client.connector.http.HttpClientConnectionH
elper.connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspe
ct.aj(1k):1222)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.au
thenticate$ajcPostAround24(FormAuthentication.java;org/apache/cactus/util/log/Lo
gAspect.aj(1k):299)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.au
thenticate$ajcPostAround24$ajcVoidWrapper(FormAuthentication.java;org/apache/cac
tus/util/log/LogAspect.aj(1k))
[junit] at org.apache.cactus.client.authentication.FormAuthentication.au
thenticate(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1
151)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.co
nfigure$ajcPostAround15(FormAuthentication.java;org/apache/cactus/util/log/LogAs
pect.aj(1k):155)
[junit] at org.apache.cactus.client.authentication.FormAuthentication.co
nfigure$ajcPostAround15$ajcVoidWrapper(FormAuthentication.java;org/apache/cactus
/util/log/LogAspect.aj(1k))
[junit] at org.apache.cactus.client.authentication.FormAuthentication.co
nfigure(FormAuthentication.java;org/apache/cactus/util/log/LogAspect.aj(1k):1151
)
[junit] at org.apache.cactus.client.connector.http.HttpClientConnectionH
elper.connect$ajcPostAround9(HttpClientConnectionHelper.java;org/apache/cactus/u
til/log/LogAspect.aj(1k):123)
[junit] at org.apache.cactus.client.connector.http.HttpClientConnectionH
elper.connect(HttpClientConnectionHelper.java;org/apache/cactus/util/log/LogAspe
ct.aj(1k):1222)
[junit] at org.apache.cactus.client.connector.http.DefaultHttpClient.cal
lRunTest(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):202)
[junit] at org.apache.cactus.client.connector.http.DefaultHttpClient.doT
est$ajcPostAround7(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.a
j(1k):119)
[junit] at org.apache.cactus.client.connector.http.DefaultHttpClient.doT
est(DefaultHttpClient.java;org/apache/cactus/util/log/LogAspect.aj(1k):1222)
[junit] at org.apache.cactus.AbstractWebServerTestCase.runWebTest(Abstra
ctWebServerTestCase.java:272)
[junit] at org.apache.cactus.AbstractWebServerTestCase.runGenericTest(Ab
stractWebServerTestCase.java:214)
[junit] at org.apache.cactus.AbstractWebServerTestCase.runTest(AbstractW
ebServerTestCase.java:287)
[junit] at org.apache.cactus.AbstractClientTestCase.runBare(AbstractClie
ntTestCase.java:289)
[junit] TEST com.i2.mdo.unittest.MarkdownSearchTest FAILED
[echo] creating D:\CCVws\mdo_nov22_view\RetailPriceOptimizer\build\tests\report
---------------------------------
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Vincent Massol [mailto:vmassol@pivolis.com]
> Sent: 26 June 2003 09:05
> To: 'Cactus Users List'
> Subject: RE: Building Cactus with Maven -> I'd like to volonteer
[snip]
>
> Yes, Maven can handle this. The easiest solution (if we don't want to
> change the current src structure), involves doing some copy: copy
> j2ee${j2ee.api}/** and share/** to a target-${j2ee.api}/src directory
> and then point Maven to target-${j2ee.api}/src.
Actually I forgot that there is another solution (reminded to me by
Brett on the maven mailing list):
<preGoal name="java:compile">
<ant:path id="maven.j2ee.compile.src.set"
location="${pom.build.sourceDirectory}/../${j2ee.version}"/>
<maven:addPath id="maven.compile.src.set"
refid="maven.j2ee.compile.src.set"/>
</preGoal>
[snip]
-Vincent
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 25 June 2003 23:33
> To: Cactus Users List
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
[snip]
> > - Maven does *not* understand multiple source directories. It is
> possible to
> > give it the root of the source directories, and then it will walk
thru
> them
> > (nice), but in Cactus' case there are the same classes in the j2ee12
and
> > j2ee13 repositories, so I'm having some duplicate class errors. What
> you're
> > doing here (copy/pasting directories) is too Ant-like I'm afraid.
> Besides,
> > it's a really weird idea... Couldn't you put everything in the same
> tree, and
> > use a factory?? I understand that some parts of the j2ee 1.2 spec
are
> > deprecated and outdated, but hey, there's anyway lots of
old/deprecated
> stuff
> > in the "share" directory.
> > Anyway, I don't think a Maven build can be done easily without a
grand
> unified
> > source tree.
> > BTW, my build succeeds because I wiped off the j2ee12 tree, which is
> useless
> > to me.
>
> It is not easily possible to eliminate the parallel source directories
> for j2ee12/j2ee13. It's not just about deprecation, but also about new
> methods and interfaces that have been added in j2ee13.
>
> I would assume that Maven can actually handle this, and that you've
just
> not found the correct approach yet. If it can't handle this, well, ...
> ugh. Show stopper.
Yes, Maven can handle this. The easiest solution (if we don't want to
change the current src structure), involves doing some copy: copy
j2ee${j2ee.api}/** and share/** to a target-${j2ee.api}/src directory
and then point Maven to target-${j2ee.api}/src.
[snip]
> > - The PMD & checkstyle reports are producing lots of errors (wrong
> brackets
> > and everything), but some interesting things do show up (use of
Vector
> for
> > example)
>
> Why would we want to run both PMD and Checkstyle? We have been running
> Checkstyle all the time, and there's a configuration file in the root
> dir (checkstyle.xml). Certainly using any kind of default
configuration
> would cause a lot of violations.
Running PMD is nice I think but we need to decide what rules we would
like to verify. It's good to run them all, look at the generated report
and then tune the rules. For checkstyle, as Chris said, we already know
what we want.
>
> > - The Clover report seems to be half broken, but I think it's the
> > maven-clover-plugin's fault. Anyway that's a non-free software, who
> would
> > actually use that to do some serious work :-)
That's not correct. Cactus owns a Clover license and it's free. I know
you were joking but I really like Clover ;-)
>
> IIUC, the Clover support in Maven isn't quite up to the task yet,
> because we need to generate the report after multiple test runs and
> builds of sub-projects have finished (framework, integration/ant,
> samples/servlet)... Vincent should know the details.
Yep... :-) There's some work to be done there but it's quite easy I
think. Maven has a "clover:on", "clover:off" feature that should support
this use case. Need to experiment with it though.
>
> > - JUnit, javadoc and all the other reports I've tried were ok.
> >
> > Concerning today's emails :
> > - I think the Maven-built web site can be customized. I have never
done
> it
> > before, thus.
It is possible by providing our own templates (by overriding the
maven.xdoc.pomDocuments and maven.xdoc.projectInfo properties). These
templates have to be velocity templates ATM.
That said, we are free to not use the xdoc and sites plugins provided by
Maven and instead use ours. It is quite easy to do actually. Another,
probably easier solution is to modify the xdoc plugin to support XSL
stylesheets.
The devil is probably in the details... :-) (like parameter passing,
etc)
> > - There's a maven-gump plug-in, so Gump intergration should be
possible.
> I'm a
> > CruiseControl user, so I can't really say more about Gump.
>
> The maven-gump plugin would only solve a tiny bit of the problem (it
> just generates the gump descriptor AFAIK). The real problem is that
> Maven needs to be bootstrappable by Gump (which I think is just noble
> theory as of yet), and the Gump must be able to execute our build,
which
> doesn't currently work using a Maven-based build. All this due to
> community "incompatibility", not technical reasons. Sigh.
Yep. I had seen some discussion about this on the Gump mailing list but
I can't recall the outcome (if there were any!).
-Vincent
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Christopher Lenz <cm...@gmx.de>.
Julien Dubois wrote:
> Hi everybody,
Hi Julien,
> I've done 2 maven builds files : one for the framework, and one for the whole
> project (using the Maven Reactor).
> The one I did for the framework is running quite well, it compiles the whole
> thing and creates a web site with lots of cool-looking reports. However I
Would be nice if the reports also had some usefulness ;-)
> have some questions/remarks :
>
> - Maven does *not* understand multiple source directories. It is possible to
> give it the root of the source directories, and then it will walk thru them
> (nice), but in Cactus' case there are the same classes in the j2ee12 and
> j2ee13 repositories, so I'm having some duplicate class errors. What you're
> doing here (copy/pasting directories) is too Ant-like I'm afraid. Besides,
> it's a really weird idea... Couldn't you put everything in the same tree, and
> use a factory?? I understand that some parts of the j2ee 1.2 spec are
> deprecated and outdated, but hey, there's anyway lots of old/deprecated stuff
> in the "share" directory.
> Anyway, I don't think a Maven build can be done easily without a grand unified
> source tree.
> BTW, my build succeeds because I wiped off the j2ee12 tree, which is useless
> to me.
It is not easily possible to eliminate the parallel source directories
for j2ee12/j2ee13. It's not just about deprecation, but also about new
methods and interfaces that have been added in j2ee13.
I would assume that Maven can actually handle this, and that you've just
not found the correct approach yet. If it can't handle this, well, ...
ugh. Show stopper.
> - The AspectJ stuff seems to be working, but are you just using it for logging
> the methods?? Or is there some other use i haven't found out? I'm an
> AspectWerkz user, so I'm not AspectJ-familiar and I might not have this
> right.
Right, AspectJ is only used for logging. I'm not particularly happy
about that personally, but there are plans -- albeit not concrete -- to
extend the usage of AspectJ to other areas.
> - The PMD & checkstyle reports are producing lots of errors (wrong brackets
> and everything), but some interesting things do show up (use of Vector for
> example)
Why would we want to run both PMD and Checkstyle? We have been running
Checkstyle all the time, and there's a configuration file in the root
dir (checkstyle.xml). Certainly using any kind of default configuration
would cause a lot of violations.
> - The Clover report seems to be half broken, but I think it's the
> maven-clover-plugin's fault. Anyway that's a non-free software, who would
> actually use that to do some serious work :-)
IIUC, the Clover support in Maven isn't quite up to the task yet,
because we need to generate the report after multiple test runs and
builds of sub-projects have finished (framework, integration/ant,
samples/servlet)... Vincent should know the details.
> - JUnit, javadoc and all the other reports I've tried were ok.
>
> Concerning today's emails :
> - I think the Maven-built web site can be customized. I have never done it
> before, thus.
> - There's a maven-gump plug-in, so Gump intergration should be possible. I'm a
> CruiseControl user, so I can't really say more about Gump.
The maven-gump plugin would only solve a tiny bit of the problem (it
just generates the gump descriptor AFAIK). The real problem is that
Maven needs to be bootstrappable by Gump (which I think is just noble
theory as of yet), and the Gump must be able to execute our build, which
doesn't currently work using a Maven-based build. All this due to
community "incompatibility", not technical reasons. Sigh.
--
Christopher Lenz
/=/ cmlenz at gmx.de
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: Christopher Lenz [mailto:cmlenz@gmx.de]
> Sent: 27 June 2003 10:38
> To: Cactus Users List
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
>
> Julien Dubois wrote:
> > - The PMD & checkstyle reports are producing lots of errors (wrong
> brackets
> > and everything), but some interesting things do show up (use of
Vector
> for
> > example)
>
> Hmm, we should get rid of Vector and Hashtable, and use Lists and Maps
> instead. Anyone opposed to such a move (post 1.5)? Otherwise I'll add
it
> to the TODO list.
You mean drop support for JDK 1.1? Yeah, I guess we could do that. +0
from me.
-Vincent
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Christopher Lenz <cm...@gmx.de>.
Julien Dubois wrote:
> - The PMD & checkstyle reports are producing lots of errors (wrong brackets
> and everything), but some interesting things do show up (use of Vector for
> example)
Hmm, we should get rid of Vector and Hashtable, and use Lists and Maps
instead. Anyone opposed to such a move (post 1.5)? Otherwise I'll add it
to the TODO list.
--
Christopher Lenz
/=/ cmlenz at gmx.de
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Julien Dubois <ju...@julien-dubois.com>.
Hi everybody,
I've done 2 maven builds files : one for the framework, and one for the whole
project (using the Maven Reactor).
The one I did for the framework is running quite well, it compiles the whole
thing and creates a web site with lots of cool-looking reports. However I
have some questions/remarks :
- Maven does *not* understand multiple source directories. It is possible to
give it the root of the source directories, and then it will walk thru them
(nice), but in Cactus' case there are the same classes in the j2ee12 and
j2ee13 repositories, so I'm having some duplicate class errors. What you're
doing here (copy/pasting directories) is too Ant-like I'm afraid. Besides,
it's a really weird idea... Couldn't you put everything in the same tree, and
use a factory?? I understand that some parts of the j2ee 1.2 spec are
deprecated and outdated, but hey, there's anyway lots of old/deprecated stuff
in the "share" directory.
Anyway, I don't think a Maven build can be done easily without a grand unified
source tree.
BTW, my build succeeds because I wiped off the j2ee12 tree, which is useless
to me.
- The AspectJ stuff seems to be working, but are you just using it for logging
the methods?? Or is there some other use i haven't found out? I'm an
AspectWerkz user, so I'm not AspectJ-familiar and I might not have this
right.
- The PMD & checkstyle reports are producing lots of errors (wrong brackets
and everything), but some interesting things do show up (use of Vector for
example)
- The Clover report seems to be half broken, but I think it's the
maven-clover-plugin's fault. Anyway that's a non-free software, who would
actually use that to do some serious work :-)
- JUnit, javadoc and all the other reports I've tried were ok.
Concerning today's emails :
- I think the Maven-built web site can be customized. I have never done it
before, thus.
- There's a maven-gump plug-in, so Gump intergration should be possible. I'm a
CruiseControl user, so I can't really say more about Gump.
HTH,
--
Julien Dubois
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: news [mailto:news@main.gmane.org] On Behalf Of Christopher Lenz
> Sent: 25 June 2003 14:36
> To: cactus-user@jakarta.apache.org
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
>
[snip]
> > Not sure here. I'd say the requirements is that there is at least a
> > nightly build done with recent versions of dependencies. I'm not
sure it
> > has to be done by gump though. But ok to start with this req.
>
> I'm sure the Maven community is planning the next big thing to replace
> Gump ;-)
>
> Anyway, I'd consider moving away from Gump a very radical step. OTOH I
> think
> we have been stretching Gump a bit, by trying to make it generate our
> nightly builds, publish our website, etc.
>
> I have been thinking about setting up CruiseControl somewhere to do
> nightly
> builds. In contrast to Gump, it'd use the lated released version of
any
> dependancy, because that's also the baseline for releases. It would
upload
> the files to our nightly build area, and publish the website,
including
> Clover coverage reports etc. So we'd have more reliable nightly builds
and
> website updates, while the integration builds would be performed by
Gump.
>
> When moving towards a release, we could even promote an existing
stable
> nightly build to beta, rc or release status (similar to what the
eclipse
> guys do AFAIK).
>
> The only question is where that should be setup. I will probably start
on
> my
> home machine, and see how well it goes.
Sure. Using Maven and CruiseControl is something that I'd also like to
try... while waiting for Continuum to appear... ;-)
>
> >>- I don't like the default Maven documentation/site style. It should
> > be
> >>possible to keep our current style, which we put a lot of work into.
> >
> > ... or improve the Maven style... ;-)
>
> Nah, I really dislike that so many of the Maven generated sites look
> exactly
> the same. Cactus is a Jakarta subproject, and should strive to keep a
> somewhat consistent look with the rest of the family (too many
subprojects
> ignore this already, many of which have left the jakarta umbrella
> recently).
>
> It's not that Maven doesn't allow pluggable styles, is it?
I think you can provide your own stylesheet but I'll need to give it a
closer look as I've never used that feature.
>
> > Honestly, my interest in moving the build to Maven is twice:
> > - get a simpler build system for Cactus
> > - at the same time, test and improve Maven using Cactus as a guinea
pig.
> > In other words, I trust in Maven but it has some rough edges and
using a
> > real and complex project to smoothen them is the best way to go I
> > believe.
>
> If it makes the build simpler, cool.
It will.
>
> If it's just about auto-downloading JAR files, we could also add an
Ant
> script similar to what the Tomcat folks have done. A benefit of that
> approach is that the downloading is optional and only performed when
the
> user explicitly requests it.
Same with Maven... :-)
-Vincent
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
>>Let me add a couple of concerns/requirements:
>>
>>- We should not depend on Maven CVS HEAD or SNAPSHOT-something for the
>>build, only on a released "stable" version. Of course that would slow
> down
>>the migration if our build requires changes to Maven, because we'd
> need to
>>wait until those changes get incorporated into a release.
>
> Hum... Why not view it this way:
> - we use the latest Maven from CVS (we have to) to create the build
> system
> - once we consider it good enough for our users we wait for a stable
> Maven release and announce it as ready.
Okay
>>- Instead of putting the Maven-based build into a branch, we should be
>>able
>>to just put it in CVS HEAD. But maybe I'm missing something, and it
> may
>>conflict with the Ant-based build?
>
> No it's not conflicting. I'd just not like to commit something that is
> half working in HEAD for the 1.5 release with is Real Soon Now (TM) :-)
Oh yes. We *really* need to get this release thing sorted out... sigh
>>- The Ant build files remain the authorative, official build process
>>*until*
>>a vote is casted and agreed upon to completely switch to Maven.
>
> Yep. Agreed.
>
>>- Cactus *must* be buildable by Gump. While I don't know the details,
> it
>>seems like many Mavenized projects either don't care about Gump, or
> keep a
>>separately maintained Ant build file. IIRC Maven can autogenerate Ant
>>build
>>files, but how well does that work for a non-trivial project?
>
> Not sure here. I'd say the requirements is that there is at least a
> nightly build done with recent versions of dependencies. I'm not sure it
> has to be done by gump though. But ok to start with this req.
I'm sure the Maven community is planning the next big thing to replace Gump ;-)
Anyway, I'd consider moving away from Gump a very radical step. OTOH I think
we have been stretching Gump a bit, by trying to make it generate our
nightly builds, publish our website, etc.
I have been thinking about setting up CruiseControl somewhere to do nightly
builds. In contrast to Gump, it'd use the lated released version of any
dependancy, because that's also the baseline for releases. It would upload
the files to our nightly build area, and publish the website, including
Clover coverage reports etc. So we'd have more reliable nightly builds and
website updates, while the integration builds would be performed by Gump.
When moving towards a release, we could even promote an existing stable
nightly build to beta, rc or release status (similar to what the eclipse
guys do AFAIK).
The only question is where that should be setup. I will probably start on my
home machine, and see how well it goes.
>>- I don't like the default Maven documentation/site style. It should
> be
>>possible to keep our current style, which we put a lot of work into.
>
> ... or improve the Maven style... ;-)
Nah, I really dislike that so many of the Maven generated sites look exactly
the same. Cactus is a Jakarta subproject, and should strive to keep a
somewhat consistent look with the rest of the family (too many subprojects
ignore this already, many of which have left the jakarta umbrella recently).
It's not that Maven doesn't allow pluggable styles, is it?
> Honestly, my interest in moving the build to Maven is twice:
> - get a simpler build system for Cactus
> - at the same time, test and improve Maven using Cactus as a guinea pig.
> In other words, I trust in Maven but it has some rough edges and using a
> real and complex project to smoothen them is the best way to go I
> believe.
If it makes the build simpler, cool.
If it's just about auto-downloading JAR files, we could also add an Ant
script similar to what the Tomcat folks have done. A benefit of that
approach is that the downloading is optional and only performed when the
user explicitly requests it.
-chris
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
> -----Original Message-----
> From: news [mailto:news@main.gmane.org] On Behalf Of Christopher Lenz
> Sent: 25 June 2003 12:47
> To: cactus-user@jakarta.apache.org
> Subject: Re: Building Cactus with Maven -> I'd like to volonteer
>
> Vincent Massol wrote:
> >>-----Original Message-----
> >>From: Julien Dubois [mailto:julien@julien-dubois.com]
> >>Sent: 23 June 2003 21:26
> >>To: cactus-user@jakarta.apache.org
> >>Subject: Building Cactus with Maven -> I'd like to volonteer
> >>
> >>I don't want to spend too much time downloading stuff/configuring
> >>eclipse, so I'd like to volonteer for porting Cactus to Maven. I see
> >>that you plan to do so, and I've already worked with Maven before,
so
> >>I think I should be able to help.
>
> I don't think that a migration to Maven will be faster than
downloading a
> couple of JARs, but anyway...
certainly not! There are several order of magnitude of complexity and
time differences... Julien, I hope that this is not your only motivation
:-)
>
> > Very cool :-). I'm all for trying the move to Maven. However, there
is
> > one rule that I'd like us to follow: we must not loose any build
feature
> > when moving to Maven compared to our existing Ant build. This will
be
> > *very* challenging and will require Maven changes too (but that's
ok,
> > I'm a Maven committer and I can commit these changes).
> >
> > So here's my suggestion:
> > - you start making the move for some subproject. Probably starting
with
> > jakarta-cactus/framework is the easiest
> > - you send us the patch on the Cactus dev mailing list
> > - we'll review it and comment on it
> > - if ok, I'll create a branch until we finish releasing Cactus 1.5
and
> > then move the Maven build to HEAD.
> > - as you get more and more confident about the Cactus build and if
> > you're still interested in participating and maintaining the Cactus
> > build, then we would eventually be able to vote you in as a
committer
> > (please realize that we will need to ensure of your commitment and
> > Cactus build knowledge before making such a decision).
>
> deja vu
> http://archives.apache.org/eyebrowse/ReadMsg?listName=cactus-
> dev@jakarta.apache.org&msgId=371570
> ;-)
hey, that's true. Jason, what's up? :-)
>
> > What you must realize is that once you start working on this, you'll
> > have to help us all the way till the full Maven build works. It will
be
> > a long running project as we're doing clever stuff in the Ant
build...
> > :-)
>
> Let me add a couple of concerns/requirements:
>
> - We should not depend on Maven CVS HEAD or SNAPSHOT-something for the
> build, only on a released "stable" version. Of course that would slow
down
> the migration if our build requires changes to Maven, because we'd
need to
> wait until those changes get incorporated into a release.
Hum... Why not view it this way:
- we use the latest Maven from CVS (we have to) to create the build
system
- once we consider it good enough for our users we wait for a stable
Maven release and announce it as ready.
>
> - Instead of putting the Maven-based build into a branch, we should be
> able
> to just put it in CVS HEAD. But maybe I'm missing something, and it
may
> conflict with the Ant-based build?
No it's not conflicting. I'd just not like to commit something that is
half working in HEAD for the 1.5 release with is Real Soon Now (TM) :-)
>
> - The Ant build files remain the authorative, official build process
> *until*
> a vote is casted and agreed upon to completely switch to Maven.
Yep. Agreed.
>
> - Cactus *must* be buildable by Gump. While I don't know the details,
it
> seems like many Mavenized projects either don't care about Gump, or
keep a
> separately maintained Ant build file. IIRC Maven can autogenerate Ant
> build
> files, but how well does that work for a non-trivial project?
Not sure here. I'd say the requirements is that there is at least a
nightly build done with recent versions of dependencies. I'm not sure it
has to be done by gump though. But ok to start with this req.
>
> - I don't like the default Maven documentation/site style. It should
be
> possible to keep our current style, which we put a lot of work into.
... or improve the Maven style... ;-)
Honestly, my interest in moving the build to Maven is twice:
- get a simpler build system for Cactus
- at the same time, test and improve Maven using Cactus as a guinea pig.
In other words, I trust in Maven but it has some rough edges and using a
real and complex project to smoothen them is the best way to go I
believe.
That said, getting help from Jason would also help tremendously... ;-)
Thanks
-Vincent
Re: Building Cactus with Maven -> I'd like to volonteer
Posted by Christopher Lenz <cm...@gmx.de>.
Vincent Massol wrote:
>>-----Original Message-----
>>From: Julien Dubois [mailto:julien@julien-dubois.com]
>>Sent: 23 June 2003 21:26
>>To: cactus-user@jakarta.apache.org
>>Subject: Building Cactus with Maven -> I'd like to volonteer
>>
>>I don't want to spend too much time downloading stuff/configuring
>>eclipse, so I'd like to volonteer for porting Cactus to Maven. I see
>>that you plan to do so, and I've already worked with Maven before, so
>>I think I should be able to help.
I don't think that a migration to Maven will be faster than downloading a
couple of JARs, but anyway...
> Very cool :-). I'm all for trying the move to Maven. However, there is
> one rule that I'd like us to follow: we must not loose any build feature
> when moving to Maven compared to our existing Ant build. This will be
> *very* challenging and will require Maven changes too (but that's ok,
> I'm a Maven committer and I can commit these changes).
>
> So here's my suggestion:
> - you start making the move for some subproject. Probably starting with
> jakarta-cactus/framework is the easiest
> - you send us the patch on the Cactus dev mailing list
> - we'll review it and comment on it
> - if ok, I'll create a branch until we finish releasing Cactus 1.5 and
> then move the Maven build to HEAD.
> - as you get more and more confident about the Cactus build and if
> you're still interested in participating and maintaining the Cactus
> build, then we would eventually be able to vote you in as a committer
> (please realize that we will need to ensure of your commitment and
> Cactus build knowledge before making such a decision).
deja vu
http://archives.apache.org/eyebrowse/ReadMsg?listName=cactus-dev@jakarta.apache.org&msgId=371570
;-)
> What you must realize is that once you start working on this, you'll
> have to help us all the way till the full Maven build works. It will be
> a long running project as we're doing clever stuff in the Ant build...
> :-)
Let me add a couple of concerns/requirements:
- We should not depend on Maven CVS HEAD or SNAPSHOT-something for the
build, only on a released "stable" version. Of course that would slow down
the migration if our build requires changes to Maven, because we'd need to
wait until those changes get incorporated into a release.
- Instead of putting the Maven-based build into a branch, we should be able
to just put it in CVS HEAD. But maybe I'm missing something, and it may
conflict with the Ant-based build?
- The Ant build files remain the authorative, official build process *until*
a vote is casted and agreed upon to completely switch to Maven.
- Cactus *must* be buildable by Gump. While I don't know the details, it
seems like many Mavenized projects either don't care about Gump, or keep a
separately maintained Ant build file. IIRC Maven can autogenerate Ant build
files, but how well does that work for a non-trivial project?
- I don't like the default Maven documentation/site style. It should be
possible to keep our current style, which we put a lot of work into.
-chris
RE: Building Cactus with Maven -> I'd like to volonteer
Posted by Vincent Massol <vm...@pivolis.com>.
Hi Julien,
> -----Original Message-----
> From: Julien Dubois [mailto:julien@julien-dubois.com]
> Sent: 23 June 2003 21:26
> To: cactus-user@jakarta.apache.org
> Subject: Building Cactus with Maven -> I'd like to volonteer
>
> Hi,
>
> I'm trying to compile Cactus from CVS HEAD, and it's quite difficult
> because
> you need to grab several libraries (and I'm not the only one, see
>
http://www.mail-archive.com/cactus-user@jakarta.apache.org/msg03273.html
).
true
>
> Besides, the "building cactus" page
> (http://jakarta.apache.org/cactus/participating/howto_build.html)
seems to
> lack some information. For example, there's nothing concerning the
> HttpClient
> library, which is needed (for example for compiling the WebResponse
> class).
I guess Chris has just updated this in CVS and the web site will be
updated by the next GUMP build in a few hours.
>
> I don't want to spend too much time downloading stuff/configuring
eclipse,
> so
> I'd like to volonteer for porting Cactus to Maven. I see that you plan
to
> do
> so, and I've already worked with Maven before, so I think I should be
able
> to
> help.
Very cool :-). I'm all for trying the move to Maven. However, there is
one rule that I'd like us to follow: we must not loose any build feature
when moving to Maven compared to our existing Ant build. This will be
*very* challenging and will require Maven changes too (but that's ok,
I'm a Maven committer and I can commit these changes).
So here's my suggestion:
- you start making the move for some subproject. Probably starting with
jakarta-cactus/framework is the easiest
- you send us the patch on the Cactus dev mailing list
- we'll review it and comment on it
- if ok, I'll create a branch until we finish releasing Cactus 1.5 and
then move the Maven build to HEAD.
- as you get more and more confident about the Cactus build and if
you're still interested in participating and maintaining the Cactus
build, then we would eventually be able to vote you in as a committer
(please realize that we will need to ensure of your commitment and
Cactus build knowledge before making such a decision).
What you must realize is that once you start working on this, you'll
have to help us all the way till the full Maven build works. It will be
a long running project as we're doing clever stuff in the Ant build...
:-)
If I haven't scared you, then, welcome aboard! Awaiting eagerly your
patches :-)
Thanks!
-Vincent
>
> Waiting for your response,
> --
>
> Julien Dubois
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org