[jira] Updated: (MCHECKSTYLE-130) multimodule project requires src/main/java after 2.5 update
[
http://jira.codehaus.org/browse/MCHECKSTYLE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated MCHECKSTYLE-130:
---
Attachment: multimoduleproject.zip
Hmm...in my environment the sample works with 2.4 and produces the exception
with 2.5.
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_17
Java home: D:\java\jdk1.6.0_17\jre
Default locale: de_DE, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
I've removed the custom config from the sample.
> multimodule project requires src/main/java after 2.5 update
> ---
>
> Key: MCHECKSTYLE-130
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-130
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
>Reporter: Dennis Kieselhorst
>Assignee: Olivier Lamy
> Fix For: 2.6
>
> Attachments: multimoduleproject.zip, multimoduleproject.zip
>
>
> Updated to 2.5, it seems that src/main/java is now required.
> [INFO] [checkstyle:check {execution: checkstyle}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] basedir D:\projects\multimoduleproject\src\main\java does not exist
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalStateException: basedir
> D:\projects\multimoduleproject\src\main\java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at
> org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at
> org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at
> org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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)
--
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: (MRELEASE-524) command line versions don't seem to work on release:branch for specific format
command line versions don't seem to work on release:branch for specific format Key: MRELEASE-524 URL: http://jira.codehaus.org/browse/MRELEASE-524 Project: Maven 2.x Release Plugin Issue Type: Bug Components: branch Affects Versions: 2.0 Environment: maven 2.2.1 Reporter: Max Schaefer I have tried passing versions for certain modules to the command line while making a branch. The plugin ignores my parameters when running release:branch. It injects the defaults if I pass parameters in batch mode. E.g. this command taken from the documentation does not work. mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -Dproject.rel.org.myCompany:projectA=1.2 \ -Dproject.dev.org.myCompany:projectA=2.0-SNAPSHOT release:prepare supports this specific format for setting these values at command line. Setting these values in a release.properties file e.g. project.dev.org.myCompany\:projectA=2.0-SNAPSHOT project.rel.org.myCompany\:projectA=1.2 works also fine. Specifying the default at commandline works also e.g. mvn --batch-mode release:branch -DbranchName=my-branch-1.2 -DreleaseVersion=1.2 \ -DdevelopmentVersion=2.0-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] Issue Comment Edited: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210395#action_210395
]
Matthew McCullough edited comment on MINVOKER-99 at 2/16/10 7:52 PM:
-
Benjamin - When you say wrong, can you be more specific? I'm not quite
following where I should be looking to fix this yet.
In the pom.xml, I have this parameter specified as
{{${project.build.directory}/it/repo}}
which should resolve at POM interpolation time, right? If I look at the
{{localRepositoryPath}} parameter passed in to the invoker plugin in the
Maven3MainBuild.log file attached earlier, I see it fully resolved to the
complete path
{{/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo}}:
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-invoker-plugin:1.5:install (integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${localRepository}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${project}
${invoker.skip}
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:integration-test
(default-integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${project}
${archetype.test.skip}
[DEBUG] ---
[DEBUG] Goal: org.apache.maven.plugins:maven-invoker-plugin:1.5:run
(integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${invoker.addTestClassPath}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/projects
${invoker.debug}
${invoker.disableReports}
${encoding}
org.apache.maven.plugins:maven-archetype-plugin:generate
${invoker.goalsFile}
${maven.test.failure.ignore}
${invoker.invokerPropertiesFile}
${invoker.test}
${invoker.javaHome}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${invoker.mavenHome}
${invoker.mavenOpts}
${invoker.noLog}
${invoker.pom}
*
${invoker.postBuildHookScript}
${invoker.preBuildHookScript}
${invoker.profilesFile}
${project}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/src/it/projects
quickstartBROKENIT
org.sonatype.maven.archetype
local
0.8.4-SNAPSHOT
install
false
${invoker.reportsDirectory}
${invoker.selectorScript}
${settings}
${invoker.settingsFile}
${invoker.showErrors}
${invoker.showVersion}
${invoker.skip}
true
${invoker.testPropertiesFile}
was (Author: programr):
Benjamin - When you say wrong, can you be more specific? I'm not quite
following where I should be looking to fix this yet.
In the pom.xml, I have this parameter specified as
{{${project.build.directory}/it/repo}}
which should resolve at POM interpolation time, right? If I look at the
{{localRepositoryPath}} parameter passed in to the invoker plugin in the
Maven3MainBuild.log file attached earlier, I see it fully resolved to the
complete path
{{/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo}}:
{{[DEBUG]
---
[DEBUG] Goal:
org.apache.maven.plugins:maven-invoker-plugin:1.5:install (integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${localRepository}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${project}
${invoker.skip}
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:integration-test
(default-integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${project}
${archetype.test.skip}
[DEBUG] ---
[DEBUG] Goal: org.apache.maven.plugins:maven-invoker-plugin:1.5:run
(integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${invoker.addTestClassPath}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/projects
${invoker.debug}
${invoker.disableReports}
${encoding}
org.apache.maven.plugins:maven-archetype-plugin:generate
${invoker.goalsFile}
${maven.test.failure.ignore}
${invoker.invokerPropertiesFile}
${invoker.test}
${invoker.javaHome}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${invoker.mavenHome}
${invoker.mavenOpts}
${invoker.noLog}
${invoker.pom}
*
${invoker.postBuildHookScript}
${invoker.preBuildHookScript}
${invoker.profilesFile}
${project}
/Users/mccm06/Docume
[jira] Issue Comment Edited: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210395#action_210395
]
Matthew McCullough edited comment on MINVOKER-99 at 2/16/10 7:50 PM:
-
Benjamin - When you say wrong, can you be more specific? I'm not quite
following where I should be looking to fix this yet.
In the pom.xml, I have this parameter specified as
{{${project.build.directory}/it/repo}}
which should resolve at POM interpolation time, right? If I look at the
{{localRepositoryPath}} parameter passed in to the invoker plugin in the
Maven3MainBuild.log file attached earlier, I see it fully resolved to the
complete path
{{/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo}}:
{{[DEBUG]
---
[DEBUG] Goal:
org.apache.maven.plugins:maven-invoker-plugin:1.5:install (integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${localRepository}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${project}
${invoker.skip}
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:integration-test
(default-integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${project}
${archetype.test.skip}
[DEBUG] ---
[DEBUG] Goal: org.apache.maven.plugins:maven-invoker-plugin:1.5:run
(integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${invoker.addTestClassPath}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/projects
${invoker.debug}
${invoker.disableReports}
${encoding}
org.apache.maven.plugins:maven-archetype-plugin:generate
${invoker.goalsFile}
${maven.test.failure.ignore}
${invoker.invokerPropertiesFile}
${invoker.test}
${invoker.javaHome}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${invoker.mavenHome}
${invoker.mavenOpts}
${invoker.noLog}
${invoker.pom}
*
${invoker.postBuildHookScript}
${invoker.preBuildHookScript}
${invoker.profilesFile}
${project}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/src/it/projects
quickstartBROKENIT
org.sonatype.maven.archetype
local
0.8.4-SNAPSHOT
install
false
${invoker.reportsDirectory}
${invoker.selectorScript}
${settings}
${invoker.settingsFile}
${invoker.showErrors}
${invoker.showVersion}
${invoker.skip}
true
${invoker.testPropertiesFile}
}}
was (Author: programr):
Benjamin - When you say wrong, can you be more specific? I'm not quite
following where I should be looking to fix this yet.
In the pom.xml, I have this parameter specified as
{{${project.build.directory}/it/repo}}
which should resolve at POM interpolation time, right? If I look at the
{{localRepositoryPath}} parameter passed in to the invoker plugin in the
Maven3MainBuild.log file attached earlier, I see it fully resolved to the
complete path
{{/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo}}:
{{
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-invoker-plugin:1.5:install (integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${localRepository}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${project}
${invoker.skip}
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:integration-test
(default-integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${project}
${archetype.test.skip}
[DEBUG] ---
[DEBUG] Goal: org.apache.maven.plugins:maven-invoker-plugin:1.5:run
(integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${invoker.addTestClassPath}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/projects
${invoker.debug}
${invoker.disableReports}
${encoding}
org.apache.maven.plugins:maven-archetype-plugin:generate
${invoker.goalsFile}
${maven.test.failure.ignore}
${invoker.invokerPropertiesFile}
${invoker.test}
${invoker.javaHome}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${invoker.mavenHome}
${invoker.mavenOpts}
${invoker.noLog}
${invoker.pom}
*
${invoker.postBuildHookScript}
${invoker.preBuildHookScript}
${invoker.profilesFile}
${project}
/Users/mccm06/Do
[jira] Commented: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210395#action_210395
]
Matthew McCullough commented on MINVOKER-99:
Benjamin - When you say wrong, can you be more specific? I'm not quite
following where I should be looking to fix this yet.
In the pom.xml, I have this parameter specified as
{{${project.build.directory}/it/repo}}
which should resolve at POM interpolation time, right? If I look at the
{{localRepositoryPath}} parameter passed in to the invoker plugin in the
Maven3MainBuild.log file attached earlier, I see it fully resolved to the
complete path
{{/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo}}:
{{
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-invoker-plugin:1.5:install (integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${localRepository}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${project}
${invoker.skip}
[DEBUG] ---
[DEBUG] Goal:
org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:integration-test
(default-integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${project}
${archetype.test.skip}
[DEBUG] ---
[DEBUG] Goal: org.apache.maven.plugins:maven-invoker-plugin:1.5:run
(integration-test)
[DEBUG] Style: Regular
[DEBUG] Configuration:
${invoker.addTestClassPath}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/projects
${invoker.debug}
${invoker.disableReports}
${encoding}
org.apache.maven.plugins:maven-archetype-plugin:generate
${invoker.goalsFile}
${maven.test.failure.ignore}
${invoker.invokerPropertiesFile}
${invoker.test}
${invoker.javaHome}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo
${invoker.mavenHome}
${invoker.mavenOpts}
${invoker.noLog}
${invoker.pom}
*
${invoker.postBuildHookScript}
${invoker.preBuildHookScript}
${invoker.profilesFile}
${project}
/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/src/it/projects
quickstartBROKENIT
org.sonatype.maven.archetype
local
0.8.4-SNAPSHOT
install
false
${invoker.reportsDirectory}
${invoker.selectorScript}
${settings}
${invoker.settingsFile}
${invoker.showErrors}
${invoker.showVersion}
${invoker.skip}
true
${invoker.testPropertiesFile}
}}
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: Maven2MainBuild.log, Maven2Success_BUILD-quickstart.xml,
> Maven2Success_build.log, Maven3Failure_BUILD-quickstart.xml,
> Maven3Failure_build.log, Maven3MainBuild.log, quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-p
[jira] Commented: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210393#action_210393
]
Benjamin Bentmann commented on MINVOKER-99:
---
Thanks for the example project and the logs. This seems wrong
{noformat}
[INFO] Installing [...] to
/org/sonatype/maven/archetype/quickstartBROKENIT/0.8.4-SNAPSHOT/quickstartBROKENIT-0.8.4-SNAPSHOT.pom
[INFO] Installing [...] to
/org/sonatype/maven/archetype/quickstartBROKENIT/0.8.4-SNAPSHOT/quickstartBROKENIT-0.8.4-SNAPSHOT.jar
{noformat}
the destination paths are supposed to be absolute and hence should be prefixed
with
{{/Users/mccm06/Documents/Temp/Scratch/quickstart-itbrokenonmaven3/target/it/repo}}.
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: Maven2MainBuild.log, Maven2Success_BUILD-quickstart.xml,
> Maven2Success_build.log, Maven3Failure_BUILD-quickstart.xml,
> Maven3Failure_build.log, Maven3MainBuild.log, quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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] Updated: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew McCullough updated MINVOKER-99:
---
Attachment: Maven2MainBuild.log
Maven3MainBuild.log
The core (console, redirected) build logs on Maven 3 and 2 for comparison's
sake.
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: Maven2MainBuild.log, Maven2Success_BUILD-quickstart.xml,
> Maven2Success_build.log, Maven3Failure_BUILD-quickstart.xml,
> Maven3Failure_build.log, Maven3MainBuild.log, quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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] Updated: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew McCullough updated MINVOKER-99:
---
Attachment: Maven3Failure_build.log
Maven3Failure_BUILD-quickstart.xml
Log file from a failed run of the IT under Maven 3.0-alpha-6
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: Maven2Success_BUILD-quickstart.xml,
> Maven2Success_build.log, Maven3Failure_BUILD-quickstart.xml,
> Maven3Failure_build.log, quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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] Updated: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew McCullough updated MINVOKER-99:
---
Attachment: Maven2Success_build.log
Maven2Success_BUILD-quickstart.xml
Log files from a successful run of the IT under Maven 2.2.1
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: Maven2Success_BUILD-quickstart.xml,
> Maven2Success_build.log, quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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] Commented: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210386#action_210386
]
Matthew McCullough commented on MINVOKER-99:
I'm attaching a zip file of a sample project that fails the IT under Maven
3.0-alpha-6 but succeeds under 2.2.1. Just unzip it and run mvn install with
each version of maven. I'm also attaching the requested logs named accordingly.
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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] Updated: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthew McCullough updated MINVOKER-99:
---
Attachment: quickstart-itbrokenonmaven3.zip
Integration test that fails under Maven 3, but succeeds under Maven 2.2.1
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
> Attachments: quickstart-itbrokenonmaven3.zip
>
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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: (MNGSITE-109) "Guide to relocation" misses 4.0.0 for the minimal maven 2 pom example
[ http://jira.codehaus.org/browse/MNGSITE-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNGSITE-109. - Resolution: Fixed Assignee: Benjamin Bentmann Fixed in [r910743|http://svn.apache.org/viewvc?view=revision&revision=910743]. > "Guide to relocation" misses 4.0.0 for the > minimal maven 2 pom example > --- > > Key: MNGSITE-109 > URL: http://jira.codehaus.org/browse/MNGSITE-109 > Project: Maven 2 Project Web Site > Issue Type: Improvement >Reporter: Andreas Kohn >Assignee: Benjamin Bentmann >Priority: Minor > > I tried to follow the mini-guide to relocation, but hit an issue with the > minimal pom.xml example from the "Maven 2 artifact to different groupId" > section, as maven 2 > doesn't accept the relocation pom without the > 4.0.0 element. > Please adjust the mini-guide. > Thanks! -- 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: (SCM-445) Extend command coverage of AccuRev provider for use with Continuum and Release Plugin
[ http://jira.codehaus.org/browse/SCM-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210367#action_210367 ] Joshua Pollak commented on SCM-445: --- I get a compiler error when trying to compile a clean checkout from the URL above, am I doing something wrong? I did: svn co https://svn.apache.org/repos/asf/maven/sandbox/trunk/scm/maven-scm-provider-accurevnew/ cd maven-scm-provider-accurevnew/ mvn compile (all of which worked correctly), and then: mvn test which resulted in this: /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevCommandLineTest.java:[52,7] cannot access org.codehaus.plexus.PlexusTestCase class file for org.codehaus.plexus.PlexusTestCase not found public class AccuRevCommandLineTest /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/command/AccuRevTckUtil.java:[35,26] cannot find symbol symbol : class PlexusContainer location: package org.codehaus.plexus /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/command/AccuRevTckUtil.java:[97,28] cannot find symbol symbol : class PlexusContainer location: class org.apache.maven.scm.provider.accurev.command.AccuRevTckUtil /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/command/AccuRevTckUtil.java:[103,26] cannot find symbol symbol : class PlexusContainer location: class org.apache.maven.scm.provider.accurev.command.AccuRevTckUtil /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[29,42] package org.apache.maven.scm.manager.plexus does not exist /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[30,26] cannot find symbol symbol : class PlexusContainer location: package org.codehaus.plexus /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[31,57] package org.codehaus.plexus.component.repository.exception does not exist /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[32,34] package org.codehaus.plexus.logging does not exist /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[33,34] package org.codehaus.plexus.logging does not exist /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[58,39] cannot find symbol symbol : class PlexusContainer location: class org.apache.maven.scm.provider.accurev.cli.AccuRevJUnitUtil /Users/jpollak/src/maven-scm-provider-accurevnew/src/test/java/org/apache/maven/scm/provider/accurev/cli/AccuRevJUnitUtil.java:[59,15] cannot find symbol symbol : class ComponentLookupException location: class org.apache.maven.scm.provider.accurev.cli.AccuRevJUnitUtil > Extend command coverage of AccuRev provider for use with Continuum and > Release Plugin > - > > Key: SCM-445 > URL: http://jira.codehaus.org/browse/SCM-445 > Project: Maven SCM > Issue Type: Improvement > Components: maven-scm-provider-accurev >Reporter: Grant Gardner > Fix For: 1.4 > > Attachments: maven-scm-provider-accurev.tar.gz, > maven-scm-provider-accurev.tar.gz, maven-scm-provider-accurev.tar.gz > > > Replacement accurev provider with additional commands - Login, Checkout, > Update, Add, Changelog, CheckIn, Status, Tag, Export. See site documentation > for full coverage > Note that the URL syntax is different from the original minimal AccuRev > plugin. -- 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: (MCHECKSTYLE-130) multimodule project requires src/main/java after 2.5 update
[
http://jira.codehaus.org/browse/MCHECKSTYLE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210362#action_210362
]
Olivier Lamy commented on MCHECKSTYLE-130:
--
Thanks.
But I don't have the same exception with your testcase :
{code}
[INFO] Caused by: org.apache.maven.plugin.checkstyle.CheckstyleExecutorException
: Unable to find configuration file at location checkstyle-dekies.xml
[INFO] at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getConfi
gFile(DefaultCheckstyleExecutor.java:466)
[INFO] at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getConfi
guration(DefaultCheckstyleExecutor.java:238)
[INFO] at org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeC
heckstyle(DefaultCheckstyleExecutor.java:175)
[INFO] at org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(Che
ckstyleReport.java:576)
[INFO] ... 18 more
[INFO] Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException:
Could not find resource 'checkstyle-dekies.xml'.
{code}
This one looks reasonnable as the location is defined as this
{code:xml}
checkstyle-dekies.xml
{code}
So the child can't find it (even with 2.4 version).
btw I have added your sample project in the sources as an it test.
> multimodule project requires src/main/java after 2.5 update
> ---
>
> Key: MCHECKSTYLE-130
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-130
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
>Reporter: Dennis Kieselhorst
>Assignee: Olivier Lamy
> Fix For: 2.6
>
> Attachments: multimoduleproject.zip
>
>
> Updated to 2.5, it seems that src/main/java is now required.
> [INFO] [checkstyle:check {execution: checkstyle}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] basedir D:\projects\multimoduleproject\src\main\java does not exist
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalStateException: basedir
> D:\projects\multimoduleproject\src\main\java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at
> org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at
> org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at
> org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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
>
[jira] Created: (MNGSITE-109) "Guide to relocation" misses 4.0.0 for the minimal maven 2 pom example
"Guide to relocation" misses 4.0.0 for the minimal maven 2 pom example --- Key: MNGSITE-109 URL: http://jira.codehaus.org/browse/MNGSITE-109 Project: Maven 2 Project Web Site Issue Type: Improvement Reporter: Andreas Kohn Priority: Minor I tried to follow the mini-guide to relocation, but hit an issue with the minimal pom.xml example from the "Maven 2 artifact to different groupId" section, as maven 2 doesn't accept the relocation pom without the 4.0.0 element. Please adjust the mini-guide. Thanks! -- 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: (DOXIA-380) Use of #include in APT page causes NullPointerException during page rendering
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210355#action_210355 ] Lukas Theussl commented on DOXIA-380: - Using site-plugin 2.1 (ie Doxia-1.1) I get the same error message but the resulting index.html is actually correct. Can you confirm? > Use of #include in APT page causes NullPointerException during page rendering > - > > Key: DOXIA-380 > URL: http://jira.codehaus.org/browse/DOXIA-380 > Project: Maven Doxia > Issue Type: Bug > Components: Site Renderer > Environment: maven 2.2.1 >Reporter: Alan Alberghini >Priority: Minor > Attachments: apt-include.log, VelocityTest.tar.gz > > > In the last 2 days I tried to get this thing working. > The situation is the following: I'm working on a maven site project and, for > some pages, I'm currently using the APT format. > I'd really like to be able to include existing APT pages inside an APT page, > in order to make the collaboration between the 4 members of the project much > easier and smoother. > To give an idea, I'd like to do this: > merged-page.apt: > --- > Title > --- > --- > --- > Develeper 1 proposal: > > Developer 2 proposal: > > etc. > At first, I tried using the %snippet DOXIA macro, but the included APT page > would not be rendered to HTML even setting verbatim=false. > Then, I tried the #include macro from Velocity. I renamed my APT file to > filename.apt.vm in order to trigger the Velocity processor on it and put the > #include line in the file, but, whenever I launch maven site I keep getting > this error: > and the page is not generated. > Is there a way to fix this? -- 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: (DOXIA-380) Use of #include in APT page causes NullPointerException during page rendering
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210354#action_210354 ] Lukas Theussl commented on DOXIA-380: - For reference: this has been reported before: http://www.mail-archive.com/us...@maven.apache.org/msg98932.html > Use of #include in APT page causes NullPointerException during page rendering > - > > Key: DOXIA-380 > URL: http://jira.codehaus.org/browse/DOXIA-380 > Project: Maven Doxia > Issue Type: Bug > Components: Site Renderer > Environment: maven 2.2.1 >Reporter: Alan Alberghini >Priority: Minor > Attachments: apt-include.log, VelocityTest.tar.gz > > > In the last 2 days I tried to get this thing working. > The situation is the following: I'm working on a maven site project and, for > some pages, I'm currently using the APT format. > I'd really like to be able to include existing APT pages inside an APT page, > in order to make the collaboration between the 4 members of the project much > easier and smoother. > To give an idea, I'd like to do this: > merged-page.apt: > --- > Title > --- > --- > --- > Develeper 1 proposal: > > Developer 2 proposal: > > etc. > At first, I tried using the %snippet DOXIA macro, but the included APT page > would not be rendered to HTML even setting verbatim=false. > Then, I tried the #include macro from Velocity. I renamed my APT file to > filename.apt.vm in order to trigger the Velocity processor on it and put the > #include line in the file, but, whenever I launch maven site I keep getting > this error: > and the page is not generated. > Is there a way to fix this? -- 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: (MCHECKSTYLE-130) multimodule project requires src/main/java after 2.5 update
[
http://jira.codehaus.org/browse/MCHECKSTYLE-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated MCHECKSTYLE-130:
---
Attachment: multimoduleproject.zip
Small testcase
> multimodule project requires src/main/java after 2.5 update
> ---
>
> Key: MCHECKSTYLE-130
> URL: http://jira.codehaus.org/browse/MCHECKSTYLE-130
> Project: Maven 2.x Checkstyle Plugin
> Issue Type: Bug
>Affects Versions: 2.5
> Environment: Windows 7
>Reporter: Dennis Kieselhorst
>Assignee: Olivier Lamy
> Fix For: 2.6
>
> Attachments: multimoduleproject.zip
>
>
> Updated to 2.5, it seems that src/main/java is now required.
> [INFO] [checkstyle:check {execution: checkstyle}]
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] basedir D:\projects\multimoduleproject\src\main\java does not exist
> [INFO]
>
> [INFO] Trace
> java.lang.IllegalStateException: basedir
> D:\projects\multimoduleproject\src\main\java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:550)
> at
> org.codehaus.plexus.util.FileUtils.getFileAndDirectoryNames(FileUtils.java:1717)
> at
> org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1645)
> at
> org.codehaus.plexus.util.FileUtils.getFileNames(FileUtils.java:1627)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1601)
> at org.codehaus.plexus.util.FileUtils.getFiles(FileUtils.java:1584)
> at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.getFilesToProcess(DefaultCheckstyleExecutor.java:407)
> at
> org.apache.maven.plugin.checkstyle.DefaultCheckstyleExecutor.executeCheckstyle(DefaultCheckstyleExecutor.java:89)
> at
> org.apache.maven.plugin.checkstyle.CheckstyleViolationCheckMojo.execute(CheckstyleViolationCheckMojo.java:393)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> 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)
--
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-2745) TheseFoolishThings moved to Sonatype
TheseFoolishThings moved to Sonatype Key: MAVENUPLOAD-2745 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2745 Project: Maven Upload Requests Issue Type: Task Reporter: Fabrizio Giudici >From now on, artifacts for TheseFoolishThings won't be ever published to the >repo at: https://kenai.com/svn/tidalwave~maven-repo/release/2/it/tidalwave/thesefoolishthings/thesefoolishthings/ but to the free Sonatype hosting, whose sync-to-Central feature will be used to sync stuff to the Central Repository. The whole repo at kenai will be shut down. I suppose I have to tell you, so you remove the project from the list of things that you periodically sync. -- 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: (MEAR-118) Invalid application.xml generated
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210340#action_210340 ] Stephane Nicoll commented on MEAR-118: -- we will of course release it. > Invalid application.xml generated > - > > Key: MEAR-118 > URL: http://jira.codehaus.org/browse/MEAR-118 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: Maven 2.2.1 >Reporter: Stephen Coy >Assignee: Stephane Nicoll >Priority: Critical > Fix For: 2.4.1 > > Attachments: ApplicationXmlWriter.java.patch > > > If a project description is specified in the pom.xml, then the plugin > generates a corresponding description from pom > element in the application.xml file. > Unfortunately, it places it in the wrong location according to the schema > (for both J2EE 1.4 and JEE 5): > artifact name > project description > > ... > instead of: > project description > artifact name > > ... > This results in deployment failure on WebSphere. > Work around is to roll back to version 2.3.2 of the ear plugin. -- 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: (MEAR-118) Invalid application.xml generated
[ http://jira.codehaus.org/browse/MEAR-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210333#action_210333 ] fabrice commented on MEAR-118: -- hi Why do you not create a release instead of snapshot ? > Invalid application.xml generated > - > > Key: MEAR-118 > URL: http://jira.codehaus.org/browse/MEAR-118 > Project: Maven 2.x Ear Plugin > Issue Type: Bug >Affects Versions: 2.4 > Environment: Maven 2.2.1 >Reporter: Stephen Coy >Assignee: Stephane Nicoll >Priority: Critical > Fix For: 2.4.1 > > Attachments: ApplicationXmlWriter.java.patch > > > If a project description is specified in the pom.xml, then the plugin > generates a corresponding description from pom > element in the application.xml file. > Unfortunately, it places it in the wrong location according to the schema > (for both J2EE 1.4 and JEE 5): > artifact name > project description > > ... > instead of: > project description > artifact name > > ... > This results in deployment failure on WebSphere. > Work around is to roll back to version 2.3.2 of the ear plugin. -- 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-4562) [regression] UnsupportedOperationException with Maven AndromMDA plugin
[regression] UnsupportedOperationException with Maven AndromMDA plugin
--
Key: MNG-4562
URL: http://jira.codehaus.org/browse/MNG-4562
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0-alpha-6
Reporter: Julien HENRY
Attachments: test-bug-maven-andromda-sources.zip
Running mvn clean install -DperformRelease=true -e on the attached project
generate the following error:
{code}
[ERROR] Failed to execute goal
org.andromda.maven.plugins:andromda-maven-plugin:3.3:run (default) on project
uml: Error
running AndroMDA: UnsupportedOperationException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.andromda.maven.plugins:andromda-maven
-plugin:3.3:run (default) on project uml: Error running AndroMDA
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:570)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeForkedExecutions(DefaultLifecycleExecutor.java:645)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:553)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:317)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:247)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:104)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:422)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:157)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:122)
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.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error running
AndroMDA
at
org.andromda.maven.plugin.AbstractAndroMDAMojo.execute(AbstractAndroMDAMojo.java:116)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:562)
... 16 more
Caused by: java.lang.UnsupportedOperationException
at
java.util.Collections$UnmodifiableCollection.add(Collections.java:1018)
at
org.andromda.maven.plugin.configuration.AbstractConfigurationMojo.addDependency(AbstractConfigurationMojo.java:259)
at
org.andromda.maven.plugin.configuration.AbstractConfigurationMojo.addPluginDependencies(AbstractConfigurationMojo.java:221)
at
org.andromda.maven.plugin.AbstractAndroMDAMojo.execute(AbstractAndroMDAMojo.java:101)
... 18 more
{code}
mvn clean install (without generating attached sources) works fine.
--
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-2157) Properties defined in top-level profiles.xml do no propagate to child modules
[
http://jira.codehaus.org/browse/MNG-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MNG-2157.
--
Resolution: Won't Fix
Fix Version/s: (was: 3.0-alpha-7)
Assignee: Benjamin Bentmann
> Properties defined in top-level profiles.xml do no propagate to child modules
> -
>
> Key: MNG-2157
> URL: http://jira.codehaus.org/browse/MNG-2157
> Project: Maven 2 & 3
> Issue Type: Bug
> Components: POM
>Affects Versions: 2.0.2
>Reporter: Jason Dillon
>Assignee: Benjamin Bentmann
>Priority: Blocker
>
> I have a multi-module build, and at the top-level I have a profile called
> 'release-environment', which is activated by -Denv=release.
> I need the local release build to use different values for JDBC configuration
> to run integration tests, and defined them in a profiles.xml:
> {code}
>
>
>
>
> local-release-environment
>
>
> env
> release
>
>
>
>
> mif_jason
> mif_jason
> MIF_JASON
>
>
>
>
>
> {code}
> My project looks like:
> pom.xml
> merchant/pom.xml
> merchant/core/pom.xml
> merchant/services/pom.xml
> If i put profiles.xml as a peer to pom.xml and run {{mvn clean install
> -Denv=release}} from the top-level, I get errors because the properties are
> not propagated to the merchant/core/pom.xml module.
> If I put profiles.xml as a peer to merchant/core/pom.xml and run {{mvn clean
> install -Denv=release}}, then it works as expected... properties are set as
> they are defined in profiles.xml.
> But, this is not manageable, as I need to set some properties for all of the
> modules in a multi-module build... But I don't want to use those properties
> for all Maven2 projects, so I can not really put it into ~/.m2/settings.xml
> I had expected that a top-level profiles.xml would work, but it does not. Is
> this by design, is there another recommend way to provide per-top-level
> multi-module project configuration on a local user basis (ie. no pom.xml
> modifications)?
--
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: (MINVOKER-99) Final JAR artifact for archetype not install(ed) into localRepositoryUrl on Mavne 3.0-alpha-6
[
http://jira.codehaus.org/browse/MINVOKER-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210316#action_210316
]
Benjamin Bentmann commented on MINVOKER-99:
---
I couldn't reproduce this easily. Could you please attach full debugs logs of
the main build and the failing IT?
> Final JAR artifact for archetype not install(ed) into localRepositoryUrl on
> Mavne 3.0-alpha-6
> -
>
> Key: MINVOKER-99
> URL: http://jira.codehaus.org/browse/MINVOKER-99
> Project: Maven 2.x Invoker Plugin
> Issue Type: Bug
>Affects Versions: 1.5
> Environment: MacOS 10.6.2 with Maven 3.0-alpha6
>Reporter: Matthew McCullough
>
> I'm coding on an archetype project
> (http://github.com/sonatype/sonatype-archetype) and am using the install goal
> of Invoker 1.5. If I use an alternate repo with the ,
> the archetype JAR is not copied into the local repo location. If I use Maven
> 2.2.1, the resource is copied into the localRepositoryUrl location with no
> problem.
> I've commented out the and tags in the
> committed version so that it passes when built with Maven 3.0-alpha-6.
> File:
> http://github.com/sonatype/sonatype-archetype/blob/master/archetype-archetypes/quickstart/pom.xml
> To reproduce this.
> 1) Download Maven 3.0-alpha-6
> 2) Set it to be your active maven version
> 3) git clone g...@github.com:sonatype/sonatype-archetype.git
> 4) Hijack and uncomment the install and
> ${project.build.directory}/it/repo
> in the file archetype-archetypes/quickstart/pom.xml
> 5) build the entire source tree with "mvn install"
> 5) It will fail with the following error:
> [INFO] [INFO]
>
> [INFO] [INFO] BUILD FAILURE
> [INFO] [INFO]
>
> [INFO] [INFO] Total time: 15.576s
> [INFO] [INFO] Finished at: Mon Feb 15 19:49:33 MST 2010
> [INFO] [INFO] Final Memory: 6M/80M
> [INFO] [INFO]
>
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.0-alpha-4:generate
> (default-cli) on project standalone-pom: The desired archetype does not exist
> (org.sonatype.maven.archetype:quickstart:0.8.4-SNAPSHOT) -> [Help 1]
> [INFO] [ERROR]
> [INFO] [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [INFO] [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [INFO] [ERROR]
> [INFO] [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [INFO] [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [INFO] ..FAILED (16.8 s)
> [INFO] The build exited with code 1. See
> /Users/mccm06/Documents/Code/OpenSourceContribs/sonatype-archetype_git/archetype-archetypes/quickstart/target/it/projects/quickstart/build.log
> for details.
> [INFO] -
> [INFO] Build Summary:
> [INFO] Passed: 0, Failed: 1, Errors: 0, Skipped: 0
> [INFO] -
> [ERROR] The following builds failed:
> [ERROR] * quickstart
> [INFO] -
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 21.310s
> [INFO] Finished at: Mon Feb 15 19:49:34 MST 2010
> [INFO] Final Memory: 8M/80M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-invoker-plugin:1.5:run (integration-test) on
> project quickstart: 1 build failed. -> [Help 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] Created: (MSTAGE-13) stage plugin does not leverage the proxy settings in "settings.xml"
stage plugin does not leverage the proxy settings in "settings.xml" --- Key: MSTAGE-13 URL: http://jira.codehaus.org/browse/MSTAGE-13 Project: Maven 2.x Stage Plugin Issue Type: Bug Reporter: Matthias Weßendorf using the "stage" plugin behind a firewall is hard, as the given proxy settings in "settings.xml" are ignored. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MINSTALL-41) Install with classifier does not install pom
[ http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210315#action_210315 ] Benjamin Bentmann commented on MINSTALL-41: --- POMs never have classifiers. > Install with classifier does not install pom > > > Key: MINSTALL-41 > URL: http://jira.codehaus.org/browse/MINSTALL-41 > Project: Maven 2.x Install Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Michele Lorenzini >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.3 > > Attachments: maven-install-plugin-2.2.patch, pom.xml > > > I have a project wich I need to build only specifying a classifier (in > detail: a war project which I need to build with different profiles to > include different > configurations. So I set up different filters and the package produces > different classified wars). > When I install the artifact, I've got the attached artifact installed but the > pom is NOT installed. > The log says "No primary artifact to install, installing attached artifacts > instead". > It's maybe related to MINSTALL-18 as it seems the mojo does not recognize the > presence of a primary artifact and goes to install the attached artifacts > (without installing the POM). > Don't know if this is really a bug or if I am trying a strange/not valid > project configuration (a project without a primary artifact). -- 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: (MINSTALL-41) Install with classifier does not install pom
[ http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210314#action_210314 ] Ryan J edited comment on MINSTALL-41 at 2/16/10 6:12 AM: - Can someone clarify the correct (expected) behavior of POM installation when artifacts use classifiers for me? The way I understand it the test POM provided will produce and install classified artifacts and an unclassified POM: foobar-b-1.0-SNAPSHOT-local.jar foobar-b-1.0-SNAPSHOT-dev.jar foobar-b-1.0-SNAPSHOT-staging.jar foobar-b-1.0-SNAPSHOT.pom Eduard's comment suggests he expects the POM to also be classified: foobar-b-1.0-SNAPSHOT-local.jar foobar-b-1.0-SNAPSHOT-dev.jar foobar-b-1.0-SNAPSHOT-staging.jar foobar-b-1.0-SNAPSHOT-local.pom foobar-b-1.0-SNAPSHOT-dev.pom foobar-b-1.0-SNAPSHOT-staging.pom Which is correct? Also, Eduard, is it possible you forgot to specify a profile in the example you gave? It looks to me like an unclassified artifact was installed which would be the expected behavior if you forgot to specify a profile. was (Author: jptech): Can someone clarify the correct (expected) behavior of POM installation when artifacts use classifiers for me? The way I understand it the test POM provided will produce classified artifacts and an unclassified POM: foobar-b-1.0-SNAPSHOT-local.jar foobar-b-1.0-SNAPSHOT-dev.jar foobar-b-1.0-SNAPSHOT-staging.jar foobar-b-1.0-SNAPSHOT.pom Eduard's comment suggests he expects the POM to also be classified: foobar-b-1.0-SNAPSHOT-local.jar foobar-b-1.0-SNAPSHOT-dev.jar foobar-b-1.0-SNAPSHOT-staging.jar foobar-b-1.0-SNAPSHOT-local.pom foobar-b-1.0-SNAPSHOT-dev.pom foobar-b-1.0-SNAPSHOT-staging.pom Which is correct? Also, Eduard, is it possible you forgot to specify a profile in the example you gave? It looks to me like an unclassified artifact was installed which would be the expected behavior if you forgot to specify a profile. > Install with classifier does not install pom > > > Key: MINSTALL-41 > URL: http://jira.codehaus.org/browse/MINSTALL-41 > Project: Maven 2.x Install Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Michele Lorenzini >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.3 > > Attachments: maven-install-plugin-2.2.patch, pom.xml > > > I have a project wich I need to build only specifying a classifier (in > detail: a war project which I need to build with different profiles to > include different > configurations. So I set up different filters and the package produces > different classified wars). > When I install the artifact, I've got the attached artifact installed but the > pom is NOT installed. > The log says "No primary artifact to install, installing attached artifacts > instead". > It's maybe related to MINSTALL-18 as it seems the mojo does not recognize the > presence of a primary artifact and goes to install the attached artifacts > (without installing the POM). > Don't know if this is really a bug or if I am trying a strange/not valid > project configuration (a project without a primary artifact). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MINSTALL-41) Install with classifier does not install pom
[ http://jira.codehaus.org/browse/MINSTALL-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210314#action_210314 ] Ryan J commented on MINSTALL-41: Can someone clarify the correct (expected) behavior of POM installation when artifacts use classifiers for me? The way I understand it the test POM provided will produce classified artifacts and an unclassified POM: foobar-b-1.0-SNAPSHOT-local.jar foobar-b-1.0-SNAPSHOT-dev.jar foobar-b-1.0-SNAPSHOT-staging.jar foobar-b-1.0-SNAPSHOT.pom Eduard's comment suggests he expects the POM to also be classified: foobar-b-1.0-SNAPSHOT-local.jar foobar-b-1.0-SNAPSHOT-dev.jar foobar-b-1.0-SNAPSHOT-staging.jar foobar-b-1.0-SNAPSHOT-local.pom foobar-b-1.0-SNAPSHOT-dev.pom foobar-b-1.0-SNAPSHOT-staging.pom Which is correct? Also, Eduard, is it possible you forgot to specify a profile in the example you gave? It looks to me like an unclassified artifact was installed which would be the expected behavior if you forgot to specify a profile. > Install with classifier does not install pom > > > Key: MINSTALL-41 > URL: http://jira.codehaus.org/browse/MINSTALL-41 > Project: Maven 2.x Install Plugin > Issue Type: Bug >Affects Versions: 2.2 >Reporter: Michele Lorenzini >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.3 > > Attachments: maven-install-plugin-2.2.patch, pom.xml > > > I have a project wich I need to build only specifying a classifier (in > detail: a war project which I need to build with different profiles to > include different > configurations. So I set up different filters and the package produces > different classified wars). > When I install the artifact, I've got the attached artifact installed but the > pom is NOT installed. > The log says "No primary artifact to install, installing attached artifacts > instead". > It's maybe related to MINSTALL-18 as it seems the mojo does not recognize the > presence of a primary artifact and goes to install the attached artifacts > (without installing the POM). > Don't know if this is really a bug or if I am trying a strange/not valid > project configuration (a project without a primary artifact). -- 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: (DOXIA-380) Use of #include in APT page causes NullPointerException during page rendering
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alan Alberghini updated DOXIA-380: -- Attachment: VelocityTest.tar.gz > Use of #include in APT page causes NullPointerException during page rendering > - > > Key: DOXIA-380 > URL: http://jira.codehaus.org/browse/DOXIA-380 > Project: Maven Doxia > Issue Type: Bug > Components: Site Renderer > Environment: maven 2.2.1 >Reporter: Alan Alberghini >Priority: Minor > Attachments: apt-include.log, VelocityTest.tar.gz > > > In the last 2 days I tried to get this thing working. > The situation is the following: I'm working on a maven site project and, for > some pages, I'm currently using the APT format. > I'd really like to be able to include existing APT pages inside an APT page, > in order to make the collaboration between the 4 members of the project much > easier and smoother. > To give an idea, I'd like to do this: > merged-page.apt: > --- > Title > --- > --- > --- > Develeper 1 proposal: > > Developer 2 proposal: > > etc. > At first, I tried using the %snippet DOXIA macro, but the included APT page > would not be rendered to HTML even setting verbatim=false. > Then, I tried the #include macro from Velocity. I renamed my APT file to > filename.apt.vm in order to trigger the Velocity processor on it and put the > #include line in the file, but, whenever I launch maven site I keep getting > this error: > and the page is not generated. > Is there a way to fix this? -- 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: (DOXIA-380) Use of #include in APT page causes NullPointerException during page rendering
[ http://jira.codehaus.org/browse/DOXIA-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210302#action_210302 ] Alan Alberghini commented on DOXIA-380: --- Sure, no problem. I just stripped down my maven project and included a sample test page (index.apt.vm). The target site is rendered using "mvn site:site". The #set directive works, but the #include heavily messes things up. > Use of #include in APT page causes NullPointerException during page rendering > - > > Key: DOXIA-380 > URL: http://jira.codehaus.org/browse/DOXIA-380 > Project: Maven Doxia > Issue Type: Bug > Components: Site Renderer > Environment: maven 2.2.1 >Reporter: Alan Alberghini >Priority: Minor > Attachments: apt-include.log > > > In the last 2 days I tried to get this thing working. > The situation is the following: I'm working on a maven site project and, for > some pages, I'm currently using the APT format. > I'd really like to be able to include existing APT pages inside an APT page, > in order to make the collaboration between the 4 members of the project much > easier and smoother. > To give an idea, I'd like to do this: > merged-page.apt: > --- > Title > --- > --- > --- > Develeper 1 proposal: > > Developer 2 proposal: > > etc. > At first, I tried using the %snippet DOXIA macro, but the included APT page > would not be rendered to HTML even setting verbatim=false. > Then, I tried the #include macro from Velocity. I renamed my APT file to > filename.apt.vm in order to trigger the Velocity processor on it and put the > #include line in the file, but, whenever I launch maven site I keep getting > this error: > and the page is not generated. > Is there a way to fix this? -- 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-523) ReleaseUtil throws "java.lang.StringIndexOutOfBoundsException: String index out of range: -1"
[
http://jira.codehaus.org/browse/MRELEASE-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=210292#action_210292
]
Ulrich Hofstötter commented on MRELEASE-523:
PS: i use jdk 1.6.0_17
> ReleaseUtil throws "java.lang.StringIndexOutOfBoundsException: String index
> out of range: -1"
> -
>
> Key: MRELEASE-523
> URL: http://jira.codehaus.org/browse/MRELEASE-523
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.0
> Environment: Windows XP, Maven 2.2.1
>Reporter: Ulrich Hofstötter
> Attachments: log.txt
>
>
> Hello,
> i have an issue using the maven release plugin 2.0, previous versions did not
> have this issue.
> In a multimodule project, release:prepare exits with the attached stack trace.
> After a litte debugging, i found out that in ReleaseUtil, line 188
> String dir = FileUtils.normalize( p.getBasedir().getPath().replace( '\\', '/'
> ) );
> returns "c:\..." for the parent module, but "C:\..." for the first submodule.
> So in line 202
> basedir = StringUtils.getCommonPrefix( new String[]{dir, basedir} );
> results in an empty String, which leads to the exception in line 206.
> I will try to compose a simple example as soon as possible.
--
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: (MRELEASE-523) ReleaseUtil throws "java.lang.StringIndexOutOfBoundsException: String index out of range: -1"
ReleaseUtil throws "java.lang.StringIndexOutOfBoundsException: String index out
of range: -1"
-
Key: MRELEASE-523
URL: http://jira.codehaus.org/browse/MRELEASE-523
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.0
Environment: Windows XP, Maven 2.2.1
Reporter: Ulrich Hofstötter
Attachments: log.txt
Hello,
i have an issue using the maven release plugin 2.0, previous versions did not
have this issue.
In a multimodule project, release:prepare exits with the attached stack trace.
After a litte debugging, i found out that in ReleaseUtil, line 188
String dir = FileUtils.normalize( p.getBasedir().getPath().replace( '\\', '/' )
);
returns "c:\..." for the parent module, but "C:\..." for the first submodule.
So in line 202
basedir = StringUtils.getCommonPrefix( new String[]{dir, basedir} );
results in an empty String, which leads to the exception in line 206.
I will try to compose a simple example as soon as possible.
--
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
Re: [jira] Created: (MCHECKSTYLE-130) multimodule project requires src/main/java after 2.5 update
You should be posting this to the issue itself, replying to the mail won't be included. Maven devs - I've changed the Nabble forum to not allow posting to iss...@. Hopefully that will help. - Brett On 16/02/2010, at 10:02 AM, Briankous wrote: > > "However, you do not include java code in your web module." should read > "However, sometimes, you do not include java code in your web module." > > > Briankous wrote: >> >> It is because of a bug in check style 2.5. The check style is trying to do >> the check and if the directory is not there, it fails. However, you do not >> include java code in your web module. They say it will be fixed in 2.6. I >> do know this is not the best solution. But if you create just one >> directory without any file in it, the problem will be gone. Just a java >> directory under src\main\ >> >> Brian Ko >> > > -- > View this message in context: > http://old.nabble.com/Created%3A-%28MCHECKSTYLE-130%29-multimodule-project-requires-src-main-java-after-2.5-update-tp27592778p27601436.html > Sent from the Maven - Issues mailing list archive at Nabble.com. > -- Brett Porter br...@apache.org http://brettporter.wordpress.com/
