Hi,
This question has been asked quite a couple of times already, but I never found
a real solution nor do I know if this should really be supported:
Is it possible to do a release with the maven-release-plugin when the parent
pom.xml is not in the root of the git repo?
This is no problem with S
On 17/07/2014 1:57 PM, Anders Hammar wrote:
There is one major drawback with using the manifest file. It will not work
with unit tests as the manifest file isn't created until the jar is
created. But if your unit tests don't touch any of the code that reads the
manifest info that's not a problem.
I have added a link to Karl's blog to my article.
On 17/07/2014 1:34 PM, Curtis Rueden wrote:
Hi all,
Best and simple solution...which i wrote longer time a go a blog about
http://blog.soebes.de/blog/2014/01/02/version-information-into-your-appas-with-maven/
I agree with Karl: I think it i
Hi Cristiano,
now the artifacts are visible via search.maven.org...so it should work.
Kind regards
Karl-Heinz Marbaise
On 7/17/14 5:38 PM, Karl Heinz Marbaise wrote:
Hi Cristinano,
for whatever reason the plugin is available in Codehaus Nexus (Staging
Repository)
https://nexus.codehaus.org
> > Best and simple solution...which i wrote longer time a go a blog about
> >
>
> http://blog.soebes.de/blog/2014/01/02/version-information-into-your-appas-with-maven/
>
> I agree with Karl: I think it is much nicer to use the maven-jar-plugin to
> add the version to the JAR manifest, and just rea
+1
Op Thu, 17 Jul 2014 17:18:38 +0200 schreef Karl Heinz Marbaise
:
Hi,
> Move the Java code that should contain the version into an own
directory
tree (e.g. src/main/java-templates). Replace the version string with an
expression (e.g. "${project.version}") and use the copy-resources go
Hi all,
> Best and simple solution...which i wrote longer time a go a blog about
>
http://blog.soebes.de/blog/2014/01/02/version-information-into-your-appas-with-maven/
I agree with Karl: I think it is much nicer to use the maven-jar-plugin to
add the version to the JAR manifest, and just read it
Hi,
I would like to use the Maven Enforcer plugin to fail builds on our Jenkins
server that do not have a -SNAPSHOT version and are not a maven release build.
I've had issues where either through lack of knowledge or as fallout from a
failed release attempt where a developer tries to build what s
Hi Cristinano,
for whatever reason the plugin is available in Codehaus Nexus (Staging
Repository)
https://nexus.codehaus.org/content/groups/staging/ but it isn't being
synched to Central
Created a Haus Ticket for it:
http://jira.codehaus.org/browse/HAUS-2391
Thanks for the hint...
Hi Julien,
I wasn't able to see this version at
http://search.maven.org/#search|ga|1|sonar-maven-plugin
could you check, please?
thanks,
Cristiano
On 15-07-2014 12:08, Julien HENRY wrote:
Hi,
The Mojo team is pleased to announce the release of the SonarQube Maven Plugin
version 2.4.
Thi
Hi,
> Move the Java code that should contain the version into an own directory
tree (e.g. src/main/java-templates). Replace the version string with an
expression (e.g. "${project.version}") and use the copy-resources goal of
the resources plugin to filter the file into a target driectory tree (e
Jörg Schaible's response was so neat that I could not resist writing a
blog article about it.
http://blog.artifact-software.com/tech/?p=229 is the post.
If there are any comments about how to improve the article, I would
appreciate the feedback.
Ron
On 17/07/2014 5:03 AM, Jörg Schaible wrot
Hi Alejandro,
alejandro.e...@miranda.com wrote:
> Hi Curtis,
>
> I *think* i see you point, but wouldn't that happen ONLY if the constant
> is public and referenced in a separate jar?? where it would be inlined in
> the referring class (right?). In my case the constant is package protected
> (it
13 matches
Mail list logo
