You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pivot.apache.org by "Patrick Wright (JIRA)" <ji...@apache.org> on 2009/10/23 17:14:59 UTC
[jira] Created: (PIVOT-333) Maven POMs for Pivot (submission)
Maven POMs for Pivot (submission)
---------------------------------
Key: PIVOT-333
URL: https://issues.apache.org/jira/browse/PIVOT-333
Project: Pivot
Issue Type: Improvement
Reporter: Patrick Wright
Priority: Minor
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.
[jira] Updated: (PIVOT-333) Maven POMs for Pivot (submission)
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Brown updated PIVOT-333:
-----------------------------
Fix Version/s: 1.4
> 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
> 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.
[jira] Updated: (PIVOT-333) Maven POMs for Pivot (submission)
Posted by "Todd Volkert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Todd Volkert updated PIVOT-333:
-------------------------------
Component/s: project
> 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
> Priority: Minor
> 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.
[jira] Resolved: (PIVOT-333) Maven POMs for Pivot (submission)
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (PIVOT-333) Maven POMs for Pivot (submission)
Posted by "Patrick Wright (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Patrick Wright updated PIVOT-333:
---------------------------------
Attachment: pivot-poms.tar.gz
All Pivot Maven POM files; unpack from the top-level Pivot directory. Once unpacked, just call
mvn clean install
> Maven POMs for Pivot (submission)
> ---------------------------------
>
> Key: PIVOT-333
> URL: https://issues.apache.org/jira/browse/PIVOT-333
> Project: Pivot
> Issue Type: Improvement
> Reporter: Patrick Wright
> Priority: Minor
> 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.
[jira] Updated: (PIVOT-333) Maven POMs for Pivot (submission)
Posted by "Greg Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PIVOT-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Greg Brown updated PIVOT-333:
-----------------------------
Assignee: Greg Brown
> 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.