You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by sd...@apache.org on 2011/08/18 07:10:58 UTC
svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Author: sdeboy
Date: Thu Aug 18 05:10:58 2011
New Revision: 1159035
URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
Log:
Updating junit scope in pom.xml to runtime to get build to work with maven 3.0.3
Modified:
logging/log4j/trunk/pom.xml
Modified: logging/log4j/trunk/pom.xml
URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
==============================================================================
--- logging/log4j/trunk/pom.xml (original)
+++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
@@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>3.8.1</version>
- <scope>test</scope>
+ <scope>runtime</scope>
</dependency>
<dependency>
<groupId>sun.jdk</groupId>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Ralph Goers <ra...@dslextreme.com>.
On Aug 18, 2011, at 9:02 PM, Curt Arnold wrote:
>
> On Aug 18, 2011, at 11:35 AM, Christian Grobmeier wrote:
>
>> I think the main reason for antrun is to enhance the generated site
>> afterwards, and probably for publishing.
>> Most other stuff can be done with maven, so I would give my +1 to
>> reduce the Ant dependency to a minimum - again.
>>
>> Imho antrun should not do any tests
>>
>
> If I remember correctly, the reason antrun was used over the junit plugin, is that the log4j unit tests have side effects (typically leaving files around) and changing the order that tests are run can cause tests to fail. Not that way that it should be, but the way it was.\\
I had this problem in Log4j 2.0. The solution is
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-surefire-plugin</artifactId>
<configuration>
<forkMode>always</forkMode>
</configuration>
</plugin>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Curt Arnold <cu...@gmail.com>.
On Aug 18, 2011, at 11:35 AM, Christian Grobmeier wrote:
> I think the main reason for antrun is to enhance the generated site
> afterwards, and probably for publishing.
> Most other stuff can be done with maven, so I would give my +1 to
> reduce the Ant dependency to a minimum - again.
>
> Imho antrun should not do any tests
>
If I remember correctly, the reason antrun was used over the junit plugin, is that the log4j unit tests have side effects (typically leaving files around) and changing the order that tests are run can cause tests to fail. Not that way that it should be, but the way it was.
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
I think the main reason for antrun is to enhance the generated site
afterwards, and probably for publishing.
Most other stuff can be done with maven, so I would give my +1 to
reduce the Ant dependency to a minimum - again.
Imho antrun should not do any tests
On Thu, Aug 18, 2011 at 6:31 PM, Jacob Kjome <ho...@visi.com> wrote:
>
> This seems to be occurring in the Maven Antrun plugin. I know that Ant's
> JUnit task requires JUnit to be in Ant's classpath, which would make it a
> runtime library for Ant. That said, why is Antrun being used rather than
> directly running tests using Maven? If Antrun is truly needed, couldn't
> JUnit be provided directly as an Antrun runtime dependency rather than a
> runtime dependency of the project as a whole?
>
> Jake
>
> On Thu, 18 Aug 2011 09:26:14 -0700
> Scott Deboy <sc...@gmail.com> wrote:
>>
>> So I don't get an error on Windows, but my Mac does get the error..here it
>> is:
>>
>> [INFO] Scanning for projects...
>> mvn site[ERROR] The build could not read 1 project -> [Help 1]
>> [ERROR]
>> [ERROR] The project log4j:log4j:1.2.17-SNAPSHOT
>> (/Users/admin/work-local/log4j-trunk/log4j/pom.xml) has 1 error
>> [ERROR]
>>
>> 'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
>> for junit:junit:jar must be one of [compile, runtime, system] but is
>> 'test'.
>> @ line 321, column 20
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e
>> switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>
>> I'll look more closely into this.
>>
>> On Thu, Aug 18, 2011 at 7:36 AM, Christian Grobmeier
>> <gr...@gmail.com>wrote:
>>
>>> cool!
>>>
>>> On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com>
>>> wrote:
>>> > I reverted the change and was still able to build. I'm not sure why I
>>> had
>>> > that error.
>>> >
>>> > On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier <
>>> grobmeier@gmail.com>
>>> > wrote:
>>> >>
>>> >> weird.
>>> >>
>>> >> my suggestion is we leave it for now - but we must think about it
>>> >> shortly before the release. Because users will then need junit in
>>> >> their runtime which might annoy some of them :-)
>>> >>
>>> >> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
>>> >> wrote:
>>> >> > it failed to even build saying it must be one of build or
>>> >> > runtime. I
>>> >> > saw
>>> >> > other test scopes in the poms so I was confused myself. Maybe an
>>> >> > issue
>>> >> > with
>>> >> > my environment?
>>> >> >
>>> >> >
>>> >> >
>>> >> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <
>>> grobmeier@gmail.com>
>>> >> > wrote:
>>> >> >
>>> >> >> Not sure, but Junit should not be necessary for the runtime
>>> >> >> execution
>>> >> >> imho.
>>> >> >>
>>> >> >>
>>> >> >>
>>>
>>> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>>> >> >>
>>> >> >> I think it should be test only.
>>> >> >>
>>> >> >> I did not work without having it on runtime?
>>> >> >>
>>> >> >> runtime
>>> >> >> This scope indicates that the dependency is not required for
>>> >> >> compilation, but is for execution. It is in the runtime and test
>>> >> >> classpaths, but not the compile classpath.
>>> >> >> test
>>> >> >> This scope indicates that the dependency is not required for normal
>>> >> >> use of the application, and is only available for the test
>>> compilation
>>> >> >> and execution phases.
>>> >> >>
>>> >> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>>> >> >>>
>>> >> >>> Author: sdeboy
>>> >> >>> Date: Thu Aug 18 05:10:58 2011
>>> >> >>> New Revision: 1159035
>>> >> >>>
>>> >> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>>> >> >>> Log:
>>> >> >>> Updating junit scope in pom.xml to runtime to get build to work
>>> >> >>> with
>>> >> >>> maven 3.0.3
>>> >> >>>
>>> >> >>> Modified:
>>> >> >>> logging/log4j/trunk/pom.xml
>>> >> >>>
>>> >> >>> Modified: logging/log4j/trunk/pom.xml
>>> >> >>> URL:
>>> >> >>>
>>> >> >>>
>>>
>>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>>
>>> ==============================================================================
>>> >> >>> --- logging/log4j/trunk/pom.xml (original)
>>> >> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>>> >> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>>> >> >>> <groupId>junit</groupId>
>>> >> >>> <artifactId>junit</artifactId>
>>> >> >>> <version>3.8.1</version>
>>> >> >>> - <scope>test</scope>
>>> >> >>> + <scope>runtime</scope>
>>> >> >>> </dependency>
>>> >> >>> <dependency>
>>> >> >>> <groupId>sun.jdk</groupId>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> >> >>>
>>> ---------------------------------------------------------------------
>>> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> >> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >> >>>
>>> >> >>>
>>> >> >>
>>> >> >>
>>> >> >>
>>> >> >> --
>>> >> >> http://www.grobmeier.de
>>> >> >>
>>> >> >>
>>> >> >> ---------------------------------------------------------------------
>>> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> >> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >> >>
>>> >> >
>>> >> >
>>> >> > ---------------------------------------------------------------------
>>> >> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> >> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >> >
>>> >> >
>>> >>
>>> >>
>>> >>
>>> >> --
>>> >> http://www.grobmeier.de
>>> >>
>>> >> ---------------------------------------------------------------------
>>> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>> >>
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> http://www.grobmeier.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Jacob Kjome <ho...@visi.com>.
This seems to be occurring in the Maven Antrun plugin. I know that Ant's
JUnit task requires JUnit to be in Ant's classpath, which would make it a
runtime library for Ant. That said, why is Antrun being used rather than
directly running tests using Maven? If Antrun is truly needed, couldn't JUnit
be provided directly as an Antrun runtime dependency rather than a runtime
dependency of the project as a whole?
Jake
On Thu, 18 Aug 2011 09:26:14 -0700
Scott Deboy <sc...@gmail.com> wrote:
> So I don't get an error on Windows, but my Mac does get the error..here it
> is:
>
> [INFO] Scanning for projects...
> mvn site[ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project log4j:log4j:1.2.17-SNAPSHOT
> (/Users/admin/work-local/log4j-trunk/log4j/pom.xml) has 1 error
> [ERROR]
> 'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
> for junit:junit:jar must be one of [compile, runtime, system] but is 'test'.
> @ line 321, column 20
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> I'll look more closely into this.
>
> On Thu, Aug 18, 2011 at 7:36 AM, Christian Grobmeier
><gr...@gmail.com>wrote:
>
>> cool!
>>
>> On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com>
>> wrote:
>> > I reverted the change and was still able to build. I'm not sure why I
>> had
>> > that error.
>> >
>> > On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier <
>> grobmeier@gmail.com>
>> > wrote:
>> >>
>> >> weird.
>> >>
>> >> my suggestion is we leave it for now - but we must think about it
>> >> shortly before the release. Because users will then need junit in
>> >> their runtime which might annoy some of them :-)
>> >>
>> >> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
>> >> wrote:
>> >> > it failed to even build saying it must be one of build or runtime. I
>> >> > saw
>> >> > other test scopes in the poms so I was confused myself. Maybe an issue
>> >> > with
>> >> > my environment?
>> >> >
>> >> >
>> >> >
>> >> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <
>> grobmeier@gmail.com>
>> >> > wrote:
>> >> >
>> >> >> Not sure, but Junit should not be necessary for the runtime execution
>> >> >> imho.
>> >> >>
>> >> >>
>> >> >>
>> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>> >> >>
>> >> >> I think it should be test only.
>> >> >>
>> >> >> I did not work without having it on runtime?
>> >> >>
>> >> >> runtime
>> >> >> This scope indicates that the dependency is not required for
>> >> >> compilation, but is for execution. It is in the runtime and test
>> >> >> classpaths, but not the compile classpath.
>> >> >> test
>> >> >> This scope indicates that the dependency is not required for normal
>> >> >> use of the application, and is only available for the test
>> compilation
>> >> >> and execution phases.
>> >> >>
>> >> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>> >> >>>
>> >> >>> Author: sdeboy
>> >> >>> Date: Thu Aug 18 05:10:58 2011
>> >> >>> New Revision: 1159035
>> >> >>>
>> >> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>> >> >>> Log:
>> >> >>> Updating junit scope in pom.xml to runtime to get build to work with
>> >> >>> maven 3.0.3
>> >> >>>
>> >> >>> Modified:
>> >> >>> logging/log4j/trunk/pom.xml
>> >> >>>
>> >> >>> Modified: logging/log4j/trunk/pom.xml
>> >> >>> URL:
>> >> >>>
>> >> >>>
>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>> >> >>>
>> >> >>>
>> >> >>>
>> ==============================================================================
>> >> >>> --- logging/log4j/trunk/pom.xml (original)
>> >> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>> >> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>> >> >>> <groupId>junit</groupId>
>> >> >>> <artifactId>junit</artifactId>
>> >> >>> <version>3.8.1</version>
>> >> >>> - <scope>test</scope>
>> >> >>> + <scope>runtime</scope>
>> >> >>> </dependency>
>> >> >>> <dependency>
>> >> >>> <groupId>sun.jdk</groupId>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> ---------------------------------------------------------------------
>> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> http://www.grobmeier.de
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >>
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.grobmeier.de
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >>
>> >
>> >
>>
>>
>>
>> --
>> http://www.grobmeier.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
I use pretty the same
Apache Maven 3.0.3 (r1075438; 2011-02-28 18:31:09+0100)
Maven home: /usr/share/maven
Java version: 1.6.0_26, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: de_DE, platform encoding: MacRoman
OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac"
But I have seen only before a few hours that it is not companion
related. I will try to check it out and build it on my mac tomorrow
Maybe I can reproduce the problem
On Thu, Aug 18, 2011 at 6:42 PM, Scott Deboy <sc...@gmail.com> wrote:
> Here's the output of mvn --version
>
> Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
> Maven home: /usr/share/java/maven-3.0.3
> Java version: 1.6.0_26, vendor: Apple Inc.
> Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
> Default locale: en_US, platform encoding: MacRoman
> OS name: "mac os x", version: "10.7", arch: "x86_64", family: "mac"
>
>
>
> On Thu, Aug 18, 2011 at 9:31 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>>
>> Scott, which maven version do you use?
>>
>> I think this is a very weird one and it looks like it has something to
>> do with with antrun configuration used by site
>>
>> Did you see, there are two different Junit version used.
>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?view=markup
>> 3.8.1 and 3.8.2
>>
>> In addition I would recommend to take a look at the build.xml
>>
>>
>> On Thu, Aug 18, 2011 at 6:26 PM, Scott Deboy <sc...@gmail.com>
>> wrote:
>> > So I don't get an error on Windows, but my Mac does get the error..here
>> > it
>> > is:
>> >
>> > [INFO] Scanning for projects...
>> > mvn site[ERROR] The build could not read 1 project -> [Help 1]
>> > [ERROR]
>> > [ERROR] The project log4j:log4j:1.2.17-SNAPSHOT
>> > (/Users/admin/work-local/log4j-trunk/log4j/pom.xml) has 1 error
>> > [ERROR]
>> >
>> > 'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
>> > for junit:junit:jar must be one of [compile, runtime, system] but is
>> > 'test'.
>> > @ line 321, column 20
>> > [ERROR]
>> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> > -e
>> > switch.
>> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> >
>> > I'll look more closely into this.
>> >
>> > On Thu, Aug 18, 2011 at 7:36 AM, Christian Grobmeier
>> > <gr...@gmail.com>
>> > wrote:
>> >>
>> >> cool!
>> >>
>> >> On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com>
>> >> wrote:
>> >> > I reverted the change and was still able to build. I'm not sure why
>> >> > I
>> >> > had
>> >> > that error.
>> >> >
>> >> > On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier
>> >> > <gr...@gmail.com>
>> >> > wrote:
>> >> >>
>> >> >> weird.
>> >> >>
>> >> >> my suggestion is we leave it for now - but we must think about it
>> >> >> shortly before the release. Because users will then need junit in
>> >> >> their runtime which might annoy some of them :-)
>> >> >>
>> >> >> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
>> >> >> wrote:
>> >> >> > it failed to even build saying it must be one of build or runtime.
>> >> >> > I
>> >> >> > saw
>> >> >> > other test scopes in the poms so I was confused myself. Maybe an
>> >> >> > issue
>> >> >> > with
>> >> >> > my environment?
>> >> >> >
>> >> >> >
>> >> >> >
>> >> >> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier
>> >> >> > <gr...@gmail.com>
>> >> >> > wrote:
>> >> >> >
>> >> >> >> Not sure, but Junit should not be necessary for the runtime
>> >> >> >> execution
>> >> >> >> imho.
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>> >> >> >>
>> >> >> >> I think it should be test only.
>> >> >> >>
>> >> >> >> I did not work without having it on runtime?
>> >> >> >>
>> >> >> >> runtime
>> >> >> >> This scope indicates that the dependency is not required for
>> >> >> >> compilation, but is for execution. It is in the runtime and test
>> >> >> >> classpaths, but not the compile classpath.
>> >> >> >> test
>> >> >> >> This scope indicates that the dependency is not required for
>> >> >> >> normal
>> >> >> >> use of the application, and is only available for the test
>> >> >> >> compilation
>> >> >> >> and execution phases.
>> >> >> >>
>> >> >> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>> >> >> >>>
>> >> >> >>> Author: sdeboy
>> >> >> >>> Date: Thu Aug 18 05:10:58 2011
>> >> >> >>> New Revision: 1159035
>> >> >> >>>
>> >> >> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>> >> >> >>> Log:
>> >> >> >>> Updating junit scope in pom.xml to runtime to get build to work
>> >> >> >>> with
>> >> >> >>> maven 3.0.3
>> >> >> >>>
>> >> >> >>> Modified:
>> >> >> >>> logging/log4j/trunk/pom.xml
>> >> >> >>>
>> >> >> >>> Modified: logging/log4j/trunk/pom.xml
>> >> >> >>> URL:
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> ==============================================================================
>> >> >> >>> --- logging/log4j/trunk/pom.xml (original)
>> >> >> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>> >> >> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>> >> >> >>> <groupId>junit</groupId>
>> >> >> >>> <artifactId>junit</artifactId>
>> >> >> >>> <version>3.8.1</version>
>> >> >> >>> - <scope>test</scope>
>> >> >> >>> + <scope>runtime</scope>
>> >> >> >>> </dependency>
>> >> >> >>> <dependency>
>> >> >> >>> <groupId>sun.jdk</groupId>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>>
>> >> >> >>> ---------------------------------------------------------------------
>> >> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >> >>> For additional commands, e-mail:
>> >> >> >>> log4j-dev-help@logging.apache.org
>> >> >> >>>
>> >> >> >>>
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> --
>> >> >> >> http://www.grobmeier.de
>> >> >> >>
>> >> >> >>
>> >> >> >>
>> >> >> >> ---------------------------------------------------------------------
>> >> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >> >> For additional commands, e-mail:
>> >> >> >> log4j-dev-help@logging.apache.org
>> >> >> >>
>> >> >> >
>> >> >> >
>> >> >> > ---------------------------------------------------------------------
>> >> >> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> http://www.grobmeier.de
>> >> >>
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >>
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.grobmeier.de
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >>
>> >
>> >
>>
>>
>>
>> --
>> http://www.grobmeier.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Scott Deboy <sc...@gmail.com>.
Here's the output of mvn --version
Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
Maven home: /usr/share/java/maven-3.0.3
Java version: 1.6.0_26, vendor: Apple Inc.
Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home
Default locale: en_US, platform encoding: MacRoman
OS name: "mac os x", version: "10.7", arch: "x86_64", family: "mac"
On Thu, Aug 18, 2011 at 9:31 AM, Christian Grobmeier <gr...@gmail.com>wrote:
> Scott, which maven version do you use?
>
> I think this is a very weird one and it looks like it has something to
> do with with antrun configuration used by site
>
> Did you see, there are two different Junit version used.
> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?view=markup
> 3.8.1 and 3.8.2
>
> In addition I would recommend to take a look at the build.xml
>
>
> On Thu, Aug 18, 2011 at 6:26 PM, Scott Deboy <sc...@gmail.com>
> wrote:
> > So I don't get an error on Windows, but my Mac does get the error..here
> it
> > is:
> >
> > [INFO] Scanning for projects...
> > mvn site[ERROR] The build could not read 1 project -> [Help 1]
> > [ERROR]
> > [ERROR] The project log4j:log4j:1.2.17-SNAPSHOT
> > (/Users/admin/work-local/log4j-trunk/log4j/pom.xml) has 1 error
> > [ERROR]
> >
> 'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
> > for junit:junit:jar must be one of [compile, runtime, system] but is
> 'test'.
> > @ line 321, column 20
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> >
> > I'll look more closely into this.
> >
> > On Thu, Aug 18, 2011 at 7:36 AM, Christian Grobmeier <
> grobmeier@gmail.com>
> > wrote:
> >>
> >> cool!
> >>
> >> On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com>
> >> wrote:
> >> > I reverted the change and was still able to build. I'm not sure why I
> >> > had
> >> > that error.
> >> >
> >> > On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier
> >> > <gr...@gmail.com>
> >> > wrote:
> >> >>
> >> >> weird.
> >> >>
> >> >> my suggestion is we leave it for now - but we must think about it
> >> >> shortly before the release. Because users will then need junit in
> >> >> their runtime which might annoy some of them :-)
> >> >>
> >> >> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
> >> >> wrote:
> >> >> > it failed to even build saying it must be one of build or runtime.
> I
> >> >> > saw
> >> >> > other test scopes in the poms so I was confused myself. Maybe an
> >> >> > issue
> >> >> > with
> >> >> > my environment?
> >> >> >
> >> >> >
> >> >> >
> >> >> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier
> >> >> > <gr...@gmail.com>
> >> >> > wrote:
> >> >> >
> >> >> >> Not sure, but Junit should not be necessary for the runtime
> >> >> >> execution
> >> >> >> imho.
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> >> >> >>
> >> >> >> I think it should be test only.
> >> >> >>
> >> >> >> I did not work without having it on runtime?
> >> >> >>
> >> >> >> runtime
> >> >> >> This scope indicates that the dependency is not required for
> >> >> >> compilation, but is for execution. It is in the runtime and test
> >> >> >> classpaths, but not the compile classpath.
> >> >> >> test
> >> >> >> This scope indicates that the dependency is not required for
> normal
> >> >> >> use of the application, and is only available for the test
> >> >> >> compilation
> >> >> >> and execution phases.
> >> >> >>
> >> >> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
> >> >> >>>
> >> >> >>> Author: sdeboy
> >> >> >>> Date: Thu Aug 18 05:10:58 2011
> >> >> >>> New Revision: 1159035
> >> >> >>>
> >> >> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
> >> >> >>> Log:
> >> >> >>> Updating junit scope in pom.xml to runtime to get build to work
> >> >> >>> with
> >> >> >>> maven 3.0.3
> >> >> >>>
> >> >> >>> Modified:
> >> >> >>> logging/log4j/trunk/pom.xml
> >> >> >>>
> >> >> >>> Modified: logging/log4j/trunk/pom.xml
> >> >> >>> URL:
> >> >> >>>
> >> >> >>>
> >> >> >>>
> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> ==============================================================================
> >> >> >>> --- logging/log4j/trunk/pom.xml (original)
> >> >> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
> >> >> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
> >> >> >>> <groupId>junit</groupId>
> >> >> >>> <artifactId>junit</artifactId>
> >> >> >>> <version>3.8.1</version>
> >> >> >>> - <scope>test</scope>
> >> >> >>> + <scope>runtime</scope>
> >> >> >>> </dependency>
> >> >> >>> <dependency>
> >> >> >>> <groupId>sun.jdk</groupId>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> ---------------------------------------------------------------------
> >> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >> >>> For additional commands, e-mail:
> log4j-dev-help@logging.apache.org
> >> >> >>>
> >> >> >>>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> --
> >> >> >> http://www.grobmeier.de
> >> >> >>
> >> >> >>
> >> >> >>
> ---------------------------------------------------------------------
> >> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >> >> For additional commands, e-mail:
> log4j-dev-help@logging.apache.org
> >> >> >>
> >> >> >
> >> >> >
> ---------------------------------------------------------------------
> >> >> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> http://www.grobmeier.de
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >> >>
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> http://www.grobmeier.de
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>
> >
> >
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
Scott, which maven version do you use?
I think this is a very weird one and it looks like it has something to
do with with antrun configuration used by site
Did you see, there are two different Junit version used.
http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?view=markup
3.8.1 and 3.8.2
In addition I would recommend to take a look at the build.xml
On Thu, Aug 18, 2011 at 6:26 PM, Scott Deboy <sc...@gmail.com> wrote:
> So I don't get an error on Windows, but my Mac does get the error..here it
> is:
>
> [INFO] Scanning for projects...
> mvn site[ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project log4j:log4j:1.2.17-SNAPSHOT
> (/Users/admin/work-local/log4j-trunk/log4j/pom.xml) has 1 error
> [ERROR]
> 'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
> for junit:junit:jar must be one of [compile, runtime, system] but is 'test'.
> @ line 321, column 20
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>
> I'll look more closely into this.
>
> On Thu, Aug 18, 2011 at 7:36 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>>
>> cool!
>>
>> On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com>
>> wrote:
>> > I reverted the change and was still able to build. I'm not sure why I
>> > had
>> > that error.
>> >
>> > On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier
>> > <gr...@gmail.com>
>> > wrote:
>> >>
>> >> weird.
>> >>
>> >> my suggestion is we leave it for now - but we must think about it
>> >> shortly before the release. Because users will then need junit in
>> >> their runtime which might annoy some of them :-)
>> >>
>> >> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
>> >> wrote:
>> >> > it failed to even build saying it must be one of build or runtime. I
>> >> > saw
>> >> > other test scopes in the poms so I was confused myself. Maybe an
>> >> > issue
>> >> > with
>> >> > my environment?
>> >> >
>> >> >
>> >> >
>> >> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier
>> >> > <gr...@gmail.com>
>> >> > wrote:
>> >> >
>> >> >> Not sure, but Junit should not be necessary for the runtime
>> >> >> execution
>> >> >> imho.
>> >> >>
>> >> >>
>> >> >>
>> >> >> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>> >> >>
>> >> >> I think it should be test only.
>> >> >>
>> >> >> I did not work without having it on runtime?
>> >> >>
>> >> >> runtime
>> >> >> This scope indicates that the dependency is not required for
>> >> >> compilation, but is for execution. It is in the runtime and test
>> >> >> classpaths, but not the compile classpath.
>> >> >> test
>> >> >> This scope indicates that the dependency is not required for normal
>> >> >> use of the application, and is only available for the test
>> >> >> compilation
>> >> >> and execution phases.
>> >> >>
>> >> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>> >> >>>
>> >> >>> Author: sdeboy
>> >> >>> Date: Thu Aug 18 05:10:58 2011
>> >> >>> New Revision: 1159035
>> >> >>>
>> >> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>> >> >>> Log:
>> >> >>> Updating junit scope in pom.xml to runtime to get build to work
>> >> >>> with
>> >> >>> maven 3.0.3
>> >> >>>
>> >> >>> Modified:
>> >> >>> logging/log4j/trunk/pom.xml
>> >> >>>
>> >> >>> Modified: logging/log4j/trunk/pom.xml
>> >> >>> URL:
>> >> >>>
>> >> >>>
>> >> >>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> ==============================================================================
>> >> >>> --- logging/log4j/trunk/pom.xml (original)
>> >> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>> >> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>> >> >>> <groupId>junit</groupId>
>> >> >>> <artifactId>junit</artifactId>
>> >> >>> <version>3.8.1</version>
>> >> >>> - <scope>test</scope>
>> >> >>> + <scope>runtime</scope>
>> >> >>> </dependency>
>> >> >>> <dependency>
>> >> >>> <groupId>sun.jdk</groupId>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> ---------------------------------------------------------------------
>> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> http://www.grobmeier.de
>> >> >>
>> >> >>
>> >> >> ---------------------------------------------------------------------
>> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >>
>> >> >
>> >> > ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.grobmeier.de
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >>
>> >
>> >
>>
>>
>>
>> --
>> http://www.grobmeier.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Scott Deboy <sc...@gmail.com>.
So I don't get an error on Windows, but my Mac does get the error..here it
is:
[INFO] Scanning for projects...
mvn site[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project log4j:log4j:1.2.17-SNAPSHOT
(/Users/admin/work-local/log4j-trunk/log4j/pom.xml) has 1 error
[ERROR]
'build.plugins.plugin[org.apache.maven.plugins:maven-antrun-plugin].dependencies.dependency.scope'
for junit:junit:jar must be one of [compile, runtime, system] but is 'test'.
@ line 321, column 20
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
I'll look more closely into this.
On Thu, Aug 18, 2011 at 7:36 AM, Christian Grobmeier <gr...@gmail.com>wrote:
> cool!
>
> On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com>
> wrote:
> > I reverted the change and was still able to build. I'm not sure why I
> had
> > that error.
> >
> > On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier <
> grobmeier@gmail.com>
> > wrote:
> >>
> >> weird.
> >>
> >> my suggestion is we leave it for now - but we must think about it
> >> shortly before the release. Because users will then need junit in
> >> their runtime which might annoy some of them :-)
> >>
> >> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
> >> wrote:
> >> > it failed to even build saying it must be one of build or runtime. I
> >> > saw
> >> > other test scopes in the poms so I was confused myself. Maybe an issue
> >> > with
> >> > my environment?
> >> >
> >> >
> >> >
> >> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <
> grobmeier@gmail.com>
> >> > wrote:
> >> >
> >> >> Not sure, but Junit should not be necessary for the runtime execution
> >> >> imho.
> >> >>
> >> >>
> >> >>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> >> >>
> >> >> I think it should be test only.
> >> >>
> >> >> I did not work without having it on runtime?
> >> >>
> >> >> runtime
> >> >> This scope indicates that the dependency is not required for
> >> >> compilation, but is for execution. It is in the runtime and test
> >> >> classpaths, but not the compile classpath.
> >> >> test
> >> >> This scope indicates that the dependency is not required for normal
> >> >> use of the application, and is only available for the test
> compilation
> >> >> and execution phases.
> >> >>
> >> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
> >> >>>
> >> >>> Author: sdeboy
> >> >>> Date: Thu Aug 18 05:10:58 2011
> >> >>> New Revision: 1159035
> >> >>>
> >> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
> >> >>> Log:
> >> >>> Updating junit scope in pom.xml to runtime to get build to work with
> >> >>> maven 3.0.3
> >> >>>
> >> >>> Modified:
> >> >>> logging/log4j/trunk/pom.xml
> >> >>>
> >> >>> Modified: logging/log4j/trunk/pom.xml
> >> >>> URL:
> >> >>>
> >> >>>
> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
> >> >>>
> >> >>>
> >> >>>
> ==============================================================================
> >> >>> --- logging/log4j/trunk/pom.xml (original)
> >> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
> >> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
> >> >>> <groupId>junit</groupId>
> >> >>> <artifactId>junit</artifactId>
> >> >>> <version>3.8.1</version>
> >> >>> - <scope>test</scope>
> >> >>> + <scope>runtime</scope>
> >> >>> </dependency>
> >> >>> <dependency>
> >> >>> <groupId>sun.jdk</groupId>
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> ---------------------------------------------------------------------
> >> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> http://www.grobmeier.de
> >> >>
> >> >> ---------------------------------------------------------------------
> >> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >> >>
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >> >
> >> >
> >>
> >>
> >>
> >> --
> >> http://www.grobmeier.de
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>
> >
> >
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
cool!
On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy <sc...@gmail.com> wrote:
> I reverted the change and was still able to build. I'm not sure why I had
> that error.
>
> On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>>
>> weird.
>>
>> my suggestion is we leave it for now - but we must think about it
>> shortly before the release. Because users will then need junit in
>> their runtime which might annoy some of them :-)
>>
>> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
>> wrote:
>> > it failed to even build saying it must be one of build or runtime. I
>> > saw
>> > other test scopes in the poms so I was confused myself. Maybe an issue
>> > with
>> > my environment?
>> >
>> >
>> >
>> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <gr...@gmail.com>
>> > wrote:
>> >
>> >> Not sure, but Junit should not be necessary for the runtime execution
>> >> imho.
>> >>
>> >>
>> >> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>> >>
>> >> I think it should be test only.
>> >>
>> >> I did not work without having it on runtime?
>> >>
>> >> runtime
>> >> This scope indicates that the dependency is not required for
>> >> compilation, but is for execution. It is in the runtime and test
>> >> classpaths, but not the compile classpath.
>> >> test
>> >> This scope indicates that the dependency is not required for normal
>> >> use of the application, and is only available for the test compilation
>> >> and execution phases.
>> >>
>> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>> >>>
>> >>> Author: sdeboy
>> >>> Date: Thu Aug 18 05:10:58 2011
>> >>> New Revision: 1159035
>> >>>
>> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>> >>> Log:
>> >>> Updating junit scope in pom.xml to runtime to get build to work with
>> >>> maven 3.0.3
>> >>>
>> >>> Modified:
>> >>> logging/log4j/trunk/pom.xml
>> >>>
>> >>> Modified: logging/log4j/trunk/pom.xml
>> >>> URL:
>> >>>
>> >>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>> >>>
>> >>>
>> >>> ==============================================================================
>> >>> --- logging/log4j/trunk/pom.xml (original)
>> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>> >>> <groupId>junit</groupId>
>> >>> <artifactId>junit</artifactId>
>> >>> <version>3.8.1</version>
>> >>> - <scope>test</scope>
>> >>> + <scope>runtime</scope>
>> >>> </dependency>
>> >>> <dependency>
>> >>> <groupId>sun.jdk</groupId>
>> >>>
>> >>>
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >>>
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> http://www.grobmeier.de
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >>
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >
>> >
>>
>>
>>
>> --
>> http://www.grobmeier.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Scott Deboy <sc...@gmail.com>.
I reverted the change and was still able to build. I'm not sure why I had
that error.
On Thu, Aug 18, 2011 at 7:24 AM, Christian Grobmeier <gr...@gmail.com>wrote:
> weird.
>
> my suggestion is we leave it for now - but we must think about it
> shortly before the release. Because users will then need junit in
> their runtime which might annoy some of them :-)
>
> On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com>
> wrote:
> > it failed to even build saying it must be one of build or runtime. I saw
> > other test scopes in the poms so I was confused myself. Maybe an issue
> with
> > my environment?
> >
> >
> >
> > On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <gr...@gmail.com>
> > wrote:
> >
> >> Not sure, but Junit should not be necessary for the runtime execution
> >> imho.
> >>
> >>
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
> >>
> >> I think it should be test only.
> >>
> >> I did not work without having it on runtime?
> >>
> >> runtime
> >> This scope indicates that the dependency is not required for
> >> compilation, but is for execution. It is in the runtime and test
> >> classpaths, but not the compile classpath.
> >> test
> >> This scope indicates that the dependency is not required for normal
> >> use of the application, and is only available for the test compilation
> >> and execution phases.
> >>
> >> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
> >>>
> >>> Author: sdeboy
> >>> Date: Thu Aug 18 05:10:58 2011
> >>> New Revision: 1159035
> >>>
> >>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
> >>> Log:
> >>> Updating junit scope in pom.xml to runtime to get build to work with
> >>> maven 3.0.3
> >>>
> >>> Modified:
> >>> logging/log4j/trunk/pom.xml
> >>>
> >>> Modified: logging/log4j/trunk/pom.xml
> >>> URL:
> >>>
> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
> >>>
> >>>
> ==============================================================================
> >>> --- logging/log4j/trunk/pom.xml (original)
> >>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
> >>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
> >>> <groupId>junit</groupId>
> >>> <artifactId>junit</artifactId>
> >>> <version>3.8.1</version>
> >>> - <scope>test</scope>
> >>> + <scope>runtime</scope>
> >>> </dependency>
> >>> <dependency>
> >>> <groupId>sun.jdk</groupId>
> >>>
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>>
> >>>
> >>
> >>
> >>
> >> --
> >> http://www.grobmeier.de
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> > For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >
> >
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
weird.
my suggestion is we leave it for now - but we must think about it
shortly before the release. Because users will then need junit in
their runtime which might annoy some of them :-)
On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com> wrote:
> it failed to even build saying it must be one of build or runtime. I saw
> other test scopes in the poms so I was confused myself. Maybe an issue with
> my environment?
>
>
>
> On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>
>> Not sure, but Junit should not be necessary for the runtime execution
>> imho.
>>
>> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>>
>> I think it should be test only.
>>
>> I did not work without having it on runtime?
>>
>> runtime
>> This scope indicates that the dependency is not required for
>> compilation, but is for execution. It is in the runtime and test
>> classpaths, but not the compile classpath.
>> test
>> This scope indicates that the dependency is not required for normal
>> use of the application, and is only available for the test compilation
>> and execution phases.
>>
>> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>>>
>>> Author: sdeboy
>>> Date: Thu Aug 18 05:10:58 2011
>>> New Revision: 1159035
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>>> Log:
>>> Updating junit scope in pom.xml to runtime to get build to work with
>>> maven 3.0.3
>>>
>>> Modified:
>>> logging/log4j/trunk/pom.xml
>>>
>>> Modified: logging/log4j/trunk/pom.xml
>>> URL:
>>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>>>
>>> ==============================================================================
>>> --- logging/log4j/trunk/pom.xml (original)
>>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>>> <groupId>junit</groupId>
>>> <artifactId>junit</artifactId>
>>> <version>3.8.1</version>
>>> - <scope>test</scope>
>>> + <scope>runtime</scope>
>>> </dependency>
>>> <dependency>
>>> <groupId>sun.jdk</groupId>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>>
>>>
>>
>>
>>
>> --
>> http://www.grobmeier.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
On Thu, Aug 18, 2011 at 4:05 PM, Scott Deboy <sc...@gmail.com> wrote:
> it failed to even build saying it must be one of build or runtime. I saw
> other test scopes in the poms so I was confused myself. Maybe an issue with
> my environment?
Scott, I could now reproduce this on my mac.
I think it is because of the antrun plugin. Ant "compiles the tests",
therefore it needs it on compile scope. So you were right to change
the scope. But I would like to move it to "compile" scope now as a
workaround.
As a second step i think we should try to make the test work in a
temporary directory and then we might be able to remove the antrun for
the tests. I will check this option out now.
Cheers
>
>
>
> On Aug 18, 2011, at 12:51 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>
>> Not sure, but Junit should not be necessary for the runtime execution
>> imho.
>>
>> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>>
>> I think it should be test only.
>>
>> I did not work without having it on runtime?
>>
>> runtime
>> This scope indicates that the dependency is not required for
>> compilation, but is for execution. It is in the runtime and test
>> classpaths, but not the compile classpath.
>> test
>> This scope indicates that the dependency is not required for normal
>> use of the application, and is only available for the test compilation
>> and execution phases.
>>
>> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>>>
>>> Author: sdeboy
>>> Date: Thu Aug 18 05:10:58 2011
>>> New Revision: 1159035
>>>
>>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>>> Log:
>>> Updating junit scope in pom.xml to runtime to get build to work with
>>> maven 3.0.3
>>>
>>> Modified:
>>> logging/log4j/trunk/pom.xml
>>>
>>> Modified: logging/log4j/trunk/pom.xml
>>> URL:
>>> http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>>>
>>> ==============================================================================
>>> --- logging/log4j/trunk/pom.xml (original)
>>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>>> <groupId>junit</groupId>
>>> <artifactId>junit</artifactId>
>>> <version>3.8.1</version>
>>> - <scope>test</scope>
>>> + <scope>runtime</scope>
>>> </dependency>
>>> <dependency>
>>> <groupId>sun.jdk</groupId>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>>
>>>
>>
>>
>>
>> --
>> http://www.grobmeier.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Scott Deboy <sc...@gmail.com>.
it failed to even build saying it must be one of build or runtime. I
saw other test scopes in the poms so I was confused myself. Maybe an
issue with my environment?
On Aug 18, 2011, at 12:51 AM, Christian Grobmeier
<gr...@gmail.com> wrote:
> Not sure, but Junit should not be necessary for the runtime
> execution imho.
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
>
> I think it should be test only.
>
> I did not work without having it on runtime?
>
> runtime
> This scope indicates that the dependency is not required for
> compilation, but is for execution. It is in the runtime and test
> classpaths, but not the compile classpath.
> test
> This scope indicates that the dependency is not required for normal
> use of the application, and is only available for the test compilation
> and execution phases.
>
> On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
>> Author: sdeboy
>> Date: Thu Aug 18 05:10:58 2011
>> New Revision: 1159035
>>
>> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
>> Log:
>> Updating junit scope in pom.xml to runtime to get build to work
>> with maven 3.0.3
>>
>> Modified:
>> logging/log4j/trunk/pom.xml
>>
>> Modified: logging/log4j/trunk/pom.xml
>> URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
>> ===
>> ===
>> ===
>> =====================================================================
>> --- logging/log4j/trunk/pom.xml (original)
>> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
>> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
>> <groupId>junit</groupId>
>> <artifactId>junit</artifactId>
>> <version>3.8.1</version>
>> - <scope>test</scope>
>> + <scope>runtime</scope>
>> </dependency>
>> <dependency>
>> <groupId>sun.jdk</groupId>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>
>
>
> --
> http://www.grobmeier.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: svn commit: r1159035 - /logging/log4j/trunk/pom.xml
Posted by Christian Grobmeier <gr...@gmail.com>.
Not sure, but Junit should not be necessary for the runtime execution imho.
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
I think it should be test only.
I did not work without having it on runtime?
runtime
This scope indicates that the dependency is not required for
compilation, but is for execution. It is in the runtime and test
classpaths, but not the compile classpath.
test
This scope indicates that the dependency is not required for normal
use of the application, and is only available for the test compilation
and execution phases.
On Thu, Aug 18, 2011 at 7:10 AM, <sd...@apache.org> wrote:
> Author: sdeboy
> Date: Thu Aug 18 05:10:58 2011
> New Revision: 1159035
>
> URL: http://svn.apache.org/viewvc?rev=1159035&view=rev
> Log:
> Updating junit scope in pom.xml to runtime to get build to work with maven 3.0.3
>
> Modified:
> logging/log4j/trunk/pom.xml
>
> Modified: logging/log4j/trunk/pom.xml
> URL: http://svn.apache.org/viewvc/logging/log4j/trunk/pom.xml?rev=1159035&r1=1159034&r2=1159035&view=diff
> ==============================================================================
> --- logging/log4j/trunk/pom.xml (original)
> +++ logging/log4j/trunk/pom.xml Thu Aug 18 05:10:58 2011
> @@ -318,7 +318,7 @@ target platform and specify -Dntdll_targ
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>3.8.1</version>
> - <scope>test</scope>
> + <scope>runtime</scope>
> </dependency>
> <dependency>
> <groupId>sun.jdk</groupId>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
http://www.grobmeier.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org