[jira] Commented: (XPR-75) Migrating build to Maven

    [ http://jira.codehaus.org/browse/XPR-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=180391#action_180391 ]

Imran commented on XPR-75:
--------------------------

Hi

I know this issue is been opened for a while now. Was wondering if anyone is actively working on this. Having gone through the comments trail I sensed a bit of reluctance on converting this to a maven build (understandably based on the time frame the comments were made). However I feel maven has come along way now and there are many who have made the transition or is willing to do so. Is there any reason why XPlanner wouldn't go down that path or is it merely a bandwidth issue. Would love to help if the votes are to implement this. I'm in the process of  getting XPlanner building in my local and look forward in the possibilities of contributing to improve/add on features. Let me know your thoughts

Cheers
-- Imran

> Migrating build to Maven
> ------------------------
>
>                 Key: XPR-75
>                 URL: http://jira.codehaus.org/browse/XPR-75
>             Project: xplanner
>          Issue Type: Task
>          Components: Build
>    Affects Versions: 0.8
>         Environment: Any OS, Maven 1.1 Beta 1
>            Reporter: Brill Pappin
>            Priority: Minor
>             Fix For: 0.9
>
>         Attachments: codehaus-java-xplanner.zip, jmonkey-java-xtracker.zip
>
>   Original Estimate: 4 hours
>  Remaining Estimate: 4 hours
>
> For reference, the IDEA plugin docs can be found at:
> http://maven.apache.org/reference/plugins/idea/
> and the Eclipse plugin docs at:
> http://maven.apache.org/reference/plugins/eclipse/
> I've got a basic maven build... there are a few problems that will
> require a bit of refactoring to fix though. FYI I'm using Maven 1.1beta1
> but this stuff *should* work for Maven 1.0.3 as well.
> - A few unit tests are failing legitimately... this is likely because
> you were using TestAll suites and forgot to add them (a common problem
> which maven doesn't suffer from) though I haven't checked that.
> - The acceptance and performance tests are mixed up with your unit
> tests, so I had to exclude them temporarily until the issue can be
> properly addressed.
> - TLDs are in the WEB-INF which is not spec, they should be in
> WEB-INF/tld so I had to deviate from the standard maven war a bit to
> satisfy the current code base.
> - The Maven SOAP plugin works a little differently than the way you guys
> have your ant build setup so after adoption we'd have to write up some
> custom goals to use it the same way, or redo how those tests are run so
> that everything works. Currently those tests are excluded.
> I have not done any of the refactoring I mentioned but am willing to
> help with it should Maven be adopted by the xplanner team.
> Using Maven may have a few growing pains for you if your not used to
> using it (it's very different on the outside than Ant), but the problems
> are likely easy to explain and I can help with those.
> Two files are attached:
> codehaus-java-xplanner.zip is the xplanner demo
> jmonkey-java-xtracker.zip is the current version of xtracker for comparison.
> To use codehaus-java-xplanner.zip:
> - extract it
> - edit project.properties and change the "xplanner.module.dir" property
> to  point at your current (live) checkout.
> - run "maven xplanner:sync". This is a custom goal (in maven.xml) I
> wrote to help me port, it would be deleted if Maven is adopted.
> - from here you can simply run "maven war" to generate the war, however
> not all tests are passing and they would have to be fixed first. You can
> force it to build the war with "maven -Dmaven.test.skip=true war" but
> thats not really a good way to go :)
> - run "maven idea" to generate the IDEA project files, or "maven
> eclipse" to generate project files for Eclipse. Eclipse takes a minor
> setup procedure to work (running "maven eclipse:add-maven-repo" should
> do it though), but I've never tried it with IDEA so I don't know what
> you'll find.
> the xtracker zip is pretty much the same, only without the custom goal.
> the hibernate and deployment stuff will only partially work in xtracker
> because I've removed any of the sensitive properties they use. Maven
> uses "goal" similar to Ant "tasks" except that most of them are built
> into Maven. A list of existing plugin can be found at
> http://maven.apache.org/ (left side under Getting Plugins).
> Anyway, this should give you a good idea of how it works, although
> porting is not finished. I'd recommend that if people are interested in
> using it, you wait for your next release and spike after that iteration
> to work out the kinks.
> Feel free to ask questions or for help if you need it. There is
> certainly more work to do, but I didn't want to change anything
> fundamental until it's adopted, at which point refactoring can be done
> to make everything run smoothly.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email