Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #11215 > unrolled thread

New Package JVerein

Back to article view | Back to linux.debian.maint.java

Contents

  New Package JVerein Mechtilde <ooo@mechtilde.de> - 2019-05-25 09:00 +0200
    Re: New Package JVerein Markus Koschany <apo@debian.org> - 2019-05-25 10:40 +0200
      Re: New Package JVerein Mechtilde <ooo@mechtilde.de> - 2019-06-07 13:40 +0200
        Re: New Package JVerein Mechtilde Stehmann <mechtilde@debian.org> - 2019-08-25 08:30 +0200
          Re: New Package JVerein Markus Koschany <apo@debian.org> - 2019-08-25 14:10 +0200
            Re: New Package JVerein Mechtilde <ooo@mechtilde.de> - 2019-08-27 20:40 +0200
              Re: New Package JVerein Mechtilde <ooo@mechtilde.de> - 2019-08-31 18:50 +0200

#11215 — New Package JVerein

[Multipart message — attachments visible in raw view] — view raw

Hello,

I'm packaging my first Java Package.

ITP # 929477

It is available at people.debian.org/~mechtilde/JVerein

You can find my lintian output at
people.debian.org/~mechtilde/JVerein/Lintian.log.

I'm not shure how I have to handle it.  I know that I can ignore the
pedantic and the experimental warnings.

But how should I have to handle the normal warnings and the remaining error?

Can someone advise me through the steps?

For more inforamtiones please ask me

Kind regards

-- 
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F




-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

[toc] | [next] | [standalone]

#11216

[Multipart message — attachments visible in raw view] — view raw

Hallo Mechtilde,

Am 25.05.19 um 08:51 schrieb Mechtilde:
[...]
> Can someone advise me through the steps?

I just comment on all the warnings I can find.

source-contains-prebuilt-java-object

The upstream sources contain various jar files. We always remove them
from the upstream tarball to ensure we only build with system libraries.

package-contains-vcs-control-file

Same here, I suggest to remove the .gitignore file when you repack the
tarball anyway.

jar-contains-source

This is usually quite harmless. Normally we don't ship java source files
in our binary packages except the application functions this way
(robocode) but most of the time jar files just contain class files and
some content files like images, sounds or text files. I believe there is
probably something wrong with the build system.

In build/build.xml I can see that java files should have been excluded
when using the jar target but there may be something else, so they get
still included.

executable-jar-without-main-class

It looks like that you are shipping the prebuilt csvjdbc.jar in your
binary package.

codeless-jar

Usually harmless but can indicate an error when building the package.
itext-hyph-xml.jar should probably be a symlink to our system package of
itext.

classpath-contains-relative-path

This may work as long as all your libraries are really in your lib
directory. For instance I can't find patch.jar or metouia.jar. So you
should carefully check whether those jar files should be present in your
lib directory. We normally symlink to our system packages but you have
either installed the prebuilt once or you have copied the system jar
files to the lib directory.

You can modify the classpath by using javahelper and a manifest file

jverein.manifest

usr/share/jameica/plugins/jverein/lib/lib/nc.jar:
 Class-Path: /usr/share/java/kunststoff.jar /usr/share/java/jcalendar.jar

and so on. We recommend absolute paths because they are unambiguous. In
some cases relative paths will lead to build failures when other
packages use your package as a build dependency which makes it often
hard to debug the problem.

So far

Regards,

Markus

[toc] | [prev] | [next] | [standalone]

#11268

[Multipart message — attachments visible in raw view] — view raw

Hello Markus,

thanks for your detailed information.

Am 25.05.19 um 10:36 schrieb Markus Koschany:
> Hallo Mechtilde,
> 
> Am 25.05.19 um 08:51 schrieb Mechtilde:
> [...]
>> Can someone advise me through the steps?
> 
> I just comment on all the warnings I can find.
> 
> source-contains-prebuilt-java-object
> 
> The upstream sources contain various jar files. We always remove them
> from the upstream tarball to ensure we only build with system libraries.

