You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jspwiki.apache.org by "Daniel Johansson (JIRA)" <ji...@apache.org> on 2010/06/05 17:02:00 UTC
[jira] Created: (JSPWIKI-651) Convert JSPWiki to a Maven project
Convert JSPWiki to a Maven project
----------------------------------
Key: JSPWIKI-651
URL: https://issues.apache.org/jira/browse/JSPWIKI-651
Project: JSPWiki
Issue Type: Improvement
Reporter: Daniel Johansson
Priority: Trivial
Hello there, I was hoping to maybe one day contribute to the JSPWiki project and after having checked out the trunk code and played around somewhat I was thinking it would be very nice if this project used Maven.
I'm sure most of you are familiar with Maven in one way or another, you might even have a really good reason for not doing this to JSPWiki.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (JSPWIKI-651) Convert JSPWiki to a Maven project
Posted by Murray Altheim <mu...@altheim.com>.
Janne Jalkanen (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/JSPWIKI-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876086#action_12876086 ]
>
> Janne Jalkanen commented on JSPWIKI-651:
> ----------------------------------------
>
> Personally, I think Maven is one of the most horrendous contraptions
> ever invented by humanity, but if someone else wants to do the work
> and agree to maintain it, go right ahead :-). The reason really is
> that nobody has yet really needed Maven for anything...
>
> (However, I've been playing with Apache Ivy quite a lot lately, and
> that seems much more approachable than Maven and it has really nice
> Ant integration.)
Heh. Yup, I seem to remember that was the reason that Maven never
showed up on our doorstep, and if it did we spirited it quickly
through the house and tossed it in the dumpster.
I've been doing Spring+Ivy development lately and can confirm that
Ivy is certainly a much more reasonable solution. If one is an avid
ant user it's just a logical next step, whereas Maven is like
drinking the Koolaid or swallowing the red pill or kicking yourself
in the head, etc. I'd much rather see someone spend the time with Ivy.
Murray
...........................................................................
Murray Altheim <murray10 at altheim dot com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
[jira] Commented: (JSPWIKI-651) Convert JSPWiki to a Maven project
Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876086#action_12876086 ]
Janne Jalkanen commented on JSPWIKI-651:
----------------------------------------
Personally, I think Maven is one of the most horrendous contraptions ever invented by humanity, but if someone else wants to do the work and agree to maintain it, go right ahead :-). The reason really is that nobody has yet really needed Maven for anything...
(However, I've been playing with Apache Ivy quite a lot lately, and that seems much more approachable than Maven and it has really nice Ant integration.)
> Convert JSPWiki to a Maven project
> ----------------------------------
>
> Key: JSPWIKI-651
> URL: https://issues.apache.org/jira/browse/JSPWIKI-651
> Project: JSPWiki
> Issue Type: Improvement
> Reporter: Daniel Johansson
> Priority: Trivial
>
> Hello there, I was hoping to maybe one day contribute to the JSPWiki project and after having checked out the trunk code and played around somewhat I was thinking it would be very nice if this project used Maven.
> I'm sure most of you are familiar with Maven in one way or another, you might even have a really good reason for not doing this to JSPWiki.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (JSPWIKI-651) Convert JSPWiki to a Maven project
Posted by Murray Altheim <mu...@altheim.com>.
Janne Jalkanen (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/JSPWIKI-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876221#action_12876221 ]
>
> Janne Jalkanen commented on JSPWIKI-651:
> ----------------------------------------
>
> You have good points; it should be easier to get it deployed.
>
> One of the problems is that you need to modify jspwiki.properties
> after installation, and that can't be done if the whole thing is
> wrapped in a WAR. It would be nice if there was a simple way to
> do all that.
Janne,
I haven't worked on it in awhile, but the project I did a few years
back that incorporated an embedded JSPWiki instance used its
cascading properties feature. If that's still functional it's
relatively easy to write a file post-installation, so that's what I
was doing. It worked like a charm.
[For those who aren't aware of the cascading properties feature,
having jspwiki.properties.1, jspwiki.properties.2, etc. files in
the same dierctory as jspwiki.properties will cause overwrite of
any like-named properties.]
Murray
...........................................................................
Murray Altheim <murray10 at altheim dot com> === = =
http://www.altheim.com/murray/ = = ===
SGML Grease Monkey, Banjo Player, Wantanabe Zen Monk = = = =
Boundless wind and moon - the eye within eyes,
Inexhaustible heaven and earth - the light beyond light,
The willow dark, the flower bright - ten thousand houses,
Knock at any door - there's one who will respond.
-- The Blue Cliff Record
[jira] Commented: (JSPWIKI-651) Convert JSPWiki to a Maven project
Posted by "Janne Jalkanen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876221#action_12876221 ]
Janne Jalkanen commented on JSPWIKI-651:
----------------------------------------
You have good points; it should be easier to get it deployed.
One of the problems is that you need to modify jspwiki.properties after installation, and that can't be done if the whole thing is wrapped in a WAR. It would be nice if there was a simple way to do all that.
(One of the chief problems with dependency management systems is that not all of our dependencies are available in Maven repos and the repos can get awfully messy [he said, having spent the entire morning trying to get Selenium to just resolve.])
The best doc is at the root of the source directory in the file called "README".
> Convert JSPWiki to a Maven project
> ----------------------------------
>
> Key: JSPWIKI-651
> URL: https://issues.apache.org/jira/browse/JSPWIKI-651
> Project: JSPWiki
> Issue Type: Improvement
> Reporter: Daniel Johansson
> Priority: Trivial
>
> Hello there, I was hoping to maybe one day contribute to the JSPWiki project and after having checked out the trunk code and played around somewhat I was thinking it would be very nice if this project used Maven.
> I'm sure most of you are familiar with Maven in one way or another, you might even have a really good reason for not doing this to JSPWiki.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (JSPWIKI-651) Convert JSPWiki to a Maven project
Posted by "Daniel Johansson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JSPWIKI-651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876163#action_12876163 ]
Daniel Johansson commented on JSPWIKI-651:
------------------------------------------
Fair enough, the main reason I brought this up was that I was looking at the current ant build script as I was trying to set up my development machine and I couldn't really figure out how to easily start the wiki up after compiling so I rewrote the war build target to copy all the content that's supposed to go into the war file into the build/war directory, then I added a context file for the wiki in my tomcat setup so now I can just build it and start tomcat without having to copy/extract the war file.
There might be an easier way which I'm not aware of, the documentation said something about a build target called opened-war which doesn't exist.
One idea I had in mind was, why not try to integrate Jetty into the war file so you could run the war file using a main class that starts up the Jetty server and deploys the content for you. Maven has a plugin for this which is really nice.
I would be willing to maintain something like this however if another build system is preferred by the developers then Maven would be a step in the wrong direction.
On another note, I've not looked into Ivy that much (yet), but I shall have a look at it.
I just think the development phase needs to be simpler for the developer unless you could point me in the right direction on where I can find information on how to run the wiki locally and debug the source, I might just have missed this somewhere. Thanks.
> Convert JSPWiki to a Maven project
> ----------------------------------
>
> Key: JSPWIKI-651
> URL: https://issues.apache.org/jira/browse/JSPWIKI-651
> Project: JSPWiki
> Issue Type: Improvement
> Reporter: Daniel Johansson
> Priority: Trivial
>
> Hello there, I was hoping to maybe one day contribute to the JSPWiki project and after having checked out the trunk code and played around somewhat I was thinking it would be very nice if this project used Maven.
> I'm sure most of you are familiar with Maven in one way or another, you might even have a really good reason for not doing this to JSPWiki.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.