headers
Tommaso Teofili | 1 Oct 2010 09:01
Picon
Gravatar

Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook

+1
Tommaso

2010/10/1 Marshall Schor <msa@...>

>  There are two Jiras solved in this release.
>
> parent-pom-top: https://issues.apache.org/jira/browse/UIMA-1884 (add  <at> pre
> to
> javadoc known tags)
> parent-pom-docbook: https://issues.apache.org/jira/browse/UIMA-1888 (docbook
> builds missing a file)
>
> These poms have been released to the staging repository, along with 6 other
> build poms that recursively depend on these poms.
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheuima-001/
>
> To enable you to test this, please add this stanza to your settings.xml in
> the
> .m2 spot:
>
>    <profile>
>      <id>staged-release</id>
>      <repositories>
>        <repository>
>          <id>staged-release</id>
>          <url>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann | 1 Oct 2010 09:27
Picon

Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook

  +1

Jörn

On 10/1/10 12:05 AM, Marshall Schor wrote:
>   There are two Jiras solved in this release.
>
> parent-pom-top: https://issues.apache.org/jira/browse/UIMA-1884 (add  <at> pre to
> javadoc known tags)
> parent-pom-docbook: https://issues.apache.org/jira/browse/UIMA-1888  (docbook
> builds missing a file)
>
> These poms have been released to the staging repository, along with 6 other
> build poms that recursively depend on these poms.
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheuima-001/
>
> To enable you to test this, please add this stanza to your settings.xml in the
> .m2 spot:
>
>      <profile>
>        <id>staged-release</id>
>        <repositories>
>          <repository>
>            <id>staged-release</id>
>            <url>https://repository.apache.org/content/repositories/orgapacheuima-001/</url>
>          </repository>
>        </repositories>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Oct 2010 12:46

Re: Build failure with maven 3 beta 3

 Maven user's list now reports that Nexus support for repository.apache.org has
now bee updated, and the workaround in that thread is no longer needed.

So RC3 should now work OK for deploy (but I haven't tried it myself - still
using 3.0-beta-1).

-Marshall

On 9/30/2010 9:47 AM, Marshall Schor wrote:
>  I found this morning a problem with maven-3.0-RC3 (and RC2): the "deploy"
> action to the Apache Nexus snapshot repo appears to succeed, but the resulting
> snapshot isn't "readable" later...
>
> According to the Maven team, there's a patch for Nexus to fix this, and they're
> going to see if they can get it applied to the Apache Nexus.  See:
> http://markmail.org/message/7hpr7juygmzsmuk2
>
> This isn't a problem if you use beta-1.
>
> The maven 3.0 beta-1 (and all other releases) can be found by going to the main
> maven download page http://maven.apache.org/download.html and then going to the
> section labeled "Previous Releases" and clicking on that link.
>
>
>
>
>
>
>
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 1 Oct 2010 14:47
Picon
Favicon

[jira] Updated: (UIMA-1887) It should be possible to open a CAS file from a non Cas Editor project


     [
https://issues.apache.org/jira/browse/UIMA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann updated UIMA-1887:
--------------------------------

          Summary: It should be possible to open a CAS file from a non Cas Editor project  (was: Should be possible to
open a CAS from a non Cas Editor project with the CAS Editor)
         Assignee: Jörn Kottmann
    Fix Version/s: 2.3.1SDK
      Description: 
It should be possible to open a  CAS files which are inside an eclipse java project (and not an eclipse CAS
Editor project) with the CAS Editor.

After spending more time on the issue the plan how to implement it changed again.
The previous idea of having an additional plugin for this functionality is dropped and the change is directly
integrated into the Cas Editor plugin.

There are two changes which must be performed for this issue:

1. The Document Provider is extended with a custom logic to open a CAS file from a non Cas Editor Project.
Its assumed that the type system is placed in a certain location, if it cannot find in this location the
user if prompted by a dialog to provide a valid type system for the CAS.
This mechanism should be improved in the future to play nicely together with all other plugins wich also need
access to a type system, like the description editors.

2.
The UI to configure the annotation styles must be moved to the editor and away from the Cas Editor Project
handling code. To accomplish this the Document Provider should be responsible for accessing/modifying
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Oct 2010 16:10

another small breakthrough in my understanding of Maven

 Yesterday, when releasing the small update to parent-pom-top, I had to release
also, the other build projects which depend on it, and recursively, those that
depended on those build build projects.

For instance:

parent-pom-top
  parent-pom-docbook (yes, I know, released anyways)
    parent-pom-eclipse-plugins
      parent-pom-eclipse-plugins-ibm-notice

etc.

In the diagram above, each indented item has as its parent, the one above.

So, when parent-pom-eclipse-plugins was released, it was first updated so its
parent went from

version 3 of parent-pom-docbook to
version 4 of parent-pom-docbook,

and its own version, updated because its <parent> changed, went from

version 4-SNAPSHOT to
version 4 (in the tag) to
version 5-SNAPSHOT (next version in trunk)

So the release process went something like this:

1) update parent-pom-top, release it (to the staging repo)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Oct 2010 17:17

Re: Build failure with maven 3 beta 3

 Here's an even easier fix.

Edit your settings.xml file in your .m2 dir, to add the maven 2 repository we
used while incubating to the ones Maven uses when looking for plugins.

