You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <ji...@apache.org> on 2006/09/30 15:35:21 UTC
[jira] Created: (PLUTO-259) Automate new version numbers for new
releases
Automate new version numbers for new releases
---------------------------------------------
Key: PLUTO-259
URL: http://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
Priority: Minor
Fix For: 1.1.0
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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-259) Automate new version numbers for new
releases
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (PLUTO-259) Automate new version numbers for new
releases
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David DeWolf resolved PLUTO-259.
--------------------------------
Resolution: Fixed
only see references in pom now.
> 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.
[jira] Assigned: (PLUTO-259) Automate new version numbers for new
releases
Posted by "David DeWolf (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/PLUTO-259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David DeWolf reassigned PLUTO-259:
----------------------------------
Assignee: David DeWolf (was: Elliot Metsger)
> 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.
[jira] Updated: (PLUTO-259) Automate new version numbers for new
releases
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-259?page=all ]
Elliot Metsger updated PLUTO-259:
---------------------------------
Attachment: PLUTO-259-firstattempt.patch
expectedResults.properties, environment.properties are now interpolated during the maven lifecycle using properties set in the parent pom.
pluto-portal-driver-config.xml is interpolated as well, but using a snapshot version of the maven-war-plugin. If the war plugin isn't released soon, the portal code could be updated to search for the driver config on the classpath, which would allow it to be interpolated like the other .properties files (by being placed in src/main/resources).
I patched dist-build.xml to require the pluto.version property be set on the command line.
The pom versions would be updated automatically if the maven release plugin is used.
Assuming the maven release plugin is used, the pluto release would go something like:
1. Manually update <properties> in the parent pom.xml in the trunk working copy.
2. release:prepare, release:perform on the working copy which will tag the release in SVN with correct version numbers
3. Then, 'svn export' the newly created tag
4. Use ant -f dist-build.xml -Dpluto.version=1.1.0 to build the source and binary release packages for the tag.
There's got to be a better way of sharing properties between the ant build and the maven poms.... will continue to dig.
This patch depends on a snapshot version of the maven-war-plugin, so not suitable to be applied yet.
> Automate new version numbers for new releases
> ---------------------------------------------
>
> Key: PLUTO-259
> URL: http://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: Elliot Metsger
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-259) Automate new version numbers for new
releases
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-259?page=comments#action_12442246 ]
Elliot Metsger commented on PLUTO-259:
--------------------------------------
[[ Old comment, sent by email on Fri, 06 Oct 2006 00:18:42 -0400 ]]
I will be out of the office until Monday October 9th, 2006. If you
require assistance, please use the Systems Help Request Form:
http://intranet.mse.jhu.edu/forms/helprequest.php.
If you need immediate assistance please contact Mercy Anaba (x65306,
manaba@jhu.edu), or phone the IT@JH Help Desk (x6-HELP). If it is an
emergency, please instruct the IT@JH Help Desk to contact the Library
Systems On-Call Pager.
[ http://issues.apache.org/jira/browse/PLUTO-259?page=all ]
Elliot Metsger reassigned PLUTO-259:
------------------------------------
Assignee: Elliot Metsger
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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
> Automate new version numbers for new releases
> ---------------------------------------------
>
> Key: PLUTO-259
> URL: http://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: Elliot Metsger
> Priority: Minor
> Fix For: 1.1.0
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (PLUTO-259) Automate new version numbers for new
releases
Posted by "Craig Doremus (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-259?page=comments#action_12458900 ]
Craig Doremus commented on PLUTO-259:
-------------------------------------
The dist-build.xml Ant build file now grabs the version number from the root pom.xml using the xmlproperty task to set the pluto.version property. Commited in SVN revision 487628.
> Automate new version numbers for new releases
> ---------------------------------------------
>
> Key: PLUTO-259
> URL: http://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: Elliot Metsger
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (PLUTO-259) Automate new version numbers for new
releases
Posted by "Elliot Metsger (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/PLUTO-259?page=all ]
Elliot Metsger reassigned PLUTO-259:
------------------------------------
Assignee: Elliot Metsger
> Automate new version numbers for new releases
> ---------------------------------------------
>
> Key: PLUTO-259
> URL: http://issues.apache.org/jira/browse/PLUTO-259
> Project: Pluto
> Issue Type: Improvement
> Components: build system
> Affects Versions: 1.1.0, 1.1.0-beta2
> Reporter: Craig Doremus
> Assigned To: Elliot Metsger
> Priority: Minor
> Fix For: 1.1.0
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira