Hello Giovanni,
Try to install maven-debian-helper 1.4.1 and the latest versions of
maven-ant-helper and maven-repo-helper, then run mh_make on your
project, it will help you normally to generate most Debian packaging
files. This is a log of my session, I'm missing isorelax, but if you
have it in
On Feb 17, 2011, at 5:41 PM, Andreas Tille wrote:
> [INFO]
>
> [INFO] Cannot execute mojo: resources. It requires a project with an existing
> pom.xml, but the build is not using one.
> [INFO]
> --
Dreilinu veikalinjaa sodien var sanemt pistoli Taurus Millennium PT145
Nav vajadziga ne akceptu, ne licenzi!
Neparproti, un mekle konkretaja rajonaa: http://www.bezatlaujas.info !
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Cont
On Wed, Feb 16, 2011 at 11:29:52PM +0100, Torsten Werner wrote:
> are you looking for 'mvn package'?
$ mvn package
[INFO] Scanning for projects...
[INFO]
[INFO] Building Mave
Yes, I'll get the new upstream release compiled and uploaded today.
Thanks,
tony
On 02/17/2011 07:00 AM, Miguel Landaeta wrote:
> On Thu, Feb 17, 2011 at 12:41 AM, tony mancill wrote:
>
>> I have uploaded groovy (unstable). I'll take a look at the upload of 1.8
>> beta
>> to experimental la
On Thu, Feb 17, 2011 at 12:41 AM, tony mancill wrote:
> I have uploaded groovy (unstable). I'll take a look at the upload of 1.8 beta
> to experimental later this week or weekend.
Sure, thank you very much for uploading this.
Russel Winder brought to our attention[1] that there is a new upstrea
On Thu, Feb 17, 2011 at 3:49 AM, Andreas Tille wrote:
> The problem I had is that beast-mcmc contains more than one executables
> with more than one JAR files. Some executables are using a common JAR
> file with different main classes. As far as I have seen this case
> is not covered by the tuto
On Thu, 2011-02-17 at 12:04 +0100, Giovanni Mascellani wrote:
> The compilation runs without problems, but mh_resolve_dependencies
> seems
> to be unable to understand that some of the artifacts shouldn't be
> searched on the filesystem, because are provided by my package. This
> leads it to try so
Hi.
I'm experiencing a few problems with a Java library (compiled via maven
and maven-debian-helper) that contains a few different component (thus
different POM files) with some dependency relations among them.
I'm not sure I'm doing things The Right Way(tm), so I'd really
appreciate if someone m
On Wed, Feb 16, 2011 at 06:12:53PM -0500, Scott Howard wrote:
> I haven't built the package, but the debian/__beast-mcmc.manifest__
> doesn't appear to be in javahelper manifest form.
No it is definitely not - it was just a reminder for myself what
classes need to be called. The __*__ made sure t
10 matches
Mail list logo