[jira] Commented: (SCM-444) Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems
[ http://jira.codehaus.org/browse/SCM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209333#action_209333 ] Henric Larsson commented on SCM-444: I have to agree with making the push optional. I work on a small project, we're two developers, we don't have an upstream repository, but we still do releases. Being forced to a push makes no sense as there's nowhere to push to. The tag itself is all that's required in this case. No need to change the default behaviour, just make the push optional. > Git provider does 'git push' during 'mvn release:prepare' which causes > unwanted problems > > > Key: SCM-444 > URL: http://jira.codehaus.org/browse/SCM-444 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-git >Affects Versions: 1.1 >Reporter: Petter Måhlén >Assignee: Mark Struberg >Priority: Minor > > When doing 'mvn release:prepare' with a Git provider, a 'git push' command is > executed. This is not ideal because the push command can fail or push things > from the local repository that are not needed/wanted in the remote > repository. Some examples are: > 1. The local repository has two branches: master (tracking origin/master) and > dummy (tracking origin/dummy). The release is being made on the master > branch, and the dummy and origin/dummy branches have diverged. Running > 'release:prepare' causes a 'git push', which will succeed for the master > branch (assuming that the release preparation has been made correctly) and > fail for the dummy branch (the two branches have diverged and need to be > merged or rebased). The release preparation aborts and the directory is left > in a somewhat inconsistent state where manual cleaning up is needed (removing > pom.xml.next files, changing versions to -SNAPSHOT, etc.) > 2. The local repository has two branches: master (tracking origin/master) and > localtest (not in the origin repository). The localtest branch shouldn't be > published because it is just used for some temporary testing and doesn't even > work. It will be pushed during 'release:prepare'. > Suggested behaviour: use 'git push origin :', > or even better, query for which remote repository to push to (found in > .git/config) and which branch to push from and to. For me, it would be great > to have a 'confirm push' before doing it so as to keep things clean, but > maybe that is quite complex. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-4428) Permament move (error 301) not handled properly by Maven
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209338#action_209338 ] Data Nucleus commented on MNG-4428: --- +1. Recent changes in SUN's M2 repo has broken local repos for me for artifacts for JMX, JMXTOOLS, JMS, MAIL. > Permament move (error 301) not handled properly by Maven > > > Key: MNG-4428 > URL: http://jira.codehaus.org/browse/MNG-4428 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.1 >Reporter: Grzegorz Slowikowski >Priority: Minor > > Artifact cannot be downloaded by http-lightweight-wagon used (as default) in > all Maven versions except 2.2.0, which uses http-wagon by default. > Instead of pom and jar files html files appear in the local repo with content > like: > > > 301 Moved Permanently > > Moved Permanently > The document has moved href="http://download.java.net/maven/2/org/codehaus/castor/castor-xml-schema/1.2/castor-xml-schema-1.2.pom";>here. > > Apache Server at maven2-repository.dev.java.net Port 443 > > Only Maven 2.2.0 handles 301 properly. > By the way, I haven't expected such Apache configuration (permament move) in > central Maven repo. > As you can see this is not handled properly by almost all versions of Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MNG-4428) Permament move (error 301) not handled properly by Maven
[ http://jira.codehaus.org/browse/MNG-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209338#action_209338 ] Data Nucleus edited comment on MNG-4428 at 2/6/10 9:58 AM: --- +1. Recent changes in SUN's M2 repo has broken local repos for me for artifacts for JMX, JMXTOOLS, JMS, MAIL, as per one of the linked JIRAs (about log4j, saying it is log4j's POM fault, but then Maven shouldn't break the repo in the first place) was (Author: datanucleus): +1. Recent changes in SUN's M2 repo has broken local repos for me for artifacts for JMX, JMXTOOLS, JMS, MAIL. > Permament move (error 301) not handled properly by Maven > > > Key: MNG-4428 > URL: http://jira.codehaus.org/browse/MNG-4428 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Artifacts and Repositories >Affects Versions: 2.2.1 >Reporter: Grzegorz Slowikowski >Priority: Minor > > Artifact cannot be downloaded by http-lightweight-wagon used (as default) in > all Maven versions except 2.2.0, which uses http-wagon by default. > Instead of pom and jar files html files appear in the local repo with content > like: > > > 301 Moved Permanently > > Moved Permanently > The document has moved href="http://download.java.net/maven/2/org/codehaus/castor/castor-xml-schema/1.2/castor-xml-schema-1.2.pom";>here. > > Apache Server at maven2-repository.dev.java.net Port 443 > > Only Maven 2.2.0 handles 301 properly. > By the way, I haven't expected such Apache configuration (permament move) in > central Maven repo. > As you can see this is not handled properly by almost all versions of Maven. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MRELEASE-520) A comma separated list of release goals causes the release:perform goal to fail
[ http://jira.codehaus.org/browse/MRELEASE-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Lundberg closed MRELEASE-520. Resolution: Fixed Fix Version/s: 2.0 Assignee: Dennis Lundberg Fixed in [r907285|http://svn.apache.org/viewvc?view=revision&revision=907285]. > A comma separated list of release goals causes the release:perform goal to > fail > --- > > Key: MRELEASE-520 > URL: http://jira.codehaus.org/browse/MRELEASE-520 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: documentation >Affects Versions: 2.0-beta-9 >Reporter: Kurt Zettel >Assignee: Dennis Lundberg > Fix For: 2.0 > > > A space separated list of goals works fine but a comma separated list of > goals is causing the build to fail. The documents should be updated if this > is not supported. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-228) site missing module in maven-archetype-j2ee-simple archetype plugin
[ http://jira.codehaus.org/browse/ARCHETYPE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209352#action_209352 ] Matthew McCullough commented on ARCHETYPE-228: -- The future of this plugin for Maven 3 is over at http://github.com/sonatype/sonatype-archetype For Maven 2, I've attached a patch that basically just gets the archetypes woven into the build process (they were disabled as modules). Next up is adding back the J2ee one (a second supplemental patch) to the samples. I'll start by coping it from http://svn.apache.org/viewvc/maven/archetype/branches/archetype-1.0.x/maven-archetype-bundles/maven-archetype-j2ee-simple/ and then massaging it to fix the Maven 2 versions of the 2.0-alpha-4 plugin and the Maven 3, 0.8.7 version of the plugin. Work in progress... Check out http://github.com/matthewmccullough/sonatype-archetype for what I did on the Maven 3.0 side today. > site missing module in maven-archetype-j2ee-simple archetype plugin > --- > > Key: ARCHETYPE-228 > URL: http://jira.codehaus.org/browse/ARCHETYPE-228 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Esteban DUGUEPEROUX >Priority: Minor > > Hi, > When I create a j2ee-simple project from archetype n°10 the main pom.xml > specify a site module but without site directory. > Then at each j2ee project creation I need to delete the relevant line in > pom.xml. > Can we have a site directory generated or the relevant line in pom.xml > deleted. > Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARCHETYPE-228) site missing module in maven-archetype-j2ee-simple archetype plugin
[ http://jira.codehaus.org/browse/ARCHETYPE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew McCullough updated ARCHETYPE-228: - Attachment: ARCHETYPE-228-part1.diff This is "fix part one" that gets the samples compiling and passing tests with Maven 2.2.1. Next up is a patch that adds back the j2EE sample. > site missing module in maven-archetype-j2ee-simple archetype plugin > --- > > Key: ARCHETYPE-228 > URL: http://jira.codehaus.org/browse/ARCHETYPE-228 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Esteban DUGUEPEROUX >Priority: Minor > Attachments: ARCHETYPE-228-part1.diff > > > Hi, > When I create a j2ee-simple project from archetype n°10 the main pom.xml > specify a site module but without site directory. > Then at each j2ee project creation I need to delete the relevant line in > pom.xml. > Can we have a site directory generated or the relevant line in pom.xml > deleted. > Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (ARCHETYPE-228) site missing module in maven-archetype-j2ee-simple archetype plugin
[ http://jira.codehaus.org/browse/ARCHETYPE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew McCullough updated ARCHETYPE-228: - Attachment: ARCHETYPE-228-j2ee.diff Adding back the j2ee sample as an archetype > site missing module in maven-archetype-j2ee-simple archetype plugin > --- > > Key: ARCHETYPE-228 > URL: http://jira.codehaus.org/browse/ARCHETYPE-228 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Esteban DUGUEPEROUX >Priority: Minor > Attachments: ARCHETYPE-228-j2ee.diff, ARCHETYPE-228-part1.diff > > > Hi, > When I create a j2ee-simple project from archetype n°10 the main pom.xml > specify a site module but without site directory. > Then at each j2ee project creation I need to delete the relevant line in > pom.xml. > Can we have a site directory generated or the relevant line in pom.xml > deleted. > Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (ARCHETYPE-228) site missing module in maven-archetype-j2ee-simple archetype plugin
[ http://jira.codehaus.org/browse/ARCHETYPE-228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209355#action_209355 ] Matthew McCullough commented on ARCHETYPE-228: -- Looks like the samples that were brought over, but not active (that I activated) are not quite set up as archetypes. They need a wrapper project above them that is of type maven-archetype > site missing module in maven-archetype-j2ee-simple archetype plugin > --- > > Key: ARCHETYPE-228 > URL: http://jira.codehaus.org/browse/ARCHETYPE-228 > Project: Maven Archetype > Issue Type: Bug > Components: Generator >Reporter: Esteban DUGUEPEROUX >Priority: Minor > Attachments: ARCHETYPE-228-j2ee.diff, ARCHETYPE-228-part1.diff > > > Hi, > When I create a j2ee-simple project from archetype n°10 the main pom.xml > specify a site module but without site directory. > Then at each j2ee project creation I need to delete the relevant line in > pom.xml. > Can we have a site directory generated or the relevant line in pom.xml > deleted. > Regards. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MCHECKSTYLE-128) Please turn off the noisy velocity logs
Please turn off the noisy velocity logs
---
Key: MCHECKSTYLE-128
URL: http://jira.codehaus.org/browse/MCHECKSTYLE-128
Project: Maven 2.x Checkstyle Plugin
Issue Type: Bug
Affects Versions: 2.4
Reporter: Benson Margulies
To the best of my knowledge, the lengthy and useless spew of logging from
Velocity is triggered by checkstyle. It is very confusing and disruptive. Could
there please be some way to suppress it?
{noformat}
[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] Starting Jakarta Velocity v1.4
[INFO] RuntimeInstance initializing.
[INFO] Default Properties File:
org/apache/velocity/runtime/defaults/velocity.properties
[INFO] Default ResourceManager initializing. (class
org.apache.velocity.runtime.resource.ResourceManagerImpl)
[INFO] Resource Loader Instantiated:
org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
[INFO] ClasspathResourceLoader : initialization starting.
[INFO] ClasspathResourceLoader : initialization complete.
[INFO] ResourceCache : initialized. (class
org.apache.velocity.runtime.resource.ResourceCacheImpl)
[INFO] Default ResourceManager initialization complete.
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
[INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
[INFO] Created: 20 parsers.
[INFO] Velocimacro : initialization starting.
[INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm
[ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any
resource loader.
[INFO] Velocimacro : error using VM library template VM_global_library.vm :
org.apache.velocity.exception.ResourceNotFoundException: Unable to find
resource 'VM_global_library.vm'
[INFO] Velocimacro : VM library template macro registration complete.
[INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates
[INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT
replace previous VM definitions
[INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
global in scope if allowed.
[INFO] Velocimacro : initialization complete.
[INFO] Velocity successfully started.
[INFO] [checkstyle:checkstyle {execution: validate}]
{noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MCHECKSTYLE-128) Please turn off the noisy velocity logs
[
http://jira.codehaus.org/browse/MCHECKSTYLE-128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benson Margulies closed MCHECKSTYLE-128.
Resolution: Fixed
Never mind. THis is fixed in 2.4.
> Please turn off the noisy velocity logs
> ---
>
> Key: MCHECKSTYLE-128
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-128
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.4
>Reporter: Benson Margulies
>
> To the best of my knowledge, the lengthy and useless spew of logging from
> Velocity is triggered by checkstyle. It is very confusing and disruptive.
> Could there please be some way to suppress it?
> {noformat}
> [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] Starting Jakarta Velocity v1.4
> [INFO] RuntimeInstance initializing.
> [INFO] Default Properties File:
> org/apache/velocity/runtime/defaults/velocity.properties
> [INFO] Default ResourceManager initializing. (class
> org.apache.velocity.runtime.resource.ResourceManagerImpl)
> [INFO] Resource Loader Instantiated:
> org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader
> [INFO] ClasspathResourceLoader : initialization starting.
> [INFO] ClasspathResourceLoader : initialization complete.
> [INFO] ResourceCache : initialized. (class
> org.apache.velocity.runtime.resource.ResourceCacheImpl)
> [INFO] Default ResourceManager initialization complete.
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include
> [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach
> [INFO] Created: 20 parsers.
> [INFO] Velocimacro : initialization starting.
> [INFO] Velocimacro : adding VMs from VM library template :
> VM_global_library.vm
> [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in
> any resource loader.
> [INFO] Velocimacro : error using VM library template VM_global_library.vm :
> org.apache.velocity.exception.ResourceNotFoundException: Unable to find
> resource 'VM_global_library.vm'
> [INFO] Velocimacro : VM library template macro registration complete.
> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in
> templates
> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may
> NOT replace previous VM definitions
> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be
> global in scope if allowed.
> [INFO] Velocimacro : initialization complete.
> [INFO] Velocity successfully started.
> [INFO] [checkstyle:checkstyle {execution: validate}]
> {noformat}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MINSTALL-41) Install with classifier does not install pom
[
http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=209360#action_209360
]
Eduard Papa commented on MINSTALL-41:
-
I am still seeing this issue in version 2.3 of the maven-install-plugin with
the original attached pom.xml. I am not seeing a classified pom installed in my
local maven repository. I tried both maven 2.2.1 and 2.0.10 and got the same
result. Here is the debug log produced from the plugin:
{{
[DEBUG] Plugin dependencies for:
org.apache.maven.plugins:maven-install-plugin:2.3
are:
org.apache.maven:maven-plugin-api:jar:2.0.6:runtime
org.apache.maven:maven-project:jar:2.0.6:runtime
org.apache.maven:maven-model:jar:2.0.6:runtime
org.apache.maven:maven-artifact-manager:jar:2.0.6:runtime
org.apache.maven:maven-artifact:jar:2.0.6:runtime
org.codehaus.plexus:plexus-utils:jar:1.5.6:runtime
org.codehaus.plexus:plexus-digest:jar:1.0:runtime
[DEBUG] org.apache.maven.plugins:maven-install-plugin:maven-plugin:2.3:runtime
(selected for runtime)
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-project:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-settings:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-model:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1:runtime (selected
for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1:runtime (selected for
runtime)
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:runtime
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed -
nearer found: 1.4.1)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-profile:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-model:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.6:runtime (selected
for runtime)
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.6:runtime
(selected for runtime)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2:runtime
(selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed -
nearer found: 1.4.1)
[DEBUG] org.apache.maven:maven-plugin-registry:jar:2.0.6:runtime (selected
for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.6:runtime (selected for
runtime)
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9-stable-1:runtime
(selected for runtime)
[DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed -
nearer found: 1.4.1)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for
runtime)
[DEBUG] org.apache.maven:maven-model:jar:2.0.6:runtime (selected for runtime)
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0.6:runtime (selected
for runtime)
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0.6:runtime
(selected for runtime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-beta-2:runtime
(selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed -
nearer found: 1.4.1)
[DEBUG] org.apache.maven:maven-artifact:jar:2.0.6:runtime (selected for
runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1:runtime (removed - nearer
found: 1.5.6)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.5.6:runtime (selected for
runtime)
[DEBUG] Retrieving parent-POM: org.codehaus.plexus:plexus-components:pom:1.1.7
for project: null:plexus-digest:jar:1.0 from the repository.
[DEBUG] org.codehaus.plexus:plexus-digest:jar:1.0:runtime (selected for
runtime)
[DEBUG]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (removed -
nearer found: 1.0-alpha-9-stable-1)
[DEBUG] The following artifacts were filtered out for plugin:
org.apache.maven.plugins:maven-install-plugin:2.3 because they're already in
the core of Maven:
org.apache.maven:maven-plugin-api:jar:2.0.6:runtime
org.apache.maven:maven-project:jar:2.0.6:runtime
org.apache.maven:maven-model:jar:2.0.6:runtime
org.apache.maven:maven-artifact-manager:jar:2.0.6:runtime
org.apache.maven:maven-artifact:jar:2.0.6:runtime
These will use the artifact files already in the core ClassRealm instead, to
allow them to be included in PluginDescriptor.getArtifacts().
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-install-plugin:2.3:inst
