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

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

To build a java package with maven

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

Contents

  To build a java package with maven Mechtilde Stehmann <mechtilde@debian.org> - 2020-06-20 12:50 +0200
    Re: To build a java package with maven Thorsten Glaser <t.glaser@tarent.de> - 2020-06-20 17:00 +0200
      Re: To build a java package with maven tony mancill <tmancill@debian.org> - 2020-06-20 17:20 +0200
        Re: To build a java package with maven Emmanuel Bourg <ebourg@apache.org> - 2020-06-21 01:30 +0200
      Re: To build a java package with maven Mechtilde <ooo@mechtilde.de> - 2020-06-20 18:20 +0200
        Re: To build a java package with maven Thorsten Glaser <t.glaser@tarent.de> - 2020-06-20 19:10 +0200
          Re: To build a java package with maven Mechtilde Stehmann <mechtilde@debian.org> - 2020-06-20 20:00 +0200
            Re: To build a java package with maven Thorsten Glaser <t.glaser@tarent.de> - 2020-06-20 20:30 +0200
              Re: To build a java package with maven Mechtilde Stehmann <mechtilde@debian.org> - 2020-06-21 08:10 +0200
                Re: To build a java package with maven Emmanuel Bourg <ebourg@apache.org> - 2020-06-21 11:00 +0200
                  Re: To build a java package with maven Mechtilde Stehmann <mechtilde@debian.org> - 2020-06-21 11:40 +0200
        Re: To build a java package with maven Emmanuel Bourg <ebourg@apache.org> - 2020-06-21 01:20 +0200
          OT javax.mail (was Re: To build a java package with maven) Thorsten Glaser <t.glaser@tarent.de> - 2020-06-21 01:30 +0200
            Re: OT javax.mail (was Re: To build a java package with maven) Emmanuel Bourg <ebourg@apache.org> - 2020-06-21 01:50 +0200
          Re: To build a java package with maven Mechtilde Stehmann <mechtilde@debian.org> - 2020-06-21 08:00 +0200

#11702 — To build a java package with maven

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

Hello

