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 Gary Gregory <ga...@gmail.com> on 2012/05/26 20:27:26 UTC
Maven eclipse set up issue
Hi All:
With:
Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
Maven home: C:\Java\apache-maven-3.0.4\bin\..
Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_31\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
and: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
running "mvn eclipse:eclipse" I get:
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 143, column 15
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.logging.log4j:log4j12-api:jar:2.0-alpha1-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 151, column 19
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 244, column 15
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.logging.log4j:slf4j-impl:jar:2.0-alpha1-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 158, column 19
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.logging.log4j:log4j-jcl:jar:2.0-alpha1-SNAPSHOT
[WARNING] 'reporting.plugins.plugin.version' for
org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 155, column 19
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] Apache Log4j 2
[INFO] Log4J API
[INFO] Log4J Core
[INFO] Log4J Compatibility API
[INFO] SLF4J Binding
[INFO] Log4J Commons Logging
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Apache Log4j 2 2.0-alpha1-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j >>>
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
[INFO] Setting property: classpath.resource.loader.class =>
'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j ---
[INFO] Not running eclipse plugin goal for pom project
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container:
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Log4J API 2.0-alpha1-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api >>>
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api
---
[INFO]
[INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api <<<
[INFO]
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api ---
[INFO] Using Eclipse Workspace: null
[INFO] Adding default classpath container:
org.eclipse.jdt.launching.JRE_CONTAINER
[INFO] File C:\svn\org\apache\log4j2\trunk\api\.project already exists.
Additional settings will be preserved, run mvn eclipse:clean if you
want old settings to be removed.
[INFO] Wrote Eclipse project for "log4j-api" to
C:\svn\org\apache\log4j2\trunk\api.
[INFO]
Sources for some artifacts are not available.
Please run the same goal with the -DdownloadSources=true parameter
in order to check remote repositories for sources.
List of artifacts without a source archive:
o commons-logging:commons-logging:1.0.4
o junit:junit:4.3.1
Javadoc for some artifacts is not available.
Please run the same goal with the -DdownloadJavadocs=true parameter
in order to check remote repositories for javadoc.
List of artifacts without a javadoc archive:
o commons-httpclient:commons-httpclient:3.1
o commons-logging:commons-logging:1.0.4
o commons-codec:commons-codec:1.2
o junit:junit:4.3.1
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building Log4J Core 2.0-alpha1-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-core >>>
[INFO]
[INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-core
---
Downloading:
http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Log4j 2 .................................... SUCCESS [1.060s]
[INFO] Log4J API ......................................... SUCCESS [0.157s]
[INFO] Log4J Core ........................................ FAILURE [1.016s]
[INFO] Log4J Compatibility API ........................... SKIPPED
[INFO] SLF4J Binding ..................................... SKIPPED
[INFO] Log4J Commons Logging ............................. SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 4.002s
[INFO] Finished at: Sat May 26 14:25:22 EDT 2012
[INFO] Final Memory: 18M/220M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process
(default) on project log4j-core: Failed to resolve dependencie
s for one or more projects in the reactor. Reason: Could not transfer
artifact org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT from/to
apache.snapsho
ts (http://repository.apache.org/snapshots): Not authorized,
ReasonPhrase:Unauthorized.
[ERROR] org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] apache.snapshots (http://repository.apache.org/snapshots,
releases=false, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true,
snapshots=false)
[ERROR] Path to dependency:
[ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
[ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
[ERROR] -> [Help 1]
[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.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :log4j-core
Thoughts?
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Maven eclipse set up issue
Posted by Christian Grobmeier <gr...@gmail.com>.
>> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
>>
>> Its not existing. As it does not exist, maybe a "mvn install" in front
>> of a mvn eclipse:eclipse does help?
>
>
> Yes it does! Thank you. Now I'll have to probably run eclipse:eclipse in
> each module... and create separate Eclipse projects for each...
Cool!
But doesn't running mvn eclipse:eclipse on the top level work?
After it you should be able to import all projects at once
>
> Gary
>>
>>
>> On Sat, May 26, 2012 at 8:27 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>> > Hi All:
>> >
>> > With:
>> >
>> > Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
>> > Maven home: C:\Java\apache-maven-3.0.4\bin\..
>> > Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
>> > Java home: C:\Program Files\Java\jdk1.6.0_31\jre
>> > Default locale: en_US, platform encoding: Cp1252
>> > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>> >
>> > and: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
>> >
>> > running "mvn eclipse:eclipse" I get:
>> >
>> > [INFO] Scanning for projects...
>> > [WARNING]
>> > [WARNING] Some problems were encountered while building the effective
>> > model
>> > for org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
>> > [WARNING] 'reporting.plugins.plugin.version' for
>> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 143, column
>> > 15
>> > [WARNING]
>> > [WARNING] Some problems were encountered while building the effective
>> > model
>> > for org.apache.logging.log4j:log4j12-api:jar:2.0-alpha1-SNAPSHOT
>> > [WARNING] 'reporting.plugins.plugin.version' for
>> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 151, column
>> > 19
>> > [WARNING]
>> > [WARNING] Some problems were encountered while building the effective
>> > model
>> > for org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
>> > [WARNING] 'reporting.plugins.plugin.version' for
>> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 244, column
>> > 15
>> > [WARNING]
>> > [WARNING] Some problems were encountered while building the effective
>> > model
>> > for org.apache.logging.log4j:slf4j-impl:jar:2.0-alpha1-SNAPSHOT
>> > [WARNING] 'reporting.plugins.plugin.version' for
>> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 158, column
>> > 19
>> > [WARNING]
>> > [WARNING] Some problems were encountered while building the effective
>> > model
>> > for org.apache.logging.log4j:log4j-jcl:jar:2.0-alpha1-SNAPSHOT
>> > [WARNING] 'reporting.plugins.plugin.version' for
>> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 155, column
>> > 19
>> > [WARNING]
>> > [WARNING] It is highly recommended to fix these problems because they
>> > threaten the stability of your build.
>> > [WARNING]
>> > [WARNING] For this reason, future Maven versions might no longer support
>> > building such malformed projects.
>> > [WARNING]
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Reactor Build Order:
>> > [INFO]
>> > [INFO] Apache Log4j 2
>> > [INFO] Log4J API
>> > [INFO] Log4J Core
>> > [INFO] Log4J Compatibility API
>> > [INFO] SLF4J Binding
>> > [INFO] Log4J Commons Logging
>> > [INFO]
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Building Apache Log4j 2 2.0-alpha1-SNAPSHOT
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO]
>> > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j >>>
>> > [INFO]
>> > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j
>> > ---
>> > [INFO] Setting property: classpath.resource.loader.class =>
>> > 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
>> > [INFO] Setting property: velocimacro.messages.on => 'false'.
>> > [INFO] Setting property: resource.loader => 'classpath'.
>> > [INFO] Setting property: resource.manager.logwhenfound => 'false'.
>> > [INFO]
>> > [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j <<<
>> > [INFO]
>> > [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j ---
>> > [INFO] Not running eclipse plugin goal for pom project
>> > [INFO] Using Eclipse Workspace: null
>> > [INFO] Adding default classpath container:
>> > org.eclipse.jdt.launching.JRE_CONTAINER
>> > [INFO]
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Building Log4J API 2.0-alpha1-SNAPSHOT
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO]
>> > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api
>> > >>>
>> > [INFO]
>> > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @
>> > log4j-api
>> > ---
>> > [INFO]
>> > [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api
>> > <<<
>> > [INFO]
>> > [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api
>> > ---
>> > [INFO] Using Eclipse Workspace: null
>> > [INFO] Adding default classpath container:
>> > org.eclipse.jdt.launching.JRE_CONTAINER
>> > [INFO] File C:\svn\org\apache\log4j2\trunk\api\.project already exists.
>> > Additional settings will be preserved, run mvn eclipse:clean if
>> > you
>> > want old settings to be removed.
>> > [INFO] Wrote Eclipse project for "log4j-api" to
>> > C:\svn\org\apache\log4j2\trunk\api.
>> > [INFO]
>> > Sources for some artifacts are not available.
>> > Please run the same goal with the -DdownloadSources=true
>> > parameter in
>> > order to check remote repositories for sources.
>> > List of artifacts without a source archive:
>> > o commons-logging:commons-logging:1.0.4
>> > o junit:junit:4.3.1
>> >
>> > Javadoc for some artifacts is not available.
>> > Please run the same goal with the -DdownloadJavadocs=true
>> > parameter
>> > in order to check remote repositories for javadoc.
>> > List of artifacts without a javadoc archive:
>> > o commons-httpclient:commons-httpclient:3.1
>> > o commons-logging:commons-logging:1.0.4
>> > o commons-codec:commons-codec:1.2
>> > o junit:junit:4.3.1
>> >
>> > [INFO]
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Building Log4J Core 2.0-alpha1-SNAPSHOT
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO]
>> > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-core
>> > >>>
>> > [INFO]
>> > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @
>> > log4j-core
>> > ---
>> > Downloading:
>> >
>> > http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Reactor Summary:
>> > [INFO]
>> > [INFO] Apache Log4j 2 .................................... SUCCESS
>> > [1.060s]
>> > [INFO] Log4J API ......................................... SUCCESS
>> > [0.157s]
>> > [INFO] Log4J Core ........................................ FAILURE
>> > [1.016s]
>> > [INFO] Log4J Compatibility API ........................... SKIPPED
>> > [INFO] SLF4J Binding ..................................... SKIPPED
>> > [INFO] Log4J Commons Logging ............................. SKIPPED
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] BUILD FAILURE
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [INFO] Total time: 4.002s
>> > [INFO] Finished at: Sat May 26 14:25:22 EDT 2012
>> > [INFO] Final Memory: 18M/220M
>> > [INFO]
>> > ------------------------------------------------------------------------
>> > [ERROR] Failed to execute goal
>> > org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process
>> > (default)
>> > on project log4j-core: Failed to resolve dependencie
>> > s for one or more projects in the reactor. Reason: Could not transfer
>> > artifact org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
>> > from/to
>> > apache.snapsho
>> > ts (http://repository.apache.org/snapshots): Not authorized,
>> > ReasonPhrase:Unauthorized.
>> > [ERROR] org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
>> > [ERROR]
>> > [ERROR] from the specified remote repositories:
>> > [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
>> > releases=false, snapshots=true),
>> > [ERROR] central (http://repo.maven.apache.org/maven2, releases=true,
>> > snapshots=false)
>> > [ERROR] Path to dependency:
>> > [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
>> > [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
>> > [ERROR] -> [Help 1]
>> > [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.
>> > [ERROR]
>> > [ERROR] For more information about the errors and possible solutions,
>> > please
>> > read the following articles:
>> > [ERROR] [Help 1]
>> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
>> > [ERROR]
>> > [ERROR] After correcting the problems, you can resume the build with the
>> > command
>> > [ERROR] mvn <goals> -rf :log4j-core
>> >
>> > Thoughts?
>> >
>> >
>> > --
>> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> > Spring Batch in Action: http://bit.ly/bqpbCK
>> > Blog: http://garygregory.wordpress.com
>> > Home: http://garygregory.com/
>> > Tweet! http://twitter.com/GaryGregory
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Maven eclipse set up issue
Posted by Gary Gregory <ga...@gmail.com>.
On May 26, 2012, at 15:52, Ralph Goers <ra...@dslextreme.com> wrote:
On May 26, 2012, at 12:12 PM, Gary Gregory wrote:
On Sat, May 26, 2012 at 2:55 PM, Christian Grobmeier <gr...@gmail.com>wrote:
> Hi,
>
> I am wondering why it tries to download:
>
> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
>
> Its not existing. As it does not exist, maybe a "mvn install" in front
> of a mvn eclipse:eclipse does help?
>
Yes it does! Thank you. Now I'll have to probably run eclipse:eclipse in
each module... and create separate Eclipse projects for each…
If you do mvn -Dmaven.test.skip=true install then you should be able to run
mvn eclipse:eclipse from the root. Skipping the tests will allow
everything to build and install regardless of test failures.
Yep, that did it. Thank you.
Gary
Ralph
Re: Maven eclipse set up issue
Posted by Ralph Goers <ra...@dslextreme.com>.
On May 26, 2012, at 12:12 PM, Gary Gregory wrote:
> On Sat, May 26, 2012 at 2:55 PM, Christian Grobmeier <gr...@gmail.com> wrote:
> Hi,
>
> I am wondering why it tries to download:
> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
>
> Its not existing. As it does not exist, maybe a "mvn install" in front
> of a mvn eclipse:eclipse does help?
>
> Yes it does! Thank you. Now I'll have to probably run eclipse:eclipse in each module... and create separate Eclipse projects for each…
>
If you do mvn -Dmaven.test.skip=true install then you should be able to run mvn eclipse:eclipse from the root. Skipping the tests will allow everything to build and install regardless of test failures.
Ralph
Re: Maven eclipse set up issue
Posted by Gary Gregory <ga...@gmail.com>.
On Sat, May 26, 2012 at 2:55 PM, Christian Grobmeier <gr...@gmail.com>wrote:
> Hi,
>
> I am wondering why it tries to download:
>
> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
>
> Its not existing. As it does not exist, maybe a "mvn install" in front
> of a mvn eclipse:eclipse does help?
>
Yes it does! Thank you. Now I'll have to probably run eclipse:eclipse in
each module... and create separate Eclipse projects for each...
Gary
>
> On Sat, May 26, 2012 at 8:27 PM, Gary Gregory <ga...@gmail.com>
> wrote:
> > Hi All:
> >
> > With:
> >
> > Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> > Maven home: C:\Java\apache-maven-3.0.4\bin\..
> > Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
> > Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> > Default locale: en_US, platform encoding: Cp1252
> > OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
> >
> > and: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
> >
> > running "mvn eclipse:eclipse" I get:
> >
> > [INFO] Scanning for projects...
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model
> > for org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> > [WARNING] 'reporting.plugins.plugin.version' for
> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 143, column
> 15
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model
> > for org.apache.logging.log4j:log4j12-api:jar:2.0-alpha1-SNAPSHOT
> > [WARNING] 'reporting.plugins.plugin.version' for
> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 151, column
> 19
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model
> > for org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
> > [WARNING] 'reporting.plugins.plugin.version' for
> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 244, column
> 15
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model
> > for org.apache.logging.log4j:slf4j-impl:jar:2.0-alpha1-SNAPSHOT
> > [WARNING] 'reporting.plugins.plugin.version' for
> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 158, column
> 19
> > [WARNING]
> > [WARNING] Some problems were encountered while building the effective
> model
> > for org.apache.logging.log4j:log4j-jcl:jar:2.0-alpha1-SNAPSHOT
> > [WARNING] 'reporting.plugins.plugin.version' for
> > org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 155, column
> 19
> > [WARNING]
> > [WARNING] It is highly recommended to fix these problems because they
> > threaten the stability of your build.
> > [WARNING]
> > [WARNING] For this reason, future Maven versions might no longer support
> > building such malformed projects.
> > [WARNING]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Reactor Build Order:
> > [INFO]
> > [INFO] Apache Log4j 2
> > [INFO] Log4J API
> > [INFO] Log4J Core
> > [INFO] Log4J Compatibility API
> > [INFO] SLF4J Binding
> > [INFO] Log4J Commons Logging
> > [INFO]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Building Apache Log4j 2 2.0-alpha1-SNAPSHOT
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO]
> > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j >>>
> > [INFO]
> > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j
> ---
> > [INFO] Setting property: classpath.resource.loader.class =>
> > 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> > [INFO] Setting property: velocimacro.messages.on => 'false'.
> > [INFO] Setting property: resource.loader => 'classpath'.
> > [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> > [INFO]
> > [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j <<<
> > [INFO]
> > [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j ---
> > [INFO] Not running eclipse plugin goal for pom project
> > [INFO] Using Eclipse Workspace: null
> > [INFO] Adding default classpath container:
> > org.eclipse.jdt.launching.JRE_CONTAINER
> > [INFO]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Building Log4J API 2.0-alpha1-SNAPSHOT
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO]
> > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api >>>
> > [INFO]
> > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @
> log4j-api
> > ---
> > [INFO]
> > [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api <<<
> > [INFO]
> > [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api ---
> > [INFO] Using Eclipse Workspace: null
> > [INFO] Adding default classpath container:
> > org.eclipse.jdt.launching.JRE_CONTAINER
> > [INFO] File C:\svn\org\apache\log4j2\trunk\api\.project already exists.
> > Additional settings will be preserved, run mvn eclipse:clean if
> you
> > want old settings to be removed.
> > [INFO] Wrote Eclipse project for "log4j-api" to
> > C:\svn\org\apache\log4j2\trunk\api.
> > [INFO]
> > Sources for some artifacts are not available.
> > Please run the same goal with the -DdownloadSources=true
> parameter in
> > order to check remote repositories for sources.
> > List of artifacts without a source archive:
> > o commons-logging:commons-logging:1.0.4
> > o junit:junit:4.3.1
> >
> > Javadoc for some artifacts is not available.
> > Please run the same goal with the -DdownloadJavadocs=true
> parameter
> > in order to check remote repositories for javadoc.
> > List of artifacts without a javadoc archive:
> > o commons-httpclient:commons-httpclient:3.1
> > o commons-logging:commons-logging:1.0.4
> > o commons-codec:commons-codec:1.2
> > o junit:junit:4.3.1
> >
> > [INFO]
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Building Log4J Core 2.0-alpha1-SNAPSHOT
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO]
> > [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-core
> >>>
> > [INFO]
> > [INFO] --- maven-remote-resources-plugin:1.1:process (default) @
> log4j-core
> > ---
> > Downloading:
> >
> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Reactor Summary:
> > [INFO]
> > [INFO] Apache Log4j 2 .................................... SUCCESS
> [1.060s]
> > [INFO] Log4J API ......................................... SUCCESS
> [0.157s]
> > [INFO] Log4J Core ........................................ FAILURE
> [1.016s]
> > [INFO] Log4J Compatibility API ........................... SKIPPED
> > [INFO] SLF4J Binding ..................................... SKIPPED
> > [INFO] Log4J Commons Logging ............................. SKIPPED
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] BUILD FAILURE
> > [INFO]
> > ------------------------------------------------------------------------
> > [INFO] Total time: 4.002s
> > [INFO] Finished at: Sat May 26 14:25:22 EDT 2012
> > [INFO] Final Memory: 18M/220M
> > [INFO]
> > ------------------------------------------------------------------------
> > [ERROR] Failed to execute goal
> > org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process
> (default)
> > on project log4j-core: Failed to resolve dependencie
> > s for one or more projects in the reactor. Reason: Could not transfer
> > artifact org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> from/to
> > apache.snapsho
> > ts (http://repository.apache.org/snapshots): Not authorized,
> > ReasonPhrase:Unauthorized.
> > [ERROR] org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> > [ERROR]
> > [ERROR] from the specified remote repositories:
> > [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
> > releases=false, snapshots=true),
> > [ERROR] central (http://repo.maven.apache.org/maven2, releases=true,
> > snapshots=false)
> > [ERROR] Path to dependency:
> > [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
> > [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> > [ERROR] -> [Help 1]
> > [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.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> please
> > read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> > [ERROR]
> > [ERROR] After correcting the problems, you can resume the build with the
> > command
> > [ERROR] mvn <goals> -rf :log4j-core
> >
> > Thoughts?
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> > Spring Batch in Action: http://bit.ly/bqpbCK
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: Maven eclipse set up issue
Posted by Christian Grobmeier <gr...@gmail.com>.
Hi,
I am wondering why it tries to download:
http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
Its not existing. As it does not exist, maybe a "mvn install" in front
of a mvn eclipse:eclipse does help?
On Sat, May 26, 2012 at 8:27 PM, Gary Gregory <ga...@gmail.com> wrote:
> Hi All:
>
> With:
>
> Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>
> and: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
>
> running "mvn eclipse:eclipse" I get:
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 143, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.logging.log4j:log4j12-api:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 151, column 19
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 244, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.logging.log4j:slf4j-impl:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 158, column 19
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model
> for org.apache.logging.log4j:log4j-jcl:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for
> org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 155, column 19
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Log4j 2
> [INFO] Log4J API
> [INFO] Log4J Core
> [INFO] Log4J Compatibility API
> [INFO] SLF4J Binding
> [INFO] Log4J Commons Logging
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Apache Log4j 2 2.0-alpha1-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
> [INFO] Setting property: classpath.resource.loader.class =>
> 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO]
> [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j <<<
> [INFO]
> [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j ---
> [INFO] Not running eclipse plugin goal for pom project
> [INFO] Using Eclipse Workspace: null
> [INFO] Adding default classpath container:
> org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Log4J API 2.0-alpha1-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api
> ---
> [INFO]
> [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api <<<
> [INFO]
> [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api ---
> [INFO] Using Eclipse Workspace: null
> [INFO] Adding default classpath container:
> org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO] File C:\svn\org\apache\log4j2\trunk\api\.project already exists.
> Additional settings will be preserved, run mvn eclipse:clean if you
> want old settings to be removed.
> [INFO] Wrote Eclipse project for "log4j-api" to
> C:\svn\org\apache\log4j2\trunk\api.
> [INFO]
> Sources for some artifacts are not available.
> Please run the same goal with the -DdownloadSources=true parameter in
> order to check remote repositories for sources.
> List of artifacts without a source archive:
> o commons-logging:commons-logging:1.0.4
> o junit:junit:4.3.1
>
> Javadoc for some artifacts is not available.
> Please run the same goal with the -DdownloadJavadocs=true parameter
> in order to check remote repositories for javadoc.
> List of artifacts without a javadoc archive:
> o commons-httpclient:commons-httpclient:3.1
> o commons-logging:commons-logging:1.0.4
> o commons-codec:commons-codec:1.2
> o junit:junit:4.3.1
>
> [INFO]
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building Log4J Core 2.0-alpha1-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-core >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-core
> ---
> Downloading:
> http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.060s]
> [INFO] Log4J API ......................................... SUCCESS [0.157s]
> [INFO] Log4J Core ........................................ FAILURE [1.016s]
> [INFO] Log4J Compatibility API ........................... SKIPPED
> [INFO] SLF4J Binding ..................................... SKIPPED
> [INFO] Log4J Commons Logging ............................. SKIPPED
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 4.002s
> [INFO] Finished at: Sat May 26 14:25:22 EDT 2012
> [INFO] Final Memory: 18M/220M
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default)
> on project log4j-core: Failed to resolve dependencie
> s for one or more projects in the reactor. Reason: Could not transfer
> artifact org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT from/to
> apache.snapsho
> ts (http://repository.apache.org/snapshots): Not authorized,
> ReasonPhrase:Unauthorized.
> [ERROR] org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
> releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> [ERROR] -> [Help 1]
> [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.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the
> command
> [ERROR] mvn <goals> -rf :log4j-core
>
> Thoughts?
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: Maven eclipse set up issue
Posted by Ralph Goers <ra...@dslextreme.com>.
From what I can tell you are going to have to run mvn install (or maven -Dmaven.test.skip=true install) first as it seems to be trying to find the dependencies.
I use IntelliJ and I just tell it where the root of the project is and it does the rest so I don't know how much help I'm going to be on problems with Eclipse.
Ralph
On May 26, 2012, at 11:27 AM, Gary Gregory wrote:
> Hi All:
>
> With:
>
> Apache Maven 3.0.4 (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>
> and: https://svn.apache.org/repos/asf/logging/log4j/log4j2/trunk
>
> running "mvn eclipse:eclipse" I get:
>
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 143, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.logging.log4j:log4j12-api:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 151, column 19
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 244, column 15
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.logging.log4j:slf4j-impl:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 158, column 19
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.logging.log4j:log4j-jcl:jar:2.0-alpha1-SNAPSHOT
> [WARNING] 'reporting.plugins.plugin.version' for org.apache.maven.plugins:maven-pmd-plugin is missing. @ line 155, column 19
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Build Order:
> [INFO]
> [INFO] Apache Log4j 2
> [INFO] Log4J API
> [INFO] Log4J Core
> [INFO] Log4J Compatibility API
> [INFO] SLF4J Binding
> [INFO] Log4J Commons Logging
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Apache Log4j 2 2.0-alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j ---
> [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
> [INFO] Setting property: velocimacro.messages.on => 'false'.
> [INFO] Setting property: resource.loader => 'classpath'.
> [INFO] Setting property: resource.manager.logwhenfound => 'false'.
> [INFO]
> [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j <<<
> [INFO]
> [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j ---
> [INFO] Not running eclipse plugin goal for pom project
> [INFO] Using Eclipse Workspace: null
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Log4J API 2.0-alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-api ---
> [INFO]
> [INFO] <<< maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api <<<
> [INFO]
> [INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-api ---
> [INFO] Using Eclipse Workspace: null
> [INFO] Adding default classpath container: org.eclipse.jdt.launching.JRE_CONTAINER
> [INFO] File C:\svn\org\apache\log4j2\trunk\api\.project already exists.
> Additional settings will be preserved, run mvn eclipse:clean if you want old settings to be removed.
> [INFO] Wrote Eclipse project for "log4j-api" to C:\svn\org\apache\log4j2\trunk\api.
> [INFO]
> Sources for some artifacts are not available.
> Please run the same goal with the -DdownloadSources=true parameter in order to check remote repositories for sources.
> List of artifacts without a source archive:
> o commons-logging:commons-logging:1.0.4
> o junit:junit:4.3.1
>
> Javadoc for some artifacts is not available.
> Please run the same goal with the -DdownloadJavadocs=true parameter in order to check remote repositories for javadoc.
> List of artifacts without a javadoc archive:
> o commons-httpclient:commons-httpclient:3.1
> o commons-logging:commons-logging:1.0.4
> o commons-codec:commons-codec:1.2
> o junit:junit:4.3.1
>
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building Log4J Core 2.0-alpha1-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [INFO]
> [INFO] >>> maven-eclipse-plugin:2.8:eclipse (default-cli) @ log4j-core >>>
> [INFO]
> [INFO] --- maven-remote-resources-plugin:1.1:process (default) @ log4j-core ---
> Downloading: http://repository.apache.org/snapshots/org/apache/logging/log4j/log4j-api/2.0-alpha1-SNAPSHOT/log4j-api-2.0-alpha1-SNAPSHOT.jar
> [INFO] ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> [INFO] Apache Log4j 2 .................................... SUCCESS [1.060s]
> [INFO] Log4J API ......................................... SUCCESS [0.157s]
> [INFO] Log4J Core ........................................ FAILURE [1.016s]
> [INFO] Log4J Compatibility API ........................... SKIPPED
> [INFO] SLF4J Binding ..................................... SKIPPED
> [INFO] Log4J Commons Logging ............................. SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 4.002s
> [INFO] Finished at: Sat May 26 14:25:22 EDT 2012
> [INFO] Final Memory: 18M/220M
> [INFO] ------------------------------------------------------------------------
> [ERROR] Failed to execute goal org.apache.maven.plugins:maven-remote-resources-plugin:1.1:process (default) on project log4j-core: Failed to resolve dependencie
> s for one or more projects in the reactor. Reason: Could not transfer artifact org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT from/to apache.snapsho
> ts (http://repository.apache.org/snapshots): Not authorized, ReasonPhrase:Unauthorized.
> [ERROR] org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots, releases=false, snapshots=true),
> [ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=false)
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.logging.log4j:log4j-core:jar:2.0-alpha1-SNAPSHOT
> [ERROR] 2) org.apache.logging.log4j:log4j-api:jar:2.0-alpha1-SNAPSHOT
> [ERROR] -> [Help 1]
> [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.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> [ERROR] mvn <goals> -rf :log4j-core
>
> Thoughts?
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory