On Thu, Mar 26, 2009 at 2:19 PM, Toni Menzel <t...@okidokiteam.com> wrote:
> Also cool but i am just working on that again:
> Usage of the dir handler.
> Do not look on the wiki for explanation but here:
> It has currently has this syntax:
> dir:<folder_on_disk>$param=value;param=value

I guess it would be better to have a more url-ish syntax like:
dir:<folder_on_disk>?param=value&param=value

This is more like what people know from the http protocol and also is
the same for wrap: and war:

> General ideas for proveasyo :
> - easier to type name, please ;)
> - Thinking about making it a neat osgi toolchain that has a simple name as
> "git" but a flexible commandset.
> Then i would like the following usecase:
> - "pax metadata wrap:mvn:foo:bar"
> Running the download as before, wrap and "just print the metadata like
> MANIFEST to check what wrap calculated.
> - "pax maven-install mvn:foo:bar"
> Get the artifact and store it in local maven repository
> and so on.
> If it grows like that, it should have a pluggable infrastructe similar to
> what we have in pax url and runner. (bundles itself).
> I know that pax runner will get a self-update mechanism, i think for
> "proveasyo" it would be crucial to have 100% networked capability itself
> once it has been installed by the user.
> Oh man, i can think of very much for this tool.

instead of "proveasyo.sh mvn:org.ops4j.pax.web/pax-web-service target"
doing "pax push mvn:org.ops4j.pax.web/pax-web-service target"  (git my
friends :) would be cool.

Yep, having a pluggable "pax" command line tool can be quite cool.

-- 
Alin Dreghiciu
http://www.ops4j.org - New Energy for OSS Communities - Open
Participation Software.
http://www.qi4j.org - New Energy for Java - Domain Driven Development.
Looking for a job.
Sent from: Cluj-Napoca CJ Romania.

_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to