This is great. One question I have is however what happens if a dependency
is not packaged in debian as the flow shows but is required at runtime.
Will it be included in the package or will it be ignored and therefore a
potentially non functioning package produced.
Another question... can we have
> Andreas Tille writes:
>
>> I'm actually not very keen on really using maven as long as I can get
>> the package working at all - but I actually have no real clue what
>> command line would trigger the build process (and upstream) seems to be
>> dead. So in principle the most simple help would b
Its gonna be more hazzle.There are references to these two classes
import Time.TimeManager;
import Process.Process;
as well as to
net.iharder.dnd.FileDrop(motif, new net.iharder.dnd.FileDrop.Listener
You will have to find whatever the Time and Process libraries are...looks
like a mess to me.
m
> Hi,
>
> inspired by some hints about Java packaging I tried another package. It
> is called patristic[1] (just another biological phylogeny software). It
> comes just with a directory full of *.java files and the binary download
> just tells in what directory layout the classes should end up.
> Giovanni Mascellani writes:
>
>> There's something funny about this command: I executed it and it had to
>> download about 30 different files before being able to do something
>> really dump (copy some simple templates in the working directory).
>
> Yeah, that's typical for Maven. It's absolute
> BTW, working on this just made me notice that some new versions of
> FreeHEP were released some months ago. These releases were deployed on
> maven repositories, but I didn't notice them because they were not
> deployed on the site where development happened before. This is one of
> the many thi
On Tue, July 26, 2011 9:16 pm, Thomas Koch wrote:
> Niels Thykier:
>> I do not have a lot planned for these, so it would be great if you are
>> armed with curiosity and questions. I am more than happy to give people
>> a practical session on building eclipse for that BoF as well.
>
> Thank you for
On 11-12-30 07:45 AM, Damien Raude-Morvan wrote:
Hi Java team!
Maven 3.x is now available in experimental in a new _maven_ debian package.
You'll also need updated _maven2_ package (>= 2.2.1-11) to allow side-by-side
installation (I'm using alternatives to allow user to choose between "mvn" cli
On 12-03-19 09:51 AM, Andrew Haley wrote:
On 03/19/2012 02:04 PM, Barry Hawkins wrote:
For example, JetBrains IntelliJ IDEA, one of the main IDEs for Java
development, still doesn't endorse the use of OpenJDK. If you download
IDEA and launch it via a terminal, you will see the following warning:
nOn 12-03-23 05:41 AM, Matthias-Christian Ott wrote:
On Fri, Mar 23, 2012 at 08:06:25AM -0400, Barry Hawkins wrote:
On 3/23/12 6:47 AM, Matthias-Christian Ott wrote:
Hi,
I have been assigned to a legacy Java project, which uses several messed
up Ant buildfiles. I'm going to replace or clean up
On Fri, May 18, 2012 12:29 am, Thomas Koch wrote:
> Hi,
>
> I want to introduce a cli option parsing library for maven-debian-helper.
> There a tons of such java libraries out there:
>
> http://jewelcli.lexicalscope.com/related.html
>
> Just FYI, I had a look, which of these we have in Debian:
>
>
Hi all,
Some clarifications..
> Hi Emmanuel,
>
> I'm happy to find someone from the java side, especially from apache here
> on a
> debian list. Perhaps you could help us as an intermediator and raise
> awareness
> for the pain we have when dealing with java in general and often the ASF
> in
> sp
> Le 18/03/2013 22:44, Manfred Moser a écrit :
>
>> If there is interest in the debian community to have a controlled
>> repository server running that only provides approved jars you could run
>> Sonatype Professsional. As an open source project you could get a free
>
> Le 29/05/2013 16:22, Manfred Moser a écrit :
>
>> Imho we should sort out all situations where people think they have to
>> stick to Maven 2, migrate them and then deprecate support for Maven 2.
>
> I personally stick to Maven 2 because I need the uniqueVersion feature
> Le 29/05/2013 16:46, Manfred Moser a écrit :
>
>> Can you clarify the details of what you mean with that?
>
> See:
> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-NonuniqueSnapshotDeployments
>
> I can no longer deploy non
> Hi all,
>
> There is an increasing number of Maven plugins that require Maven 3 and
> can't be upgraded without breaking Maven 2. For example
> maven-install-plugin 2.3 works with Maven 2 and Maven 3, but the version
> 2.4 is for Maven 3 only.
>
> What's the proper way to handle this situation? S
> Le 29/05/2013 17:06, Manfred Moser a écrit :
>
>> What are you deploying to if you are not using a repo manager?
>
> I simply deploy to a remote server via SSH. The artifacts are served by
> Apache.
Ah... ouch.
>> And why not use e.g. Nexus and just have the snaps
ing
system?
And a last one.. have you announced the package on the maven lists?
manfred
--
Manfred Moser
Vancouver Island Java User Group
http://www.mosabuam.com/vijug
skype: mosabua
http://www.linkedin.com/in/manfredmoser
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of &q
too.
manfred
--
Manfred Moser
Vancouver Island Java User Group
http://www.mosabuam.com/vijug
skype: mosabua
http://www.linkedin.com/in/manfredmoser
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Friday May 4 2007, David Herron wrote:
> Manfred Moser wrote:
> > Hi!
> >
> > Just wondering if anybody on the list will be at JavaOne next
> > week and if there is some sort of meeting I could attend. I would
> > love to meet some of you.
> >
> >
aim at an earlier stage here as far as I understand it would
actually be feasible to use the binary package for developing these
processes now.
Anyway.. just an idea. Integrating maven will include lots of other
tasks like a debian build system private repository and so on.
manfred
--
Ma
t; earlier this month about "java dependency substvars"?
I missed that discussion. I do assume that with some sort of lookup
list of "debian" approved/included dependencies even that might be
possible. Certainly something to be considered as a second step once
the creation
ne that the Debian team is packaging Maven and he was astonished and
delighted. He or somebody else might be able to give a good tip here
and there.
I hope this helps a bit.
manfred
--
Manfred Moser
http://www.mosabuam.com
skype: mosabua
http://www.linkedin.com/in/manfredmoser
--
To U
g
the package from the upstream source. The information in the pom can
be used to derive a lot of data in the debian control files.
In addition when another version is available from upstream the pom
content can be verified back into the control files to do amendments.
That wont be fully automat
re
are valid reasons to support the old and the new API at the same
time.
manfred
--
Manfred Moser
http://www.mosabuam.com
skype: mosabua
http://www.linkedin.com/in/manfredmoser
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
look forward to the progress. I wish I could help more but time is
very short at the moment... at least I hope to be able to help by
giving my input.
manfred
--
Manfred Moser
http://www.mosabuam.com
skype: mosabua
http://www.linkedin.com/in/manfredmoser
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
26 matches
Mail list logo
