[jira] Created: (MAVENUPLOAD-1283) jsap-2.1
jsap-2.1 Key: MAVENUPLOAD-1283 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1283 Project: maven-upload-requests Issue Type: Task Reporter: David Bernard I need to publish jsap (before publishing spoon library http://spoon.gforge.inria.fr) -- 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-2711) Maven cannot share properties with other tools (e.g. ant)
Maven cannot share properties with other tools (e.g. ant) - Key: MNG-2711 URL: http://jira.codehaus.org/browse/MNG-2711 Project: Maven 2 Issue Type: Improvement Components: POM, Profiles, Settings Affects Versions: 2.0.4 Reporter: Aaron Digulla I have a project which is built with Ant *and* Maven. It installs/deploys a set of third party JARs to our inhouse repository. Basically, I'm using Ant to invoke Maven several times to install each JAR. In Ant, I can export the properties to a file but maven can't do this. Therefore, I have to define all properties at least twice. I suggest to add a new element propertyFiles to the POM, Profiles and settings.xml where you can specify a list of files to be read. If a property is defined twice, the latest definition should win (unlike Ant), so you can control the properties using profiles. -- 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: (MIDEA-82) [Patch] EJB module packaging is not generated correctly, and also does not support EJB 3.0
[Patch] EJB module packaging is not generated correctly, and also does not support EJB 3.0 -- Key: MIDEA-82 URL: http://jira.codehaus.org/browse/MIDEA-82 Project: Maven 2.x Idea Plugin Issue Type: Bug Affects Versions: 2.0, 2.1 Environment: All Reporter: Arik Kfir Priority: Critical Attachments: MEJB-ejb3_and_ejb_deployment.patch When the plugin generates an IML for a module of EJB packaging, IDEA's Ejb Module Settings section is not generated correctly. The dependencies themselves are generated fine, but the settings for how they are deployed is wrong. Each EJB module in IDEA has an EJB Module Settings tab where each of the EJB module's dependencies is configured for deployment (link via manifest, target directory in the EAR, etc). Currently, the plugin specifies WEB-INF/classes as the target directory for each dependency, which is obviously wrong. Attached is a patch which does: 1. Adds the ideaVersion parameter to the IdeaModuleMojo. This is needed so that the name attribute of a module is not added to it in IDEA 6.x (other version will receive it as before) 2. Extracts the ejbVersion parameter from the maven-ejb-plugin configuration in the pom (if present). If not available, defaults to 2.x as before. If present and equals 3.0, will mark the ejb-jar.xml as such and make it optional (as the ejb spec specified). 3. Fixes EJB deployment directory for ejb modules' dependencies from /WEB-INF/classes to /lib/artifact-id.jar. This is consistent with the JEE spec. 4. Adds the missing url element for each dependency of EJB modules, pointing to the local repo. 5. Adds a new method getJarUrl which accepts a File instance and returns an IDEA-style URL (jar://myjar!/) and modified the getLibraryUrl method to use the new method. This was required for cases when you don't have an Artifact instance in hand. 6. In IdeaMojo, pass ideaVersion to the IdeaModuleMojo instance (see 1) 7. Updates IdeaModuleTest.java to accomodate new changes -- 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: (MASSEMBLY-118) assembly files uses maven parent relative path and not the modules relative path
[ http://jira.codehaus.org/browse/MASSEMBLY-118?page=all ]
Kenney Westerhof closed MASSEMBLY-118.
--
Resolution: Fixed
with the latest HEAD of the assembly plugin, this problem cannot be reproduced.
I recognize that it indeed
was a problem, that why it's not 'closed - cannot reproduce'.
Committed the JUnit tests patch (with attribution) in revision 489633.
(Minor change: removed the unused imports).
assembly files uses maven parent relative path and not the modules relative
path
--
Key: MASSEMBLY-118
URL: http://jira.codehaus.org/browse/MASSEMBLY-118
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Baerrach bonDierne
Assigned To: Kenney Westerhof
Fix For: 2.2
Attachments: MASSEMBLY-118-patch.txt, MASSEMBLY-118-patch.txt,
MASSEMBLY-118-patch.txt, MASSEMBLY-118-patch.txt, Maven Assembly Bug.zip
In mvn 2.0.4 if I have an assemly descriptor that has the following:
files
file
sourcesrc/site/apt/index.apt/source
outputDirectory/outputDirectory
destNameREADME.txt/destName
/file
/files
and a maven project that looks like:
Maven Assembly Bug
- pom.xml
- assembly-bug-module
- pom.xml
- src/site/apt/index.apt
with the assembly:assembly bound to the package phase inside
assembly-bug-module/pom.xml as
build
plugins
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
idpackage-assembly/id
phasepackage/phase
goals
goalassembly/goal
/goals
configuration
descriptors
descriptor
src/main/assembly/bin.xml
/descriptor
/descriptors
/configuration
/execution
/executions
/plugin
then when I run mvn install inside assembly-bug-module:
assembly-bug-module mvn install
the command works fine
When I run mvn install inside the Maven Assembly Bug directory the command
will fail
Maven Assembly Bug mvn install
[INFO] [assembly:assembly {execution: package-assembly}]
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error adding file to archive: path\Maven Assembly
Bug\src\site\apt\index.apt isn't a file.
Example project is attached as a zip file.
Trying to change the descriptor to use ${project.build.sourceDirectory} does
not work as this is not resoolved.
[INFO] Error adding file to archive: path\Maven Assembly
Bug\assembly-bug-module\${project.build.sourceDirectory}
\site\apt\index.apt isn't a file.
--
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] Work started: (MRM-261) Repository conversion is not working in central repo
[ http://jira.codehaus.org/browse/MRM-261?page=all ] Work on MRM-261 started by Carlos Sanchez. Repository conversion is not working in central repo Key: MRM-261 URL: http://jira.codehaus.org/browse/MRM-261 Project: Archiva Issue Type: Bug Components: repository-converter Affects Versions: 1.0 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Priority: Critical Several synced projects are not being converted: All org.apache.ant http://repo1.maven.org/maven/org.apache.ant/ http://repo1.maven.org/maven2-converted-from-maven1/org/apache/ant/ groovy-1.0-RC-01 http://repo1.maven.org/maven/groovy/jars/ http://repo1.maven.org/maven2-converted-from-maven1/groovy/groovy -- 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: (MEV-477) stax:stax:1.2.0 pom is missing
stax:stax:1.2.0 pom is missing -- Key: MEV-477 URL: http://jira.codehaus.org/browse/MEV-477 Project: Maven Evangelism Issue Type: Bug Components: Missing POM Reporter: Emmanuel Venisse -- 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: (MEV-477) stax:stax:1.2.0 pom is missing
[ http://jira.codehaus.org/browse/MEV-477?page=all ] Emmanuel Venisse updated MEV-477: - Attachment: stax-1.2.0.pom I attached a pom created from the previous version stax:stax:1.2.0 pom is missing -- Key: MEV-477 URL: http://jira.codehaus.org/browse/MEV-477 Project: Maven Evangelism Issue Type: Bug Components: Missing POM Reporter: Emmanuel Venisse Attachments: stax-1.2.0.pom -- 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: (MRM-143) improve error reporting on corrupt jars, poms, etc
[ http://jira.codehaus.org/browse/MRM-143?page=comments#action_83245 ] Carlos Sanchez commented on MRM-143: Deleting the health-report it seems to work /maven2-converted-from-maven1/.reports/health-report.xml improve error reporting on corrupt jars, poms, etc -- Key: MRM-143 URL: http://jira.codehaus.org/browse/MRM-143 Project: Archiva Issue Type: Improvement Components: indexing Reporter: Brett Porter Assigned To: Brett Porter Fix For: 1.0 currently, many failures can be detected during indexing but none are reported anywhere other than the logs. Either these need to be sent through the regular reporting mechanism, or the regular reporting mechanism needs to be able to come back later and pick up the same issues. -- 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: (MRM-143) improve error reporting on corrupt jars, poms, etc
[ http://jira.codehaus.org/browse/MRM-143?page=all ] Carlos Sanchez updated MRM-143: --- Comment: was deleted improve error reporting on corrupt jars, poms, etc -- Key: MRM-143 URL: http://jira.codehaus.org/browse/MRM-143 Project: Archiva Issue Type: Improvement Components: indexing Reporter: Brett Porter Assigned To: Brett Porter Fix For: 1.0 currently, many failures can be detected during indexing but none are reported anywhere other than the logs. Either these need to be sent through the regular reporting mechanism, or the regular reporting mechanism needs to be able to come back later and pick up the same issues. -- 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: (MRM-261) Repository conversion is not working in central repo
[ http://jira.codehaus.org/browse/MRM-261?page=comments#action_83246 ] Carlos Sanchez commented on MRM-261: Caused by an OOM exception reading the health report Deleting it seems to work /maven2-converted-from-maven1/.reports/health-report.xml Underlying problem is that errors are always added to the report, creating duplicated entries that make it grow exponentially Repository conversion is not working in central repo Key: MRM-261 URL: http://jira.codehaus.org/browse/MRM-261 Project: Archiva Issue Type: Bug Components: repository-converter Affects Versions: 1.0 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Priority: Critical Several synced projects are not being converted: All org.apache.ant http://repo1.maven.org/maven/org.apache.ant/ http://repo1.maven.org/maven2-converted-from-maven1/org/apache/ant/ groovy-1.0-RC-01 http://repo1.maven.org/maven/groovy/jars/ http://repo1.maven.org/maven2-converted-from-maven1/groovy/groovy -- 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-2225) Classloader problem when adding jars to M2_HOME
[ http://jira.codehaus.org/browse/MNG-2225?page=comments#action_83247 ]
Kenney Westerhof commented on MNG-2225:
---
It would be better if mojo dependencies took precedence over those in the core
realm, especially with all the plexus-utils problems.
Mojo's should be able to use any component version they desire. Only core
components api's that are already used by the maven
core should take precedence; in this case only maven-project, maven-plugin-api
and possibly maven-artifact; the rest is not needed
and can be replaced by custom versions used by mojo's.
it comes down to limiting items in mojo's parent classloader to ONLY the
interfaces/instances that maven core uses and cannot
be replaced. These are: (amongst others):
* MavenProject
* ArtifactFactory
* ArtifactResolution stuff
this list should be as small as possible - no implementations whatsoever should
be exported to mojo's.
Here's the current list:
|| Loc || Artifact || Export to Mojo ||
| core/ |plexus-component-api-1.0-alpha-13.jar | (-) |
| core/ |plexus-container-default-1.0-alpha-14.jar| (-) |
| core/ |plexus-utils-1.1.jar| (-) |
| core/boot | plexus-classworlds-1.2-alpha-5.jar| (-) |
| lib/ |commons-cli-1.0.jar | (-) |
| lib/ |doxia-sink-api-1.0-alpha-9-20061107.221350-3.jar | (-) |
| lib/ |jsch-0.1.27.jar | (-) |
| lib/ |jtidy-4aug2000r7-dev.jar | (-) |
| lib/ |maven-artifact-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-artifact-manager-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-cli-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-core-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-embedder-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-error-diagnostics-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-model-2.1-SNAPSHOT.jar | (+) |
| lib/ |maven-monitor-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-plugin-api-2.1-SNAPSHOT.jar | (+) |
| lib/ |maven-plugin-descriptor-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-plugin-parameter-documenter-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-plugin-registry-2.1-SNAPSHOT.jar | (?) |
| lib/ |maven-profile-2.1-SNAPSHOT.jar | (?) |
| lib/ |maven-project-2.1-SNAPSHOT.jar | (+) |
| lib/ |maven-reporting-api-2.1-SNAPSHOT.jar | (+) |
| lib/ |maven-repository-metadata-2.1-SNAPSHOT.jar | (-) |
| lib/ |maven-settings-2.1-SNAPSHOT.jar | (?) |
| lib/ |maven-tools-2.1-SNAPSHOT.jar | (?) |
| lib/ |plexus-interactivity-api-1.0-alpha-4.jar | (-) |
| lib/ |wagon-file-1.0-beta-2.jar | (-) |
| lib/ |wagon-http-lightweight-1.0-beta-2.jar | (-) |
| lib/ |wagon-http-shared-1.0-beta-2.jar | (-) |
| lib/ |wagon-provider-api-1.0-beta-2.jar | (?) |
| lib/ |wagon-ssh-1.0-beta-2.jar | (-) |
| lib/ |wagon-ssh-common-1.0-beta-2.jar | (-) |
| lib/ |wagon-ssh-external-1.0-beta-2.jar | (-) |
| lib/ |xml-apis-1.0.b2.jar | (-) |
So basically everything that's maven-version specific - only APIs, modello
models and in this case also MavenProject since it
contains the runtime project representation.
I think this is easily solved by updating the m2.conf and add another
classloader.
Classloader problem when adding jars to M2_HOME
---
Key: MNG-2225
URL: http://jira.codehaus.org/browse/MNG-2225
Project: Maven 2
Issue Type: Bug
Components: Dependencies
Affects Versions: 2.0.4
Reporter: Carlos Sanchez
Priority: Critical
Fix For: 2.1
Attachments: testwagonscm.tgz
Added these jars to M2_HOME/custom to allow using scm based remote repos
http://www.ibiblio.org/maven2/org/apache/maven/scm/maven-scm-api/1.0-beta-2/maven-scm-api-1.0-beta-2.jar
http://www.ibiblio.org/maven2/org/apache/maven/scm/maven-scm-manager-plexus/1.0-beta-2/maven-scm-manager-plexus-1.0-beta-2.jar
http://www.ibiblio.org/maven2/org/apache/maven/scm/maven-scm-provider-svn/1.0-beta-2/maven-scm-provider-svn-1.0-beta-2.jar
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/wagon/wagon-scm/1.0-alpha-7-SNAPSHOT/wagon-scm-1.0-alpha-7-20060308.183410-3.jar
bin/m2.conf
main is org.apache.maven.cli.MavenCli from plexus.core.maven
set maven.home default ${user.home}/m2
[plexus.core]
load ${maven.home}/core/*.jar
[plexus.core.maven]
load ${maven.home}/custom/*.jar
load ${maven.home}/lib/*.jar
When running mvn install and mvn testwagonscm:test in the attached test
case you get a ClassCastException although the Class to assign to and the
assigned one are the same. The problem seems to be that they come from
different classloaders. This problem makes the project-info-report:scm goal
fail.
--
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: (MPH-20) help:dependencies not consistent with maven core's dependency tree
help:dependencies not consistent with maven core's dependency tree
--
Key: MPH-20
URL: http://jira.codehaus.org/browse/MPH-20
Project: Maven 2.x Help Plugin
Issue Type: Bug
Affects Versions: 2.1
Reporter: Kenney Westerhof
This plugin applies dependencyManagement to transitive dependencies (which is
really what I want),
but maven itself does not.
For instance, mvn help:dependencies on sandbox/maven-plug-it-plugin lists:
{noformat}
[INFO] org.apache.maven.plugins:maven-plug-it-plugin:maven-plugin:1.0-SNAPSHOT
[INFO]junit:junit:jar:3.8.1:test
[INFO]org.apache.maven.shared:file-management:jar:1.1:compile
[INFO] org.apache.maven.shared:maven-shared-io:jar:1.0:compile
[INFO]org.apache.maven:maven-settings:jar:2.0:compile
[INFO]org.apache.maven:maven-plugin-api:jar:2.0.4:compile
[INFO]
org.apache.maven.shared:maven-test-tools:jar:1.0-20061102.004837-1:test
[INFO] easymock:easymock:jar:1.2_Java1.3:test
[INFO]org.codehaus.plexus:plexus-velocity:jar:1.1.3:compile
[INFO]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:compile
[INFO] commons-collections:commons-collections:jar:2.0:compile
[INFO] velocity:velocity:jar:1.4:compile
[INFO] velocity:velocity-dep:jar:1.4:runtime
[INFO]
org.apache.maven.shared:maven-plugin-testing-tools:jar:1.0-alpha-2-20061221.044609-6:compile
[INFO] org.apache.maven:maven-model:jar:2.0:compile
[INFO]
org.apache.maven.shared:maven-repository-builder:jar:1.0-alpha-1:compile
[INFO] org.apache.maven:maven-artifact-manager:jar:2.0:compile
[INFO] org.apache.maven:maven-project:jar:2.0:compile
[INFO]
org.apache.maven.shared:maven-common-artifact-filters:jar:1.0-alpha-1:compile
[INFO] org.apache.maven:maven-artifact:jar:2.0:compile
[INFO] org.apache.maven.shared:maven-invoker:jar:2.0.5:compile
[INFO] org.codehaus.plexus:plexus-utils:jar:1.0.4:compile
[INFO] org.apache.maven:maven-monitor:jar:2.0:compile
{noformat}
Adding 'dependencyManagement' for plexus-utils to force it to 1.1 (which
doesn't work in m2 itself), it lists:
{noformat}
[INFO] org.apache.maven.plugins:maven-plug-it-plugin:maven-plugin:1.0-SNAPSHOT
[INFO]junit:junit:jar:3.8.1:test
[INFO]org.apache.maven.shared:file-management:jar:1.1:compile
[INFO] org.codehaus.plexus:plexus-utils:jar:1.1:compile
[INFO] org.apache.maven.shared:maven-shared-io:jar:1.0:compile
[INFO]org.apache.maven:maven-settings:jar:2.0:compile
[INFO]org.apache.maven:maven-plugin-api:jar:2.0.4:compile
[INFO]
org.apache.maven.shared:maven-test-tools:jar:1.0-20061102.004837-1:test
[INFO] easymock:easymock:jar:1.2_Java1.3:test
[INFO]org.codehaus.plexus:plexus-velocity:jar:1.1.3:compile
[INFO]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-9:compile
[INFO] commons-collections:commons-collections:jar:2.0:compile
[INFO] velocity:velocity:jar:1.4:compile
[INFO] velocity:velocity-dep:jar:1.4:runtime
[INFO]
org.apache.maven.shared:maven-plugin-testing-tools:jar:1.0-alpha-2-20061221.044609-6:compile
[INFO] org.apache.maven:maven-model:jar:2.0:compile
[INFO]
org.apache.maven.shared:maven-repository-builder:jar:1.0-alpha-1:compile
[INFO] org.apache.maven:maven-artifact-manager:jar:2.0:compile
[INFO] org.apache.maven:maven-project:jar:2.0:compile
[INFO]
org.apache.maven.shared:maven-common-artifact-filters:jar:1.0-alpha-1:compile
[INFO] org.apache.maven:maven-artifact:jar:2.0:compile
[INFO] org.apache.maven.shared:maven-invoker:jar:2.0.5:compile
[INFO] org.apache.maven:maven-monitor:jar:2.0:compile
{noformat}
Either we say this is the desired behavior (+1), or MNG-1577 should be fixed.
The problem here is that if MNG-1577 is going for the
if-pom-version-is-this-then-do-that-otherwise-do-that,
this plugin should exhibit the same behaviour.
I'd like both maven core and this plugin to use the same dependency resolution
code, or drop
the dependency-tree code and use maven's internal dependency graph (which
doesn't exist yet).
--
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: (MRM-262) Reporting adds duplicated entries on each run
Reporting adds duplicated entries on each run - Key: MRM-262 URL: http://jira.codehaus.org/browse/MRM-262 Project: Archiva Issue Type: Bug Components: reporting Affects Versions: 1.0 Reporter: Carlos Sanchez The health report adds new entries every time it runs, although they already exist warnings warning reason=The artifact had no POM in the source repository. / warning reason=The artifact had no POM in the source repository. / /warnings -- 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: (MRM-262) Reporting adds duplicated entries on each run
[ http://jira.codehaus.org/browse/MRM-262?page=all ] Carlos Sanchez closed MRM-262. -- Assignee: Carlos Sanchez Resolution: Fixed Fix Version/s: 1.0 Reporting adds duplicated entries on each run - Key: MRM-262 URL: http://jira.codehaus.org/browse/MRM-262 Project: Archiva Issue Type: Bug Components: reporting Affects Versions: 1.0 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Fix For: 1.0 The health report adds new entries every time it runs, although they already exist warnings warning reason=The artifact had no POM in the source repository. / warning reason=The artifact had no POM in the source repository. / /warnings -- 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: (MRM-261) Repository conversion is not working in central repo
[ http://jira.codehaus.org/browse/MRM-261?page=all ] Carlos Sanchez closed MRM-261. -- Resolution: Fixed Fix Version/s: 1.0 Latest snapshot of archiva-cli has been deployed to maven-meeper in maven.org Repository conversion is not working in central repo Key: MRM-261 URL: http://jira.codehaus.org/browse/MRM-261 Project: Archiva Issue Type: Bug Components: repository-converter Affects Versions: 1.0 Reporter: Carlos Sanchez Assigned To: Carlos Sanchez Priority: Critical Fix For: 1.0 Several synced projects are not being converted: All org.apache.ant http://repo1.maven.org/maven/org.apache.ant/ http://repo1.maven.org/maven2-converted-from-maven1/org/apache/ant/ groovy-1.0-RC-01 http://repo1.maven.org/maven/groovy/jars/ http://repo1.maven.org/maven2-converted-from-maven1/groovy/groovy -- 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: (MECLIPSE-210) version 0.9 cannot run under eclipse 3.2.1 and 3.2 and 3.1 and Together 2006 R2!!!
version 0.9 cannot run under eclipse 3.2.1 and 3.2 and 3.1 and Together 2006 R2!!! -- Key: MECLIPSE-210 URL: http://jira.codehaus.org/browse/MECLIPSE-210 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: PDE support Environment: Borland Together 2006 Release 2 Eclipse 3.1 MyEclipse 5.1 GA Reporter: Edward Priority: Blocker Attachments: error1.JPG, error2.JPG I have installed M2Eclipse plugin version 0.9 by update site. But when I navigated to Maven2 item in Preferences window, it show an error window (error1.jpg). As well, when selected the Maven | Enable in popup context menu, got The chosen operation is not currently avaiable. I have tried with Eclipse 3.1, MyEclipse 5.1 and borland Together 2006 R2. But the same result. What a shame you guys. Please put your attention on Quality!!! -- 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: (MASSEMBLY-171) Fix / speedup integration tests
Fix / speedup integration tests
---
Key: MASSEMBLY-171
URL: http://jira.codehaus.org/browse/MASSEMBLY-171
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2
Reporter: Kenney Westerhof
Priority: Blocker
After hacking for quite a while in other projects to get the it's to run,
(fixing sandbox/plugins/maven-plug-it-plugin, shared/maven-plugin-testing-tools
and components/maven-settings)
I found, after 9 minutes, this:
{noformat}
---
Execution Summary:
Builds Passing: 24
Builds Failing: 14
---
The following builds failed:
* multimodule/twoLevel-includeSubModules-excludeSubModuleSourceDirs/pom.xml
* multimodule/two-level-multimodule-dontIncludeSubModules/pom.xml
* multimodule/two-level-multimodule/pom.xml
* multimodule/two-levels-includeBaseDirectory-withSources/pom.xml
* multimodule/twoLevel-dontIncludeSubModules-artifactIdExprOutDir/pom.xml
* multimodule/two-levels-includeBaseDirectory-withBinaries/pom.xml
* mojo-tests/single-twice-in-multimodule-hierarchy/pom.xml
* mojo-tests/single-in-one-project-hierarchy/pom.xml
* mojo-tests/single-twice-in-one-project-hierarchy/pom.xml
* basic-features/outputFileNameMapping-withArtifactBaseVersion/pom.xml
* basic-features/outputFileNameMapping-simple/pom.xml
* repository-assembly/pom.xml
* descriptor-refs/jar-with-dependencies/component-descriptors-merged/pom.xml
* file-sets/same-source-name-different-output/pom.xml
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] : [EMAIL PROTECTED]
One or more builds failed.
14 builds failed.
[INFO]
[INFO] Total time: 8 minutes 58 seconds
[INFO] Finished at: Fri Dec 22 18:25:56 CET 2006
[INFO] Final Memory: 22M/57M
[INFO]
FATAL ERROR: Unable to configure the Maven application
For more information, run with the -e flag
{noformat}
Most failed builds had this in the build.log:
{noformat}
url = http://snapshots.repository.codehaus.org
Downloading:
http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-plugins/4-SNAPSHOT/maven-plugins-4-SNAPSHOT.pom
[WARNING] Unable to get resource
'org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT' from repository
codehaus.org (http://snapshots.repository.codehaus.org)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
GroupId: org.apache.maven.plugins
ArtifactId: maven-plugins
Version: 4-SNAPSHOT
Reason: Unable to download the artifact from any repository
org.apache.maven.plugins:maven-plugins:pom:4-SNAPSHOT
from the specified remote repositories:
codehaus.org (http://snapshots.repository.codehaus.org),
central (http://repo1.maven.org/maven2)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Fri Dec 22 18:18:25 CET 2006
[INFO] Final Memory: 2M/6M
[INFO]
FATAL ERROR: Unable to configure the Maven application
For more information, run with the -e flag
{noformat}
That repo isn't used anymore, plus 4-SNAPSHOT is in my local repo already.
I think repo isolation is good but the builds takes very very long because it
tries to download
artifacts 71 times (only 57 are succesfully downloaded), using the wrong repo.
Can't the local repo serve as a fallback, or at least serve non-snapshots, so
we can't install
the test plugin?
Reasoning; in order to test the current plugin, it must be available in a local
repository
structure for maven to find it, due to a bug in maven (MNG-2677).
This requires a new local repo, initially empty. The plugin is added there.
But Maven can only handle 1 local repo at a time, so all the cached data there
is not used.
--
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-2704) Range check don't work correct
[ http://jira.codehaus.org/browse/MNG-2704?page=comments#action_83257 ] Stephan Zehrer commented on MNG-2704: - I don't know why, but today the problem was gone. Has somebody fixed something? Even my workaround (see http://www.stephan-zehrer.de/Maven2) did not work anymore and tried the correct solution again, and know it works. So close this PTR. Range check don't work correct -- Key: MNG-2704 URL: http://jira.codehaus.org/browse/MNG-2704 Project: Maven 2 Issue Type: Bug Components: Dependencies Affects Versions: 2.0.4 Environment: OS: Windows XP Java: jdk1.5.0_10 Reporter: Stephan Zehrer Priority: Minor Attachments: demo.zip I included the following part in my pom.xml: dependency groupIdorg.eclipse.jface/groupId artifactIdorg.eclipse.jface/artifactId version3.2.0/version /dependency I always get the following error No versions are present in the repository for the artifact with a range [3.2.0,4.0.0) org.eclipse.equinox:org.eclipse.equinox.common:jar:null But I am sure that version 3.2.0 is available in the repository. If I define only a dependency on this library like this dependency groupIdorg.eclipse.equinox/groupId artifactIdorg.eclipse.equinox.common/artifactId version3.2.0/version /dependency it works! If I define both it will not work. Why? According http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution It could be forced by this My current workaround is the exclusion definition. What did I wrong or is this a bug? See the demo I Attached, you need the Eclipse repository. -- 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-1050) [2.0,) should not select 3.0 and above by default
[ http://jira.codehaus.org/browse/MNG-1050?page=comments#action_83259 ] Kenney Westerhof commented on MNG-1050: --- If you want 2.*, you should write [2, 3) (or [2.0, 3.0) ); I think this is perfectly legal. If you want the latest version, whatever that is, you could use [0,) Leaving the high-end limit out means unlimited, just as in the math notation, so I say leave it like this. There's a discussion about versioning and a wiki page in the 2.1 design documents where we need to address this. I think version ranges are flexible enough as is to support any scheme or any version range people want. If you were to limit [2.0,) to [2.0,3.0), how would you specify 2.0 or higher, even including 10.0? Also, linux kernels use a different scheme, where 2.x.* is compatible with 2.(x+1).*, where odd-x'es are comparable to 'alpha'. (so 2.5.10 is actually an alpha for 2.6.0). I opt for close won't fix. [2.0,) should not select 3.0 and above by default - Key: MNG-1050 URL: http://jira.codehaus.org/browse/MNG-1050 Project: Maven 2 Issue Type: Bug Components: Artifacts and Repositories Reporter: Brett Porter Fix For: 2.1 I think that we need to assume major versions are incompatible as it is easier to later state compatibility than fix it when broken. This might just be a default compatibility scheme, but a project can define its own (eg, compatible-since 2.1). -- 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-2712) update policy 'daily' not honored
[ http://jira.codehaus.org/browse/MNG-2712?page=all ] Kenney Westerhof closed MNG-2712. - Resolution: Fixed Fix Version/s: 2.1 Fixed in revision 489724. Also updated unit test to test that the files ARE written, even if the metadata contains LATEST/RELEASE, but without the version tag. Ran integration tests on the core, and there don't seem to be any problems with this. update policy 'daily' not honored - Key: MNG-2712 URL: http://jira.codehaus.org/browse/MNG-2712 Project: Maven 2 Issue Type: Bug Reporter: Kenney Westerhof Assigned To: Kenney Westerhof Fix For: 2.1 under certain circumstances, the 'updatePolicydaily/updatePolicy' isn't honored. This is the case where the remote metadata file doesn't exist, or contains versionRELEASE/LATEST (which should never happen).. The timestamp used to compare for the update is 0L, because the local file doesn't exist. Then the remote file is retrieved, which also doesn't exist, and no metadatafile is created. The next time an up2date check is done, again against timestamp 0 for a non-existent file. This means that if you define a custom snapshot repo in settings.xml or a pom, and you have 500 transitive deps, the repo's that don't have that artifact are consulted 500 times for each mvn invocation. A build that normally takes about 20 seconds takes more than 10 minutes because of this bug. -- 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-1284) upload new artifact to The Central Repository
upload new artifact to The Central Repository - Key: MAVENUPLOAD-1284 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1284 Project: maven-upload-requests Issue Type: Task Reporter: Fernando Boaglio Hello, I'm one of the developers of Mentawai Web Framework, an open source Java web framework. Please upload! =) -- 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: (MSUREFIREREP-36) Source repository information on the web site is out of date
Source repository information on the web site is out of date Key: MSUREFIREREP-36 URL: http://jira.codehaus.org/browse/MSUREFIREREP-36 Project: Maven 2.x Surefire report Plugin Issue Type: Bug Affects Versions: 2.1 Reporter: Ryan Hoegg The source repository information on the web site refers to the old location in the repository under maven/plugins, but this plugin was moved under surefire. http://maven.apache.org/plugins/maven-surefire-report-plugin/source-repository.html -- 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: (MASSEMBLY-169) Document new elements in the assembly descriptor as Since 2.2
[ http://jira.codehaus.org/browse/MASSEMBLY-169?page=comments#action_83269 ] Dennis Lundberg commented on MASSEMBLY-169: --- The code has been committed to modello now. I made an additional change so that the since column will not appear unless you specify a firstVersion that is less than the version of the model. Document new elements in the assembly descriptor as Since 2.2 --- Key: MASSEMBLY-169 URL: http://jira.codehaus.org/browse/MASSEMBLY-169 Project: Maven 2.x Assembly Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Wendy Smoak Attachments: assembly-since-2.2.patch The assembly.html page includes elements introduced after the 2.1 release. These need to be documented as Since 2.2 to avoid confusion. (Another option would be for modello:xdoc to generate something based on the version in the model.) -- 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: (MPLUGIN-20) java.util.MissingResourceException when execute site goal.
[ http://jira.codehaus.org/browse/MPLUGIN-20?page=all ] Brett Porter updated MPLUGIN-20: Fix Version/s: 2.2 java.util.MissingResourceException when execute site goal. Key: MPLUGIN-20 URL: http://jira.codehaus.org/browse/MPLUGIN-20 Project: Maven 2.x Plugin Plugin Issue Type: Bug Environment: WinXP Maven 2.0.4 Reporter: Willie Vu Fix For: 2.2 [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Can't find bundle for base name plugin-report, locale zh_CN [INFO] [INFO] Trace java.util.MissingResourceException: Can't find bundle for base name plugin-report, locale zh_CN at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:804) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:773) at java.util.ResourceBundle.getBundle(ResourceBundle.java:661) at org.apache.maven.plugin.plugin.PluginReport.getBundle(PluginReport.java:200) at org.apache.maven.plugin.plugin.PluginReport.getName(PluginReport.java:169) at org.apache.maven.plugins.site.ReportComparator.compare(ReportComparator.java:40) at java.util.Arrays.mergeSort(Arrays.java:1278) at java.util.Arrays.sort(Arrays.java:1219) at java.util.Collections.sort(Collections.java:155) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:240) Need a default ResourceBundle. Possible resolution: rename plugin-report_en.properties to plugin-report.properties. -- 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: (MPLUGIN-21) Use of Java 5 annotations in Mojos produce error in QDox Parser
[ http://jira.codehaus.org/browse/MPLUGIN-21?page=all ]
Brett Porter closed MPLUGIN-21.
---
Assignee: Brett Porter
Resolution: Duplicate
Use of Java 5 annotations in Mojos produce error in QDox Parser
---
Key: MPLUGIN-21
URL: http://jira.codehaus.org/browse/MPLUGIN-21
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: Windows 2000
JAVA5 1.5.0_06
Reporter: Chris Wewerka
Assigned To: Brett Porter
If you use Java5 annotations in Mojos, the java extractor throws the
following exception:
com.thoughtworks.qdox.parser.ParseException: syntax error @[16,5] in
file:/E:/prj/o2/o2-sg/sd_area51_3/OcToPuS/tools/maven/plugins/maven-jax
wstools-plugin/src/main/java/com/o2/m2/plugins/jaxwstools/TestMojo.java
at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504)
[...]
The mojo I've used:
package com.o2.m2.plugins.jaxwstools;
import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;
import org.apache.maven.plugin.MojoFailureException;
/**
* @goal testgoal
* @phase process-classes
*
*/
public class TestMojo extends AbstractMojo
{
@Override
public boolean equals(Object obj)
{ return super.equals(obj); }
public void execute() throws MojoExecutionException, MojoFailureException
{}
}
--
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: (MPLUGIN-1) Maven fails while developing plugin with 1.5 compliant sources
[ http://jira.codehaus.org/browse/MPLUGIN-1?page=all ] Brett Porter updated MPLUGIN-1: --- Fix Version/s: 2.2 Maven fails while developing plugin with 1.5 compliant sources -- Key: MPLUGIN-1 URL: http://jira.codehaus.org/browse/MPLUGIN-1 Project: Maven 2.x Plugin Plugin Issue Type: Bug Reporter: Jose Gonzalez Gomez Fix For: 2.2 I'm developing a plugin for Maven, and my sources contains 1.5 features, such as use of generics. When I try to install the plugin in my local repository I get the following: [INFO] Scanning for projects... [INFO] [INFO] Building Maven Docbook plugin [INFO]task-segment: [install] [INFO] [INFO] [plugin:descriptor] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] syntax error @[129,64] in file:/C:/Documents and Settings/jgonzalez/Mis documentos/proyectos/otros/maven-opendocbook-plugin/src/ main/java/com/openinput/tools/maven/opendocbook/TransformMojo.java [INFO] [INFO] Trace com.thoughtworks.qdox.parser.ParseException: syntax error @[129,64] in file:/C:/Documents and Settings/jgonzalez/Mis documentos/proyectos/otros/maven-opendocbook-plugin/src/main/java/com/openinput/tools/maven/opendocbook/TransformMojo.java at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504) at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610) at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308) at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:99) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) 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:585) at
[jira] Updated: (MPLUGIN-18) Report should list phase for a goal, if any
[ http://jira.codehaus.org/browse/MPLUGIN-18?page=all ] Brett Porter updated MPLUGIN-18: Fix Version/s: 2.2 Report should list phase for a goal, if any --- Key: MPLUGIN-18 URL: http://jira.codehaus.org/browse/MPLUGIN-18 Project: Maven 2.x Plugin Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Matthew Beermann Priority: Minor Fix For: 2.2 The report page for a goal should list the phase the goal has bound itself to, if any. The results can be moderately disastrous if you unknowingly try to bind a goal to a phase where it doesn't want to be. -- 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: (MPLUGIN-25) Fixed Site Docu's banner and sidebar
[ http://jira.codehaus.org/browse/MPLUGIN-25?page=all ] Brett Porter updated MPLUGIN-25: Fix Version/s: 2.2 Fixed Site Docu's banner and sidebar Key: MPLUGIN-25 URL: http://jira.codehaus.org/browse/MPLUGIN-25 Project: Maven 2.x Plugin Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Franz Allan Valencia See Priority: Minor Fix For: 2.2 Attachments: MPLUGIN-25-maven-plugin-plugin.patch The site docu: * does not inherit the header of maven-plugin * has the order of the Developer's section and Examples in the sidebar is reversed. * has no reports page (NOTE: before publishing, change parent pom's version to 4-SNAPSHOT) -- 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: (MPLUGIN-24) Generated Goal documentation displays incorrect type for arrays
[ http://jira.codehaus.org/browse/MPLUGIN-24?page=all ]
Brett Porter updated MPLUGIN-24:
Fix Version/s: 2.2
Generated Goal documentation displays incorrect type for arrays
---
Key: MPLUGIN-24
URL: http://jira.codehaus.org/browse/MPLUGIN-24
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Reporter: Micah Whitacre
Priority: Minor
Fix For: 2.2
The site document generated to display specific goal information
(site\Project Reports\Plugin documentation\Individual Site) does not
correctly display the type for a parameter which is an array.
An example of this would be if a goal has a parameter defined like the
example below:
/**
* @parameter expression=${vmArgs}
*/
private String[] vmArgs;
the generated site displays the parameter as only having a type of String.
This is misleading since it should be type String[].
--
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: (CONTINUUM-1080) When a build is in progress, end time is Dec 31, 1969
When a build is in progress, end time is Dec 31, 1969 - Key: CONTINUUM-1080 URL: http://jira.codehaus.org/browse/CONTINUUM-1080 Project: Continuum Issue Type: Bug Reporter: Wendy Smoak Attachments: continuum-end-time.jpg See attached image. When a build is in progress, the End Time displays as Dec 31, 1969 05:00:00 PM GMT-07:00 -- 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: (MPLUGIN-18) Report should list phase for a goal, if any
[ http://jira.codehaus.org/browse/MPLUGIN-18?page=all ] Brett Porter closed MPLUGIN-18. --- Assignee: Brett Porter Resolution: Fixed already fixed by Edwin, I believe Report should list phase for a goal, if any --- Key: MPLUGIN-18 URL: http://jira.codehaus.org/browse/MPLUGIN-18 Project: Maven 2.x Plugin Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Matthew Beermann Assigned To: Brett Porter Priority: Minor Fix For: 2.2 The report page for a goal should list the phase the goal has bound itself to, if any. The results can be moderately disastrous if you unknowingly try to bind a goal to a phase where it doesn't want to be. -- 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: (MPLUGIN-22) Allow specification of mojo extractors to be used
[ http://jira.codehaus.org/browse/MPLUGIN-22?page=all ] Brett Porter closed MPLUGIN-22. --- Assignee: Brett Porter Resolution: Fixed applied, thanks! Allow specification of mojo extractors to be used - Key: MPLUGIN-22 URL: http://jira.codehaus.org/browse/MPLUGIN-22 Project: Maven 2.x Plugin Plugin Issue Type: New Feature Affects Versions: 2.2 Reporter: Jochen Kuhnle Assigned To: Brett Porter Fix For: 2.2 Attachments: MPLUGIN-22-maven-plugin-plugin.patch, MPLUGIN-22-maven-plugin-plugin.patch, MPLUGIN-22-maven-plugin-tools-api.patch, MPLUGIN-22-maven-plugin-tools-api.patch With the attached patch, plugin plugin configuration is extended with a section extractors. This allows the user to specify which descripters are to be used in the project. The main reason for this patch are the JDK 1.5 problems with the Java extractor, which can be turned off with this patch. Also, there are projects that provide an extractor that uses Java 5 annotations [1], so there may be two kinds of extractors for the same language in the future. With this, the user should decide which one to use. The patch changes maven-plugin-plugin and maven-tools-api. It does not change the default behaviour (use all extractors). Unit tests are included. Example: plugin artifactIdmaven-plugin-plugin/artifactId version2.2-SNAPSHOT/version configuration !-- Use all extractors -- extractors/ !-- Use no extractors -- extractors extractor/ /extractors !-- Use only bsh extractor -- extractors extractorbsh/extractor /extractors /configuration /plugin [1] http://sourceforge.net/projects/mvn-anno-mojo -- 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: (MPLUGIN-20) java.util.MissingResourceException when execute site goal.
[ http://jira.codehaus.org/browse/MPLUGIN-20?page=all ] Brett Porter closed MPLUGIN-20. --- Assignee: Vincent Siveton Resolution: Fixed fixed by Vincent in r326881 java.util.MissingResourceException when execute site goal. Key: MPLUGIN-20 URL: http://jira.codehaus.org/browse/MPLUGIN-20 Project: Maven 2.x Plugin Plugin Issue Type: Bug Environment: WinXP Maven 2.0.4 Reporter: Willie Vu Assigned To: Vincent Siveton Fix For: 2.2 [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Can't find bundle for base name plugin-report, locale zh_CN [INFO] [INFO] Trace java.util.MissingResourceException: Can't find bundle for base name plugin-report, locale zh_CN at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:804) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:773) at java.util.ResourceBundle.getBundle(ResourceBundle.java:661) at org.apache.maven.plugin.plugin.PluginReport.getBundle(PluginReport.java:200) at org.apache.maven.plugin.plugin.PluginReport.getName(PluginReport.java:169) at org.apache.maven.plugins.site.ReportComparator.compare(ReportComparator.java:40) at java.util.Arrays.mergeSort(Arrays.java:1278) at java.util.Arrays.sort(Arrays.java:1219) at java.util.Collections.sort(Collections.java:155) at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:240) Need a default ResourceBundle. Possible resolution: rename plugin-report_en.properties to plugin-report.properties. -- 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: (MPLUGIN-25) Fixed Site Docu's banner and sidebar
[ http://jira.codehaus.org/browse/MPLUGIN-25?page=all ] Brett Porter closed MPLUGIN-25. --- Assignee: Brett Porter Resolution: Fixed applied, thanks Fixed Site Docu's banner and sidebar Key: MPLUGIN-25 URL: http://jira.codehaus.org/browse/MPLUGIN-25 Project: Maven 2.x Plugin Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Franz Allan Valencia See Assigned To: Brett Porter Priority: Minor Fix For: 2.2 Attachments: MPLUGIN-25-maven-plugin-plugin.patch The site docu: * does not inherit the header of maven-plugin * has the order of the Developer's section and Examples in the sidebar is reversed. * has no reports page (NOTE: before publishing, change parent pom's version to 4-SNAPSHOT) -- 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: (MRESOURCES-37) Refactor
[ http://jira.codehaus.org/browse/MRESOURCES-37?page=comments#action_83284 ] Brett Porter commented on MRESOURCES-37: unfortunately, the second patch doesn't apply, even against the latest revision. Perhaps the line endings are the problem. Can you regenerate it? Refactor Key: MRESOURCES-37 URL: http://jira.codehaus.org/browse/MRESOURCES-37 Project: Maven 2.x Resources Plugin Issue Type: Improvement Reporter: Franz Allan Valencia See Priority: Minor Attachments: MRESOURCES-37-maven-resources-plugin-2.patch, MRESOURCES-37-maven-resources-plugin.patch Good day, Right now, ResourcesMojo is inherited by TestResourcesMojo...not the usual setup (there's usually an abstract mojo to inherit, not a working concrete mojo). Furthermore, the TestResourcesMojoTest seems to be not finished as well. And it seems as though it was going to be a duplicate of ResourcesMojoTest. Thus, i refactored those too. Actually, i was about to complete the TestResourcesMojoTest when I decided to refactor everything. Anyway, I most just extracted some classes and methods. Other than that, the overall flow is still the same. ...And deleted an unused part of plugin-config.xml to avoid confusion when traciing the test cases. Cheers, Franz -- 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: (CONTINUUM-1081) From build results, clicking Project Group Summary tab results in error
From build results, clicking Project Group Summary tab results in error --- Key: CONTINUUM-1081 URL: http://jira.codehaus.org/browse/CONTINUUM-1081 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Reporter: Wendy Smoak Attachments: continuum-project-group-summary-tab-error.jpg If you're viewing a build result, clicking on the 'Project Group Summary' tab results in: Error Occurred org.apache.maven.continuum.ContinuumException: invalid group id Show/hide Stack Trace org.apache.maven.continuum.ContinuumException: invalid group id at org.apache.maven.continuum.DefaultContinuum.getProjectGroup(DefaultContinuum.java:213) at org.apache.maven.continuum.web.action.ProjectGroupAction.summary(ProjectGroupAction.java:108) 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:585) at com.opensymphony.xwork.DefaultActionInvocation.invokeAction(DefaultActionInvocation.java:364) at com.opensymphony.xwork.DefaultActionInvocation.invokeActionOnly(DefaultActionInvocation.java:216) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:190) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.apache.maven.continuum.web.interceptor.ForceContinuumConfigurationInterceptor.intercept(ForceContinuumConfigurationInterceptor.java:58) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.security.ui.web.interceptor.SecureActionInterceptor.intercept(SecureActionInterceptor.java:157) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.security.ui.web.interceptor.AutoLoginInterceptor.intercept(AutoLoginInterceptor.java:83) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.security.ui.web.interceptor.ForceAdminUserInterceptor.intercept(ForceAdminUserInterceptor.java:61) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInterceptor.intercept(EnvironmentCheckInterceptor.java:123) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at org.codehaus.plexus.xwork.interceptor.ExceptionMappingInterceptor.intercept(ExceptionMappingInterceptor.java:62) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.DefaultWorkflowInterceptor.doIntercept(DefaultWorkflowInterceptor.java:168) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.validator.ValidationInterceptor.doIntercept(ValidationInterceptor.java:115) at com.opensymphony.xwork.interceptor.MethodFilterInterceptor.intercept(MethodFilterInterceptor.java:86) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at com.opensymphony.xwork.interceptor.AroundInterceptor.intercept(AroundInterceptor.java:31) at com.opensymphony.xwork.DefaultActionInvocation.invoke(DefaultActionInvocation.java:188) at
[jira] Closed: (MPLUGIN-1) Maven fails while developing plugin with 1.5 compliant sources
[ http://jira.codehaus.org/browse/MPLUGIN-1?page=all ] Brett Porter closed MPLUGIN-1. -- Assignee: Brett Porter Resolution: Fixed Maven fails while developing plugin with 1.5 compliant sources -- Key: MPLUGIN-1 URL: http://jira.codehaus.org/browse/MPLUGIN-1 Project: Maven 2.x Plugin Plugin Issue Type: Bug Reporter: Jose Gonzalez Gomez Assigned To: Brett Porter Fix For: 2.2 I'm developing a plugin for Maven, and my sources contains 1.5 features, such as use of generics. When I try to install the plugin in my local repository I get the following: [INFO] Scanning for projects... [INFO] [INFO] Building Maven Docbook plugin [INFO]task-segment: [install] [INFO] [INFO] [plugin:descriptor] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] syntax error @[129,64] in file:/C:/Documents and Settings/jgonzalez/Mis documentos/proyectos/otros/maven-opendocbook-plugin/src/ main/java/com/openinput/tools/maven/opendocbook/TransformMojo.java [INFO] [INFO] Trace com.thoughtworks.qdox.parser.ParseException: syntax error @[129,64] in file:/C:/Documents and Settings/jgonzalez/Mis documentos/proyectos/otros/maven-opendocbook-plugin/src/main/java/com/openinput/tools/maven/opendocbook/TransformMojo.java at com.thoughtworks.qdox.parser.impl.Parser.yyerror(Parser.java:504) at com.thoughtworks.qdox.parser.impl.Parser.yyparse(Parser.java:610) at com.thoughtworks.qdox.parser.impl.Parser.parse(Parser.java:488) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:296) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:312) at com.thoughtworks.qdox.JavaDocBuilder.addSource(JavaDocBuilder.java:308) at com.thoughtworks.qdox.JavaDocBuilder$1.visitFile(JavaDocBuilder.java:365) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:43) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.walk(DirectoryScanner.java:34) at com.thoughtworks.qdox.directorywalker.DirectoryScanner.scan(DirectoryScanner.java:52) at com.thoughtworks.qdox.JavaDocBuilder.addSourceTree(JavaDocBuilder.java:362) at org.apache.maven.tools.plugin.extractor.java.JavaMojoDescriptorExtractor.execute(JavaMojoDescriptorExtractor.java:477) at org.apache.maven.tools.plugin.scanner.DefaultMojoScanner.populatePluginDescriptor(DefaultMojoScanner.java:69) at org.apache.maven.plugin.plugin.AbstractGeneratorMojo.execute(AbstractGeneratorMojo.java:99) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:469) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:448) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:301) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:268) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:137) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:316) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:113) at org.apache.maven.cli.MavenCli.main(MavenCli.java:249) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at
[jira] Closed: (MRM-239) OutOfMemory error when running Arhiva for days at a time
[ http://jira.codehaus.org/browse/MRM-239?page=all ] Brett Porter closed MRM-239. Resolution: Duplicate Fix Version/s: (was: 1.0) Carlos seems to have fixed this. I will do some more long term testing to confirm. Thanks Carlos! OutOfMemory error when running Arhiva for days at a time Key: MRM-239 URL: http://jira.codehaus.org/browse/MRM-239 Project: Archiva Issue Type: Bug Components: system Affects Versions: 1.0 Environment: Linux and Mac OS X Reporter: Greg Luck Attachments: health-report.xml I have been running Archiva as it existed in snapshot 20 November 2006. When running in Tomcat with the standard memory setting it fails after a few days. Increasing -Xmx=128m increases the time but it still gets and OutOfMemory error after a few days. This is with no activity. I came back today after the weekend and hit refresh on a Pom page and it gave the OOM. It seems to be time dependent. At home I have been running it on Mac OS X. I saw an OutOfMemory error after a week. I did even go to a page to check it. The running console had it. To reproduce simply run up archiva and leave it running. We are working around with a nightly restart. -- 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: (MPLUGIN-24) Generated Goal documentation displays incorrect type for arrays
[ http://jira.codehaus.org/browse/MPLUGIN-24?page=all ]
Brett Porter closed MPLUGIN-24.
---
Assignee: Brett Porter
Resolution: Cannot Reproduce
Fix Version/s: (was: 2.2)
can't reproduce with either 2.2 or 2.1
Generated Goal documentation displays incorrect type for arrays
---
Key: MPLUGIN-24
URL: http://jira.codehaus.org/browse/MPLUGIN-24
Project: Maven 2.x Plugin Plugin
Issue Type: Bug
Reporter: Micah Whitacre
Assigned To: Brett Porter
Priority: Minor
The site document generated to display specific goal information
(site\Project Reports\Plugin documentation\Individual Site) does not
correctly display the type for a parameter which is an array.
An example of this would be if a goal has a parameter defined like the
example below:
/**
* @parameter expression=${vmArgs}
*/
private String[] vmArgs;
the generated site displays the parameter as only having a type of String.
This is misleading since it should be type String[].
--
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: (MRM-142) project builder cache needs to be configurable to prevent memory leaking
[ http://jira.codehaus.org/browse/MRM-142?page=all ] Brett Porter updated MRM-142: - Priority: Critical (was: Blocker) Fix Version/s: (was: 1.0) Future this is actually not critical for the release, since the entire cache is flushed every time the index is run. project builder cache needs to be configurable to prevent memory leaking Key: MRM-142 URL: http://jira.codehaus.org/browse/MRM-142 Project: Archiva Issue Type: Bug Components: indexing Reporter: Brett Porter Assigned To: Brett Porter Priority: Critical Fix For: Future Original Estimate: 1 hour Time Spent: 30 minutes Remaining Estimate: 30 minutes need to investigate if there is a memory leak, since the server received an OOME some time after successfully completing a full index with 1Gb heap with just some browsing/searching. It is most likely in the indexing itself, but there may be some in the browse/search interface too -- 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: (MRM-131) complete artifact browsing
[ http://jira.codehaus.org/browse/MRM-131?page=all ] Brett Porter closed MRM-131. Resolution: Fixed complete artifact browsing -- Key: MRM-131 URL: http://jira.codehaus.org/browse/MRM-131 Project: Archiva Issue Type: Improvement Components: web application Reporter: Brett Porter Assigned To: Brett Porter Fix For: 1.0 currently some features of the artifact display page are not implemented (links to dependencies, displaying other information from the pom, and so on) -- 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