That is solvable. I have to package some of them myself. This takes time.

> package-contains-vcs-control-file
> 
> Same here, I suggest to remove the .gitignore file when you repack the
> tarball anyway.
solved
> 
> jar-contains-source
> 
> This is usually quite harmless. Normally we don't ship java source files
> in our binary packages except the application functions this way
> (robocode) but most of the time jar files just contain class files and
> some content files like images, sounds or text files. I believe there is
> probably something wrong with the build system.
> 
> In build/build.xml I can see that java files should have been excluded
> when using the jar target but there may be something else, so they get
> still included.

Can someone give me a hint why it is included even so

> 
> executable-jar-without-main-class
> 
> It looks like that you are shipping the prebuilt csvjdbc.jar in your
> binary package.

fixed
> 
> codeless-jar
> 
> Usually harmless but can indicate an error when building the package.
> itext-hyph-xml.jar should probably be a symlink to our system package of
> itext.

Where can I find "our system package of itext"

Kind regards

Mechtilde
> 
> classpath-contains-relative-path
> 
> This may work as long as all your libraries are really in your lib
> directory. For instance I can't find patch.jar or metouia.jar. So you
> should carefully check whether those jar files should be present in your
> lib directory. We normally symlink to our system packages but you have
> either installed the prebuilt once or you have copied the system jar
> files to the lib directory.
> 
> You can modify the classpath by using javahelper and a manifest file
> 
> jverein.manifest
> 
> usr/share/jameica/plugins/jverein/lib/lib/nc.jar:
>  Class-Path: /usr/share/java/kunststoff.jar /usr/share/java/jcalendar.jar
> 
> and so on. We recommend absolute paths because they are unambiguous. In
> some cases relative paths will lead to build failures when other
> packages use your package as a build dependency which makes it often
> hard to debug the problem.
> 
> So far
> 
> Regards,
> 
> Markus
> 
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

[toc] | [prev] | [next] | [standalone]

#11335

[Multipart message — attachments visible in raw view] — view raw

Hello,

I want to work at this new Package on Salsa too.

I want to join the team Debian Java Maintainers.

My username is Mechtilde <mechtilde@debian.org>



Am 07.06.19 um 13:39 schrieb Mechtilde:
> Hello Markus,
> 
> thanks for your detailed information.
> 
> Am 25.05.19 um 10:36 schrieb Markus Koschany:
>> Hallo Mechtilde,
>>
>> Am 25.05.19 um 08:51 schrieb Mechtilde:
>> [...]
>>> Can someone advise me through the steps?
>>
>> I just comment on all the warnings I can find.
>>
>> source-contains-prebuilt-java-object
>>
>> The upstream sources contain various jar files. We always remove them
>> from the upstream tarball to ensure we only build with system libraries.
> 
> That is solvable. I have to package some of them myself. This takes time.
> 
>> package-contains-vcs-control-file
>>
>> Same here, I suggest to remove the .gitignore file when you repack the
>> tarball anyway.
> solved
>>
>> jar-contains-source
>>
>> This is usually quite harmless. Normally we don't ship java source files
>> in our binary packages except the application functions this way
>> (robocode) but most of the time jar files just contain class files and
>> some content files like images, sounds or text files. I believe there is
>> probably something wrong with the build system.
>>
>> In build/build.xml I can see that java files should have been excluded
>> when using the jar target but there may be something else, so they get
>> still included.
> 
> Can someone give me a hint why it is included even so
> 
>>
>> executable-jar-without-main-class
>>
>> It looks like that you are shipping the prebuilt csvjdbc.jar in your
>> binary package.
> 
> fixed
>>
>> codeless-jar
>>
>> Usually harmless but can indicate an error when building the package.
>> itext-hyph-xml.jar should probably be a symlink to our system package of
>> itext.
> 
> Where can I find "our system package of itext"
> 
> Kind regards
> 
> Mechtilde
>>
>> classpath-contains-relative-path
>>
>> This may work as long as all your libraries are really in your lib
>> directory. For instance I can't find patch.jar or metouia.jar. So you
>> should carefully check whether those jar files should be present in your
>> lib directory. We normally symlink to our system packages but you have
>> either installed the prebuilt once or you have copied the system jar
>> files to the lib directory.
>>
>> You can modify the classpath by using javahelper and a manifest file
>>
>> jverein.manifest
>>
>> usr/share/jameica/plugins/jverein/lib/lib/nc.jar:
>>  Class-Path: /usr/share/java/kunststoff.jar /usr/share/java/jcalendar.jar
>>
>> and so on. We recommend absolute paths because they are unambiguous. In
>> some cases relative paths will lead to build failures when other
>> packages use your package as a build dependency which makes it often
>> hard to debug the problem.
>>
>> So far
>>
>> Regards,
>>
>> Markus
>>
>>
> 

