[jira] Commented: (MAVENUPLOAD-2738) JSR330 @Inject TCK (official release) 1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223148#action_223148 ] Christian Ihle commented on MAVENUPLOAD-2738: - Thanks for your help! But the guide at http://maven.apache.org/guides/mini/guide-central-repository-upload.html doesn't mention that developer information is required. All the required fields in that guide are already in the pom. If I sign the artifacts with my own gpg key, would you accept the bundle then? > JSR330 @Inject TCK (official release) 1 > --- > > Key: MAVENUPLOAD-2738 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2738 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Paul Hammant >Assignee: Juven Xu > > I'm a commtter, I just uploaded the tck jar to the GoogleCode downloads page > for that project. > paul / codehaus == PaulHammant / GoogleCode. -- 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: (MNG-4692) Maven choose the wrong transitive dependency
[
http://jira.codehaus.org/browse/MNG-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-4692.
--
Resolution: Not A Bug
Assignee: Benjamin Bentmann
As documented in [Introduction to the Dependency
Mechanism|http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html],
conflict resolution uses a "nearest wins" strategy, not the newest version.
The relevant piece of the dependency tree for adam-services:
{noformat}
[INFO] rcpers:adam-services:jar:2.2-SNAPSHOT
...
[INFO] +- apireg:apireg:jar:2.13.0:compile
[INFO] | +- org.springframework:spring-core:jar:2.5.5:compile
...
[INFO] +- rcpers:rcpers-core:jar:2.2-SNAPSHOT:compile
[INFO] | +- org.springframework:spring-aop:jar:2.5.6.SEC01:compile
{noformat}
spring-core is a direct dependency of apireg and rcpers-core and since apireg
comes before rcpers-core in the dependency tree, its version of spring-core
wins the conflict resolution.
If the default conflict resolution doesn't work you, you can use
dependencyManagement inside the adam-services POM to enforce specific versions
of transitive dependencies.
> Maven choose the wrong transitive dependency
>
>
> Key: MNG-4692
> URL: http://jira.codehaus.org/browse/MNG-4692
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: Inheritance and Interpolation
>Affects Versions: 2.2.1
> Environment: Ubuntu Linux, JVM 1.6.0_18 OpenJdk
>Reporter: Jean-Eric Cuendet
>Assignee: Benjamin Bentmann
> Attachments: bugmaven.tar.gz
>
>
> I have a dependency used by 2 sub-projects (spring-core) but with 2 different
> versions (2.5.5 and 2.5.6.SEC01)
> My project which uses theses 2 sub-projects gets spring-core 2.5.5 instead of
> the more recent 2.5.6.SEC01
> I attach a test project which illustrates this case.
> To reproduce:
> 1. untar proj.tar.gz
> 2. Run ./build.sh
> 3. Have a look at the xxx-tree.log generated files
> The dep for apireg is 2.5.5 -> OK
> The dep for rcpers-core is 2.5.6.SEC01 -> OK
> The dep for adam-services is 2.5.5 -> NOK (Should be 2.5.6.SEC01 since it
> depends on rcpers-core)
--
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: (MAVENUPLOAD-2738) JSR330 @Inject TCK (official release) 1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223156#action_223156 ] Paul Hammant commented on MAVENUPLOAD-2738: --- I've just been through the learning curve for gpg signing for mockpico, I'll give it another go. > JSR330 @Inject TCK (official release) 1 > --- > > Key: MAVENUPLOAD-2738 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2738 > Project: Maven Upload Requests > Issue Type: Wish >Reporter: Paul Hammant >Assignee: Juven Xu > > I'm a commtter, I just uploaded the tck jar to the GoogleCode downloads page > for that project. > paul / codehaus == PaulHammant / GoogleCode. -- 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: (MAVENUPLOAD-2784) com.browseengine.bobo:bobo-browse 2.0.7
com.browseengine.bobo:bobo-browse 2.0.7 --- Key: MAVENUPLOAD-2784 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2784 Project: Maven Upload Requests Issue Type: Wish Reporter: fabrizio giustina bundle contains binary jar, sources and javadoc -- 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: (MRELEASE-414) NullPointerException at DefaultVersionInfo.java line 122
[ http://jira.codehaus.org/browse/MRELEASE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223171#action_223171 ] Bruno Medeiros commented on MRELEASE-414: - I got the same error on maven 2.0.10, 2.0.11 and 2.2.1. My dependency declaration omits the version number, that is in the dependency management of parent pom, declared as a range. I think this bug should be reopened. Snnipets: dep: br.com.company jcompany_util parent: ... br.com.company jcompany_util [1.0.0,2.0.0) Stack: [INFO] Trace java.lang.NullPointerException at java.util.regex.Matcher.getTextLength(Matcher.java:1140) at java.util.regex.Matcher.reset(Matcher.java:291) at java.util.regex.Matcher.(Matcher.java:211) at java.util.regex.Pattern.matcher(Pattern.java:888) at org.apache.maven.shared.release.versions.DefaultVersionInfo.(DefaultVersionInfo.java:123) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.processSnapshot(CheckDependencySnapshotsPhase.java:399) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.resolveSnapshots(CheckDependencySnapshotsPhase.java:346) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.checkProject(CheckDependencySnapshotsPhase.java:228) at org.apache.maven.shared.release.phase.CheckDependencySnapshotsPhase.execute(CheckDependencySnapshotsPhase.java:107) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:196) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:133) at org.apache.maven.shared.release.DefaultReleaseManager.prepare(DefaultReleaseManager.java:96) at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:161) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:513) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:228) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:345) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:132) at org.apache.maven.cli.MavenCli.main(MavenCli.java:290) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > NullPointerException at DefaultVersionInfo.java line 122 > > > Key: MRELEASE-414 > URL: http://jira.codehaus.org/browse/MRELEASE-414 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-8 > Environment: Windows XP Home SP3 > JDK 1.6.0_11 >Reporter: Markus KARG >Priority: Blocker > Attachments: pom.xml > > > mvn release:prepare produces NullPointerException: > C:\addressbook>mvn release:prepare > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'release'. > WAGON_VERSION: 1.0-beta-2 > [INFO] > > [INFO] Building WebDAV Support for JAX-RS Address-Book Sample > [INFO]task-segment: [release:prepare] (aggregator-style) > [INFO] > > [INFO] [release:prepare] > [INFO] Resuming release from phase 'check-dependency-snapshots' > [INFO] Checking dependencies and plugins for snapshots ... > There are still so
[jira] Created: (MNG-4693) add a dependency graph with image map to navigate easily to modules
add a dependency graph with image map to navigate easily to modules --- Key: MNG-4693 URL: http://jira.codehaus.org/browse/MNG-4693 Project: Maven 2 & 3 Issue Type: Improvement Components: Documentation: General Affects Versions: 3.0-beta-1 Reporter: Herve Boutemy like already done for [Doxia|http://maven.apache.org/doxia/doxia/], [Doxia Sitetools|http://maven.apache.org/doxia/doxia-sitetools/], [Mercury|http://maven.apache.org/mercury/] or [Modello|http://modello.codehaus.org/]. -- 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: (MNG-4693) add a dependency graph with image map to navigate easily to modules
[ http://jira.codehaus.org/browse/MNG-4693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed MNG-4693. -- Resolution: Fixed Fix Version/s: 3.0-beta-2 Assignee: Herve Boutemy done in [r949572|http://svn.apache.org/viewvc?view=revision&revision=949572] > add a dependency graph with image map to navigate easily to modules > --- > > Key: MNG-4693 > URL: http://jira.codehaus.org/browse/MNG-4693 > Project: Maven 2 & 3 > Issue Type: Improvement > Components: Documentation: General >Affects Versions: 3.0-beta-1 >Reporter: Herve Boutemy >Assignee: Herve Boutemy > Fix For: 3.0-beta-2 > > > like already done for [Doxia|http://maven.apache.org/doxia/doxia/], [Doxia > Sitetools|http://maven.apache.org/doxia/doxia-sitetools/], > [Mercury|http://maven.apache.org/mercury/] or > [Modello|http://modello.codehaus.org/]. -- 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: (MNG-4694) extractor for language: ant fails to detect Ant mojos
extractor for language: ant fails to detect Ant mojos - Key: MNG-4694 URL: http://jira.codehaus.org/browse/MNG-4694 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0-beta-1 Environment: Any Reporter: Kaizer Sogiawala Using simple project to develop Ant plugins described at- http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html I noticed the maven-plugin-plugin/Extractor is not able to detect any Ant mojos. This same example works fine in mvn-2.2.1 --- SNIP --- [INFO] --- maven-plugin-plugin:2.3:descriptor (default-descriptor) @ maven-javac-plugin --- [WARNING] Goal prefix is: javac; Maven currently expects it to be javac [INFO] Using 3 extractors. [INFO] Applying extractor for language: java [INFO] Extractor for language: java found 0 mojo descriptors. [INFO] Applying extractor for language: ant [INFO] Extractor for language: ant found 0 mojo descriptors. [INFO] Applying extractor for language: bsh [INFO] Extractor for language: bsh found 0 mojo descriptors. --- SNIP --- $ mvn -v Apache Maven 3.0-beta-1 (r935667; 2010-04-19 10:00:39-0700) Java version: 1.6.0_20 Java home: /opt/jdk1.6.0_20/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux" version: "2.6.32-21-generic-pae" arch: "i386" Family: "unix" -- 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-4694) extractor for language: ant fails to detect Ant mojos
[ http://jira.codehaus.org/browse/MNG-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223183#action_223183 ] Kaizer Sogiawala commented on MNG-4694: --- Updating the dependencies (maven-script-ant and maven-plugin-tools-ant) and maven-plugin-plugin to current versions resolved this issue. This issue can be closed. org.apache.maven maven-script-ant 2.2.1 src/main/scripts org.apache.maven.plugins maven-plugin-plugin 2.6 org.apache.maven.plugin-tools maven-plugin-tools-ant 2.6 javac > extractor for language: ant fails to detect Ant mojos > - > > Key: MNG-4694 > URL: http://jira.codehaus.org/browse/MNG-4694 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-1 > Environment: Any >Reporter: Kaizer Sogiawala > > Using simple project to develop Ant plugins described at- > http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html > I noticed the maven-plugin-plugin/Extractor is not able to detect any Ant > mojos. This same example works fine in mvn-2.2.1 > --- SNIP --- > [INFO] --- maven-plugin-plugin:2.3:descriptor (default-descriptor) @ > maven-javac-plugin --- > [WARNING] Goal prefix is: javac; Maven currently expects it to be javac > [INFO] Using 3 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 0 mojo descriptors. > [INFO] Applying extractor for language: ant > [INFO] Extractor for language: ant found 0 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > --- SNIP --- > $ mvn -v > Apache Maven 3.0-beta-1 (r935667; 2010-04-19 10:00:39-0700) > Java version: 1.6.0_20 > Java home: /opt/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-21-generic-pae" arch: "i386" Family: "unix" -- 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: (MNG-4694) extractor for language: ant fails to detect Ant mojos
[ http://jira.codehaus.org/browse/MNG-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kaizer Sogiawala closed MNG-4694. - Resolution: Not A Bug Fix Version/s: 3.0-beta-1 The plugin works as specified in the documentation for 2.x. > extractor for language: ant fails to detect Ant mojos > - > > Key: MNG-4694 > URL: http://jira.codehaus.org/browse/MNG-4694 > Project: Maven 2 & 3 > Issue Type: Bug >Affects Versions: 3.0-beta-1 > Environment: Any >Reporter: Kaizer Sogiawala > Fix For: 3.0-beta-1 > > > Using simple project to develop Ant plugins described at- > http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html > I noticed the maven-plugin-plugin/Extractor is not able to detect any Ant > mojos. This same example works fine in mvn-2.2.1 > --- SNIP --- > [INFO] --- maven-plugin-plugin:2.3:descriptor (default-descriptor) @ > maven-javac-plugin --- > [WARNING] Goal prefix is: javac; Maven currently expects it to be javac > [INFO] Using 3 extractors. > [INFO] Applying extractor for language: java > [INFO] Extractor for language: java found 0 mojo descriptors. > [INFO] Applying extractor for language: ant > [INFO] Extractor for language: ant found 0 mojo descriptors. > [INFO] Applying extractor for language: bsh > [INFO] Extractor for language: bsh found 0 mojo descriptors. > --- SNIP --- > $ mvn -v > Apache Maven 3.0-beta-1 (r935667; 2010-04-19 10:00:39-0700) > Java version: 1.6.0_20 > Java home: /opt/jdk1.6.0_20/jre > Default locale: en_US, platform encoding: UTF-8 > OS name: "linux" version: "2.6.32-21-generic-pae" arch: "i386" Family: "unix" -- 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-4694) extractor for language: ant fails to detect Ant mojos
[
http://jira.codehaus.org/browse/MNG-4694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=223183#action_223183
]
Kaizer Sogiawala edited comment on MNG-4694 at 5/30/10 11:06 PM:
-
Updating the dependencies (maven-script-ant and maven-plugin-tools-ant) and
maven-plugin-plugin to current versions resolved this issue. This issue can be
closed.
{noformat}
org.apache.maven
maven-script-ant
2.2.1
src/main/scripts
org.apache.maven.plugins
maven-plugin-plugin
2.6
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.6
javac
{noformat}
was (Author: kaizers):
Updating the dependencies (maven-script-ant and maven-plugin-tools-ant) and
maven-plugin-plugin to current versions resolved this issue. This issue can be
closed.
org.apache.maven
maven-script-ant
2.2.1
src/main/scripts
org.apache.maven.plugins
maven-plugin-plugin
2.6
org.apache.maven.plugin-tools
maven-plugin-tools-ant
2.6
javac
> extractor for language: ant fails to detect Ant mojos
> -
>
> Key: MNG-4694
> URL: http://jira.codehaus.org/browse/MNG-4694
> Project: Maven 2 & 3
> Issue Type: Bug
>Affects Versions: 3.0-beta-1
> Environment: Any
>Reporter: Kaizer Sogiawala
> Fix For: 3.0-beta-1
>
>
> Using simple project to develop Ant plugins described at-
> http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html
> I noticed the maven-plugin-plugin/Extractor is not able to detect any Ant
> mojos. This same example works fine in mvn-2.2.1
> --- SNIP ---
> [INFO] --- maven-plugin-plugin:2.3:descriptor (default-descriptor) @
> maven-javac-plugin ---
> [WARNING] Goal prefix is: javac; Maven currently expects it to be javac
> [INFO] Using 3 extractors.
> [INFO] Applying extractor for language: java
> [INFO] Extractor for language: java found 0 mojo descriptors.
> [INFO] Applying extractor for language: ant
> [INFO] Extractor for language: ant found 0 mojo descriptors.
> [INFO] Applying extractor for language: bsh
> [INFO] Extractor for language: bsh found 0 mojo descriptors.
> --- SNIP ---
> $ mvn -v
> Apache Maven 3.0-beta-1 (r935667; 2010-04-19 10:00:39-0700)
> Java version: 1.6.0_20
> Java home: /opt/jdk1.6.0_20/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-21-generic-pae" arch: "i386" Family: "unix"
--
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
