Probable you know already the reason why there is a timestamp and a
buildnumber being attached to your Manifest classpath but for all those who
will have the same issue I will provide a solution:
You just have to add the following entry to your manifest configuration
bundled with the maven war
Just resending the part of Michael's email/post that was eaten by
Nabble and not forwarded...
You just have to add the following entry to your manifest
configuration bundled with the maven war plguin:
manifest
addClasspathtrue/addClasspath
useUniqueVersionsfalse/useUniqueVersions
Hello all,
We recently changed the packaging of some modules in our application :
dependency
groupIdmy.company/groupId
artifactIdmy.artifact.core/artifactId
version2.5.0-SNAPSHOT/version
/dependency
to
dependency
groupIdmy.company.internal/groupId
What are you trying to accomplish?
Why is your situation different from the normal system development
process that everyone else uses.
What version do you want to run at run-time?
In the pom of the artifact that you are making, set the dependency to
the version of
Hi all,
I'm having an issue with a plugin. I have two mojos with the following
annotations (yes, I haven't yet moved to Java5 annotations):
* @goal run-codeserver
* @execute phase=process-classes
* @requiresDirectInvocation
* @requiresDependencyResolution compile
Source:
What have you tried and what did it do?
Did you read up on multi-module builds to see how they are supposed to
work and what you need to do to make it happen?
Ron
On 05/10/2012 10:56 AM, Jan wrote:
Hi All,
I'm trying to see is there any best way or process to do incremental build
using
Hello Ron,
Let me try to explain with other terms what we have and we want to do
: we have refactored an artifact, changing his name and even its group
name;
* from version 1.0.0 to 2.5.0, this artifact was named
my.company:my.artifact.core:version
* from version 2.5.1 and up , this artifact is
Sorry for more questions than answers.
I am glad that it provided a creative push.
We use exclusions extensively in our builds to ensure that we get the
right version at run-time and they work as advertised.
Ron
On 05/10/2012 11:30 AM, Anthony Dahanne wrote:
Hello Ron,
Let me try to explain
Currently i use buildforge with maven but i do execute them separately for
each module, means runs mvn clean install commands from each module. This
will basically cleans and compiles everything whether there is change or
not. Now i'm trying to make use of incremental build function, so i changed
Greetings maven-nar-plugin hackers!
I am writing to gauge interest in a unified implementation of
maven-nar-plugin. It seems there are several active (and not-so-active)
forks. It seems the original implementation (@duns) is no longer active,
but both @GregDomjan and @richardkerr have active
Hi all,
Replying back with defunct email addresses purged, so that any future
replies don't keep receiving bounces.
-Curtis
On Fri, Oct 5, 2012 at 11:09 AM, Curtis Rueden ctrue...@wisc.edu wrote:
Greetings maven-nar-plugin hackers!
I am writing to gauge interest in a unified implementation
Hi.
However the first topic is to group a team that will be well active and
that will be adoting all forks. I suggest to choose one github project and
declare it to be the new main project.
One fork by one should be merged and than deleted. Maybe we should choose
richards or gregs project (that
Hi,
The Mojo team is pleased to announce the release of the SiteSkinner Maven
Plugin version 1.0.
The siteskinner-maven-plugin can update or apply a new skin on published sites
generated by Maven without changing its content.
http://mojo.codehaus.org/siteskinner-maven-plugin/
To use
Hey y’all,
I am trying to link one project’s jar to another project. I am totally
confused and hope someone can take some time to explain. I have been
reading the following pages on the site:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
14 matches
Mail list logo
