Hi,
thanks for your comments, I will try to keep the maven part then. Since
I am unfamilar with maven one question remains:
* The package was getting its POM file through the get-orig-pom
target via:
wget -O debian/pom.xml
http://repository.sonatype.org/service/local/repositories/central/content/com/fifesoft/$(PKGNAME)/$(VERSION)/$(PKGNAME)-$(VERSION).pom
This is now access protected. I have located the pom at:
http://repo1.maven.org/maven2/com/fifesoft/rsyntaxtextarea/2.0.7/rsyntaxtextarea-2.0.7.pom
Which is also used by e.g. easymock. Who is maintaining those
pom-files? Are they somehow automatically maintained, so there
is always an appropriate pom file for the most recent version
available?
It seems that there is a really good integration of maven_repo_helper
with java helper today. So the packaging will actually not look much
more complicated then without maven.
Best regards
Ben
On Sun, 2013-09-22 at 00:00 +0200, Emmanuel Bourg wrote:
> Le 21/09/2013 10:58, Benjamin Mesing a écrit :
>
> > When packaging the new version I intend to remove the maven parts,
> > because they are not provided upstream and add to the packaging
> > complexity.
>
> Hi Benjamin,
>
> Thank you for taking care of this package.
>
> I think it would be preferable to preserve the Maven artifacts. Even if
> they are not provided upstream they can be found in the central Maven
> repository, that means other Maven based projects are likely to depend
> on rsyntaxtextarea. If the Maven artifacts are provided by the Debian
> package it'll be much easier to package these projects in the future.
>
> Emmanuel Bourg
>
>
--
To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1379844011.3628.10.ca...@athlon-x2.fritz.box
