[
https://issues.apache.org/jira/browse/PIVOT-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-333.
------------------------------
Resolution: Fixed
POMs for all projects have been checked in, and a "maven-install" target has
been added to the build script.
> Maven POMs for Pivot (submission)
> ---------------------------------
>
> Key: PIVOT-333
> URL: https://issues.apache.org/jira/browse/PIVOT-333
> Project: Pivot
> Issue Type: Improvement
> Components: project
> Reporter: Patrick Wright
> Assignee: Greg Brown
> Priority: Minor
> Fix For: 1.4
>
> Attachments: pivot-poms.tar.gz
>
>
> I'm attaching some Maven POM files for Pivot (all subprojects). I wanted
> these to be able to work more easily with other projects that depend on
> Pivot. I realize these may never be picked up by the project team, as there
> was already some discussion about this months back. Still, it's been helpful
> to me.
> You can build the whole project from the top level, or build any individual
> sub-project. Dependencies between modules are handled correctly, as long as
> you have installed the upstream JAR before (or run an install from the top
> level).
> It works, though there are some kinks to work out. Known issues:
> - when generating the site (website) documentation, the site plugin links to
> submodules are broken, although each submodule website is correctly built
> - the generated JAR file names are not the same as the current Pivot release
> for the wtk and web projects, where more than one JAR file is generated; the
> fix is probably to work with the assembly plugin, but am not sure.
> - missing generation of the demo and tutorials WAR files, and the
> accompanying signed JAR files
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