Again I'm trying to build a< new Java library which I need as a
dependency. This is Jcabi-Aspects (https://github.com/jcabi/jcabi-aspects)

when I build it, the compiler claims that the dependency can't be resolved:
javax.validation:validation-api:jar:debian for the file
https://github.com/jcabi/jcabi-aspects/blob/master/src/main/java/com/jcabi/aspects/aj/MethodValidator.java

line 36-39

I hoped to found a solution in building
https://github.com/eclipse-ee4j/beanvalidation-api as
libbeanvalidation-api-java.

which contains the class Validation.

In the d/rules I did the entry

export CLASSPATH := /usr/share/java/jakarta.validation-api.jar

This is the jar file in the package libbeanvalidation-api-java

and in d/maven.rules
s/javax.validation/jakarta.validation/
s/validation-api/jakarta.validation-api/ * s/.*/debian/ * compile

In the pom.xml I found the entry.

        <dependency>
            <groupId>javax.validation</groupId>
             <artifactId>validation-api</artifactId>
             <scope>compile</scope>
        </dependency>
When I look into the package libbeanvalidation-api-java I found this entry:
/usr/share/maven-repo/jakarta/validation/jakarta.validation-api/debian/jakarta.validation-api-debian.jar

But I get the error message that
package javax.validation does not exist

Can someone point me to the right entries?

Thanks in advance

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

[toc] | [next] | [standalone]

#11703

On Sat, 20 Jun 2020, Mechtilde Stehmann wrote:

> In the d/rules I did the entry
> 
> export CLASSPATH := /usr/share/java/jakarta.validation-api.jar

There is no file named jakarta.validation-api.jar in Debian,
according to a file search on packages.debian.org.

Furthermore, for Maven dependency resolution, you must not
set $CLASSPATH; only the information in the pom.xml file counts.

> In the pom.xml I found the entry.
> 
>         <dependency>
>             <groupId>javax.validation</groupId>
>              <artifactId>validation-api</artifactId>
>              <scope>compile</scope>
>         </dependency>

You have to insert the correct coordinates here. Sadly, according
to https://wiki.debian.org/Java/MavenPkgs/Unstable neither
javax.validation nor jakarta.validation are packaged in Debian yet,
so they have to be packaged.

> When I look into the package libbeanvalidation-api-java I found this entry:

There is no package libbeanvalidation-api-java in Debian.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

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

#11704

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

On Sat, Jun 20, 2020 at 04:57:06PM +0200, Thorsten Glaser wrote:
> On Sat, 20 Jun 2020, Mechtilde Stehmann wrote:
> 
> > In the d/rules I did the entry
> > 
> > export CLASSPATH := /usr/share/java/jakarta.validation-api.jar
> 
> There is no file named jakarta.validation-api.jar in Debian,
> according to a file search on packages.debian.org.
> 
> Furthermore, for Maven dependency resolution, you must not
> set $CLASSPATH; only the information in the pom.xml file counts.
> 
> > In the pom.xml I found the entry.
> > 
> >         <dependency>
> >             <groupId>javax.validation</groupId>
> >              <artifactId>validation-api</artifactId>
> >              <scope>compile</scope>
> >         </dependency>
> 
> You have to insert the correct coordinates here. Sadly, according
> to https://wiki.debian.org/Java/MavenPkgs/Unstable neither
> javax.validation nor jakarta.validation are packaged in Debian yet,
> so they have to be packaged.

javax.activation is found in geronimo-validation-1.1-spec.jar in the
libgeronimo-validation-1.1-spec-java package.

I believe we do need to package something for jakarta.validation. 

Cheers,
tony

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

#11710

Le 20/06/2020 à 17:13, tony mancill a écrit :

> javax.activation is found in geronimo-validation-1.1-spec.jar in the
> libgeronimo-validation-1.1-spec-java package.

Tony is right (modulo s/activation/validation/), you want to use the
libgeronimo-validation-1.1-spec-java package with the following Maven
rule:

  s/javax.validation/org.apache.geronimo.specs/ s/validation-api/geronimo-validation_1.1_spec/ * s/.*/debian/ * *

If you depend on jakarta-validation you'll have to patch all the Java
classes to replace "import javax.validation" with "import jakarta.validation".

Emmanuel Bourg

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

#11705

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

Hello Thorsten,

I know your list at https://wiki.debian.org/Java/MavenPkgs/Unstable

thanks for that work.

 But I packaged libbeanvalidation-api-java myself. It is now in the
NewQueue. I described it at the beginning of my question.


<cite>
I hoped to found a solution in building
https://github.com/eclipse-ee4j/beanvalidation-api as
libbeanvalidation-api-java.

which contains the class Validation.
</cite>

So I have this package at my local machine.

Kind regards

Mechtilde

Am 20.06.20 um 16:57 schrieb Thorsten Glaser:
> On Sat, 20 Jun 2020, Mechtilde Stehmann wrote:
> 
>> In the d/rules I did the entry
>>
>> export CLASSPATH := /usr/share/java/jakarta.validation-api.jar
> 
> There is no file named jakarta.validation-api.jar in Debian,
> according to a file search on packages.debian.org.
> 
> Furthermore, for Maven dependency resolution, you must not
> set $CLASSPATH; only the information in the pom.xml file counts.
> 
>> In the pom.xml I found the entry.
>>
>>         <dependency>
>>             <groupId>javax.validation</groupId>
>>              <artifactId>validation-api</artifactId>
>>              <scope>compile</scope>
>>         </dependency>
> 
> You have to insert the correct coordinates here. Sadly, according
> to https://wiki.debian.org/Java/MavenPkgs/Unstable neither
> javax.validation nor jakarta.validation are packaged in Debian yet,
> so they have to be packaged.
> 
>> When I look into the package libbeanvalidation-api-java I found this entry:
> 
> There is no package libbeanvalidation-api-java in Debian.
> 
> bye,
> //mirabilos
> 

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

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

#11706

On Sat, 20 Jun 2020, Mechtilde wrote:

>  But I packaged libbeanvalidation-api-java myself. It is now in the
> NewQueue. I described it at the beginning of my question.
> 
> 
> <cite>
> I hoped to found a solution in building
> https://github.com/eclipse-ee4j/beanvalidation-api as
> libbeanvalidation-api-java.
> 
> which contains the class Validation.
> </cite>

Ah okay, I didn’t fully understand that part.

(Besides that, something with jakarta.validation-api would
have been a more easily understood name… but given where
javax.activation is packaged in Debian that cause is lost
anyway…)

Looking at
https://ftp-master.debian.org/new/beanvalidation-api_3.0.0-M1-1~exp1.html
you also packaged a beta version (-M* are milestones, nowhere
near production-ready releases or stable APIs). From looking at
https://mvnrepository.com/artifact/jakarta.validation/jakarta.validation-api
you should almost certainly have packaged version 2.0.2 instead.

But ignoring that and looking at the package list…

-rw-r--r-- root/root      1321 2020-06-19 17:51 ./usr/share/maven-repo/jakarta/validation/jakarta.validation-api/debian/jakarta.validation-api-debian.pom

… is enough to get the following POM dependency work…

<dependency>
	<groupId>jakarta.validation</groupId>
	<artifactId>jakarta.validation-api</artifactId>
	<version>debian</version>
</dependency>

… if the package is in Build-Depends(‑Indep) / installed.
AIUI, the replacement of the real version with “debian”
is done by the packaging tools.

>>>In the pom.xml I found the entry.
>>>
>>>        <dependency>
>>>            <groupId>javax.validation</groupId>
>>>             <artifactId>validation-api</artifactId>
>>>             <scope>compile</scope>
>>>        </dependency>

Yes, change the groupId and artifactId; this is the new name.
If after that you still miss javax.validation:validation-api
then a dependency also wants it and you’ll have to use
exclusions, but given we only use packaged dependencies
this won’t happen.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

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

#11707

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

Hello

Am 20.06.20 um 19:09 schrieb Thorsten Glaser:
> On Sat, 20 Jun 2020, Mechtilde wrote:
> 
>>  But I packaged libbeanvalidation-api-java myself. It is now in the
>> NewQueue. I described it at the beginning of my question.
>>
>>
>> <cite>
>> I hoped to found a solution in building
>> https://github.com/eclipse-ee4j/beanvalidation-api as
>> libbeanvalidation-api-java.
>>
>> which contains the class Validation.
>> </cite>
> 
> Ah okay, I didn’t fully understand that part.
> 
> (Besides that, something with jakarta.validation-api would
> have been a more easily understood name… but given where
> javax.activation is packaged in Debian that cause is lost
> anyway…)
> 
> Looking at
> https://ftp-master.debian.org/new/beanvalidation-api_3.0.0-M1-1~exp1.html
> you also packaged a beta version (-M* are milestones, nowhere
> near production-ready releases or stable APIs). From looking at
> https://mvnrepository.com/artifact/jakarta.validation/jakarta.validation-api
> you should almost certainly have packaged version 2.0.2 instead.
> 
> But ignoring that and looking at the package list…
> 
> -rw-r--r-- root/root      1321 2020-06-19 17:51 ./usr/share/maven-repo/jakarta/validation/jakarta.validation-api/debian/jakarta.validation-api-debian.pom
> 
> … is enough to get the following POM dependency work…
> 
> <dependency>
> 	<groupId>jakarta.validation</groupId>
> 	<artifactId>jakarta.validation-api</artifactId>
> 	<version>debian</version>
> </dependency>
> 
> … if the package is in Build-Depends(‑Indep) / installed.
> AIUI, the replacement of the real version with “debian”
> is done by the packaging tools.
> 
>>>> In the pom.xml I found the entry.
>>>>
>>>>        <dependency>
>>>>            <groupId>javax.validation</groupId>
>>>>             <artifactId>validation-api</artifactId>
>>>>             <scope>compile</scope>
>>>>        </dependency>
> 
> Yes, change the groupId and artifactId; this is the new name.
> If after that you still miss javax.validation:validation-api
> then a dependency also wants it and you’ll have to use
> exclusions, but given we only use packaged dependencies
> this won’t happen.

That is excactly my problem. I installed libbeanvalidation-api-java from
my local repo with apt. I get the message that the package
javas.validation does not exists as described.
> 
> bye,
> //mirabilos
> 

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

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

#11708

On Sat, 20 Jun 2020, Mechtilde Stehmann wrote:

> That is excactly my problem. I installed libbeanvalidation-api-java from
> my local repo with apt. I get the message that the package
> javas.validation does not exists as described.

Yes, because jakarta.validation replaced javax.validation,
so you have to patch the POM.

bye,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

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

#11715

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

Hello and good morning,

do I understand it in a right way?

I patch the entry for the dependency part from javax.validation to
jakarta.vvalidation etc

then I use in maven.rules
s/javax.validation/jakarta.validation/
s/validation-api/jakarta.validation-api/ * s/.*/debian/ * *

So the import line import javax.validation.ConstraintViolation;
etc. should work.

I will wait till Emmanuel will do a new upload to the NewQueue.

Kind regards

Mechtilde

Am 20.06.20 um 20:25 schrieb Thorsten Glaser:
> On Sat, 20 Jun 2020, Mechtilde Stehmann wrote:
> 
>> That is excactly my problem. I installed libbeanvalidation-api-java from
>> my local repo with apt. I get the message that the package
>> javas.validation does not exists as described.
> 
> Yes, because jakarta.validation replaced javax.validation,
> so you have to patch the POM.
> 
> bye,
> //mirabilos
> 

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

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

#11717

Le 21/06/2020 à 08:01, Mechtilde Stehmann a écrit :

> do I understand it in a right way?
> 
> I patch the entry for the dependency part from javax.validation to
> jakarta.vvalidation etc
> 
> then I use in maven.rules
> s/javax.validation/jakarta.validation/
> s/validation-api/jakarta.validation-api/ * s/.*/debian/ * *
> 
> So the import line import javax.validation.ConstraintViolation;
> etc. should work.

No it won't, because the classes in the jakarta artifact are in the
jakarta.* package, not javax.*, so you would have to patch the Java files
to change the import statements.

The easiest solution is to depend on libgeronimo-validation-1.1-spec-java
and use this substitution rule:

  s/javax.validation/org.apache.geronimo.specs/ s/validation-api/geronimo-validation_1.1_spec/ * s/.*/debian/ * *

That's what the eclipselink package does for example:

  https://sources.debian.org/src/eclipselink/2.6.6-1/debian/maven.rules/?hl=2#L2

Emmanuel Bourg

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

#11719

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

Hello Emmanuel

Am 21.06.20 um 10:55 schrieb Emmanuel Bourg:
> Le 21/06/2020 à 08:01, Mechtilde Stehmann a écrit :
> 
>> do I understand it in a right way?
>>
>> I patch the entry for the dependency part from javax.validation to
>> jakarta.vvalidation etc
>>
>> then I use in maven.rules
>> s/javax.validation/jakarta.validation/
>> s/validation-api/jakarta.validation-api/ * s/.*/debian/ * *
>>
>> So the import line import javax.validation.ConstraintViolation;
>> etc. should work.
> 
> No it won't, because the classes in the jakarta artifact are in the
> jakarta.* package, not javax.*, so you would have to patch the Java files
> to change the import statements.
> 
> The easiest solution is to depend on libgeronimo-validation-1.1-spec-java
> and use this substitution rule:
> 
>   s/javax.validation/org.apache.geronimo.specs/ s/validation-api/geronimo-validation_1.1_spec/ * s/.*/debian/ * *
> 
> That's what the eclipselink package does for example:
> 
>   https://sources.debian.org/src/eclipselink/2.6.6-1/debian/maven.rules/?hl=2#L2

I will patch the lines from import javax.valitation.* to import
jakarta.validation.

so I can exercise how to do it.

I guess I will get more packages whre I have to patch upstream code ;-)
> 
> Emmanuel Bourg
> 

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

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

