You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org> on 2008/09/20 19:37:44 UTC

[jira] Created: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
---------------------------------------------------------------------

                 Key: CLI-168
                 URL: https://issues.apache.org/jira/browse/CLI-168
             Project: Commons CLI
          Issue Type: New Feature
          Components: CLI-2.x
    Affects Versions: 2.0
         Environment: All
            Reporter: Karl Heinz Marbaise


It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
It should be distributed via an Maven Repository to have access to the release.

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


[jira] Commented: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712857#action_12712857 ] 

Henri Yandell commented on CLI-168:
-----------------------------------

Realizing that I already moved it to the Sandbox back in March, so it's a separate project already: http://commons.apache.org/sandbox/cli2/

The only overlap left is that they share the same JIRA project, which doesn't seem too bad.

Yes it means that only Apache committers can work on it directly. That's a 50 fold increase on the number of people who could work on it in the released components directory though (proper/). 

I'd recommend mailing commons-dev@ to see if anyone is aiming to work on it and can work with you via patches etc.

> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
>                 Key: CLI-168
>                 URL: https://issues.apache.org/jira/browse/CLI-168
>             Project: Commons CLI
>          Issue Type: New Feature
>          Components: CLI-2.x
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>             Fix For: 2.0
>
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the release.

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


[jira] Commented: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

Posted by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712756#action_12712756 ] 

Karl Heinz Marbaise commented on CLI-168:
-----------------------------------------

That means in other word no one except Apache committers could do the work and releasing it hm...not so good......I would like to start working on it...of course because I'm using it.

> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
>                 Key: CLI-168
>                 URL: https://issues.apache.org/jira/browse/CLI-168
>             Project: Commons CLI
>          Issue Type: New Feature
>          Components: CLI-2.x
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>             Fix For: 2.0
>
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the release.

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


[jira] Commented: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663634#action_12663634 ] 

Henri Yandell commented on CLI-168:
-----------------------------------

That means the decision to release 2.0 rather than continuing to work on the 1.x code and making a fresh start on a 2.0 someday.

> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
>                 Key: CLI-168
>                 URL: https://issues.apache.org/jira/browse/CLI-168
>             Project: Commons CLI
>          Issue Type: New Feature
>          Components: CLI-2.x
>    Affects Versions: 2.0
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the release.

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


[jira] Commented: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

Posted by "Karl Heinz Marbaise (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712539#action_12712539 ] 

Karl Heinz Marbaise commented on CLI-168:
-----------------------------------------

No I don't see it that way, cause CLI2 and CLI Release 1.X have different interest and destinations. I would suggest to see CLI2 as a different project.

> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
>                 Key: CLI-168
>                 URL: https://issues.apache.org/jira/browse/CLI-168
>             Project: Commons CLI
>          Issue Type: New Feature
>          Components: CLI-2.x
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>             Fix For: 2.0
>
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the release.

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


[jira] Commented: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CLI-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712750#action_12712750 ] 

Henri Yandell commented on CLI-168:
-----------------------------------

That's the plan now. CLI2 to move into Commons Sandbox as a different project. It has no committers working on it - so releasing would be bad, however this will make it clear what needs to be done to get it out. Any Apache committer will be able to work on it while in there, so there's potential.

> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
>                 Key: CLI-168
>                 URL: https://issues.apache.org/jira/browse/CLI-168
>             Project: Commons CLI
>          Issue Type: New Feature
>          Components: CLI-2.x
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>             Fix For: 2.0
>
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the release.

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


[jira] Updated: (CLI-168) Maven Repository Distribution as at least as -BETA may be as SNAPSHOT

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

Henri Yandell updated CLI-168:
------------------------------

    Affects Version/s:     (was: 2.0)
        Fix Version/s: 2.0

> Maven Repository Distribution as at least as -BETA may be as SNAPSHOT
> ---------------------------------------------------------------------
>
>                 Key: CLI-168
>                 URL: https://issues.apache.org/jira/browse/CLI-168
>             Project: Commons CLI
>          Issue Type: New Feature
>          Components: CLI-2.x
>         Environment: All
>            Reporter: Karl Heinz Marbaise
>             Fix For: 2.0
>
>
> It would be good to have at least a -BETA Releae of 2.0, so it could be used in Maven based builds. Otherwise it's complicated to use the commons-cli-2.0-DEV.
> It should be distributed via an Maven Repository to have access to the release.

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