You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ivy-commits@incubator.apache.org by "Tjeerd Verhagen (JIRA)" <ji...@apache.org> on 2007/07/09 18:30:04 UTC

[jira] Created: (IVY-567) Update MANIFEST to make Ivy runnable with java -jar

Update MANIFEST to make Ivy runnable with java -jar
---------------------------------------------------

                 Key: IVY-567
                 URL: https://issues.apache.org/jira/browse/IVY-567
             Project: Ivy
          Issue Type: Improvement
          Components: Core
    Affects Versions: 2.0.0-alpha-1
         Environment: Development
            Reporter: Tjeerd Verhagen
            Priority: Trivial
             Fix For: 2.0


Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).

To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
java  -jar ivy-core.jar
No additional path to the class 'org.apache.ivy.Main' is needed any more.

WARINIG: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.

To read more about these keys, see paragraph 'Main Attributes':
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-567) Update MANIFEST to make Ivy runnable with java -jar

Posted by "Tjeerd Verhagen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tjeerd Verhagen updated IVY-567:
--------------------------------

    Attachment: patch_build.xml_correction_in_jar_readme.txt

> Update MANIFEST to make Ivy runnable with java -jar
> ---------------------------------------------------
>
>                 Key: IVY-567
>                 URL: https://issues.apache.org/jira/browse/IVY-567
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-alpha-1
>         Environment: Development
>            Reporter: Tjeerd Verhagen
>            Priority: Trivial
>             Fix For: 2.0
>
>         Attachments: patch_build.xml_add_main_and_path_20070708.txt, patch_build.xml_correction_in_jar_readme.txt
>
>
> Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).
> To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
> java  -jar ivy-core.jar
> No additional path to the class 'org.apache.ivy.Main' is needed any more.
> WARINIG: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.
> To read more about these keys, see paragraph 'Main Attributes':
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-567) Update MANIFEST to make Ivy runnable with java -jar

Posted by "Tjeerd Verhagen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tjeerd Verhagen updated IVY-567:
--------------------------------


The file 'patch_build.xml_correction_in_jar_readme.txt' makes the build.xml cleaner (keeps the indention nice) and removes the double <new-line>s in the created file 'readme.txt'.

> Update MANIFEST to make Ivy runnable with java -jar
> ---------------------------------------------------
>
>                 Key: IVY-567
>                 URL: https://issues.apache.org/jira/browse/IVY-567
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-alpha-1
>         Environment: Development
>            Reporter: Tjeerd Verhagen
>            Priority: Trivial
>             Fix For: 2.0
>
>         Attachments: patch_build.xml_add_main_and_path_20070708.txt, patch_build.xml_correction_in_jar_readme.txt
>
>
> Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).
> To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
> java  -jar ivy-core.jar
> No additional path to the class 'org.apache.ivy.Main' is needed any more.
> WARNING: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.
> To read more about these keys, see paragraph 'Main Attributes':
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-567) Update MANIFEST to make Ivy runnable with java -jar

Posted by "Tjeerd Verhagen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tjeerd Verhagen updated IVY-567:
--------------------------------

    Attachment: patch_build.xml_add_main_and_path_20070708.txt

> Update MANIFEST to make Ivy runnable with java -jar
> ---------------------------------------------------
>
>                 Key: IVY-567
>                 URL: https://issues.apache.org/jira/browse/IVY-567
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-alpha-1
>         Environment: Development
>            Reporter: Tjeerd Verhagen
>            Priority: Trivial
>             Fix For: 2.0
>
>         Attachments: patch_build.xml_add_main_and_path_20070708.txt
>
>
> Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).
> To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
> java  -jar ivy-core.jar
> No additional path to the class 'org.apache.ivy.Main' is needed any more.
> WARINIG: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.
> To read more about these keys, see paragraph 'Main Attributes':
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (IVY-567) Update MANIFEST to make Ivy runnable with java -jar

Posted by "Tjeerd Verhagen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/IVY-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tjeerd Verhagen updated IVY-567:
--------------------------------

    Description: 
Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).

To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
java  -jar ivy-core.jar
No additional path to the class 'org.apache.ivy.Main' is needed any more.

WARNING: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.

To read more about these keys, see paragraph 'Main Attributes':
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes

  was:
Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).

To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
java  -jar ivy-core.jar
No additional path to the class 'org.apache.ivy.Main' is needed any more.

WARINIG: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.

To read more about these keys, see paragraph 'Main Attributes':
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes


> Update MANIFEST to make Ivy runnable with java -jar
> ---------------------------------------------------
>
>                 Key: IVY-567
>                 URL: https://issues.apache.org/jira/browse/IVY-567
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.0.0-alpha-1
>         Environment: Development
>            Reporter: Tjeerd Verhagen
>            Priority: Trivial
>             Fix For: 2.0
>
>         Attachments: patch_build.xml_add_main_and_path_20070708.txt, patch_build.xml_correction_in_jar_readme.txt
>
>
> Update the MANIFEST.MF, in which the (main) key 'Class-Path' can be specified. The value of this key should hold the path's to the other requered jars. For Ivy this means, it should reference to the 'commons-cli.jar' (and maybe other / extra jars in the future).
> To make the jar runnable the key 'Main-Class' is needed, which makes it possible to just 'run the jar', as:
> java  -jar ivy-core.jar
> No additional path to the class 'org.apache.ivy.Main' is needed any more.
> WARNING: Check this patch 'patch_build.xml_add_main_and_path_20070708.txt' the key 'Class-Path' does (only) work if the created artifact is in it's build/articaft directory! I didn't check how ivy-core.jar is normally distributed (where it's dependencies lib is). Probalbly there should be a small change of the referenced path here.
> To read more about these keys, see paragraph 'Main Attributes':
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html
> http://java.sun.com/j2se/1.4.2/docs/guide/jar/jar.html#Main%20Attributes

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.