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/10/26 21:38:19 UTC
[jira] Created: (UIMA-1914) merge build tooling artifacts into one,
to simplify release process
merge build tooling artifacts into one, to simplify release process
-------------------------------------------------------------------
Key: UIMA-1914
URL: https://issues.apache.org/jira/browse/UIMA-1914
Project: UIMA
Issue Type: Improvement
Components: Build, Packaging and Test
Reporter: Marshall Schor
Assignee: Marshall Schor
When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
"marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1914) merge build tooling artifacts into one,
to simplify release process
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor closed UIMA-1914.
--------------------------------
Resolution: Fixed
Fix Version/s: build-parent-pom-1
> merge build tooling artifacts into one, to simplify release process
> -------------------------------------------------------------------
>
> Key: UIMA-1914
> URL: https://issues.apache.org/jira/browse/UIMA-1914
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Fix For: build-parent-pom-1
>
>
> When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
> Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
> Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
> "marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
> Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
> Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Commented: (UIMA-1914) merge build tooling artifacts into
one, to simplify release process
Posted by Marshall Schor <ms...@schor.com>.
There is no current plan, and it may be possible. The build system is already
working,
though, with the single parent-pom and one "Jar" project for docbook resources,
so I'm not sure there's a lot of motivation to change this.
Of course, releasing may show up more issues...
-Marshall
On 10/26/2010 4:49 PM, Richard Eckart de Castilho (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925130#action_12925130 ]
>
> Richard Eckart de Castilho commented on UIMA-1914:
> --------------------------------------------------
>
> Is there any possibility/plan of UIMA switching to a non-flat project stucture?
>
>> merge build tooling artifacts into one, to simplify release process
>> -------------------------------------------------------------------
>>
>> Key: UIMA-1914
>> URL: https://issues.apache.org/jira/browse/UIMA-1914
>> Project: UIMA
>> Issue Type: Improvement
>> Components: Build, Packaging and Test
>> Reporter: Marshall Schor
>> Assignee: Marshall Schor
>>
>> When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
>> Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
>> Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
>> "marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
>> Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
>> Update the projects to use the new parent pom.
[jira] Commented: (UIMA-1914) merge build tooling artifacts into
one, to simplify release process
Posted by "Richard Eckart de Castilho (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925130#action_12925130 ]
Richard Eckart de Castilho commented on UIMA-1914:
--------------------------------------------------
Is there any possibility/plan of UIMA switching to a non-flat project stucture?
> merge build tooling artifacts into one, to simplify release process
> -------------------------------------------------------------------
>
> Key: UIMA-1914
> URL: https://issues.apache.org/jira/browse/UIMA-1914
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
> Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
> Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
> "marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
> Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
> Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1914) merge build tooling artifacts into
one, to simplify release process
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925324#action_12925324 ]
Marshall Schor commented on UIMA-1914:
--------------------------------------
Re: switching to a non-flat project structure - It may be possible, but currently there is no plan to do this.
> merge build tooling artifacts into one, to simplify release process
> -------------------------------------------------------------------
>
> Key: UIMA-1914
> URL: https://issues.apache.org/jira/browse/UIMA-1914
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
> Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
> Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
> "marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
> Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
> Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1914) merge build tooling artifacts into one,
to simplify release process
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marshall Schor updated UIMA-1914:
---------------------------------
Well, this doesn't work - parent poms must have packaging of POM, and can't have packaging of JAR, so change tthis to have 2 artifacts - a parent--pom, and a uima-build-resources, where building the parent-pom doesn't have a dependency on uima-build-resources.
> merge build tooling artifacts into one, to simplify release process
> -------------------------------------------------------------------
>
> Key: UIMA-1914
> URL: https://issues.apache.org/jira/browse/UIMA-1914
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
> Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
> Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
> "marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
> Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
> Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1914) merge build tooling artifacts into
one, to simplify release process
Posted by "Marshall Schor (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12925326#action_12925326 ]
Marshall Schor commented on UIMA-1914:
--------------------------------------
The assembly change to use just references to descriptors in the parent-pom doesn't work - because when the assembly build step is inherited by a child pom, those references become relative to the child pom, not the parent-pom. So - go back to the previous method of putting the assembly descriptors into the common parent shared build resource bundle.
> merge build tooling artifacts into one, to simplify release process
> -------------------------------------------------------------------
>
> Key: UIMA-1914
> URL: https://issues.apache.org/jira/browse/UIMA-1914
> Project: UIMA
> Issue Type: Improvement
> Components: Build, Packaging and Test
> Reporter: Marshall Schor
> Assignee: Marshall Schor
>
> When build artifacts are updated, releasing can be difficult. This is because some of the artifacts are dependent on the top parent pom being built, and those artifacts, in turn, depend on the top parent pom (circular refs). Based on discussion on the mailing list (see http://uima.markmail.org/thread/ryh6voctne6vqb7d ), it would simplify things to collapse all of the build artifacts into just one parent-pom.
> Do this, making the packaging of that a Jar, and putting into it also the resource bundles needed by the other parent poms. Change the resource bundle need for assemblies to just plain descriptor references, eliminating the need for bundle refs. Do what's needed to override the normal source-release assembly, so that our "improved" version is used (it works with flat-hierarchies).
> Merge all the other parent-poms into one, using either the existence of some file/directory (e.g. src/docbook ) to trigger the particular profile, or, where none can be found, make a new trigger consisting of a file at the top level called something like:
> "marker-file-identifying-xxxxxx". Those projects which need these profiles will need to have (empty) files like this to trigger the profile.
> Use this mechanism instead of pointing to different parent-poms to control the build (as there will now be just one parent pom for all uima projects).
> Update the projects to use the new parent pom.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.