You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "erik daughtrey (JIRA)" <de...@geronimo.apache.org> on 2005/12/14 18:10:47 UTC
[jira] Created: (GERONIMO-1362) Release notes changes just before 1.0 tag cut caused installer build errors
Release notes changes just before 1.0 tag cut caused installer build errors
---------------------------------------------------------------------------
Key: GERONIMO-1362
URL: http://issues.apache.org/jira/browse/GERONIMO-1362
Project: Geronimo
Type: Bug
Components: installer
Versions: 1.0-M5
Reporter: erik daughtrey
The release notes for prior milestones were deleted and new release notes for 1.0 created.
This caused the installer build to fail since it had hard coded references.
The patch assumes that a RELEASE-NOTES-${pom.currentVersion}.txt will always exist as it now does. This seems reasonable as we move forward even into 1.1. We just need to ensure that a
release notes version for the currentVersion exists.
--
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] Updated: (GERONIMO-1362) Release notes changes just before 1.0 tag cut caused installer build errors
Posted by "erik daughtrey (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1362?page=all ]
erik daughtrey updated GERONIMO-1362:
-------------------------------------
Attachment: installer-1.0-build.patch
This patch fixes the 1.0 build problem related to the IzPack based installer.
To apply the patch:
1. Download the patch to the root of the svn build tree
2. cd to the svn tree for geronimo i.e. the build root
3. run "patch -p0 < installer-1.0-build.patch"
> Release notes changes just before 1.0 tag cut caused installer build errors
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-1362
> URL: http://issues.apache.org/jira/browse/GERONIMO-1362
> Project: Geronimo
> Type: Bug
> Components: installer
> Versions: 1.0
> Reporter: erik daughtrey
> Attachments: installer-1.0-build.patch
>
> The release notes for prior milestones were deleted and new release notes for 1.0 created.
> This caused the installer build to fail since it had hard coded references.
> The patch assumes that a RELEASE-NOTES-${pom.currentVersion}.txt will always exist as it now does. This seems reasonable as we move forward even into 1.1. We just need to ensure that a
> release notes version for the currentVersion exists.
--
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] Closed: (GERONIMO-1362) Release notes changes just before 1.0 tag cut caused installer build errors
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1362?page=all ]
Aaron Mulder closed GERONIMO-1362:
----------------------------------
Fix Version: 1.0
Resolution: Invalid
Assign To: Aaron Mulder
This patch is so... yesterday! (which is to say thanks, but we already fixed the branch :)
> Release notes changes just before 1.0 tag cut caused installer build errors
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-1362
> URL: http://issues.apache.org/jira/browse/GERONIMO-1362
> Project: Geronimo
> Type: Bug
> Components: installer
> Versions: 1.0
> Reporter: erik daughtrey
> Assignee: Aaron Mulder
> Fix For: 1.0
> Attachments: installer-1.0-build.patch
>
> The release notes for prior milestones were deleted and new release notes for 1.0 created.
> This caused the installer build to fail since it had hard coded references.
> The patch assumes that a RELEASE-NOTES-${pom.currentVersion}.txt will always exist as it now does. This seems reasonable as we move forward even into 1.1. We just need to ensure that a
> release notes version for the currentVersion exists.
--
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] Updated: (GERONIMO-1362) Release notes changes just before 1.0 tag cut caused installer build errors
Posted by "erik daughtrey (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-1362?page=all ]
erik daughtrey updated GERONIMO-1362:
-------------------------------------
Version: 1.0
(was: 1.0-M5)
> Release notes changes just before 1.0 tag cut caused installer build errors
> ---------------------------------------------------------------------------
>
> Key: GERONIMO-1362
> URL: http://issues.apache.org/jira/browse/GERONIMO-1362
> Project: Geronimo
> Type: Bug
> Components: installer
> Versions: 1.0
> Reporter: erik daughtrey
>
> The release notes for prior milestones were deleted and new release notes for 1.0 created.
> This caused the installer build to fail since it had hard coded references.
> The patch assumes that a RELEASE-NOTES-${pom.currentVersion}.txt will always exist as it now does. This seems reasonable as we move forward even into 1.1. We just need to ensure that a
> release notes version for the currentVersion exists.
--
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