The XML stanzas should look something like:

<pluginRepositories>
  <pluginRepository>
    <id>incubating</id>
    <url>http://http://people.apache.org/repo/m2-incubating-repository</url>
  </pluginRepository>
</pluginRepositories>

Then, Maven will find the 2.3.0-incubating release (I hope). 

-Marshall

On 9/30/2010 10:02 AM, Marshall Schor wrote:
>  Here's an easier fix.
>
> (Note that this issue is only arising because our previous build for this didn't
> push maven artifacts to maven central.)
>
> Open the PearPackagingMavenPlugin project's pom.xml file and temporarily change
> its version from 2.3.1-SNAPSHOT to 2.3.0-incubating.  Then run mvn install. 
> This will put it into your local .m2 repository.  Then "revert" the pom change :-)
>
> I think that then the sandbox projects should find it...
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Oct 2010 17:41

Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook

 I spot checked parent-pom-docbook for the proper source-zip - looks fine, has
the licenses / notice files, builds from source fine with maven-3.0-rc3.

I built the docbooks ok, and uimaj-distr ran without the extra  <at> pre warnings.

+1 to release.

-Marshall

On 9/30/2010 6:05 PM, Marshall Schor wrote:
>  There are two Jiras solved in this release.
>
> parent-pom-top: https://issues.apache.org/jira/browse/UIMA-1884 (add  <at> pre to
> javadoc known tags)
> parent-pom-docbook: https://issues.apache.org/jira/browse/UIMA-1888  (docbook
> builds missing a file)
>
> These poms have been released to the staging repository, along with 6 other
> build poms that recursively depend on these poms.
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheuima-001/
>
> To enable you to test this, please add this stanza to your settings.xml in the
> .m2 spot:
>
>     <profile>
>       <id>staged-release</id>
>       <repositories>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 1 Oct 2010 17:43

Re: [VOTE] Release build poms: parent-pom-top and parent-pom-docbook

 Being that these were such small changes, and concerns just build tooling, and
with very little likelyhood of causing release issues, I plan to close the vote
on these a bit early - this evening.

-Marshall

On 9/30/2010 6:05 PM, Marshall Schor wrote:
>  There are two Jiras solved in this release.
>
> parent-pom-top: https://issues.apache.org/jira/browse/UIMA-1884 (add  <at> pre to
> javadoc known tags)
> parent-pom-docbook: https://issues.apache.org/jira/browse/UIMA-1888  (docbook
> builds missing a file)
>
> These poms have been released to the staging repository, along with 6 other
> build poms that recursively depend on these poms.
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheuima-001/
>
> To enable you to test this, please add this stanza to your settings.xml in the
> .m2 spot:
>
>     <profile>
>       <id>staged-release</id>
>       <repositories>
>         <repository>
>           <id>staged-release</id>        
>           <url>https://repository.apache.org/content/repositories/orgapacheuima-001/</url>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jörn Kottmann (JIRA | 2 Oct 2010 17:31
Picon
Favicon

[jira] Commented: (UIMA-1887) It should be possible to open a CAS file from a non Cas Editor project


    [
https://issues.apache.org/jira/browse/UIMA-1887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12917202#action_12917202
] 

Jörn Kottmann commented on UIMA-1887:
-------------------------------------

2. Is now done.

1. Is half done, the dialog to choose a type system is still missing, and the error handling still needs to be
improved in case the type system is invalid (e.g. invalid xml) or not compatible with the CAS.

> It should be possible to open a CAS file from a non Cas Editor project
> ----------------------------------------------------------------------
>
>                 Key: UIMA-1887
>                 URL: https://issues.apache.org/jira/browse/UIMA-1887
>             Project: UIMA
>          Issue Type: New Feature
>          Components: CasEditor
>            Reporter: Jörn Kottmann
>            Assignee: Jörn Kottmann
>             Fix For: 2.3.1SDK
>
>
> It should be possible to open a  CAS files which are inside an eclipse java project (and not an eclipse CAS
Editor project) with the CAS Editor.
> After spending more time on the issue the plan how to implement it changed again.
> The previous idea of having an additional plugin for this functionality is dropped and the change is directly
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marshall Schor | 4 Oct 2010 16:09

[VOTE][RESULT] Release build poms: parent-pom-top and parent-pom-docbook

 The vote passes:

+1 Jörn Kottmann
+1 Tommasso Teofili
+1 Marshall Schor

No other votes were received.

-Marshall Schor

On 9/30/2010 6:05 PM, Marshall Schor wrote:
>  There are two Jiras solved in this release.
>
> parent-pom-top: https://issues.apache.org/jira/browse/UIMA-1884 (add  <at> pre to
> javadoc known tags)
> parent-pom-docbook: https://issues.apache.org/jira/browse/UIMA-1888  (docbook
> builds missing a file)
>
> These poms have been released to the staging repository, along with 6 other
> build poms that recursively depend on these poms.
>
> The staging repository is here:
>
> https://repository.apache.org/content/repositories/orgapacheuima-001/
>
> To enable you to test this, please add this stanza to your settings.xml in the
> .m2 spot:
>
>     <profile>
>       <id>staged-release</id>
(Continue reading)

Permalink | Reply | 0 comments |

Gmane