Le 17/10/2013 07:44, tony mancill a écrit :
> The packaging itself looks good. There are some files in
> ./contrib/src/java/org/jdom2/contrib that don't contain a license
> statement.
>
> Examples include (but aren't limited to):
>
> android/TranslateTests.java
> ids/doc-files/TestI
On 10/15/2013 10:54 PM, Emmanuel Bourg wrote:
> Hi all,
>
> I'm looking for a sponsor to upload libjdom2-java. This is a new package
> derived from libjdom1-java. The new API is incompatible and requires a
> new package. jdom2 is a dependency of the latest version of xstream.
>
> Here is the chan
Hi Emmanuel,
that did the trick!
Thank you very much,
Alex
On 16.10.2013, at 18:18, Emmanuel Bourg wrote:
> Hi Alex,
>
> Quite often the projects requiring Maven 3 still build fine with Maven
> 2. You just have to patch the prereq in the pom.xml.
>
> Replace:
>
>
>3.0.0
>
>
Hi Alex,
Quite often the projects requiring Maven 3 still build fine with Maven
2. You just have to patch the prereq in the pom.xml.
Replace:
3.0.0
with:
2.2.1
Emmanuel Bourg
Le 16/10/2013 17:58, Alexander Holupirek a écrit :
> Hi all,
>
> i'm in the progress of updatin
On Thu, Oct 10, 2013 at 11:22 AM, Emmanuel Bourg wrote:
> Le 10/10/2013 15:30, Stephen Nelson a écrit :
> > I'm looking at packaging a new upstream version of libspring-java.
> > However upstream has switched to using gradle to build the code. What
> > is the correct way to package for Debian in
Hi all,
i'm in the progress of updating the java package basex [1].
However, upstream has changed their build process to maven3.
How do we proceed in cases like this?
Cheers,
Alex
[1] http://packages.qa.debian.org/b/basex.html
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debi
6 matches
Mail list logo
