Thanks,
this looks close to what I was looking for.
I will need custom rules though but it seems to be a good starting point.
Best regards
Gerhard
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:wayne...@gmail.com]
Gesendet: Donnerstag, 26. Juli 2012 15:49
An: Maven Users List
Betref
I've resolved the issue by setting the proxy in settings.xml file.
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-Repository-initial-setp-error-tp5714848p5715045.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
I just started using "maven-failsafe-plugin" and
"maven-surefire-report-plugin" so my apologies in advance...
For starters, I've configured maven-failsafe-plugin and
maven-surefire-report-plugin as such (respectively):
org.apache.maven.plugins
The *only* way to make surefire use threads is to set the
attribute to some legal value. Use mvn help:effective-pom to see if
this is set. I can see from your log output that this is not set, so
this is something happening in your code/libs.
I might suggest using -Dmaven.surefire.debug=true and a
> Maven version 3.0.1
> maven-surefire-plugin version 2.11
> I haven't set other than exclude and include optional parameters of
> surefire.
> JUnit 4.10
> So, I believe that surefire is using junit 4 provider.
> JRE version 1.6
> OS: Windows XP
Can you try Maven 3.0.4 and Surefire 2.12? Also perh
Hey Markus,
I happened to be working in a project that currently uses hamcrest-core 1.1
transitively via junit 4.10, we also use nexus. If I add an explicit
dependency for org.hamcrest:hamcrest-core:[1.3] to the pom I get the
requested 1.3 version as expected. I tested this on 2 machines: my Mac
d
On Fri, Jul 27, 2012 at 7:57 AM, Barrie Treloar wrote:
> On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wrote:
>>> Long story short, I tried to modify eclipse project generation so that
>>> in the .settings/org.eclipse.jdt.core.prefs instead of this:
>>> org.eclipse.jdt.core.compiler.compliance=1
On Fri, Jul 27, 2012 at 7:13 AM, Wayne Fay wrote:
>> Long story short, I tried to modify eclipse project generation so that
>> in the .settings/org.eclipse.jdt.core.prefs instead of this:
>> org.eclipse.jdt.core.compiler.compliance=1.5
>> I get this (look at the compliance):
>> org.eclipse
> Long story short, I tried to modify eclipse project generation so that
> in the .settings/org.eclipse.jdt.core.prefs instead of this:
> org.eclipse.jdt.core.compiler.compliance=1.5
> I get this (look at the compliance):
> org.eclipse.jdt.core.compiler.compliance=1.6
> but didn't find a wa
Hi,
I've tried to checkout Jenkins CI source code and generate an Eclipse project
for it (see instructions in [1]). Unfortunately generated Eclipse projects
seemed to contain errors, which I first reported as a Jenkins bug [2]. Further
investigation revealed that even though Jenkins is build wi
Dear group,
I would like to know whether the maven-surefire-plugin has been designed to
use multi threads automatically if possible during a test method execution?
(Please allow me to remind that I'm using default setting of
maven-surefire-plugin other than include and exclude optional parameters.
How does that explain the local behaviour? I remove everything (the complete
groupId folder) from my local repo and Nexus instance, trigger a build, and get
the same problem again: The file with version 1.3 is then found in Nexus and
local repo, but maven still says that 1.3 is not existing when
Even if I remove *all* hamcrest-core artifacts from my Nexus and local repo,
Maven 3.0.4 again pulls some artifacts, but does not use 1.3 when I say
[1.3]. But I want exactly 1.3. So what next to try? Can you give me an idea
how a test case should be made up to let you reproduce this?
> -Origi
> net.sf.mavenjython
> jython-compile-maven-plugin
You probably need to find someone else in the world who is using this
plugin and see if they can give you specific help with it. Possibly
even the author of the plugin.
BTW I searched Github and found zero hits for
"jython-compile-maven-plugin" w
> I am pretty new in Maven. Please bear with me.
>
> How would pom and assembly file would look like on parent project?
You may benefit from reading the freely available books at
http://maven.apache.org/articles.html
Wayne
-
To
I am pretty new in Maven. Please bear with me.
How would pom and assembly file would look like on parent project?
Thank you.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-dependency-and-war-file-tp5714894p5714957.html
Sent from the Maven - Users mailing list archive
> I am looking for a plugin that tests the pom-files of a project to adhere to
> certain standards.
> The reason behind is that I want/need to enforce certain rules About the
> project layout (like URLK set/not set, scm links present, ...) for all
> colleagues
> that work on the same set of artifa
idea: custom rules for m-enforcer-p?
Am 26.07.2012 15:32 schrieb "Dünnebeil Gerhard" <
gerhard.duenneb...@ait.ac.at>:
> Hello everybody,
>
> I am looking for a plugin that tests the pom-files of a project to adhere
> to certain standards.
> The reason behind is that I want/need to enforce certain
Hello everybody,
I am looking for a plugin that tests the pom-files of a project to adhere to
certain standards.
The reason behind is that I want/need to enforce certain rules About the
project layout (like URLK set/not set, scm links present, ...) for all
colleagues that work on the same set o
cool. it seems thats exactly what i need. I was a little bit surprised with the
SourceInclusionScanner, but i hope it will load all the source files.
1] in this part:
@Override
@SuppressWarnings("rawtypes")
public Set getTargetFiles(File targetDir, String source)
cool. it seems thats exactly what i need. I was a little bit surprised with the
SourceInclusionScanner, but i hope it will load all the source files.
1] in this part:
@Override
@SuppressWarnings("rawtypes")
public Set getTargetFiles(File targetDir, String source) {
21 matches
Mail list logo