#11709

Hi Mechtilde,

Le 20/06/2020 à 18:17, Mechtilde a écrit :

>  But I packaged libbeanvalidation-api-java myself. It is now in the
> NewQueue. I described it at the beginning of my question.

Thank you for packaging Jakarta Bean Validation.

The Jakarta EE project has inherited from the JavaEE components
(servlet, activation, mail, jax*...), they are basically the same but
with the packages renamed from javax.* to jakarta.*.

This is a great opportunity to harmonize the EE packages in Debian
because we have so far a mix of geronimo, glassfish and xxx-api packages.

For the new Jakarta package I'd like to adopt a consistent naming if
possible: jakarta-* for the source packages, and libjakarta-*-java for
the binary packages. I've uploaded jakarta-activation today with this
convention, and I plan to follow with jakarta-mail and jakarta-servlet
when the final versions are released.

Do you mind if we drop libbeanvalidation-api-java from the NEW queue and
upload it again with the proposed naming? I can take care of this.

Emmanuel Bourg

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

#11711 — OT javax.mail (was Re: To build a java package with maven)

On Sun, 21 Jun 2020, Emmanuel Bourg wrote:

> convention, and I plan to follow with jakarta-mail and jakarta-servlet

WTF, jakarta-mail?

I just switched from javax.mail:javax.mail-api 1.4.7 to
com.sun.mail:javax.mail 1.6.2… and now see both
com.sun.mail:jakarta.mail and jakarta.mail:jakarta.mail-api
in versions 1.6.5 and am again confused by the move and by
which I should use… (I assume they are API-compatible enough
to javax.mail), do you have any extra info about these?
Feel free to follow up to just me about this if you think it too OT.

