You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <de...@uima.apache.org> on 2011/08/02 15:19:27 UTC

[jira] [Created] (UIMA-2195) TextMarker: Fix broken imports

TextMarker: Fix broken imports
------------------------------

                 Key: UIMA-2195
                 URL: https://issues.apache.org/jira/browse/UIMA-2195
             Project: UIMA
          Issue Type: Bug
          Components: TextMarker
            Reporter: Jörn Kottmann


During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Closed] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann closed UIMA-2195.
-------------------------------

    Resolution: Fixed

Seems to work now after applying the provided patch.

Can you please open an issue for this TextMarkerCommonTab, now it does not display an error message anymore.

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>         Attachments: patch.txt
>
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Peter Klügl (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076200#comment-13076200 ] 

Peter Klügl commented on UIMA-2195:
-----------------------------------

Ok, did that. However, I have a different problem with the imports because uima runtime stuff cannot be located. Do the uima imports work for you, e.g., in org.apache.uima.tm.textmarker.engine.TextMarkerEngine?

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076205#comment-13076205 ] 

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

The missing constant is referenced from here:
org.apache.uima.tm.dltk.internal.debug.ui.launchConfigurations.TextMarkerCommonTab at line 783.

I tried to install the XPcom plugin and XULRunner, but that does not seem to work with my eclipse (3.7).

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Peter Klügl (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Klügl updated UIMA-2195:
------------------------------

    Assignee: Peter Klügl

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Peter Klügl (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076249#comment-13076249 ] 

Peter Klügl commented on UIMA-2195:
-----------------------------------

About org.apache.uima.tm.dltk.internal.debug.ui.launchConfigurations.TextMarkerCommonTab at line 783:

They removed the constant in eclipse 3.7 I think. I'll just comment the line, add a TODO and add a patch to this issue.

PS: I'm now using only installed uima plugins and not the sources. Works fine now.

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076202#comment-13076202 ] 

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

Yes, they work fine. I have the uimaj-runtime installed, or maybe it is using the included uima jar files, not sure. Now I only get compile errors for the extension points (UIMA-2191), for a string constant which cannot be found and for some mozilla classes, still need to install this plugin.
 

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Updated] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Peter Klügl (JIRA)" <de...@uima.apache.org>.
     [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Peter Klügl updated UIMA-2195:
------------------------------

    Attachment: patch.txt

Commented org.apache.uima.tm.dltk.internal.debug.ui.launchConfigurations.TextMarkerCommonTab at line 783 due to missing constant in Eclipse 3.7


> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>         Attachments: patch.txt
>
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076189#comment-13076189 ] 

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

Make an update first, I fixed a few of them.

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13078614#comment-13078614 ] 

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

Patch applied.

> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>         Attachments: patch.txt
>
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

[jira] [Commented] (UIMA-2195) TextMarker: Fix broken imports

Posted by "Peter Klügl (JIRA)" <de...@uima.apache.org>.
    [ https://issues.apache.org/jira/browse/UIMA-2195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13076215#comment-13076215 ] 

Peter Klügl commented on UIMA-2195:
-----------------------------------

you can maybe just ignore the cev.html plugin. The xpcom integration is hardly maintainable, maybe it's better to abandon it for now.

I still wonder about my problem and if I did something wrong with the setup.

uimaj-ep-runtime says it builds successfully but I get an IDE error. Is that problematic?

org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.1:unpack-dependencies (unpackDependentJars) on project uimaj-ep-runtime: Unknown archiver type
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.maven.ide.eclipse.internal.embedder.MavenImpl.execute(MavenImpl.java:223)
at org.maven.ide.eclipse.internal.project.GenericBuildParticipant.filterResources(GenericBuildParticipant.java:184)
at org.maven.ide.eclipse.internal.project.GenericBuildParticipant.processResources(GenericBuildParticipant.java:161)
at org.maven.ide.eclipse.internal.project.GenericBuildParticipant.build(GenericBuildParticipant.java:83)
at org.maven.ide.eclipse.internal.builder.MavenBuilder.build(MavenBuilder.java:153)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:627)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:170)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:201)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:253)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:256)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:309)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:341)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:140)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:238)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.apache.maven.plugin.MojoExecutionException: Unknown archiver type
at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:264)
at org.apache.maven.plugin.dependency.UnpackDependenciesMojo.execute(UnpackDependenciesMojo.java:90)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:107)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 25 more
Caused by: org.codehaus.plexus.archiver.manager.NoSuchArchiverException: No such archiver: '1312189298082\jvinci\target\classes'.
at org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArchiver(DefaultArchiverManager.java:80)
at org.codehaus.plexus.archiver.manager.DefaultArchiverManager.getUnArchiver(DefaultArchiverManager.java:114)
at org.apache.maven.plugin.dependency.AbstractDependencyMojo.unpack(AbstractDependencyMojo.java:230)
... 28 more



> TextMarker: Fix broken imports
> ------------------------------
>
>                 Key: UIMA-2195
>                 URL: https://issues.apache.org/jira/browse/UIMA-2195
>             Project: UIMA
>          Issue Type: Bug
>          Components: TextMarker
>            Reporter: Jörn Kottmann
>            Assignee: Peter Klügl
>
> During the import the packages have been renamed to the apache uima name space, in some places this did not work correctly and must be fixed manually.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira