This was added to 2.1, it won't happen in 2.0.x. A flag to force it
needs to be added to the interface and to the deploy plugin, and it
should be backported to 2.0. Can you write a jira?
-Original Message-
From: Thomas Tardy [mailto:[EMAIL PROTECTED]
Sent: Monday, January 21, 2008 9:01 AM
And there was much rejoicing.
On Jan 21, 2008, at 5:51 PM, Stuart McCulloch wrote:
Hi folks,
maven-bundle-plugin 1.2.0 has reached the central repository, so you
can now use:
org.apache.felix
maven-bundle-plugin
1.2.0
if you find any issues (or would
Hi folks,
maven-bundle-plugin 1.2.0 has reached the central repository, so you can now
use:
org.apache.felix
maven-bundle-plugin
1.2.0
if you find any issues (or would like to request new features) please raise
them at:
http://issues.apache.org/jira/b
I have an artifact in my project with a file extension of "xtc" and I'd like
to use parameter binding in the same way that you can in xml artifacts.
Currently, param binding works fine using the following format,
${project.artifactId}, in xml files. How do I add the "xtc" extension so
that files
I see in version 2.2 I can include all dependencies using the new
wildcard syntax:
lib
*:jar
However how do I also include the current artifact (the one that this
project is building?) Note I have a single jar type project
Ok, I tried to add site:site build definition just under my install build
definition. Then at noon my build is suppose to kick off and here are mo
logs:
*2008-01-21 12:03:14,436 [pool-1-thread-1] INFO
org.apache.maven.continuum.scm.ContinuumScm:default - Updated 185 files.
2008-01-21 12:03:14,558
Hi I have been trying to deploy the latest version of
the Archiva war to JBoss version 4.2.2 without
success. Has anyone else been successful in deploying
the latest version of Archiva to JBoss?
I would really like to get this working and appreciate
any help anyone can offer!
I have seen the foll
In order to have a stable system you MUST understand what the latest release
means... if you introduce this into your build you have no control over what
actually ends up in it. As an end user this is not a huge deal directly
except when people start using RELEASE/STABLE in libraries in the main
Hi,
Is there way to remove an artifact from my internal repository that setup by
Archiva?
i have a tree of modules projects to aggregate all of my projects together for
CI, it works very well...
NOTE the modules projects are not parents but siblings of the modules they
aggregate
On Tue, 22 Jan 2008 01:43:50 Jan Torben Heuer wrote:
> Hi,
>
> I have a tree of projects which depend on
annoying indeed but you only have to set the scm urls once in the each
artifact and with an archetype well only once.
i think its dumb to have the parent of several modules the same... if you
think OO then the parent of any artifact should define common behaviour for
articfacts of that type...
Hi there,
I'm involved currently with implementing a custom skin for a Maven project
generated website. Everything is great regarding the pages template (which
uses velocity and the DecorationModel), but we could use a bit more
flexibility for the sections in the body content. More specifically, e
It might work without the tags. But it certainly will not
work without the .
Wayne
On 1/21/08, Jan Torben Heuer <[EMAIL PROTECTED]> wrote:
> Wayne Fay wrote:
>
> > Make sure you have and tags set up properly. It
> > should go into each child directory and build all the various projects
> > in
Hi Matthew,
Your use case seems ideal for Maven Ant Tasks: instead of running 'mvn
dependency:unpack-dependencies', you can add a target to your buildfile that
use dependencies task, either with an external pom or dependencies declared
directly in the buildfile.
See http://maven.apache.org/ant
actually, why can't you just add ${buildNumber} to your Versions.txt ???
On Jan 21, 2008 10:17 AM, Mick Knutson <[EMAIL PROTECTED]> wrote:
> Add this to your filter.properties:
>
> BUILDTIME=${buildNumber}
>
>
>
> On Jan 21, 2008 9:10 AM, Rex Huang <[EMAIL PROTECTED]> wrote:
>
> > yah, use build
Add this to your filter.properties:
BUILDTIME=${buildNumber}
On Jan 21, 2008 9:10 AM, Rex Huang <[EMAIL PROTECTED]> wrote:
> yah, use buildnumber-maven-plugin may be better.
> one strange thing is I can't use ${buildNumber} in filter,
> when I want to replace $BUILDTIME in the resource file.
>
Since these questions have come from time to time on the mailing list
without good answers, I'll write down some experiences from the field.
First, for the parent links (when browsing a child module in a multimodule
project), the only way I've been able to make them appear is I have to have
a site.
yah, use buildnumber-maven-plugin may be better.
one strange thing is I can't use ${buildNumber} in filter,
when I want to replace $BUILDTIME in the resource file.
such as:
in pom.xml
${buildNumber}
src/main/resources
true
Version.txt
Wayne Fay wrote:
> Make sure you have and tags set up properly. It
> should go into each child directory and build all the various projects
> in the proper order etc if you build from the top.
so I need this bi-directional connection with parent and module. There is
not a simpler way? I'd rathe
Make sure you have and tags set up properly. It
should go into each child directory and build all the various projects
in the proper order etc if you build from the top.
Wayne
On 1/21/08, Rex Huang <[EMAIL PROTECTED]> wrote:
> If you setup the multi-module-projects correctly.
> it will build ch
org.codehaus.mojo
buildnumber-maven-plugin
1.0-beta-1-SNAPSHOT
validate
The newer version of this plugin is found here:
http://mojo.codehaus.org/buildnumber-maven-plugin/
And the artifacts can also be found on central:
http://mvnrepository.com/artifact/org.codehaus.mojo/buildnumber-maven-plugin
Hth,
Nick Stolwijk
-Original Message-
From: Rex Huang [mailt
try to use "Dependency Version Ranges"
http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution
Rex
On Jan 21, 2008 8:49 AM, amit kumar <[EMAIL PROTECTED]> wrote:
> I am using buildnumber plugin now to append timestamp to the builds.
> But at continuous integration ( C
If you setup the multi-module-projects correctly.
it will build child projects if the parent project is built.
Rex
On Jan 21, 2008 1:43 PM, Jan Torben Heuer <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I have a tree of projects which depend on each other and of course its
> parents. It is a xmlbeans sch
I found information of maven-buildnumber-plugin here:
http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/howto.html
it's works!
Rex
On Jan 18, 2008 3:33 PM, Mark Eramo <[EMAIL PROTECTED]> wrote:
> Rex,
> Have a look at the Maven build number plugin. It may be able to do
> what you ne
> What you could possibly do is create a profile that you would use for
> compiling. In this profile, add the problem dependencies with scope of
> "compile". But in the main part, add the problem dependencies with scope of
> "runtime", so that projects which just *use* your code (via its pom) see t
Hi again,
I clean my local repository and the remote repository. I don't know how
maven finds out, that the artefact has already been deployed. I still get
the same message.
Thanks for your help!
Thomas
On Jan 21, 2008 2:53 PM, Thomas Tardy <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> is there a
Hi all,
is there a possibility to enforce the redeployment of an artefact during the
build? I get the message 'The artifact xxx has already been deployed. Not
deploying again.'
Yes, it exists but I want to replace it.
Thanks for any advice!
Kind Regards,
Thomas
On 21/01/2008, Tomasz Pik <[EMAIL PROTECTED]> wrote:
> On Jan 21, 2008 2:21 PM, Guillaume Lederrey
> <[EMAIL PROTECTED]> wrote:
> > On 20/01/2008, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > > You can use dependencyManagment in a parent pom to avoid specifying the
> > > version in all your child po
Guillaume Lederrey <[EMAIL PROTECTED]> schrieb:
> On 17/01/2008, Simon Kitching <[EMAIL PROTECTED]> wrote:
> > Suppose your project depends on class Foo from project p1 (and so declares
> > a compile-scope dependency on p1).
> >
> > But class Foo extends class Base from project p2 (and so p1
On 21/01/2008, Nicole Lacoste <[EMAIL PROTECTED]> wrote:
> Does this (Have all sources for all modules in the parent src folder) work
> with the release plugin? I would be very surprised if it did... Since the
> release plugin checks out a tagged version of everything to a different
> folder anyt
On Jan 21, 2008 2:21 PM, Guillaume Lederrey
<[EMAIL PROTECTED]> wrote:
> On 20/01/2008, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > You can use dependencyManagment in a parent pom to avoid specifying the
> > version in all your child poms. If you really want the "latest" you have
> > two choices:
>
Hi,
Does this (Have all sources for all modules in the parent src folder) work
with the release plugin? I would be very surprised if it did... Since the
release plugin checks out a tagged version of everything to a different
folder anything relative is lost.
Another option would be to have an a
On 20/01/2008, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> You can use dependencyManagment in a parent pom to avoid specifying the
> version in all your child poms. If you really want the "latest" you have
> two choices:
> LATEST - latest snapshot
> RELEASE - latest release
>
> Or you could specify a
On 18/01/2008, Adamson, Eric (DIT) <[EMAIL PROTECTED]> wrote:
> I'm relatively new to Maven 2, and am seeking advice regarding the
> following problem: I have written a data transfer object
> (MailMergeRequest) that will be passed (serialized to XML using Xstream)
> between web client, app server
I am working on migrating existing build scripts (Ant) to a Maven pom. I can
run our suite of Junit tests, some of these fail because of the modified
environment. The xml/txt files are created in the arget/surefire-reports
folder without problems. However I get the following error when I try to
ge
Hi,
I have a tree of projects which depend on each other and of course its
parents. It is a xmlbeans schema tree, but that should not matter.
Right now, I have simple projects in the filesystem, but it is very hard to
compile or built them, because I have to invoke maven on each project.
Is ther
On 17/01/2008, Simon Kitching <[EMAIL PROTECTED]> wrote:
> Suppose your project depends on class Foo from project p1 (and so declares a
> compile-scope dependency on p1).
>
> But class Foo extends class Base from project p2 (and so p1 has a
> compile-scope dependency on p2). So project p2 (even t
In my opinion, trunk is the development version aka SNAPSHOT. Only the tags
should contain the released version number. Each module should provide the
parent version it needs and can only be released if that is a non-SNAPSHOT
version.
With regards,
Nick Stolwijk
-Original Message-
Fr
I do/did understand you meant to say "release:prepare".
I do however see this message when using 2.0.8 w/ release-plugin 2.0-beta-7
and I do NOT have SNAPSHOT dependencies. What I do have are dependencies
using version ranges w/o SNAPSHOTS. I suspect I am getting tripped up by
the never-ending
hi,
currently i am having problems with importing maven dependencies. we've got
different datastructures (from xsd) from different versions, so i am mapping
these to the version flag of pom.
bla:datastructures:1.0
bla:datastructures:1.1
inside a project i want to import both:
...
bla
datastr
On Jan 21, 2008 11:48 AM, <[EMAIL PROTECTED]> wrote:
> But normally the trunk should always contain a SNAPSHOT version, but only the
> submodules don't
> have it as parent as long as they don't need to rely on the changes in the
> parent.
I do not know, why it "should". We do not do it that way
But normally the trunk should always contain a SNAPSHOT version, but only the
submodules don't have it as parent as long as they don't need to rely on the
changes in the parent. But if you use the release plugin to release the parent,
will the tag contain only the parent or all the submodules as
Hi all,
I am looking at the best approach to importing maven built products into
an ANT build. The approach I have at the moment is having a
maven-imports folder within my build directory, and within that folder I
have a pom.xml describing a list of dependencies that are required by my
ANT build.
Hi Dave,
dhoffer wrote:
>
> Just wondering, did you figure this out? I too have this problem and I
> don't have any snapshot dependencies parent or otherwise.
>
I wrongly wrote "release-perform", but in fact i talked about
"release:prepare"! Sorry for the confusion! If you don't have any SN
On Jan 21, 2008 11:00 AM, <[EMAIL PROTECTED]> wrote:
> But when you release the parent, do you also release all the submodules or do
> you run mvn with non-recursive?
If the parent hasn't changed (in other words, if it hasn't a SNAPSHOT
version), then I am happy to release the submodules only.
Hello,
I used maven-2.0.8 and Archiva 1.0.
I have a plugin with a version 1.2-TOMCAT6-SNAPSHOT.
I deploy it into the entreprise company snapshot repository and the
version becomes 1.2-TOMCAT6-20080121.095115-1
I clean my local repo but i have this error when i construct a project
depend on it
But when you release the parent, do you also release all the submodules or do
you run mvn with non-recursive?
With regards,
Nick Stolwijk
-Original Message-
From: Jochen Wiedmann [mailto:[EMAIL PROTECTED]
Sent: Mon 1/21/2008 10:52 AM
To: Maven Users List
Subject: Re: Best practices for
Hi Michael,
While adding the project in continuum I have to add choosing the
option of "load the parent project recursively in case of multi module
project", otherwise it doesn't get build.
But after I select this option, the added project doesn't show me sub
modules to add notifiers to. Only the p
On Jan 21, 2008 10:42 AM, <[EMAIL PROTECTED]> wrote:
> Is it advisable to move the commons-parent to another subdirectory or is this
> layout the preferred way?
I was experiencing with the former, but gave it up. The reason is that
far too many plugins are not suitable to use it. Examples inclu
At our company we are busy with a commons project, which has a few submodules.
Our current layout is:
commons-parent/
commons-module-1/
pom.xml
src/
commons-module-2/
commons-module-3/
pom.xml
Now we want to do seperate releases of the commons-parent and the modules, just
51 matches
Mail list logo
