-Original Message-
From: Jason Chaffee [mailto:[EMAIL PROTECTED]
Sent: Sunday, April 01, 2007 1:06 PM
To: Maven Users List
Subject: maven-2.0.6 throws NPE in surefire
This works fine in maven-2.0.5.
I have the following surefire configuration:
org.apache.maven.plugi
I've whipped up a patch that implements this pair and muxing here:
http://jira.codehaus.org/browse/SUREFIRE-315
Can someone please have a look at this?
Thanks,
--jason
On Apr 1, 2007, at 5:13 PM, Jason Dillon wrote:
I'm starting to think that surefire-booter needs a
ForkingStreamConsu
It'd be better somewhere under http://people.apache.org/repo/
On 4/1/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Sounds good to me.
Does the stage-plugin delete the staging repo after successfully
copying it?
- Brett
On 02/04/2007, at 3:01 AM, Jason van Zyl wrote:
> Hi,
>
> I wanted to setup
I'm starting to think that surefire-booter needs a
ForkingStreamConsumerPair, which has getOut(), getErr() that can
return StreamConsumer for the proper stream, sharing that foundTest
flag, and PrintWriter ref and prefixing the output based on if its
out or err output.
--jason
On Apr 1,
I've figured out what is broken... the problem is that
ForkingStreamConsumer.consumeLine(String) is calling
"outputConsumer.consumeOutputLine( line );" before
outputConsumer.testSetStarting() can be invoked, which causes the
FileOutputConsumerProxy.consumeOutputLine() to throw an ISE (which
What was the final verdict on the velocity processing?
I can see this doesn't break a lot now because it's only properties,
but I know the next thing someone is going to ask for is to filter $
{project.*} which will break a bunch of docs. I'd still prefer the
user make a conscious decision t
I couldn't build a correct site out of the box with these changes,
due to:
- using the site plugin latest release (which is the default), I get $
{currentVersion} and other stuff showing up as text
- I tried to build the site plugin snapshot, but it doesn't compile
due to out of date doxia s
Sounds good to me.
Does the stage-plugin delete the staging repo after successfully
copying it?
- Brett
On 02/04/2007, at 3:01 AM, Jason van Zyl wrote:
Hi,
I wanted to setup a common base directory for staging releases so
that each person doesn't have to change their setting each time
On Apr 1, 2007, at 2:38 PM, David J. M. Karlsen wrote:
Jason Dillon skrev:
Whats the easiest way to add an extra directory to the classpath
which surefire will use when running tests?
http://jira.codehaus.org/browse/SUREFIRE-180
Also - you could try defining system scoped dependencies - or
d
Jason Dillon skrev:
Whats the easiest way to add an extra directory to the classpath which
surefire will use when running tests?
http://jira.codehaus.org/browse/SUREFIRE-180
Also - you could try defining system scoped dependencies - or define
them as testResource's
-
Whats the easiest way to add an extra directory to the classpath
which surefire will use when running tests?
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
As promised I'll get these out for release this week. I did find a
problem with new container components (doxia, i18n) running in the
older container so I have to fix that first later today and then I
will do the Doxia release process and then the site plugin process. I
know there ar
Hi,
The staging repository is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
tasks-2.0.6/
The uber jar that people will want to try is here:
http://people.apache.org/~jvanzyl/staging-repository/maven-ant-
tasks-2.0.6/org/apache/maven/maven-ant-tasks/2.0.6/
Road map:
On 1 Apr 07, at 12:14 PM 1 Apr 07, Gregory Kick wrote:
Thanks for the release. Just thought that I'd point out that the main
maven.apache.org page still says 2.0.5.
Fixed, thanks.
On 4/1/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks!
On 01/04/2007, at 11:25 PM, Jason van Zyl wrote:
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 1 Apr 07, at 6:49 AM 1 Apr 07, Milos Kleint wrote:
>>
>
> exactly this is a showstopper for me in the current archetype when I
> attempted to create an archetype for netbeans module development. I
> need to place Bundle.properties and layer
Hi,
I wanted to setup a common base directory for staging releases so
that each person doesn't have to change their setting each time they
stage, or use a -D parameter. I would just like to have a commons
base directory and then use information about the project to
construct the staging r
Thanks for the release. Just thought that I'd point out that the main
maven.apache.org page still says 2.0.5.
On 4/1/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Thanks!
On 01/04/2007, at 11:25 PM, Jason van Zyl wrote:
>
> On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
>
>>
>> On 01/04/
On 1 Apr 07, at 10:17 AM 1 Apr 07, Brett Porter wrote:
On 02/04/2007, at 12:07 AM, Brett Porter wrote:
On 01/04/2007, at 11:55 PM, Jason van Zyl wrote:
On 1 Apr 07, at 9:41 AM 1 Apr 07, Brett Porter wrote:
I still find the versioning confusing, even if the artifact ID
has changed. This
On 1 Apr 07, at 10:07 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:55 PM, Jason van Zyl wrote:
On 1 Apr 07, at 9:41 AM 1 Apr 07, Brett Porter wrote:
I still find the versioning confusing, even if the artifact ID
has changed. This seems like it should be 2.1 to me
2.1 or 2.0.6?
On 02/04/2007, at 12:07 AM, Brett Porter wrote:
On 01/04/2007, at 11:55 PM, Jason van Zyl wrote:
On 1 Apr 07, at 9:41 AM 1 Apr 07, Brett Porter wrote:
I still find the versioning confusing, even if the artifact ID
has changed. This seems like it should be 2.1 to me
2.1 or 2.0.6? These a
On 01/04/2007, at 11:55 PM, Jason van Zyl wrote:
On 1 Apr 07, at 9:41 AM 1 Apr 07, Brett Porter wrote:
I still find the versioning confusing, even if the artifact ID has
changed. This seems like it should be 2.1 to me
2.1 or 2.0.6? These are matched against 2.0.6. Is the confusion not
ma
On 1 Apr 07, at 9:41 AM 1 Apr 07, Brett Porter wrote:
I still find the versioning confusing, even if the artifact ID has
changed. This seems like it should be 2.1 to me
2.1 or 2.0.6? These are matched against 2.0.6. Is the confusion not
matching the version against the base release of Mave
I will test this once more today with the Ant Tasks, then I'll write
it up and put the plugin up for a 1.0-alpha-1. It's really a stopgap
until we have a proper solution but will work for any of our releases
in the meantime.
Jason.
On 1 Apr 07, at 9:21 AM 1 Apr 07, Jason van Zyl wrote:
H
I still find the versioning confusing, even if the artifact ID has
changed. This seems like it should be 2.1 to me (with the features
added in those patches) if it is going down the separate version path.
As for inclusions, I couldn't find the issue, though was sure there
was one, to make i
Hi,
I've synced up the Ant Tasks with the 2.0.6 release and picked a few
issues that people have provided patches for:
http://jira.codehaus.org/secure/IssueNavigator.jspa?
reset=true&&pid=11533&resolution=-1&fixfor=13337&sorter/
field=priority&sorter/order=DESC
The rest of the issues are
Thanks!
On 01/04/2007, at 11:25 PM, Jason van Zyl wrote:
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like p
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like previous releases?
Forgot to mention I updated that and de
On 1 Apr 07, at 9:04 AM 1 Apr 07, Brett Porter wrote:
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like previous releases?
I added a pointer to the roadmap, I don
Hi,
Yesterday I whipped off a staging repository copier and it focuses on
pulling from any source, but only deploys using scp. I did this
because it's the only method we have for reliably getting a release
to a server and being able to recover if something goes wrong.
Ideally this would b
use
svn co https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.4
and fix your smtp server ;)
Peter Anning wrote:
Spam detection software, running on the system "fire.homenet.neonics.com", has
identified this incoming email as possible spam. The original message
has been attach
On 01/04/2007, at 11:00 PM, Jason van Zyl wrote:
You can find the release notes here:
http://maven.apache.org/release-notes.html
Should this include the full change log like previous releases?
Thanks,
Brett
-
To unsubscrib
On 4/1/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5 should be pain free. We corrected a major flaw in
the artifact resolution mechanism and we can
The Apache Maven team would like to announce the availability of
Maven 2.0.6. We have closed out 22 issues for this release and the
upgrade from 2.0.5 should be pain free. We corrected a major flaw in
the artifact resolution mechanism and we cannot find any problems but
information about th
On 1 Apr 07, at 6:49 AM 1 Apr 07, Milos Kleint wrote:
exactly this is a showstopper for me in the current archetype when I
attempted to create an archetype for netbeans module development. I
need to place Bundle.properties and layer.xml file in resources into
the proper package.
That's fi
Hi,
I didn't expected so many answers :)
for archetype, there is two process:
- generation of a project from an archetype
- creation of an archetype from a project
The generation reads the descriptor and files in jar to
generate the project's files. The required properties
are used as extra con
On 3/31/07, Heinrich Nirschl <[EMAIL PROTECTED]> wrote:
On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> On 31 Mar 07, at 12:08 PM 31 Mar 07, Heinrich Nirschl wrote:
>
> > On 3/31/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> >>
> >> On 31 Mar 07, at 10:07 AM 31 Mar 07, Raphaël Piéroni w
36 matches
Mail list logo
