You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Michael Baessler (JIRA)" <ui...@incubator.apache.org> on 2007/04/18 17:43:15 UTC
[jira] Created: (UIMA-377) add API to build PEAR packages
add API to build PEAR packages
------------------------------
Key: UIMA-377
URL: https://issues.apache.org/jira/browse/UIMA-377
Project: UIMA
Issue Type: New Feature
Components: Core Java Framework
Reporter: Michael Baessler
Assigned To: Michael Baessler
Priority: Minor
Fix For: 2.2
Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Created: (UIMA-377) add API to build PEAR packages
Posted by Michael Baessler <mb...@michael-baessler.de>.
Michael Baessler (JIRA) wrote:
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assigned To: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
>
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven
I just want to get some other opinion about where to check-in the Java
class for the ANT task. The class has a dependency on uima_core and to
an ANT jar.
What do you think...
1) add it to the uima_core project where all the other pear stuff is
checked-in
2) add it to a new project in the sandbox
-- Michael
Re: [jira] Commented: (UIMA-377) add API to build PEAR packages
Posted by Lev Kozakov <le...@gmail.com>.
On 4/24/07, Michael Baessler (JIRA) <ui...@incubator.apache.org> wrote:
> OK, what I would like to say is. The classpath or datapath can be specified relative to the main_root directory but it can also be a absolute path to an installed application or resource.
Well, the whole idea of PEAR is about being as much as possible
independent of the global environment to allow for installation and
deployment of encapsulated components in any target environment.
> I think the pear packager eclipse plugin does the same. The user must specify the path names using $main_root macros and nothing is added automatically. So the behavior is the same.
The PEAR packager recommends avoiding absolute paths in environment
variables (see PEAR Packager user's guide) and using $main_root macros
instead.
-- Lev
[jira] Commented: (UIMA-377) add API to build PEAR packages
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490510 ]
Michael Baessler commented on UIMA-377:
---------------------------------------
Ok, I will check the classpath value that it only contains ";" as path separator.
I only add the $main_root to the mainComponentDesc since the component descriptor must be in the pear package.
The classpath and datapth may be in the pear package, but it must be. If I add automatically to each classpath or datapath entry the $main_root macro it will not be possible to specify absolut path names that may be required by the pear package. But I document this, so that the user know what to do.
Sounds this reasonable?
-- Michael
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assigned To: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-377) add API to build PEAR packages
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Baessler closed UIMA-377.
---------------------------------
Resolution: Fixed
finished the implementation and added documentation for the PackageCreator API and the PearPackager command line tooling.
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assignee: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-377) add API to build PEAR packages
Posted by "Lev Kozakov (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490997 ]
Lev Kozakov commented on UIMA-377:
----------------------------------
"The classpath and datapth may be in the pear package, but it must be" - could you, please, explain what do you mean here.
Actually, I don't believe it's a good idea to specify absolute classpath/dtapath in PEAR installation descriptor. I would rather do it thru global environment variables. PEAR can be installed anywhere, so having dependencies on absolute paths is a kind of unnecessary limitation.
-- Lev
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assigned To: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-377) add API to build PEAR packages
Posted by "Lev Kozakov (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490452 ]
Lev Kozakov commented on UIMA-377:
----------------------------------
I looked at the PackageCreator code - everything looks fine. I would, probably, add default value for 'targetDir' argument (current working directory), but not sure if this is useful.
Good work.
-- Lev
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assigned To: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-377) add API to build PEAR packages
Posted by "Michael Baessler (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12491332 ]
Michael Baessler commented on UIMA-377:
---------------------------------------
OK, what I would like to say is. The classpath or datapath can be specified relative to the main_root directory but it can also be a absolute path to an installed application or resource.
I think the pear packager eclipse plugin does the same. The user must specify the path names using $main_root macros and nothing is added automatically. So the behavior is the same.
-- Michael
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assigned To: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-377) add API to build PEAR packages
Posted by "Lev Kozakov (JIRA)" <ui...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490463 ]
Lev Kozakov commented on UIMA-377:
----------------------------------
More comments on the PackageCreator code:
- 'classpath' argument may contain several path expressions; in this case only the ';' (semicolon) path separator should be used for all OSs;
- you add $main_root to the 'mainComponentDesc' argument programmatically, but don't do it for 'classpath' and 'datapath' arguments (a caller is required to put $main_root in these 2 arguments); what was the reason for treating the latter 2 arguments in a different way?
-- Lev
> add API to build PEAR packages
> ------------------------------
>
> Key: UIMA-377
> URL: https://issues.apache.org/jira/browse/UIMA-377
> Project: UIMA
> Issue Type: New Feature
> Components: Core Java Framework
> Reporter: Michael Baessler
> Assigned To: Michael Baessler
> Priority: Minor
> Fix For: 2.2
>
>
> Currently pear packages can only be created when having the PearPackager plugin installed. I would like to add a pear packager API to create pear files without using the pearPackager eclipse plugin.
> Also I plan to create an ANT task to build pear packages directly in the build. I choose ANT since I think it is more common. We can run it in our Maven build and annotator developers can run it in their build as well even when they don't use Maven.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.