To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-extras has an issue affecting its community integration.
Thi
To whom it may engage...
This is an automated request, but not an unsolicited one. For
more information please visit http://gump.apache.org/nagged.html,
and/or contact the folk at gene...@gump.apache.org.
Project logging-log4j-component has an issue affecting its community
integration.
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
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
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", v
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: MacRom
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
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.
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
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
[E
cool!
On Thu, Aug 18, 2011 at 4:35 PM, Scott Deboy 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
> wrote:
>>
>> weird.
>>
>> my suggestion is we leave it for now - but we must think about
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 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
> t
Author: sdeboy
Date: Thu Aug 18 14:35:10 2011
New Revision: 1159247
URL: http://svn.apache.org/viewvc?rev=1159247&view=rev
Log:
Reverting r1159035 - change to junit scope
Modified:
logging/log4j/trunk/pom.xml
Modified: logging/log4j/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/logging/lo
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 wrote:
> it failed to even build saying it must be one of build
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
wrote:
Not sure, but Junit should not be necessary for the runtime
e
Scott, it works good for me in the sub module folder:
cd apache-log4j-component
mvn clean
mvn site assembly:single
I get the same error when I do mvn clean and mvn assembly:single in
the parent folder.
For some reason you must type:
cd apache-log4j-companions-parent
mvn clean
mvn site package a
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 r
17 matches
Mail list logo