-- 
Mechtilde Stehmann
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

[toc] | [prev] | [next] | [standalone]

#11336

[Multipart message — attachments visible in raw view] — view raw

Hello Mechtilde,

Am 25.08.19 um 08:24 schrieb Mechtilde Stehmann:
> Hello,
> 
> I want to work at this new Package on Salsa too.
> 
> I want to join the team Debian Java Maintainers.
> 
> My username is Mechtilde <mechtilde@debian.org>

I've just added you to the java-team on salsa.

Cheers,

Markus

[toc] | [prev] | [next] | [standalone]

#11339

[Multipart message — attachments visible in raw view] — view raw

Hello

to package jverein I stumble from one problem to the next.

I take the pckage <hibiscus> as a template. I created a similar links file

I started to remove the shipped java libraries step-by step.

To remove bsh-core shows me the Error <warning: [options] bootstrap
class path not set in conjunction with -source 7
    [javac]
/build/jverein-ds3-2.8.18+ds/src/de/jost_net/JVerein/util/LesefeldAuswerter.java:25:
error: package bsh does not exist
    [javac] import bsh.EvalError;

I installed libbsh-java as build dependencies and this package contains
the the same jar file as I found in the upsteeam code.[1]

Where should I look? Can somme point me to the infos I need?

Please ask if you need more information


[1] https://github.com/jverein/jverein

Thanks in advance


Am 25.08.19 um 14:03 schrieb Markus Koschany:
> Hello Mechtilde,
> 
> Am 25.08.19 um 08:24 schrieb Mechtilde Stehmann:
>> Hello,
>>
>> I want to work at this new Package on Salsa too.
>>
>> I want to join the team Debian Java Maintainers.
>>
>> My username is Mechtilde <mechtilde@debian.org>
> 
> I've just added you to the java-team on salsa.
> 
> Cheers,
> 
> Markus
> 

-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

[toc] | [prev] | [next] | [standalone]

#11347

[Multipart message — attachments visible in raw view] — view raw

Hello,

the problem with bsh-core is solved . thanks to Jochen

Am 27.08.19 um 20:30 schrieb Mechtilde:
> Hello
>> to package jverein [1] I stumble from one problem to the next.

I tried to exclude the *.java from the jverein.jar

At least I tried the following changes (added exclude name)

@@ -123,6 +127,7 @@
                <zip casesensitive="true"
zipfile="${project.release}/${define.srcfilename}">
                        <fileset dir="${project.tmp}">
                                <include name="${plugin.name}/**" />
+                               <exclude name="${plugin.name}/**/*.java"  />
                        </fileset>
                </zip>
        </target>

in [2]

But this isn't correct. Can someone give me a hint to the right place?

> 
> [1] https://github.com/jverein/jverein
[2] https://github.com/jverein/jverein/blob/master/build/build.xml#L123

Thanks in advance


-- 
Mechtilde Stehmann
## Apache OpenOffice
## Freie Office Suite für Linux, MacOSX, Windows
## Debian Developer
## PGP encryption welcome
## F0E3 7F3D C87A 4998 2899  39E7 F287 7BBA 141A AD7F

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.maint.java

csiph-web