[jira] (MNG-5185) Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested
[ https://jira.codehaus.org/browse/MNG-5185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MNG-5185: --- Summary: Improve "missing dependency" error message when _maven.repositories/_remote.repositories contains other repository ids than requested (was: Improve "missing dependency" error message when _maven.repositories contains other repository ids than requested) > Improve "missing dependency" error message when > _maven.repositories/_remote.repositories contains other repository ids than > requested > - > > Key: MNG-5185 > URL: https://jira.codehaus.org/browse/MNG-5185 > Project: Maven 2 & 3 > Issue Type: Improvement >Affects Versions: 3.0.2, 3.0.3, 3.0.4 >Reporter: Mark Derricutt >Assignee: Olivier Lamy > Fix For: 3.1.x > > Attachments: > 0001-MNG-5185-Warn-about-artifacts-present-but-not-availa.patch > > > Based on a discussion on the users list [1], [Maven 3 has changed how it > resolves artifacts from local > repositories|https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ResolutionfromLocalRepository]. > Unfortunately, when "conflicts" arise (GAV is cached in local repo, but > restricted to some repository ids, and actual POM has no matching repository > id declared), Maven just tells the user that the artifact could not be > resolved. > This leads to confusion from users who find the .jar files in their local > repository without knowing this restriction feature: they just get frustrated > and complain that "maven sucks". > It would be good if Maven was updated with some improved error messages along > the lines of: > "The (GAV) artifact was found in your local repository, but came from remote > repository "xxx": either configure this in your pom with (insert sample XML > block in error message), or in your "yyy" mirror." > The "mirror" section of the error message should be included -if- the current > ~/.m2/settings.xml declares a mirror. By improving the messages here we can > help the users move on to building software, rather than pulling out their > hair :) > [1] > http://maven.40175.n5.nabble.com/Maven-3-maven-repositories-and-lastUpdated-td4927537.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5482) Catch NoClassDefFoundError org/sonatype/aether
[
https://jira.codehaus.org/browse/MNG-5482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=325864#comment-325864
]
Herve Boutemy edited comment on MNG-5482 at 7/28/13 6:36 AM:
-
IT added in
[d2e33275|http://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/d2e33275]
Maven improved in
[ac64dd6b|http://git-wip-us.apache.org/repos/asf/maven/commit/ac64dd6b], which
will provide a link to
http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound (article
that still needs to be written)
was (Author: hboutemy):
IT added in
[d2e33275|ttp://git-wip-us.apache.org/repos/asf/maven-integration-testing/commit/d2e33275]
Maven improved in
[ac64dd6b|http://git-wip-us.apache.org/repos/asf/maven/commit/ac64dd6b], which
will provide a link to
http://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound (article
that still needs to be written)
> Catch NoClassDefFoundError org/sonatype/aether
> --
>
> Key: MNG-5482
> URL: https://jira.codehaus.org/browse/MNG-5482
> Project: Maven 2 & 3
> Issue Type: Improvement
> Components: Plugins and Lifecycle
>Affects Versions: 3.1.0-alpha-1
>Reporter: Arnaud Heritier
>Assignee: Herve Boutemy
> Fix For: 3.1.0-alpha-1
>
>
> In Maven 3.1 Sonatype Aether was replaced by Eclipse Aether where the root
> package was changed org.sonatype.aether -> org.eclipse.aether
> Due to this all plugins which are using directly aether have to be updated to
> support both packages.
> For now with old plugins the user receive such ugly error :
> {code}
> [INFO] Dependency-reduced POM written at:
> /Users/arnaud/Code/eXo/platform-public-distributions/plf-tomcat-extensions-manager/dependency-reduced-pom.xml
> [WARNING] Error injecting:
> org.apache.maven.shared.dependency.graph.internal.Maven3DependencyGraphBuilder
> java.lang.NoClassDefFoundError: org/sonatype/aether/graph/Dependency
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2436)
> at java.lang.Class.getDeclaredMethods(Class.java:1793)
> at
> com.google.inject.spi.InjectionPoint.getInjectionPoints(InjectionPoint.java:674)
> at
> com.google.inject.spi.InjectionPoint.forInstanceMethodsAndFields(InjectionPoint.java:366)
> at
> com.google.inject.internal.ConstructorBindingImpl.getInternalDependencies(ConstructorBindingImpl.java:165)
> at
> com.google.inject.internal.InjectorImpl.getInternalDependencies(InjectorImpl.java:609)
> at
> com.google.inject.internal.InjectorImpl.cleanup(InjectorImpl.java:565)
> at
> com.google.inject.internal.InjectorImpl.initializeJitBinding(InjectorImpl.java:551)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBinding(InjectorImpl.java:865)
> at
> com.google.inject.internal.InjectorImpl.createJustInTimeBindingRecursive(InjectorImpl.java:790)
> at
> com.google.inject.internal.InjectorImpl.getJustInTimeBinding(InjectorImpl.java:278)
> at
> com.google.inject.internal.InjectorImpl.getBindingOrThrow(InjectorImpl.java:210)
> at
> com.google.inject.internal.InjectorImpl.getProviderOrThrow(InjectorImpl.java:986)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1019)
> at
> com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:982)
> at
> com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1032)
> at
> org.eclipse.sisu.reflect.AbstractDeferredClass.get(AbstractDeferredClass.java:44)
> at
> com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:86)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:55)
> at
> com.google.inject.internal.ProviderInternalFactory$1.call(ProviderInternalFactory.java:70)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:100)
> at
> org.eclipse.sisu.plexus.lifecycles.PlexusLifecycleManager.onProvision(PlexusLifecycleManager.java:134)
> at
> com.google.inject.internal.ProvisionListenerStackCallback$Provision.provision(ProvisionListenerStackCallback.java:109)
> at
> com.google.inject.internal.ProvisionListenerStackCallback.provision(ProvisionListenerStackCallback.java:55)
> at
> com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:68)
> at
> com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
> at
> com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call
[jira] (MNG-3092) Version ranges with non-snapshot bounds can contain snapshot versions
[ https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-3092: --- Fix Version/s: (was: 3.1.1) 3.1.2 > Version ranges with non-snapshot bounds can contain snapshot versions > - > > Key: MNG-3092 > URL: https://jira.codehaus.org/browse/MNG-3092 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Dependencies >Reporter: Mark Hobson >Assignee: Jason van Zyl > Fix For: 3.1.2 > > Attachments: MNG-3092.patch, MNG-3092.patch > > > Contrary to the 2.0 design docs: > "Resolution of dependency ranges should not resolve to a snapshot > (development version) unless it is included as an explicit boundary." > -- from > http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-Incorporating%7B%7BSNAPSHOT%7D%7Dversionsintothespecification > The following is equates to true: > VersionRange.createFromVersionSpec( "[1.0,1.1]" ).containsVersion( new > DefaultArtifactVersion( "1.1-SNAPSHOT" ) ) > The attached patch only allows snapshot versions to be contained in a range > if they are equal to one of the boundaries. Note that this is a strict > equality, so [1.0,1.2-SNAPSHOT] will not contain 1.1-SNAPSHOT. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5207) [Regression] Maven 3 fails to calculate proper build order
[ https://jira.codehaus.org/browse/MNG-5207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5207: --- Fix Version/s: (was: 3.1.1) 3.1.2 > [Regression] Maven 3 fails to calculate proper build order > -- > > Key: MNG-5207 > URL: https://jira.codehaus.org/browse/MNG-5207 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Reactor and workspace >Affects Versions: 3.0.3 >Reporter: Jörg Schaible >Assignee: Kristian Rosenvold >Priority: Critical > Fix For: 3.1.2 > > Attachments: mng5207-it.tgz, MNG-5207.tgz > > > Maven 3.0.3 and 3.0.4 RC1 fails to build the projects of the reactor in > proper order, if a transitive dependency (that is part of the reactor build) > is overruled in the dependencyManagement section with the current SNAPSHOT > version. Build order is perfectly calculated with Maven 2.2.1. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5353) Ignore pre-releases in exclusive upper bound [lw,up)
[ https://jira.codehaus.org/browse/MNG-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5353: --- Fix Version/s: (was: 3.1.1) 3.1.2 > Ignore pre-releases in exclusive upper bound [lw,up) > > > Key: MNG-5353 > URL: https://jira.codehaus.org/browse/MNG-5353 > Project: Maven 2 & 3 > Issue Type: Wish > Components: Dependencies >Affects Versions: 2.0.11, 2.2.1, 3.0.4 >Reporter: Jesse Long >Assignee: Jason van Zyl > Fix For: 3.1.2 > > > Please change the behaviour of exclusive upper bounds to the following: > In a version range, like [1.7.0,1.8.0), 1.8.0-alpha1 should not be included > in the range. 1.8.0* should not be included in the range. > This allows for us configure natural ranges for projects using semantic > versioning. > Please see: > http://markmail.org/message/4tubas4uok6ahbcp > http://markmail.org/message/s2ry2uru4ibub43q -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5494) Add a license file that corresponds to each GAV in the distribution
[ https://jira.codehaus.org/browse/MNG-5494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5494: --- Fix Version/s: (was: 3.1.1) 3.1.2 > Add a license file that corresponds to each GAV in the distribution > --- > > Key: MNG-5494 > URL: https://jira.codehaus.org/browse/MNG-5494 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.1.0 >Reporter: Jason van Zyl >Assignee: Jason van Zyl > Fix For: 3.1.2 > > > Right now we are not collecting the licenses for each binary artifact in the > distribution. We tentatively decided that we will create a license file per > artifact and include that in the distribution. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5470) Fix license headers on source files
[
https://jira.codehaus.org/browse/MNG-5470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-5470:
---
Fix Version/s: (was: 3.1.1)
3.1.2
> Fix license headers on source files
> ---
>
> Key: MNG-5470
> URL: https://jira.codehaus.org/browse/MNG-5470
> Project: Maven 2 & 3
> Issue Type: Task
> Components: General
>Affects Versions: 3.1.0-alpha-1
>Reporter: Stephen Connolly
>Priority: Blocker
> Fix For: 3.1.2
>
> Attachments: rat.txt
>
>
> RAT is reporting GIT HASH 262b9bb1ef91d1414e5162d9dd0f5522e7186202 has 391
> files that are either missing license headers or have not been flagged as
> files that cannot support a license header.
> Most of these are test data files and I would be happy to argue that the test
> may require a specific exact content for reproducibility, but the following I
> do not feel we can make a case for:
> {code}
> apache-maven/src/bin/m2.conf
> apache-maven/src/conf/logging/simplelogger.properties
>
> maven-aether-provider/src/main/java/org/apache/maven/repository/internal/package.html
> maven-aether-provider/src/site/apt/index.apt
> maven-artifact/src/site/apt/index.apt
> maven-compat/compatibility.cfl
> maven-compat/src/main/resources/META-INF/maven/plugin.xml
> maven-core/lifecycle-executor.txt
> maven-core/plugin-manager.txt
> maven-core/project-builder.txt
> maven-core/src/main/resources/org/apache/maven/messages/build.properties
> maven-core/src/site/apt/artifact-handlers.apt
> maven-core/src/site/apt/configuration-management.apt
> maven-core/src/site/apt/default-bindings.apt.vm
> maven-core/src/site/apt/getting-to-container-configured-mojos.apt
> maven-core/src/site/apt/index.apt
> maven-core/src/site/apt/inheritance.apt
> maven-core/src/site/apt/lifecycles.apt.vm
> maven-core/src/site/apt/offline-mode.apt
> maven-core/src/site/apt/plugin-execution-isolation.apt
> maven-core/src/site/apt/scripting-support/marmalade-support.apt
> maven-core/src/site/resources/design/2.1-lifecycle-refactor.graffle
>
> maven-embedder/src/examples/simple-project/src/main/java/org/apache/maven/embedder/App.java
>
> maven-embedder/src/examples/simple-project/src/test/java/org/apache/maven/embedder/AppTest.java
> maven-embedder/src/main/resources/META-INF/MANIFEST.MF
>
> maven-embedder/src/main/resources/META-INF/maven/slf4j-configuration.properties
> maven-embedder/src/site/apt/cli.apt.vm
> maven-embedder/src/site/apt/index.apt.vm
> maven-embedder/src/site/apt/logging.apt
> maven-model/src/main/java/org/apache/maven/model/io/xpp3/package.html
> maven-model/src/main/java/org/apache/maven/model/merge/package.html
> maven-model/src/main/java/org/apache/maven/model/package.html
> maven-model/src/site/apt/index.apt
> maven-model-builder/src/site/apt/index.apt
> maven-model-builder/src/site/apt/super-pom.apt.vm
> maven-plugin-api/src/site/apt/index.apt
> maven-plugin-api/src/test/resources/plugin.xml
> maven-repository-metadata/src/site/apt/index.apt
> maven-settings/src/site/apt/index.apt
> {code}
> Attached is the full RAT report
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5205) Memory leak in StringSearchModelInterpolator
[
https://jira.codehaus.org/browse/MNG-5205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-5205:
---
Fix Version/s: (was: 3.1.1)
3.1.2
> Memory leak in StringSearchModelInterpolator
>
>
> Key: MNG-5205
> URL: https://jira.codehaus.org/browse/MNG-5205
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.3
>Reporter: Jesse Glick
>Assignee: Kristian Rosenvold
>Priority: Minor
> Fix For: 3.1.2
>
> Attachments: x.diff
>
>
> {{StringSearchModelInterpolator}} abuses {{WeakHashMap}}; the {{Field}}
> values of {{fieldsByClass}} hold hard references to the {{Class}} keys,
> making it useless. Thus if you passed any {{Class}} to it, that class and its
> {{ClassLoader}} and the transitive static graph therefrom would never be
> collectible.
> Anyway a cache is unnecessary, since {{Class}} does its own caching of fields!
> Also removing the ill-conceived {{fieldIsPrimitiveByClass}} - not a memory
> leak, but likely unnecessary complication.
> The class is deprecated anyway, but just in case it is used by someone it
> should be fixed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5389) AbstractMavenLifecycleParticipant need a afterSessionEnd
[ https://jira.codehaus.org/browse/MNG-5389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5389: --- Fix Version/s: (was: 3.1.1) 3.1.2 > AbstractMavenLifecycleParticipant need a afterSessionEnd > > > Key: MNG-5389 > URL: https://jira.codehaus.org/browse/MNG-5389 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Plugins and Lifecycle >Affects Versions: 3.0.4 >Reporter: Olivier Lamy >Assignee: Olivier Lamy > Fix For: 3.1.2 > > > we don't have way to know the build end with > AbstractMavenLifecycleParticipant. > So adding a method afterSessionEnd(MavenSession session) could help -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-2199) Version ranges not supported for parent artifacts
[
https://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl updated MNG-2199:
---
Fix Version/s: (was: 3.1.1)
3.1.2
> Version ranges not supported for parent artifacts
> -
>
> Key: MNG-2199
> URL: https://jira.codehaus.org/browse/MNG-2199
> Project: Maven 2 & 3
> Issue Type: Wish
> Components: Inheritance and Interpolation, POM, Reactor and workspace
>Affects Versions: 2.0.3
>Reporter: Christian Schulte
> Fix For: 3.1.2
>
> Attachments: MNG-2199-3.0.4.patch, MNG-2199-3.0.4.patch,
> MNG-2199-3.1.0-alpha-1.patch, MNG-2199.patch, MNG-2199.patch, MNG-2199.patch,
> MNG-2199.patch, MNG-2199.patch, MNG-2199.patch
>
>
> It would be great if Maven supports version ranges when specifying parent
> artifacts in a multi-module build. Currently this does not work.
>
> artifactId
> groupId
> [2.0, 2.0.1]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> 2.0.1]/artifactId-[2.0, 2.0.1].pom
> Additionally it would be great if this
>
> artifactId
> groupId
> [2.0, ${pom.version}]
>
> [INFO] Scanning for projects...
> Downloading: http://repo1.maven.org/maven2/groupId/artifactId/[2.0,
> ${pom.version}]/artifactId-[2.0, ${pom.version}].pom
> would also work, if the version is specified in the same pom.xml which
> defines this parent definition.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5356) Make encrypt/decrypt logic pluggable
[ https://jira.codehaus.org/browse/MNG-5356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-5356: --- Fix Version/s: (was: 3.1.1) 3.1.2 > Make encrypt/decrypt logic pluggable > > > Key: MNG-5356 > URL: https://jira.codehaus.org/browse/MNG-5356 > Project: Maven 2 & 3 > Issue Type: Improvement > Environment: n/a >Reporter: Anders Hammar >Assignee: Anders Hammar > Fix For: 3.1.2 > > > It would be good if Maven Core facilitated the encryption (and decryption) > logic to be replaceable. Today's solution is very much hard-coded to the > plexus logic. > This would make it possible for enterprise environments to re-use existing > solutions, like for eg smart cards, for this. The default should be the > current implementation though. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
[
https://jira.codehaus.org/browse/MNG-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason van Zyl closed MNG-5495.
--
Resolution: Fixed
> API incompatibility causes Swagger Maven Plugin (and others) to fail under
> Maven 3.1.0
> --
>
> Key: MNG-5495
> URL: https://jira.codehaus.org/browse/MNG-5495
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Brett Porter
>Assignee: Jason van Zyl
> Fix For: 3.1.1
>
>
> {code}
> ERROR] Failed to execute goal
> com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
> maestro-webapp: An API incompatibility was encountered during configuration
> of mojo com.github.kongchen:swagger-maven-plugin:1.1.1:generate:
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
> [ERROR] -
> [ERROR] realm =plugin>com.github.kongchen:swagger-maven-plugin:1.1.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/brett/.m2/repository/com/github/kongchen/swagger-maven-plugin/1.1.1/swagger-maven-plugin-1.1.1.jar
> [ERROR] urls[1] =
> file:/Users/brett/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
[
https://jira.codehaus.org/browse/MNG-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329708#comment-329708
]
Jason van Zyl commented on MNG-5495:
This sample project: https://github.com/kongchen/swagger-maven-plugin
Now runs correctly under 3.1.1-SNAPSHOT so I consider this issue resolved:
bash-3.2$ mvn clean package
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building swagger-maven-example 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ swagger-maven-example
---
[INFO] Deleting /private/tmp/swagger-maven-example/target
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
swagger-maven-example ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/private/tmp/swagger-maven-example/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @
swagger-maven-example ---
[WARNING] File encoding has not been set, using platform encoding UTF-8, i.e.
build is platform dependent!
[INFO] Compiling 5 source files to
/private/tmp/swagger-maven-example/target/classes
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (default) @ swagger-maven-example ---
[INFO] Executing tasks
get markdown.mustache:
[get] Getting:
https://raw.github.com/kongchen/api-doc-template/master/v1.1/markdown.mustache
[get] To: /private/tmp/swagger-maven-example/markdown.mustache
[INFO] Executed tasks
[INFO]
[INFO] --- swagger-maven-plugin:1.1:generate (default) @ swagger-maven-example
---
[INFO] Reflections took 49 ms to scan 1 urls, producing 3 keys and 9 values
[INFO] Class com.foo.bar.model.Garage is not annotated with a @XmlRootElement
annotation, using Garage
[INFO] Class com.foo.bar.model.Garage is not annotated with a @XmlRootElement
annotation, using Garage
[INFO] Class com.foo.bar.model.Garage is not annotated with a @XmlRootElement
annotation, using Garage
[INFO] Detect Resource:com.foo.bar.api.garage.GarageResourceV1
[INFO] Class com.foo.bar.model.Car is not annotated with a @XmlRootElement
annotation, using Car
[INFO] Class com.foo.bar.model.Car is not annotated with a @XmlRootElement
annotation, using Car
[ERROR] Unable to load class float
[ERROR] Unable to resolve class float
[INFO] Class com.foo.bar.model.Car is not annotated with a @XmlRootElement
annotation, using Car
[INFO] Detect Resource:com.foo.bar.api.car.CarResourceV1
[INFO] Class com.foo.bar.model.Car is not annotated with a @XmlRootElement
annotation, using Car
[INFO] Class com.foo.bar.model.Car is not annotated with a @XmlRootElement
annotation, using Car
[ERROR] Unable to resolve class float
[INFO] Detect Resource:com.foo.bar.api.car.CarResourceV2
[INFO] Writing doc to generated/strapdown.html...
[INFO] Done!
[INFO]
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @
swagger-maven-example ---
[WARNING] Using platform encoding (UTF-8 actually) to copy filtered resources,
i.e. build is platform dependent!
[INFO] skip non existing resourceDirectory
/private/tmp/swagger-maven-example/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.3.2:testCompile (default-testCompile) @
swagger-maven-example ---
[INFO] No sources to compile
[INFO]
[INFO] --- maven-surefire-plugin:2.12.4:test (default-test) @
swagger-maven-example ---
[INFO] No tests to run.
[INFO]
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ swagger-maven-example ---
[INFO] Building jar:
/private/tmp/swagger-maven-example/target/swagger-maven-example-1.0-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 4.251s
[INFO] Finished at: Sun Jul 28 12:00:52 EDT 2013
[INFO] Final Memory: 28M/335M
[INFO]
> API incompatibility causes Swagger Maven Plugin (and others) to fail under
> Maven 3.1.0
> --
>
> Key: MNG-5495
> URL: https://jira.codehaus.org/browse/MNG-5495
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Brett Porter
>Assignee: Jason van Zyl
> Fix For: 3.1.1
>
>
> {code}
> ERROR] Failed to execute goal
> com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
> maestro-webapp: An API incompatibility was encountered during configuration
> of mojo com.g
[jira] (MNG-5500) help for --legacy-local-repository option explains _maven.repositories instead of _remote.repositories
Herve Boutemy created MNG-5500: -- Summary: help for --legacy-local-repository option explains _maven.repositories instead of _remote.repositories Key: MNG-5500 URL: https://jira.codehaus.org/browse/MNG-5500 Project: Maven 2 & 3 Issue Type: Bug Components: Command Line Affects Versions: 3.1.0 Reporter: Herve Boutemy Priority: Trivial enhanced tracker file was renamed in MNG-5461 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5500) help for --legacy-local-repository option explains _maven.repositories instead of _remote.repositories
[ https://jira.codehaus.org/browse/MNG-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-5500. -- Resolution: Fixed Fix Version/s: 3.1.1 Assignee: Herve Boutemy fixed in [b83de53e|http://git-wip-us.apache.org/repos/asf/maven/commit/b83de53e] > help for --legacy-local-repository option explains _maven.repositories > instead of _remote.repositories > -- > > Key: MNG-5500 > URL: https://jira.codehaus.org/browse/MNG-5500 > Project: Maven 2 & 3 > Issue Type: Bug > Components: Command Line >Affects Versions: 3.1.0 >Reporter: Herve Boutemy >Assignee: Herve Boutemy >Priority: Trivial > Fix For: 3.1.1 > > > enhanced tracker file was renamed in MNG-5461 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds
[
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329716#comment-329716
]
Karthikeyan Kulasekaran commented on MNG-5315:
--
Please fix this issue as well MNG-5252. This is related to MNG-5315
> Artifact resolution sporadically fails in parallel builds
> -
>
> Key: MNG-5315
> URL: https://jira.codehaus.org/browse/MNG-5315
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.4
>Reporter: Ivan S. Dubrov
>Assignee: Jason van Zyl
>Priority: Minor
>
> Artifact resolution can fail during the parallel build if it was downloaded
> during the same session.
> Scenario:
> 1) Delete the whole Maven local repository.
> 2) Run build "mvn compile -T1.5C"
> 3) Build fails (see log extracts below)
> 4) If I run build again, it succeeds.
> It seems like the problem is due to two thread trying to resolve same
> artifact concurrently. This problem never happens once I have all
> dependencies cached in the local repository.
> Extracts from the log output:
> {noformat}Downloading:
> http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
> 12444/13937 KB ...
> ...
> [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2,
> already updated during this session.
> [DEBUG] Skipped remote update check for
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this
> session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4,
> already updated during this session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4,
> already updated during this session.
> ...
> [ERROR] Failed to execute goal on project util: Could not resolve
> dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The
> following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project util: Could not resolve dependencies for project
> com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not
> be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencie
[jira] (MNG-5097) @parameter using 'property' to allow custom naming convention, throws a NPE if the parameter is defined, but empty.
[
https://jira.codehaus.org/browse/MNG-5097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MNG-5097.
Resolution: Fixed
Fix Version/s: 3.1.0
Was fixed in 3.1.0 (see @mcculls comment)
> @parameter using 'property' to allow custom naming convention, throws a NPE
> if the parameter is defined, but empty.
> ---
>
> Key: MNG-5097
> URL: https://jira.codehaus.org/browse/MNG-5097
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Plugin API
>Affects Versions: 3.0.3
> Environment: Gentoo Linux, amd64, multicore.
>Reporter: rydnr
>Priority: Minor
> Fix For: 3.1.0
>
> Attachments: build.log, empty-string-npe.zip
>
>
> The test case (not JUnit) is attached.
> If a Maven plugin runs within Maven 3.0.3, and defines
> /**
> * @parameter property="abc"
> */
> private String somethingDifferentThanAbc;
> public void setAbc(String value) {
> somethingDifferentThanAbc = value;
> }
> Works for non-empty values:
> abc-value
> But throws a NPE in
> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter:331
>
> (fieldTypeConverter is null) with empty values:
>
> It works in Maven 2.x. It works if you declare the
> property with no naming conventions:
> private String abc;
> As a side note, the plexus classes being used are not the ones declared in
> the pom, but the ones bundled within
> $MAVEN_HOME/lib/sisu-inject-plexus-2.1.1.jar.
> I couldn't find sisu-inject-plexus-2.1.1-sources.jar anywhere, but the
> repository itself is fortunately available at
> https://github.com/sonatype/sisu.git
> And then within
> /sisu-inject/containers/guice-plexus/guice-plexus-shim/src/main/java/
> I could have try to post a patch, but I'm not really sure about why this
> corner case is producing plexus-container's misbehavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
[
https://jira.codehaus.org/browse/MNG-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329724#comment-329724
]
Brett Porter commented on MNG-5495:
---
Yep, works for me too.
> API incompatibility causes Swagger Maven Plugin (and others) to fail under
> Maven 3.1.0
> --
>
> Key: MNG-5495
> URL: https://jira.codehaus.org/browse/MNG-5495
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Brett Porter
>Assignee: Jason van Zyl
> Fix For: 3.1.1
>
>
> {code}
> ERROR] Failed to execute goal
> com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
> maestro-webapp: An API incompatibility was encountered during configuration
> of mojo com.github.kongchen:swagger-maven-plugin:1.1.1:generate:
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
> [ERROR] -
> [ERROR] realm =plugin>com.github.kongchen:swagger-maven-plugin:1.1.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/brett/.m2/repository/com/github/kongchen/swagger-maven-plugin/1.1.1/swagger-maven-plugin-1.1.1.jar
> [ERROR] urls[1] =
> file:/Users/brett/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5495) API incompatibility causes Swagger Maven Plugin (and others) to fail under Maven 3.1.0
[
https://jira.codehaus.org/browse/MNG-5495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329725#comment-329725
]
Jason van Zyl commented on MNG-5495:
Cool.
> API incompatibility causes Swagger Maven Plugin (and others) to fail under
> Maven 3.1.0
> --
>
> Key: MNG-5495
> URL: https://jira.codehaus.org/browse/MNG-5495
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Brett Porter
>Assignee: Jason van Zyl
> Fix For: 3.1.1
>
>
> {code}
> ERROR] Failed to execute goal
> com.github.kongchen:swagger-maven-plugin:1.1.1:generate (default) on project
> maestro-webapp: An API incompatibility was encountered during configuration
> of mojo com.github.kongchen:swagger-maven-plugin:1.1.1:generate:
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.component.configurator.converters.special.ClassRealmConverter.(Lorg/codehaus/classworlds/ClassRealm;)V
> [ERROR] -
> [ERROR] realm =plugin>com.github.kongchen:swagger-maven-plugin:1.1.1
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> [ERROR] urls[0] =
> file:/Users/brett/.m2/repository/com/github/kongchen/swagger-maven-plugin/1.1.1/swagger-maven-plugin-1.1.1.jar
> [ERROR] urls[1] =
> file:/Users/brett/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.15/plexus-utils-1.5.15.jar
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5315) Artifact resolution sporadically fails in parallel builds
[
https://jira.codehaus.org/browse/MNG-5315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=329727#comment-329727
]
Kristian Rosenvold commented on MNG-5315:
-
Can you please re-test with maven 3.1.0 ? The root cause of this issue may be
fixed there.
> Artifact resolution sporadically fails in parallel builds
> -
>
> Key: MNG-5315
> URL: https://jira.codehaus.org/browse/MNG-5315
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.0.4
>Reporter: Ivan S. Dubrov
>Assignee: Jason van Zyl
>Priority: Minor
>
> Artifact resolution can fail during the parallel build if it was downloaded
> during the same session.
> Scenario:
> 1) Delete the whole Maven local repository.
> 2) Run build "mvn compile -T1.5C"
> 3) Build fails (see log extracts below)
> 4) If I run build again, it succeeds.
> It seems like the problem is due to two thread trying to resolve same
> artifact concurrently. This problem never happens once I have all
> dependencies cached in the local repository.
> Extracts from the log output:
> {noformat}Downloading:
> http://nexus/content/repositories/thirdparty/com/googlecode/guava-osgi/guava-osgi/11.0.0/guava-osgi-11.0.0.jar
> 12444/13937 KB ...
> ...
> [DEBUG] Skipped remote update check for commons-cli:commons-cli:jar:1.2,
> already updated during this session.
> [DEBUG] Skipped remote update check for
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0, already updated during this
> session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-api:jar:1.6.4,
> already updated during this session.
> [DEBUG] Skipped remote update check for org.slf4j:slf4j-jdk14:jar:1.6.4,
> already updated during this session.
> ...
> [ERROR] Failed to execute goal on project util: Could not resolve
> dependencies for project com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The
> following artifacts could not be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal on project util: Could not resolve dependencies for project
> com.guidewire.pl:util:bundle:1.0-SNAPSHOT: The following artifacts could not
> be resolved: commons-cli:commons-cli:jar:1.2,
> com.googlecode.guava-osgi:guava-osgi:jar:11.0.0,
> org.slf4j:slf4j-api:jar:1.6.4, org.slf4j:slf4j-jdk14:jar:1.6.4: Failure to
> find commons-cli:commons-cli:jar:1.2 in
> http://nexus/content/repositories/thirdparty was cached in the local
> repository, resolution will not be reattempted until the update interval of
> gw.thirdparty has elapsed or updates are forced
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:210)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:117)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:258)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:201)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:167)
> at
> org.apache.maven.lifecycle.internal.LifecycleThreadedBuilder$1.call(LifecycleThreadedBuilder.java:163)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:662)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resol
