You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2010/06/30 21:29:49 UTC
[jira] Created: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
-----------------------------------------------------------------------------
Key: UIMA-1823
URL: https://issues.apache.org/jira/browse/UIMA-1823
Project: UIMA
Issue Type: Task
Components: Build, Packaging and Test
Reporter: Marshall Schor
Assignee: Marshall Schor
The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
Suggested order
*uima-jar-resource-bundle
*parent-pom-top (depends in build section on above)
Next batch (no intra-project dependencies)
*uima-build-helper-maven-plugin
*uima-assembly-single-project
*uima-docbook-resource-bundle
*parent-pom-distr
*parent-pom-docbook
Next batch
*parent-pom-ibm-notice
*parent-pom-eclispe-plugins
*parent-pom-annotator
*parent-pom-distr
Next
*parent-pom-eclipse-plugins-ibm-notice
The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
update this to 2.3.1.
The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
(letting us climb the learning curve on using the release plugin), and will be released only
if it is convenient in the future to re-release a bunch of these without concern for
simultaneously updating the dependency versions in the <build> sections of the sub-modules.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1823:
---------------------------------
Description:
The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
Suggested order
*uima-jar-resource-bundle (done)
*parent-pom-top (depends in build section on above) (done 7/8/2010)
Next batch (no intra-project dependencies)
*uima-build-helper-maven-plugin
*uima-assembly-single-project
*uima-docbook-resource-bundle
*parent-pom-distr
*parent-pom-docbook
Next batch
*parent-pom-ibm-notice
*parent-pom-eclispe-plugins
*parent-pom-annotator
*parent-pom-distr
Next
*parent-pom-eclipse-plugins-ibm-notice
The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
update this to 2.3.1.
The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
(letting us climb the learning curve on using the release plugin), and will be released only
if it is convenient in the future to re-release a bunch of these without concern for
simultaneously updating the dependency versions in the <build> sections of the sub-modules.
was:
The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
Suggested order
*uima-jar-resource-bundle
*parent-pom-top (depends in build section on above)
Next batch (no intra-project dependencies)
*uima-build-helper-maven-plugin
*uima-assembly-single-project
*uima-docbook-resource-bundle
*parent-pom-distr
*parent-pom-docbook
Next batch
*parent-pom-ibm-notice
*parent-pom-eclispe-plugins
*parent-pom-annotator
*parent-pom-distr
Next
*parent-pom-eclipse-plugins-ibm-notice
The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
update this to 2.3.1.
The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
(letting us climb the learning curve on using the release plugin), and will be released only
if it is convenient in the future to re-release a bunch of these without concern for
simultaneously updating the dependency versions in the <build> sections of the sub-modules.
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle (done)
> *parent-pom-top (depends in build section on above) (done 7/8/2010)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884757#action_12884757 ]
Marshall Schor commented on UIMA-1823:
--------------------------------------
I don't think Nexus supports more than one staging repo per project. The repo is set up when you ask to have your project added to Nexus. And it is "pointed to" by the Apache-wide common pom, http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom , in the entry that says:
{code:xml}
<distributionManagement>
<!-- Site omitted - each project must provide their own -->
<repository>
<id>apache.releases.https</id>
<name>Apache Release Distribution Repository</name>
<url>https://repository.apache.org/service/local/staging/deploy/maven2</url>
</repository>
...
{code}
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle
> *parent-pom-top (depends in build section on above)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Posted by "Adam Lally (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884416#action_12884416 ]
Adam Lally commented on UIMA-1823:
----------------------------------
Is it possible to do incrementally install artifacts to your local repository, and then release them all at once to the staging repository for a vote?
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle
> *parent-pom-top (depends in build section on above)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884413#action_12884413 ]
Marshall Schor commented on UIMA-1823:
--------------------------------------
One person suggested staging all the artifacts, incrementally, to the staging spot, for one vote, by temporarily altering the maven settings.xml file to specify the repository as a place to get artifacts. I thought this would work, but upon reflection, it won't because the staging repository doesn't have an accessible URL until it is "closed", and once it's closed, it can only be "promoted" or "dropped" (it can't be re-opened).
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle
> *parent-pom-top (depends in build section on above)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Posted by "Adam Lally (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884692#action_12884692 ]
Adam Lally commented on UIMA-1823:
----------------------------------
Still searching for the idea which makes all this (mainly all the separate votes) unnecessary... :)
To get around the problem that you have the close a staging repository before you use it, can you have multiple staging repositories, one for each of the different components (or sets of components that have to be "released" simultaneously)?
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle
> *parent-pom-top (depends in build section on above)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1823) Incrementally release build artifacts to
eliminate dependencies on -SNAPSHOTs
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1823.
--------------------------------
Resolution: Fixed
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle (done)
> *parent-pom-top (depends in build section on above) (done 7/8/2010)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1823) Incrementally release build artifacts
to eliminate dependencies on -SNAPSHOTs
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1823?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884680#action_12884680 ]
Marshall Schor commented on UIMA-1823:
--------------------------------------
One can "install" (i.e. "mvn install") artifacts tot he local repo. But that's not what the release process as implemented by the release plugin does.
That process includes renaming versions poms from -SNAPSHOT, fixing up pom scm tags, tagging things in SVN, pulling a fresh extract from SVN and building that in an "isolated" spot, installing that, and then deploying it to the NEXUS staging repository.
We could choose to not use the release plugin, but I'm attempting at this point to move our processes toward being as "vanilla" maven as seems feasible.
I hope that the awkwardness of this initial build tool release is a one-time (or at least, very occasional) issue. And maybe along the way we'll learn some other idea which makes all this unnecessary (that is, maybe this is just due to our not quite knowing how to "operate" maven).
> Incrementally release build artifacts to eliminate dependencies on -SNAPSHOTs
> -----------------------------------------------------------------------------
>
> Key: UIMA-1823
> URL: https://issues.apache.org/jira/browse/UIMA-1823
> Project: UIMA
> Issue Type: Task
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> The Maven release plugin updates versions in poms, parent -pom references, and dependencies, for things being released together at one go. However this doesn't work for dependencies that are within the <build> element.
> To get around this, release things in the build in the following order, updating components as needed before each release, to depend on things officially released preceeding them.
> Suggested order
> *uima-jar-resource-bundle
> *parent-pom-top (depends in build section on above)
> Next batch (no intra-project dependencies)
> *uima-build-helper-maven-plugin
> *uima-assembly-single-project
> *uima-docbook-resource-bundle
> *parent-pom-distr
> *parent-pom-docbook
> Next batch
> *parent-pom-ibm-notice
> *parent-pom-eclispe-plugins
> *parent-pom-annotator
> *parent-pom-distr
> Next
> *parent-pom-eclipse-plugins-ibm-notice
> The parent-pom-annotator has a dependency on PearPackagingMavenPlugin.
> Set this to 2.3.0-incubating for now; after uimaj has its first 2.3.1 non-incubating release,
> update this to 2.3.1.
> The aggregate-parent-poms project won't be released in this cycle; it has served its purpose
> (letting us climb the learning curve on using the release plugin), and will be released only
> if it is convenient in the future to re-release a bunch of these without concern for
> simultaneously updating the dependency versions in the <build> sections of the sub-modules.
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.