Thanks,
//mirabilos
-- 
tarent solutions GmbH
Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/
Tel: +49 228 54881-393 • Fax: +49 228 54881-235
HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941
Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg

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

#11712 — Re: OT javax.mail (was Re: To build a java package with maven)

Le 21/06/2020 à 01:23, Thorsten Glaser a écrit :

> WTF, jakarta-mail?
> 
> I just switched from javax.mail:javax.mail-api 1.4.7 to
> com.sun.mail:javax.mail 1.6.2… and now see both
> com.sun.mail:jakarta.mail and jakarta.mail:jakarta.mail-api
> in versions 1.6.5 and am again confused by the move and by
> which I should use… (I assume they are API-compatible enough
> to javax.mail), do you have any extra info about these?

The 1.6.x line is still the same API, but starting with the upcoming
version 2.0 the javax.mail package becomes jakarta.mail (the structure
of the API remains the same). They've messed a bit with the 1.6.5
release, it uses an artifact named 'jakarta' but the classes are still
in the javax.mail package (probably due to a trademark constraint
following the move to Eclipse).

Emmanuel Bourg

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

#11714

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

Hello Emmanuel

Am 21.06.20 um 01:16 schrieb Emmanuel Bourg:
> Hi Mechtilde,
> 
> Le 20/06/2020 à 18:17, Mechtilde a écrit :
> 
>>  But I packaged libbeanvalidation-api-java myself. It is now in the
>> NewQueue. I described it at the beginning of my question.
> 
> Thank you for packaging Jakarta Bean Validation.
> 
> The Jakarta EE project has inherited from the JavaEE components
> (servlet, activation, mail, jax*...), they are basically the same but
> with the packages renamed from javax.* to jakarta.*.
> 
> This is a great opportunity to harmonize the EE packages in Debian
> because we have so far a mix of geronimo, glassfish and xxx-api packages.
> 
> For the new Jakarta package I'd like to adopt a consistent naming if
> possible: jakarta-* for the source packages, and libjakarta-*-java for
> the binary packages. I've uploaded jakarta-activation today with this
> convention, and I plan to follow with jakarta-mail and jakarta-servlet
> when the final versions are released.
> 
> Do you mind if we drop libbeanvalidation-api-java from the NEW queue and
> upload it again with the proposed naming? I can take care of this.

Yes do it. Can you provide me the package, so I can work locally on the
next packages which depend on it.

> 
> Emmanuel Bourg
> 
Thanks in advance

-- 
Mechtilde Stehmann
## 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