[ANNOUNCE] Apache Commons BCEL Version 6.10.0

[Gary Gregory]

The Apache Commons BCEL team is pleased to announce the release of
Apache Commons BCEL 6.10.0.

The Byte Code Engineering Library (BCEL) is intended to give users a
convenient way to analyze, create, and manipulate compiled .class
files. Classes are represented by objects containing all the symbolic
information of the given class: methods, fields, and byte code
instructions.

Maintenance and bug fix release. Requires a minimum of Java 8.

Historical list of changes:
https://commons.apache.org/proper/commons-bcel/changes-report.html

For complete information on Apache Commons BCEL, including
instructions on how to submit bug reports, patches, or suggestions for
improvement, see the Apache Commons BCEL website:

https://commons.apache.org/proper/commons-bcel

Download it from
https://commons.apache.org/proper/commons-bcel/download_bcel.cgi

Have fun!
Gary Gregory
Apache Commons BCEL team

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Modeling a "ls" or "cp" type command?

[Eric Pugh]

In poking around, I’m seeing that it’s not obvious how to model a command like 
the classic “ls” or “cp” commands with the usage.

If I do “man cp” the output looks like: 

NAME
 cp – copy files

SYNOPSIS
 cp [-R [-H | -L | -P]] [-fi | -n] [-alpsvXx] source_file target_file

It shows the command, the various options, and then the args that it takes, in 
this case source_file and target_file.

In my Solr command line tools, I have not yet figured out how to model this.   
For example, the “ZkLsTool”, which is basically like the classic “ls” tool, 
when I ask it for usage I get:

usage: bin/solr ls --path  [-r ] [-u ] [-url 
] [-v] [-z ]

List of options:
--path  Path to list.
 -r,--recurseRecurse (true|false), default is false.
 -u,--credentialsCredentials in the format username:password. 
Example: --credentials solr:SolrRocks


However, I don’t want the path to be the option —path.   In Solr today, we do 
some swapping around in the bin/solr command to convert a “bin/solr zk ls 
/mypath” into a call that is to SolrCLI ls —path /mypath to fit how commons 
works.

We are however trying to remove the argument parsing in the shell command and 
learn more on commons-cli.   

Thoughts on this?   Do we need to have an Argument class to go along with the 
Option class?

Eric


I___
Eric Pugh | Founder | OpenSource Connections, LLC | 434.466.1467 | 
http://www.opensourceconnections.com  | 
My Free/Busy   
Co-Author: Apache Solr Enterprise Search Server, 3rd Ed 


This e-mail and all contents, including attachments, is considered to be 
Company Confidential unless explicitly stated otherwise, regardless of whether 
attachments are marked as such.