We are using a the reactor plugin extensively but have noticed that it never
installs the master pom to the local repository. We manage all of our
dependency version information in the master pom, so it is important that it
be updated in the repository.
Example:
/pom.xml -- master pom containin
Sounds useful to me.
We were going to build a similar plugin - but the plan for it to be a sonar
plugin rather than a maven plugin.
Jim
On Fri, Sep 11, 2009 at 10:23 AM, Ben Lidgey wrote:
>
> It sounds like it could be useful, but perhaps with a warning as there are
> maintenance projects appl
That aspect could certainly be better. At least here we'd like to
publish snapshots every time to the same location, and each release to
a separate location plus the latest to a fixed location. You can do
something like
scp://myproject.mycompany.com/var/www/maven-site/versions/${project.version}.
But the release cycles of the company pom and your project shouldn't
be connected. I'd argue that you should only be using the same
released version of the company pom until it doesn't work for that
project anymore, and only then change to a new released version.
Furthermore, I think you should nev
Hi folks,
Getting started with Maven 2.0.9, I want to use the Sesame RDF
library. The POM is here:
http://repo.aduna-software.org/maven2/releases/org/openrdf/sesame/sesame/2.2.4/sesame-2.2.4.pom
It has 3 modules, and those modules contain many submodules.
Can I include ALL the submodules of ses
Regarding the link:
I don't want to deploy one of the artifacts in my multi-module build.
Can I skip deployment?
Yes, you can skip deployment of individual modules by configuring the
deploy plugin as follows:
maven-deploy-plugin
X.Y
t
Hi all,
I am currently refactoring a lot of our projects and this means updating all
POMs. I was looking at the ditributionmanagement-part of my POMs, and I was
wondering why there is no different setting for the SNAPSHOT- and
RELEASE-sites, like with the repositories.
We are running nightly b
If you'll forgive another bump on this thread, I found that including the
trailing '/' in the pattern will exclude the .svn directories:
**/.svn/
I am using maven-2.1.0 and maven-war-plugin-2.1-alpha-2.
--
View this message in context:
http://www.nabble.com/Exclude-subversion-files-in-war-tp
No, it's not the parent. I haven't tried the skipping yet, I'm currently
turning our projects upside-down, so I don't have the time yet... I just
wanted to check if somebody might now the answer...
On Friday 11 September 2009 16:17, Anders Hammar wrote:
> I'm a little bit confused. Is the aggre
versions:commit does not actually commit to your scm... it just removes the
versionsBackup files (poor man's SCM)
there is nothing stopping your from running versions:update-parent from a
root aggregator pom and updating everything... then 1 big scm commit of the
pom changes
2009/9/11 Stephen Dun
It sounds like it could be useful, but perhaps with a warning as there are
maintenance projects applying bug fixes to existing projects that may not want
to update older components to avoid too many changes.
Ben
On 10/09/2009 22:03, "Wendy Smoak" wrote:
A group I work with had a requirement
I'm a little bit confused. Is the aggregator pom also the parent of the
modules? If it is, it should also be deployed.
If not, I guess it should be able to make it not deploy by doing exactly as
described in:
http://maven.apache.org/plugins/maven-deploy-plugin/faq.html#skip
Declare this in the agg
Yes, that would be the ideal solution.
In the meantime, I'm avoiding manual and error-prone work by putting the
process into a shell script.
Best regards,
Eric
> -Ursprüngliche Nachricht-
> Von: Stephen Duncan Jr [mailto:stephen.dun...@gmail.com]
> Gesendet: Freitag, 11. September 2009
I think that's what he's referring to; it is in my case. First I release
the company-wide parent POM, then I begin releasing the rest of the
projects, each of which need to have their parent declaration updated from
the SNAPSHOT version to the just-released version. Currently I do this
manually t
Yes, this is exactly what I'm doing. Still, I want to change the parent to the
released version *and* release the project in one go.
And it seems like this is only possible by combining the versions and the
release plugins.
Best regards,
Eric
> -Ursprüngliche Nachricht-
> Von: David Hof
Hi
I'm using version 2.1 of the plugin ; my artifactid is 3.1.1-SNAPSHOT,
I am also maintaining another branch of the project, under version
4.0.M4-SNAPSHOT.
I have a resolved jira entry with a Fix For: field labelled for
versions 3.1.1 and 4.0.M4.
Whenever I run mvn changes:announcement-generate
I certainly have the exact same problem. And using the versions plugin only
helps somewhat in partially automating what I currently do manually. Last
time I made the mistake of not manually changing the parent version, the
release plugin, I believe, offered to update to a released version, but
di
Woudn't it better to first release your company-wide parent poms
first? Then release projects that refer to released poms? Otherwise
it seems you would now have to chase down all the old references to
the prior snapshot parent and manually update.
-Dave
On Fri, Sep 11, 2009 at 7:51 AM, Lewis, E
Thanks, that works well!
However, I'm still wondering whether I'm the only one releasing that way.
It seems to me that the release plugin can only be used together with the
versions plugin.
I think that most developers have some sort of company-wide parent POM which
they refer to, and when relea
Hi all,
Is it possible to skip deployment of a specific module when triggering 'mvn
deploy'? I've read in [1] that it's possible, but I think this will only work
on sub-modules.
My problem is that I have an aggregator-pom that is only used as an aggregator
and should not be deployed. Since itś
before you run a release just run
mvn versions:update-parent
mvn versions:commit
mvn release:prepare release:perform
2009/9/11 Lewis, Eric
> Hi Dave
>
> Thanks for the answer, but it's not quite what I meant :-)
>
> I don't mean the parent version within the modules, but the parent version
> w
Hi,
With similar issues I fought in july.
Unfortunately Eclipse does not have individual classpath for just testing,
therefore if the .classpath file has the test directories on sources, also
WTP will put in .settings/org.eclipse.wst.common.component too. and when the
dependencies are resolved from
Hi,
i have a problem with WTP and M2 Plugin. The problem is in file:-
.settings/org.eclipse.wst.common.component. If you I use the project
(web-project) without "Resolve dependencies from Workspace ..." it's
work fine, but if i use the project with "Resolve dependencies from
Workspace ..." t
Hi Dave
Thanks for the answer, but it's not quite what I meant :-)
I don't mean the parent version within the modules, but the parent version
within the project (i.e. the module's parent).
Let's say I have a company wide POM in the repo
company-pom:1.2.0-SNAPSHOT
which has been released to
The Sonatype book
2009/9/10 James Russo :
> Thanks Wes,
>
> I understand. I guess for me, I'm really looking to automate the release
> portion of things. So, when I fix something or commit a change (to a version
> already released and deployed), I can just wait at the end of this big
> machine (
I added the assemply plug in to a project, and it creates a proper jar
that includes config files, etc when run locally on my machine using
mvn package, but the same command on our build server outputs a jar
that lacks some critical config files that need to be at the default
package level
Hi!
It sounds as you need a CI server. It would solve your issue. Take a look at
CruiseControl:
http://cruisecontrol.sourceforge.net/
Hudson:
https://hudson.dev.java.net/
/Thomas
On Thu, Sep 10, 2009 at 13:10, Matt Milliss wrote:
> I work at a company that has around 10 applications, each app
27 matches
Mail list logo
