Re: Maven UIMA and import by name
Hi Erik. you can configure Maven with an extra resources folder. http://maven.apache.org/pom.html#Resources We usually keep our descriptors under src/main/resources to have them on the classpath. But we do not care about being PEAR compatible. So adding desc as a resources folder in your POM is probably the right thing for you. -- Richard Am 11.05.2012 um 17:56 schrieb Erik Fäßler: Hello all, I have a question on how you deal with a specific use case and would like to know if you have some suggestions for me. I use Maven for all my Java projects and so I do for my UIMA related projects. Now I have a quite large pipeline with lots of descriptors. They reside in (or subdirectories of) the 'desc' directory of the 'UIMA nature' structure. Currently I am about to pack these single-AE descriptors into aggregates. For importing all single-AEs into the AAE descriptor, I would like to use import by name. However, the 'desc' directory is not a library for eclipse and thus, the AAE descriptor editor doesn't list the descriptors residing in this directory - I can't add them (and when I edit the XML, I get error messages about descriptors not found). I would like to just add the 'desc' directory to the build path as an class folder (not a source folder, this won't work), i.e. as a library. When I do this manually, Maven would overwrite it the next time it updates my project configuration. Have you any ideas here? Do you use 'import by name' for your PEARS? Do you just live with the error messages and edit the XML directly? Just would like to know how you do it - and if anyone knows a way to tell maven that 'desc' should be a library, I'd be glad :-) Best regards, Erik -- --- Richard Eckart de Castilho Technical Lead Ubiquitous Knowledge Processing Lab (UKP-TUD) FB 20 Computer Science Department Technische Universität Darmstadt Hochschulstr. 10, D-64289 Darmstadt, Germany phone [+49] (0)6151 16-7477, fax -5455, room S2/02/B117 eck...@ukp.informatik.tu-darmstadt.de www.ukp.tu-darmstadt.de Web Research at TU Darmstadt (WeRC) www.werc.tu-darmstadt.de ---
Re: Maven UIMA and import by name
Hi Erik, I mostly edit XMLs by hand (also because I use IntelliJ IDEA) but I think you may tell Maven that desc is a resource folder: build ... resources resource directorysrc/main/resources/directory directorydesc/directory /resource ... /build HTH, Tommaso 2012/5/11 Erik Fäßler erik.faess...@uni-jena.de Hello all, I have a question on how you deal with a specific use case and would like to know if you have some suggestions for me. I use Maven for all my Java projects and so I do for my UIMA related projects. Now I have a quite large pipeline with lots of descriptors. They reside in (or subdirectories of) the 'desc' directory of the 'UIMA nature' structure. Currently I am about to pack these single-AE descriptors into aggregates. For importing all single-AEs into the AAE descriptor, I would like to use import by name. However, the 'desc' directory is not a library for eclipse and thus, the AAE descriptor editor doesn't list the descriptors residing in this directory - I can't add them (and when I edit the XML, I get error messages about descriptors not found). I would like to just add the 'desc' directory to the build path as an class folder (not a source folder, this won't work), i.e. as a library. When I do this manually, Maven would overwrite it the next time it updates my project configuration. Have you any ideas here? Do you use 'import by name' for your PEARS? Do you just live with the error messages and edit the XML directly? Just would like to know how you do it - and if anyone knows a way to tell maven that 'desc' should be a library, I'd be glad :-) Best regards, Erik
Re: Maven UIMA and import by name
We use maven for our UIMA-AS projects. Here is the build section from our standard POM entries: build resources resource directorysrc/main/desc//directory /resource resource directorysrc/main/resources//directory /resource /resources pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.6/source target1.6/target /configuration /plugin /plugins /pluginManagement /build This adds the desc and resources directories as source directories that allow you to resolve the import of descriptors by name. Thanks, Thomas Ginter 801-448-7676 thomas.gin...@utah.edu On May 11, 2012, at 9:56 AM, Erik Fäßler wrote: Hello all, I have a question on how you deal with a specific use case and would like to know if you have some suggestions for me. I use Maven for all my Java projects and so I do for my UIMA related projects. Now I have a quite large pipeline with lots of descriptors. They reside in (or subdirectories of) the 'desc' directory of the 'UIMA nature' structure. Currently I am about to pack these single-AE descriptors into aggregates. For importing all single-AEs into the AAE descriptor, I would like to use import by name. However, the 'desc' directory is not a library for eclipse and thus, the AAE descriptor editor doesn't list the descriptors residing in this directory - I can't add them (and when I edit the XML, I get error messages about descriptors not found). I would like to just add the 'desc' directory to the build path as an class folder (not a source folder, this won't work), i.e. as a library. When I do this manually, Maven would overwrite it the next time it updates my project configuration. Have you any ideas here? Do you use 'import by name' for your PEARS? Do you just live with the error messages and edit the XML directly? Just would like to know how you do it - and if anyone knows a way to tell maven that 'desc' should be a library, I'd be glad :-) Best regards, Erik
Re: Maven UIMA and import by name
Hey you all, thanks a lot for your answers. I had tried to add the desc/ directory as a maven resource. However, the UIMA component editor still wouldn't show me my descriptors to choose from. I have to remove the exclude: ** entry in the build path first. Then, the whole directory is copied to the target/classes directory. I didn't like this approach too much because now I have each descriptor doubled. But I guess I can exclude the duplicates from any builds by configuring the appropriate build / package plugin. I think I will also change it from being a resource to being a source folder. This way I don't get even a third copy of all descriptors in my target/resources directory. Thanks again and a nice weekend to you! Best, Erik Am 11.05.2012 um 18:05 schrieb Thomas Ginter: We use maven for our UIMA-AS projects. Here is the build section from our standard POM entries: build resources resource directorysrc/main/desc//directory /resource resource directorysrc/main/resources//directory /resource /resources pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.6/source target1.6/target /configuration /plugin /plugins /pluginManagement /build This adds the desc and resources directories as source directories that allow you to resolve the import of descriptors by name. Thanks, Thomas Ginter 801-448-7676 thomas.gin...@utah.edu On May 11, 2012, at 9:56 AM, Erik Fäßler wrote: Hello all, I have a question on how you deal with a specific use case and would like to know if you have some suggestions for me. I use Maven for all my Java projects and so I do for my UIMA related projects. Now I have a quite large pipeline with lots of descriptors. They reside in (or subdirectories of) the 'desc' directory of the 'UIMA nature' structure. Currently I am about to pack these single-AE descriptors into aggregates. For importing all single-AEs into the AAE descriptor, I would like to use import by name. However, the 'desc' directory is not a library for eclipse and thus, the AAE descriptor editor doesn't list the descriptors residing in this directory - I can't add them (and when I edit the XML, I get error messages about descriptors not found). I would like to just add the 'desc' directory to the build path as an class folder (not a source folder, this won't work), i.e. as a library. When I do this manually, Maven would overwrite it the next time it updates my project configuration. Have you any ideas here? Do you use 'import by name' for your PEARS? Do you just live with the error messages and edit the XML directly? Just would like to know how you do it - and if anyone knows a way to tell maven that 'desc' should be a library, I'd be glad :-) Best regards, Erik
