Re: Producing java8 and java7 versions

Hello Chris, Here is one example: https://repo1.maven.org/maven2/org/postgresql/postgresql/ WBR, Maxim (from mobile, sorry for the typos) On Jun 8, 2017 10:44, "Christofer Dutz" wrote: > Hi, > > Currently the Edgent project produces two tar.gz files … one for java7

Re: Producing java8 and java7 versions

So, they are adding the java version as a suffix to the version of the artifact … don’t quite know if I really like that solution. I think It would break some version related automatisms, but it is definitely a safer solution as the classifier solution. But how would such a build look like?

Re: Producing java8 and java7 versions

I don't have computer right now, so I can't check I believe you can check pom in their repo or ask their mailing list :) Additional option might me: having version X.a.b.c for java7 and version Y.a.b.c for java8 Apache Wicket uses such naming ... WBR, Maxim (from mobile, sorry for the typos)

Naming apache artifacts

Hi, Another question that came up while at my Maven migration task in the Edgent project. Justin suggested to prefix all artifactIds with “apache-edgent-“. Having a look at the Apache Repo it feels like 80% prefix the artifacts with the “{projectname}-“ , about 10% with “apache-{projectname}”

Producing java8 and java7 versions

Hi, Currently the Edgent project produces two tar.gz files … one for java7 and one for java8. Now they would like to produce artifacts for Maven-Central. I’m currently trying to help them with their build by migrating this to maven. I think that there currently is no clean way to provide both

Re: Producing java8 and java7 versions

Perhaps not adding any suffix to the version for the java8 version would be ok and to add “java7” to the version for the legacy builds would be a good compromise. Chris Am 08.06.17, 11:11 schrieb "Christofer Dutz" : So, they are adding the java version as a

jaxws-maven-plugin: wsgen compiles with wrong source and target version

I’m using jaxws-maven-plugin to generate some java-files and compile them to classes. I’m running JDK 8 on my machine but I want the output jars to be compatible with java 7, I’ve configured the maven-compiler-plugin so all my other jars are correct but it ’s seems like the jaxws-plugin doesn’t

Re: jaxws-maven-plugin: wsgen compiles with wrong source and target version

By default the wsgen target compiles any generated classes as well, which is typically not how it should be done in a Maven project as the compilation should be handled by the maven-compile-plugin. But this is due to wsgen being a tool which is wrapped by the jaxws-maven-plugin. (However, the

Re: Producing java8 and java7 versions

Hi Chistopher, Christofer Dutz wrote: > Perhaps not adding any suffix to the version for the java8 version would > be ok and to add “java7” to the version for the legacy builds would be a > good compromise. That's what XStream has done with the last release. Cheers, Jörg