I can't seem to access either of these URLs for the last two days.
Should I be using different URLs?
http://search.maven.org/
or
http://repo2.maven.org/maven2/
Jason
Wijbenga wrote:
On 3 August 2011 18:08, Jason Chaffee jchaf...@ebates.com wrote:
I can't seem to access either of these URLs for the last two days.
Should I be using different URLs?
http://search.maven.org/
or
http://repo2.maven.org/maven2/
Both work fine for me.
Works here too - what IPs
Sounds like something WealthFront would be doing. :)
-Original Message-
From: epabst [mailto:epa...@gmail.com]
Sent: Wed 3/2/2011 7:25 AM
To: users@maven.apache.org
Subject: RE: Continuous Delivery and Maven
I've put a lot of thought into this because I'm working on designing
I am mobile so not sure if it is still supporrted, bur the war plugin
used to have a deploy goal that allowed you to deploy the war to s
running container.
Jason
On Mar 1, 2011, at 8:19 PM, Wayne Fay wayne...@gmail.com wrote:
Is there some tool or plugin to deploy/undeploy a newly built
Jason, if you do that can you post the link in this list too, please? I would
like to read it and I very seldom go check blogs, but I check my email daily.
:)
-Original Message-
From: Jason van Zyl [mailto:ja...@maven.org]
Sent: Sun 10/24/2010 6:03 AM
To: Maven Users List
Subject:
I agree with how things seem to run differently on cmd-line, vs. eclipse, vs.
Hudson. I can be extremely frustrating.
However, maven does take a convention over configuration approach to things
for the most part. Many times the problems people encounter are not following
the convention and
, Jason Chaffee wrote:
I should add that the version on all of these is 2.2.1
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Sun 10/10/2010 9:54 PM
To: Maven Users List; Maven Users List
Subject: RE: 3.0 Arftifact changes
I have these dependencies in my
-repository-metadata:jar:2.2.1
[DEBUG] Excluded: org.apache.maven:maven-artifact:jar:2.2.1
-Original Message-
From: Brett Porter on behalf of Brett Porter
Sent: Mon 10/11/2010 12:44 AM
To: Maven Users List
Subject: Re: 3.0 Arftifact changes
On 11/10/2010, at 5:42 PM, Jason Chaffee wrote
the resolver, then read
the metadata file through the artifact APIs to get the values rather
than hooking into the transformation.
Also, is this something that could be covered by the
org.codehaus.mojo:versions-maven-plugin ?
On 11/10/2010, at 7:22 PM, Jason Chaffee wrote:
Looks the maven dependencies
Nowhere. Searched my entire search tree. It cannot be found in any file.
-Original Message-
From: Niall Pemberton [mailto:niall.pember...@gmail.com]
Sent: Sat 10/9/2010 5:35 PM
To: Maven Users List
Subject: Re: ${version} in 3.0
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee jchaf
:
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee jchaf...@ebates.com wrote:
I am getting this warning for every module, yet I am not using this variable
any of the poms. Some poms do have ${project.version} but some of them
don't have any variable expressions at all and it is still outputting
I do have properties like this though:
spring.version
that I then use ${spring.version}
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Sun 10/10/2010 2:12 PM
To: Maven Users List; Maven Users List
Subject: RE: ${version} in 3.0
checked every file. It does
List
Subject: Re: ${version} in 3.0
It sounds like the warning in Maven needs to be updated to show the location.
Did you check your local repository as well?
On 11/10/2010, at 8:15 AM, Jason Chaffee wrote:
I do have properties like this though:
spring.version
that I then use
I have a custom plugin that is using the following classes from maven 2.x.
import org.apache.maven.artifact.Artifact;
import org.apache.maven.artifact.repository.ArtifactRepository;
import org.apache.maven.artifact.repository.DefaultArtifactRepository;
import
: Sun 10/10/2010 6:40 PM
To: Maven Users List
Subject: Re: 3.0 Arftifact changes
I assume you mean does not work. These APIs should continue to work without
modification, as it's commonly used in other plugins.
What's the problem you're seeing?
- Brett
On 11/10/2010, at 11:35 AM, Jason Chaffee
can see why it would have run in 2.0, but not sure how it ever compiled :)
- Brett
On 11/10/2010, at 12:56 PM, Jason Chaffee wrote:
Yes, I meant does not work.
Here are the errors:
There are several Error messages:
[ERROR] Failed to execute goal
com.ebates.maven.plugins:maven-version
I should add that the version on all of these is 2.2.1
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Sun 10/10/2010 9:54 PM
To: Maven Users List; Maven Users List
Subject: RE: 3.0 Arftifact changes
I have these dependencies in my pom:
dependency
not be
taking kindly to the _
http://maven.apache.org/enforcer/enforcer-rules/requireJavaVersion.html
On Oct 8, 2010, at 6:38 PM, Jason Chaffee wrote:
This is what I have:
properties
java.version1.6.0_20/java.version
/properties
rules
requireJavaVersion
version[${java.version
I am getting this warning for every module, yet I am not using this variable
any of the poms. Some poms do have ${project.version} but some of them don't
have any variable expressions at all and it is still outputting this warning.
Does this warning just get output regardless of what is the
Does maven-enforcer-plugin with maven 3.0? The same rules are working
correctly in 2.0.
I have the following error:
[INFO] --- maven-enforcer-plugin:1.0-beta-1:enforce (enforce-versions) @
cbsp ---
[WARNING] This rule is not compatible with the current version of Maven.
The rule is not
you the rule doesn't work in 3.x, that's the current
state. 3.x has similar functionality built in
Sent from my iPad
On Oct 8, 2010, at 4:33 PM, Jason Chaffee jchaf...@ebates.com wrote:
Does maven-enforcer-plugin with maven 3.0? The same rules are working
correctly in 2.0.
I have
the tag for the rule that is failing for you?
---
Nayan Hajratwala
http://agileshrugged.com
http://twitter.com/nhajratw
734.658.6032
On Oct 8, 2010, at 6:00 PM, Jason Chaffee wrote:
So is there documentation on how I can configure that rule in 3.0? I
looked around the site, couldn't find anything
Is there a way to use the path to a jar in the local respository using
variables in the pom?
I know I can use the dependency plugin to copy the jar to my target
directory, but I would prefer to just use the location in the repo. For
example,
plugin
I tried to upgrade to version 2.5 and I started to get the following
error all projects that we using the assembly to attach artifacts. It
works correctly on my jar, war and pom only projects though. Does
anyone have any idea why this happening?
[INFO]
Is there a way to turn off javadoc execution during release:perform? I
using -Dgoals=deploy, but javadoc execution is still happening.
I need to turn it off because it is causing the release to fail. I
don't have time to debug the javadoc failure on an internal dependency
that does not
it). Examples can be found in the Maven and ASF parent POM.
- Brett
On 11/09/2009, at 12:41 PM, Jason Chaffee wrote:
Is there a way to turn off javadoc execution during
release:perform? I
using -Dgoals=deploy, but javadoc execution is still happening.
I need to turn it off because
I am not able to exclude directories for some reason. I have several
directories that are identified with .temp and I have particular directory
config that I would like to exclude them as follows:
fileSet
directory${project.build.directory}/ux/directory
Is there a particular reason why pluginManagement does not work for reporting
plugins? I would like to manage reporting plugins just as much as any other
plugin.
I am curious if there is a design reason, or if this was a simply an oversight
that could possibly be changed in the future?
UmlGraph is in the central repo:
docletorg.umlgraph.doclet.UmlGraphDoc/doclet
docletArtifact
groupIdorg.umlgraph/groupId
artifactIddoclet/artifactId
version5.1/version
/docletArtifact
Jason
see http://repo2.maven.org/maven2/org/umlgraph/
Jason
From: Jason Chaffee [jason.chaf...@zilliontv.tv]
Sent: Thursday, July 09, 2009 12:45 AM
To: Maven Users List
Subject: RE: Using UmlGraphDoc with Maven
UmlGraph is in the central repo
I have not been able to download this release. It seems the artifact(s) are
not at the specified URL.
-Original Message-
From: John Casey [mailto:jdca...@apache.org]
Sent: Tuesday, June 30, 2009 3:21 PM
To: annou...@maven.apache.org; Maven Users List
Subject: [ANN] Maven 2.2.0
To: Maven Users List
Subject: RE: [ANN] Maven 2.2.0 Released
Works for me.
Sometimes it takes a bit for all mirrors to get synced.
Please try it again in a a few hours.
LieGrue,
strub
--- Jason Chaffee jason.chaf...@zilliontv.tv schrieb am Mi, 1.7.2009:
Von: Jason Chaffee jason.chaf
One way around the excludes hack is to adopt a different directory structure
for it tests and unit tests. For example
src/test -- unit tests
src/itest -- integration tests
Jason
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, May 26,
Maven Plugin 2.4.3-alpha-1 released.
but that looses source folder config in ide setup, and hacks with test-
compile
Sent from my [rhymes with myPod] ;-)
On 26 May 2009, at 20:22, Jason Chaffee jason.chaf...@zilliontv.tv
wrote:
One way around the excludes hack is to adopt a different
, Jason Chaffee jason.chaf...@zilliontv.tv
wrote:
Yes, it would basically force Maven to adopt it as a standard and it
would might mean even adding a itest-compile phase, etc.
Not sure if I prefer this idea over the current protocol, but I do
think the FailSafe plugin is very good
[mailto:stephen.alan.conno...@gmail.com]
Sent: Tuesday, May 26, 2009 2:14 PM
To: Maven Users List
Cc: Maven Developers List
Subject: Re: [ANN] Failsafe Maven Plugin 2.4.3-alpha-1 released.
2009/5/26 Jason Chaffee jason.chaf...@zilliontv.tv
Yep, I concur with you a 100%. I think the solutions
verify-tests and report-only would only be meaningful if
run-tests gets executed ahead of them.
Does this make any sense to others? Is it feasible with what Maven 2
currently provides?
Regards,
Stevo.
On Wed, May 27, 2009 at 12:25 AM, Jason Chaffee
jason.chaf...@zilliontv.tvwrote:
I really like
Is there a timeline for a release and there anywhere I can find documentation
on the new features/improvements/changes in said release?
regards,
Jason
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional
realized this as well.
kudos.
Now I am even more excited for this release. Any idea when it might happen?
Is there any chance to play around with a beta?
regards,
Jason
From: Jason Chaffee [jason.chaf...@zilliontv.tv]
Sent: Wednesday, February 04, 2009 7
I am having an issue on 2.0.9. Basicallly, I have a custom plugin that has
it's own packaging type and creates a file of it's own extension type. This
only happens if I run a reactor build. If run maven in that project, it works
correctly. For example,
packagingmy-bundle/packaging
will
I am having an issue on 2.0.9. Basicallly, I have a custom plugin that has
it's own packaging type and creates a file of it's own extension type. This
only happens if I run a reactor build. If run maven in that project, it works
correctly. For example,
packagingmy-bundle/packaging
will
I am having an issue on 2.0.9. Basicallly, I have a custom plugin that has
it's own packaging type and creates a file of it's own extension type. For
example,
packagingmy-bundle/packaging
will create artifactId-version.exe
However, with maven-2.0.9 it creates the the file correcting in the
BTW, this only happens with recursive builds. If only build that particular
project, then everything installs/deploys properly.
-Original Message-
From: Jason Chaffee [mailto:jason.chaf...@zilliontv.tv]
Sent: Friday, January 30, 2009 1:19 PM
To: users@maven.apache.org
Subject: Custom
I know we have used the NAR plugin, but it doesn't have native support
for cppunit with maven and it appears to be a dormant project. We were
looking into modifying the native plugin to change the test-compile and
test lifescylce bindings to bind to the native plugin itself so as to
allow it to
Any plans to have it also remove artifacts from a remote repository? I
know that sometimes we have have intermittent failures when doing a
deploy for a project with modules and sometimes we need to delete the
previous artifacts and start over again. This would be a nice a feature
to be able to
You can you -Dmaven.test.skip.exec=true or -DskipTests instead of
-Dmaven.test.skip=true and it will still be created.
-Original Message-
From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED]
Sent: Monday, April 14, 2008 4:14 AM
To: Maven Users List
Subject: Re: Packaging of test-jar
The
Gomez [mailto:[EMAIL PROTECTED]
Sent: Saturday, April 12, 2008 9:50 AM
To: archiva-users@maven.apache.org
Subject: Re: too many open files with 1.0.2
I see that also but it was releated to a problem with Tomcat 6.x and
libtcnative.
Is it your setting ?
2008/4/11, Jason Chaffee [EMAIL PROTECTED
With Archvia-1.0.2 running in tomcat, I am getting too many open files
errors at least twice a day, forcing a reboot of archiva to fix the
issue. When I run lsof, I see that the database files are open more
than once so I suspect a resource leak. Is anyone else seeing this?
correct the plugin group metadata).
- Brett
On 09/04/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
According to the documentation the metadata-updater will do the
following:
metadata-updater - Updates artifact metadata files depending on the
content of the repository.
I have been testing
-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 3:54 PM
To: archiva-users@maven.apache.org
Subject: Re: metadata -updater does not appear to be working!
On 09/04/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I will file it today. Is there any chance of getting
deleting files.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 08, 2008 4:34 PM
To: archiva-users@maven.apache.org
Subject: Re: metadata -updater does not appear to be working!
On 09/04/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
1) touching the old
According to the documentation the metadata-updater will do the
following:
metadata-updater - Updates artifact metadata files depending on the
content of the repository.
I have been testing this by deploying several artifacts to the
repository and getting a specific timestamp and build
Also, if the artifact is in the local cache and this failure happens,
shouldn't is simply log it and then return the cached artifact?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 03, 2008 6:29 AM
To: archiva-users@maven.apache.org
Subject: Re:
Brian,
Is there any documentation about the new locked down plugin in feature
in 2.0.9?
I would like to know how it works, how it impacts not having plugins
locked vs. having them locked down already in your pom and how it would
impact the enforcer plugin as well.
Thanks.
-Original
FYI, I have noticed something similar after Archiva is up for a while
and I thought it was related to my other consumer issues so I didn't
mention it. One possibility to consider is the difference of Archiva
being used as both a proxy and repository manager as opposed to just a
proxy.
Anyway, I
I came across OpenMake's meister over the weekend and wondered if anyone
on this list has any experience with or any comparison with Maven? I
was just curious what the maven community's impression/response would be
because they claim to have maven-like features, but they also claim to
go above
]
Sent: Thursday, March 20, 2008 5:28 PM
To: Maven Users List
Subject: Re: surefire and testng integration issues with surefire-2.4.2
On 20-Mar-08, at 3:39 PM, Jason Chaffee wrote:
Jason van Zyl,
First, let me apologize for the tone of my emails and to anyone I
offended.
I doubt you offended
I brought this up in the past the maven guys were adamant that they were
not able to get per test information to output on the console unless
testng changed. I felt all along that this was not correct and I
finally had a chance to look into it. Surefire could simply register a
listener to get
of classes
so if you have more than one, you can do that.
Good Luck,
Dana H. P'Simer
Dana.P'[EMAIL PROTECTED]
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 5:32 AM
To: Maven Developers List
Cc: Maven Users List
Subject: surefire and testng
, March 20, 2008 10:05 AM
To: Maven Developers List
Cc: Maven Users List; [EMAIL PROTECTED]
Subject: Re: surefire and testng integration issues with surefire-2.4.2
Jason Chaffee wrote:
I brought this up in the past the maven guys were adamant that they
were
not able to get per test information
Maybe our disconnect is about callbacks after the class vs. the method.
That could be where the misunderstanding is coming from.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 10:11 AM
To: [EMAIL PROTECTED]; Maven Developers List
Cc: Maven
We are listening. Can you make a patch for surefire?
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 12:57 PM
To: Maven Developers List; Maven Users List
Subject: RE: surefire and testng integration issues with surefire-2.4.2
Yeah, I have
if the behavior still works as expected.
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 10:18 AM
To: Maven Developers List
Cc: [EMAIL PROTECTED]; Maven Users List
Subject: Re: surefire and testng integration issues with surefire-2.4.2
Jason Chaffee wrote
some gains in the next releases.
As far as TestNG support goes, this is still new and I think the users
are in the minority, so I guess I'm not really surprised that it's not
perfect yet.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 1:17 PM
]
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 1:25 PM
To: Maven Developers List
Cc: [EMAIL PROTECTED]; Maven Users List
Subject: Re: surefire and testng integration issues with surefire-2.4.2
Jason Chaffee wrote:
Maybe our disconnect is about
Well said. I appreciate this kind of feedback.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 12:10 PM
To: Maven Users List
Subject: Re: surefire and testng integration issues with surefire-2.4.2
On 20-Mar-08, at 10:47 AM, Jason Chaffee
with venom.
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 12:10 PM
To: Maven Users List
Subject: Re: surefire and testng integration issues with surefire-2.4.2
On 20-Mar-08, at 10:47 AM, Jason Chaffee wrote:
I am simply glad that it got
points out there so I'd love to
have a list.
Thanks,
Brian
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 20, 2008 6:40 PM
To: Maven Users List
Subject: RE: surefire and testng integration issues with surefire-2.4.2
Jason van Zyl,
First, let me
?
Cheers,
Brett
On 14/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
Here is a snippet from the log file:
431177909 [pool-2-thread-1] ERROR
org.apache.maven.archiva.repository.scanner.RepositoryScanner:default
-
Consumer [repository-purge] had an error when processing file
Here is my archiva.xml, in case it provides any other info.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 19, 2008 9:33 PM
To: archiva-users@maven.apache.org
Subject: RE: archiva-1.0.2 eta?
I was using the metdata-updater at one time, but we
: archiva-1.0.2 eta?
On 20/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I just sent my archiva.xml, which should give you a complete picture.
Ok, so I will file a new issue, but removing *.xml from your artifacts
list temporarily will fix the exception problems you were having with
the latest code
to the list and it ran through the unit tests on the branch
just fine.
- Brett
On 14/03/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I am using the SNAPSHOT that Brett provided, and MRM-691 seems to be
fixed, but not MRM-632 as I am still seeing that for some artifacts.
-Original Message
The antrun-plugin has been a major pain in the butt for a couple of
years now and there are so many people wanting this fixed. Every time
someone asks about it, it falls on deaf ears, or so it seems.
This is one of the reasons when you go to conferences you always hear
well respected engineers
It appears that archiva consumers modify the repository and change
timestamps to GMT. The next time I try to deploy an artifact it starts
over at build number 1, even though the previous build number was 30.
I am not sure what I can do to resolve this either in Archvia or maven??
It appears that archiva consumers modify the repository and change
timestamps to GMT. The next time I try to deploy an artifact it starts
over at build number 1, even though the previous build number was 30.
I am not sure what I can do to resolve this either in Archvia or maven??
I recently made some changes to my poms migrated to use Archiva as my
proxy. I tried to do a deploy on a parent pom that was already on build
30. When it deployed, it reverted it back to build 1. I tried it a
couple of more times and everytime it created a build 1, but with a
different
maven-enforcer-plugin
you might have to build the latest from source to get all the documented
functionality as the current released one doesn't support everything on
the Web site.
-Original Message-
From: Ken Liu [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 28, 2008 3:06 PM
To:
/log4j:configuration
Brett Porter wrote:
On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I have not. Is that configured in the plexus.xml?
No, log4j.xml - but it seems like the problem is just too many
exception messages? Is that what is filling the log so fast?
- Brett
?
- Brett
On 27/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
I think it has something to do with the log file reaching 2 GB in
size.
I couldn't even restart it until I remove the log files.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26
I found it in apps/archiva/webapp/WEB-INF/classes
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 26, 2008 10:52 PM
To: [EMAIL PROTECTED]
Subject: RE: archiva-1.0.2 eta?
Yep, that is what causing it to manifest. However, I would like to
change
the fixes so far, or if more
investigation is needed.
Thanks,
Brett
On 25/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
Actually, I misspoke. I checked the logs again today and saw the NPE
during the database scanning. I am not sure what is going on because
I
didn't change any
in the bug tracking system that you feel
need attention?
Archiva 1.0.2 tasked bugs - http://urltea.com/2rqi
Archiva overall open (non-future) bugs - http://urltea.com/2rqj
- Joakim
Jason Chaffee wrote:
Is there an ETA on the 1.0.2 release? I would really like to get
I found the following FAQ about Q4E:
http://code.google.com/p/q4e/wiki/FAQ
Features
* running Maven goals from the IDE
* dependency managing using the Maven POM, with automatic download
of dependencies
* keeping Eclipse classpath synchronized with Maven POM
*
I am running the standalone archiva and I have about 4 managed
repositories (including a proxy repo), and about 6 or 7 remote
repositories. I create a single proxy connector to all of the remote
repositories and changed my settings.xml to be a mirrorOf *. Currently,
I only have my Continuous
. We have 5 repositories and
about 6 remote repositories and we too are using the standalone product
and nearly all consumers.
What platform are you running on?
Eric
On Fri, 2008-02-22 at 12:40 -0800, Jason Chaffee wrote:
I am running the standalone archiva and I have about 4 managed
no answers.
i eventually had to reinstall fresh to get around it but all works great
now.
FYI, we're on RHEL 4 update 4 as well.
Eric
On Fri, 2008-02-22 at 13:01 -0800, Jason Chaffee wrote:
I am running on RedHat Enterprise 4 update 4. It has crashed on m2 at
least 6 times in the last two weeks
of days
We use:
0 30 2 * * ? - daily at 2:30 am
0 30 * * * ? - every 30 mins
The default out of the box shouldn't be an issue I wouldn't think. How
large are your repos?
Ours:
344Mjasper
332Kplugins
203Mproxied
107Mreleases
239Msnapshots
On Fri, 2008-02-22 at 13:28 -0800, Jason
Hmmm, the bug says it is fixed in 2.4.1 and it still produces a single
suite file and single suite output to the console. I agree with you
Benjamin, I don't think Dan understood the problem and thus didn't
actually fix it. Instead, the fix was for the reporting.
-Original Message-
From:
I am pretty familiar with testng code, so I would like to look into this
further. Is it a correct statement to say that the output we are seeing
on the console is coming directly from testng?
-Original Message-
From: Dan Fabulich [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 12,
Surefire-2.3.1 used to output which test was running and it would create
an output file for each test. For example,
[INFO] [surefire:test]
[INFO] Surefire report directory:
/usr/local/hudson/workspace/common/common/management/target/surefire-rep
orts
)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker
.run(ThreadPoolExecutor.java:690)
at java.lang.Thread.run(Thread.java:595)
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Monday, February 11, 2008 12:57 PM
To: archiva-users@maven.apache.org
Subject: RE: repository purge isn't
(Thread.java:595)
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Sunday, February 10, 2008 11:33 PM
To: [EMAIL PROTECTED]
Subject: repository purge isn't working in 1.0.1
For some reason, the repository purge hasn't been working for me. I
configured the date to be 0
if it
isn't relevant so we can clear that up.
Also, if you could post the failed task that you think needs more info
and some context we can look at ways to troubleshoot and improve the
logging in the future.
- Brett
On 11/02/2008, Jason Chaffee [EMAIL PROTECTED] wrote:
For some reason, the repository
For some reason, the repository purge hasn't been working for me. I
configured the date to be 0 and the purge count to be 10, yet after
running for 3 days there are still some snapshots with over 50
artifacts. I did see the log said something about the a failed task for
repository-job:snapshots,
Never mind. I found it under /maven/enforcer.
-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Friday, January 25, 2008 11:44 AM
To: Maven Developers List
Cc: Maven Users List
Subject: where is the source for maven-enforcer-plugin in SVN?
It doesn't seem to live
It doesn't seem to live in maven/plugins/trunk and the latest build
1.0-alpha-3 doesn't have the all of the functionality documented on the
site. In particular, it does not support requiresPluginVersions which
I would like to use.
Is nexus going to be open source or is the expectation that support is
bought from sonatype?
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 21, 2007 3:10 PM
To: Maven Users List
Subject: Maven users interested in the future of Proximity
Use TestNG to run your tests in surefire and then you can use TestNG
groups. For example,
mvn test -Dgroups=smoke-test
-Original Message-
From: Michael McCallum [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 12, 2007 2:20 PM
To: Maven Users List
Subject: Re: Surefire support for
You can still write your tests in JUnit, TestNG will run JUnit tests.
-Original Message-
From: Brad from MA [mailto:[EMAIL PROTECTED]
Sent: Wednesday, September 12, 2007 6:20 PM
To: users@maven.apache.org
Subject: RE: Surefire support for 'smoke tests'
Alas, we're making heavy use of
I just started converting to Hudson as well. It is extremely well
written and it by far and away blows continuum out of the water, in
features, in functionality, and of course stability.
-Original Message-
From: Gregory Kick [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 08, 2007 9:51 PM
1 - 100 of 116 matches
Mail list logo
