Hi,
Tim from Sonatype gave us 4 different books / documentation about Maven and
Maven related stuff.
"Maven the definitive guide" (published by O'reilly)
http://www.sonatype.com/products/maven/documentation/book-defguide
"Nexus documentation
http://www.sonatype.com/products/nexus/documentation/boo
Hi!
thanks for that answer... but why does it use pmd-jdk14 and not the
pmd-4.2.2.jar ?
(i looked for this jar as dependency and so i couldnt find the version...)
Is there a plan to adapt the maven-pmd-plugin to 4.2.5? (cause
ruleset- exclude patterns doesnt work with the actual plugin... but
wit
On 16/07/2009, at 1:11 PM, Mohan KR wrote:
Sorry, I'm looking at the stack trace, it appears the svn executable
is not
found.
How are you launching Hudson? Make sure the startup script that
launches
Hudson
has /usr/local/bin in its PATH.
it was already on the path -- but to be sure we add
Sorry, I'm looking at the stack trace, it appears the svn executable is not
found.
How are you launching Hudson? Make sure the startup script that launches
Hudson
has /usr/local/bin in its PATH.
Thanks,
mohan kr
-Original Message-
From: Lachlan Deck [mailto:lachlan.d...@gmail.com]
Sent:
On 16/07/2009, at 12:21 PM, Mohan KR wrote:
I don't have access to the project right now. I remember it is the
incompatibility with the
svn versions.
IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the
sources
the metadata is
1.5 compatible.
Actually we just checked and it's
you need to downgrade to 1.5.x to match hudsons version.
I just installed 1.5.x client on the Hudson box...you basically have to
match the Hudson internal svn version.
Thanks,
mohan kr
-Original Message-
From: Lachlan Deck [mailto:lachlan.d...@gmail.com]
Sent: Wednesday, July 15, 2009 9
On 16/07/2009, at 12:21 PM, Mohan KR wrote:
I don't have access to the project right now. I remember it is the
incompatibility with the
svn versions.
IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the
sources
the metadata is
1.5 compatible. So if your /usr/local/svn is 1.4 th
I don't have access to the project right now. I remember it is the
incompatibility with the
svn versions.
IIRC Hudson built-in (svn kit) uses 1.5, so when it checks out the sources
the metadata is
1.5 compatible. So if your /usr/local/svn is 1.4 then you will get the
error.
Thanks,
mohan kr
--
I have a package in which I want to include a shaded jar in an
assembly. What phases would folks recommend for shade and assembly?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users
Hi there,
We've set up hudson on our build server but are invariably finding
that it fails to find the svn executable when building (see below
stack trace).
We've defined in hudson the environment variable 'svn' as /usr/local/
bin/svn. However this doesn't seem to be working (or not always
Mine now looks like the following, and the last three excludes are
ineffectual in excluding.
lib
false
compile
org.springframework:*
com.basistech.rlpj:rlp-bl-lucene2.4
com.basistech.rlpj:rlp-common
com.basistech.rlpj:dictionaries
I never attached the workaround to the JIRA. It is MSITE-409. I'm
trying to get organized to try to fix it. However, the whole idea of a
'parent' link needs thought.
On Wed, Jul 15, 2009 at 2:54 PM, David C. Hicks wrote:
> Benson Margulies wrote:
>> I've filed a JIRA on this and also posted a work
Twice I've tried to build a small maven persistence app in netbeans 6.7.
Each time maven takes over and starts downloading pom files at a
ridiculously slow rate (i.e. 2k file in 5 minutes). It takes an hour and 43
minutes to download all the pom files. I have a fast connection. If the
other end
Benson Margulies wrote:
> I've filed a JIRA on this and also posted a workaround, you have to
> set up the URL for each project yourself. If you can't find my posted
> workaround I can post it again.
>
Benson, can you give us a JIRA number? I didn't find anything that
appeared to be the right o
Thanks for the workaround, Benson. I was able to get it to work in my
little test project. Now, I'm going after the big project.
Benson Margulies wrote:
> yes
>
> On Wed, Jul 15, 2009 at 2:50 PM, jaybytez wrote:
>
>> Is this the post:
>> http://n2.nabble.com/Site-generation-tutorials--td32333
Hi guys,
One of the fellows working on my project is suddenly having a problem
with one module. We've narrowed down the problem, but I have no idea
why it's happening. One of the resources in the "test/resources" tree
gets filtered with the ${project.build.directory}. In his case, he gets
a lot
This is an excerpt from my assembly.xml. It uses the Maven style
descriptors for inclusion. Versions are assumed to be those referenced
by the module (or in dependency management).
com.allureglobal:salient-war
com.allureglobal:salient-da
This page:
http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html
talks about group:artifact:classifier:version
but all the examples I can find seem to be just filtering filenames.
Are both formats supposed to work?
Thanks for the workaround, Benson. I was able to get it to work in my
little test project. Now, I'm going after the big project.
Benson Margulies wrote:
> yes
>
> On Wed, Jul 15, 2009 at 2:50 PM, jaybytez wrote:
>
>> Is this the post:
>> http://n2.nabble.com/Site-generation-tutorials--td32333
yes
On Wed, Jul 15, 2009 at 2:50 PM, jaybytez wrote:
>
> Is this the post:
> http://n2.nabble.com/Site-generation-tutorials--td327.html#a3239539
>
>
> Benson Margulies wrote:
>>
>> I've filed a JIRA on this and also posted a workaround, you have to
>> set up the URL for each project yourself.
Is this the post:
http://n2.nabble.com/Site-generation-tutorials--td327.html#a3239539
Benson Margulies wrote:
>
> I've filed a JIRA on this and also posted a workaround, you have to
> set up the URL for each project yourself. If you can't find my posted
> workaround I can post it again.
>
I've filed a JIRA on this and also posted a workaround, you have to
set up the URL for each project yourself. If you can't find my posted
workaround I can post it again.
On Wed, Jul 15, 2009 at 11:58 AM, jaybytez wrote:
>
> Okay...so I verified that each one of the sub projects has a site.xml with
I was using 2.0-beta-7 until yesterday. I changed to 2.1.
At the time, I only had a single site.xml at the parent level. It
included the tag. Assuming that all of the
tags are inherited, I would have thought this would work. I've also
tried it with site.xml in each module with equivalent tag
2009/7/15 Martin Gainty :
>
> someone from struts put in a hard version tag of 1.2 for building xwork 2.1.2
> (instead of the more recent shade-plugin-1.2.1)
>
Make sure you file a JIRA with xwork.
-Wes
--
Wes Wannemacher
Author - Struts 2 In Practice
Includes coverage of Struts 2.1, Spring, JP
I didn't see junit 3 in the dependency tree. I'm just using junit 4.
javabrett wrote:
>
> I've not dealt with this before so take this advice with a grain of
> salt, but here's something to try: Run mvn dependency:tree to see if
> another dependency elsewhere is relying on junit 3.x - maybe
The schema annotation says the following:
A reference to a pre-defined menu,
such as a reports, modules or
parentProject.
So it says a value of parentProject as opposed to parent.
--
View this message in context:
http://www.nabble.com/site.xml-for-parent-child-site-which-are-siblings-tp244892
someone from struts put in a hard version tag of 1.2 for building xwork 2.1.2
(instead of the more recent shade-plugin-1.2.1)
maven-shade-plugin
1.2
package
shade
xwork
junit:junit
commons-logging:commons-logging
opensymphony:ognl
org.springframework:spring-core
org.springframework:spring
http://maven.apache.org/plugins/maven-shade-plugin/source-repository.html
-Wes
2009/7/15 Martin Gainty :
>
> desperately trying to locate maven-shade 1.2
> i see maven-shade 1.0?
> i also maven-shade 1.2.2-SNAPSHOT?
>
> i'll take the source and build here if someone knows maven-shade-plugin
> so
I could achieve this by configuring the ear plugin like this:
org.apache.maven.plugins
maven-ear-plugin
war
E:\Programs\JBoss510\server\default\deploy\ejb3Test2.ear
desperately trying to locate maven-shade 1.2
i see maven-shade 1.0?
i also maven-shade 1.2.2-SNAPSHOT?
i'll take the source and build here if someone knows maven-shade-plugin source
location
thanks
Martin Gainty
__
Jogi és Bizalmassági kinyilatkoztat
Okay...so I verified that each one of the sub projects has a site.xml with a
and I verified that I am running site-plugin 2.0-beta-7
and my sub projects still don't produce a link based on .
I did not change the skin yet, but that should just be based on the CSS
exposed...otherwise that shouldn'
You might try adding an element to each of the settings to make
them distinct.
From http://maven.apache.org/settings.html#Proxies:
"id - The unique identifier for this proxy. This is used to
differentiate between proxy elements."
Joe Hindsley
Koerner, Ron wrote:
Hi list,
I use several r
Tim O'Brien wrote:
>
> Alright, time to update this example to use a gov't feed from the US NWS.
>
> Thanks for letting me know.
>
u are welcome~~
that's my pleasure =P
--
View this message in context:
http://www.nabble.com/exec%3Ajava-problem-tp24491018p24499961.html
Sent from the Maven -
On Wed, Jul 15, 2009 at 1:42 AM, ykyuen wrote:
>
> it works in windows now.
> the problem is previously, i created the maven project directly in eclipse
> by the m2eclipse plugin and the project is located in the workspace.
>
> then i try to create the project in the maven repository by the mvn
> a
Hello all
I am facing one problem.
I am using maven for building the project and running Junit test cases,
it also includes hibernate.
In this process hibernate creates lot of INFO log statements, which is
printed on console. I want to skip all the verbose log generated by
hibernate and log
Hello all
I am facing one problem.
I am using maven for building the project and running Junit test cases, it
also includes hibernate.
In this process hibernate creates lot of INFO log statements, which is
printed on console. I want to skip all the verbose log generated by
hibernate and log only
PMD 4.2.2http://maven.apache.org/plugins/maven-pmd-plugin/dependencies.html
Cheers,
Arnaud
# Arnaud Héritier
# Software Factory Manager
# eXo Platform
# http://www.exoplatform.com
# http://blog.aheritier.net
On Wed, Jul 15, 2009 at 3:42 PM, javadevd...@googlemail.com <
javadevd...@googlemail.c
Hello!
Does anybody know which PMD Version is included in the actual Maven-PMD plugin ?
I cant find it on the website..
thanks...
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: user
Hello,
It does not work like this. You should better use the release plugin
http://maven.apache.org/plugins/maven-release-plugin/ , It changes the
version in all projects tree and much ... ^^
Regards,
Gabriel Euzet
2009/7/15 ChipSchoch
>
> I am new to Maven and am converting a fairly large gro
I am new to Maven and am converting a fairly large group of related projects
to Maven2 build. There are about 15 projects that share the same parent
pom. In each project pom there is a parent.version tag. Is there a way to
use a property in this so when I move to another version I only have to
Hi
When you define a profile and need to exclude some resource files and you
have a multi-module application it is very hard and untidy you define that
profile in each module.
If we were able to define that profile in parent pom.xml it was really nice
but the problem is currently when you declar
I have been using menu ref, even as recently as two days ago in one of the
multi-module
project.
Which version of site-plugin are you using? I'm using 2.0-beta-7. Do all the
sibling modules
have a site descriptor, with menu ref="parent"?
The breadcrumbs could be a problem in the default skin. I d
http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site
jaybytez wrote:
> I have the following structure for my app:
> avitek
> -avitekApp (EAR)
> - pom.xml
> -avitekParent
> - src/site/site.xml
> - pom.xml
> -av
On Wed, Jul 15, 2009 at 12:17 PM, Dirk Olmes wrote:
> Hi,
>
> I'm trying to nail down some compiler settings for a project. Those are
> stored in .settings/org.eclipse.jdt.core.prefs, e.g.
>
> org.eclipse.jdt.core.compiler.problem.autoboxing=warning
>
> A quick look in the m-e-p's source makes me t
44 matches
Mail list logo
