No, it needs POM to work. My fault [?] Oh, you meant to generate dependencies
for non-maven project. I see.

2009/7/31 Lewis, Eric <[email protected]>

> Hi
>
> No, apparently dependency:build-classpath needs to have a POM to work - or
> perhaps I'm doing something wrong.
>
> Anyway, I just tried the appassembler plugin, and it works well for what I
> need, namely having a script call my JAR.
>
> Best regards,
> Eric
>
> ________________________________
> Von: Alexander [mailto:[email protected]]
> Gesendet: Freitag, 31. Juli 2009 16:28
> An: Maven Users List
> Betreff: Re: Load and run artifact from shell script
>
> Hello,
>
> What do you mean "anywhere in system"? It works fine as "mvn
> dependency:build-classpath" and could be invoked as command. You can invoke
> that action in script, parse output and use result classpath in script.
> [cid:[email protected]]
>
> To download all dependencies you could use dependency:go-offline.
> [cid:[email protected]]
>
>
> 2009/7/31 Lewis, Eric <[email protected]<mailto:[email protected]>>
> Hi
>
> I have a utility project whose classes should be called from a shell
> script.
>
> The problem is how to access it: It's in the local repo, so I would like to
> do the following:
>
> - Download it and its runtime dependencies based on group and artifact ID,
> using the latest version
> - Create a classpath to use in the shell script
>
> As far as I can see, the dependency:build-classpath would do part of it
> (not downloading, though), but it only works with a POM.
> I need to do this anywhere in the file system.
>
> Any hints how I could start?
>
> Thanks & best regards
> Eric
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]<mailto:
> [email protected]>
> For additional commands, e-mail: [email protected]<mailto:
> [email protected]>
>
>
>
>
> --
> Alexander
>
>


-- 
Alexander

Reply via email to