[
https://issues.apache.org/jira/browse/PLUTO-259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12470097
]
David DeWolf commented on PLUTO-259:
------------------------------------
I'm moving all of this to maven. We will have:
1) binary distrition - all libraries (container, web, and util, with docs)
2) source distribution - all sources
3) container-bin - all container libs
4) bundle - with tomcat
all will be created from the parent pom, however, the bundle will be created in
the assembly project and then pulled up during the package phase of the -P
assembly profile.
> Automate new version numbers for new releases
> ---------------------------------------------
>
> Key: PLUTO-259
> URL: https://issues.apache.org/jira/browse/PLUTO-259
> Project: Pluto
> Issue Type: Improvement
> Components: build system
> Affects Versions: 1.1.0-beta2, 1.1.0
> Reporter: Craig Doremus
> Assigned To: David DeWolf
> Priority: Minor
> Fix For: 1.1.0
>
> Attachments: PLUTO-259-firstattempt.patch
>
>
> When a new release is prepared version numbers need to be changed in all
> pom.xml files, dist-build.xml, the pluto-portal-driver-config.xml in the
> pluto-portal module, expectedResults.properties in the portal-testsuite
> module, and environment.properties in pluto-container module. We need to
> automate that process.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
