[jira] Updated: (MNG-2261) Profiles ignored when working with non-projects (such as archetype:create)
[ http://jira.codehaus.org/browse/MNG-2261?page=all ] Carlos Sanchez updated MNG-2261: Fix Version: 2.0.5 > Profiles ignored when working with non-projects (such as archetype:create) > -- > > Key: MNG-2261 > URL: http://jira.codehaus.org/browse/MNG-2261 > Project: Maven 2 > Type: Bug > Components: General > Versions: 2.0.4 > Reporter: Joakim Erdfelt > Fix For: 2.0.5 > Attachments: MNG-2261.patch > > > Several conditions have to be met to show this bug. > 1) Be in an environment that does not have access to repo1.maven.org, (such > as a corporate environment) > 2) Have no content in your local repository (a fresh install of maven 2.0.4) > 3) Attempt to use a plugin that has no project requirement (such as > archetype:create) > The plugin fails because access to repo1.maven.org cannot be accessed. > Recommended solution: > Create a settings.xml profile that changes the location of the 'central' > repository to point to an internal resource (such as a maven-proxy > installation). > > > > use_internal > > > central > Internal Central Repository > http://repo.internal.com/maven2 > > true > > > true > > > > > > central > Internal Central Repository > http://repo.internal.com/maven2 > > true > > > true > > > > > > > use_internal > > > Try again. > Still fails. > The reason is that the default behaviour for non-project execution is to use > the maven super pom, however there is a bug with that flow that does not > allow for the merging of the settings.xml 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] Commented: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_64536 ] Rahul Thakur commented on CONTINUUM-663: A quick note: SoC related updates can be checked out from: https://svn.codehaus.org/faqbot/trunk/sandbox/continuum-eclipse-plugin https://svn.codehaus.org/faqbot/trunk/sandbox/refactored-continuum-xfire > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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-2262) If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ
If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ -- Key: MNG-2262 URL: http://jira.codehaus.org/browse/MNG-2262 Project: Maven 2 Type: Bug Components: General Versions: 2.0.4 Reporter: james strachan Priority: Blocker We get the following... macstrac:/workspace/eclipse/activemq jstrachan$ mvn clean install -Dmaven.test.skip=true [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] ActiveMQ [INFO] ActiveMQ :: JAAS [INFO] ActiveMQ :: Core [INFO] ActiveCluster [INFO] ActiveMQ :: Console [INFO] ActiveMQ :: RA [INFO] ActiveMQ :: RAR [INFO] ActiveMQ :: Web [INFO] ActiveMQ :: Web Demo [INFO] ActiveMQ :: Optional [INFO] ActiveMQ :: GBean Interfaces [INFO] ActiveMQ :: GBeans [INFO] Bundle Plugin [INFO] ActiveMQ :: Assembly [INFO] [INFO] Building ActiveMQ [INFO]task-segment: [clean, install] [INFO] Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom [WARNING] Unable to get resource from repository codehaus.snapshots (http://snapshots.maven.codehaus.org/maven2) Downloading: http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom 0b downloaded [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING Downloading: http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom 0b downloaded [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING [WARNING] Unable to get resource from repository maven-csharp-plugins (http://maven-csharp.javaforge.com/repo) Downloading: http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom [WARNING] Unable to get resource from repository apache.snapshots (http://cvs.apache.org/maven-snapshot-repository) Downloading: http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom [WARNING] Unable to get resource from repository codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2) Downloading: http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom 0b downloaded [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING Downloading: http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom 0b downloaded [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING [WARNING] Unable to get resource from repository maven-csharp (http://maven-csharp.javaforge.com/repo) Downloading: http://cvs.apache.org/repository/org.apache.maven.plugins/poms/maven-surefire-plugin-2.1.3-SNAPSHOT.pom [WARNING] Unable to get resource from repository apache-maven1-snapshot (http://cvs.apache.org/repository) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-surefire-plugin Version: 2.1.3-SNAPSHOT Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-surefire-plugin:pom:2.1.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.maven.codehaus.org/maven2), apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), maven-csharp-plugins (http://maven-csharp.javaforge.com/repo), codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2), apache-maven1-snapshot (http://cvs.apache.org/repository), maven-csharp (http://maven-csharp.javaforge.com/repo) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 12 seconds [INFO] Finished at: Tue May 02 08:52:29 BST 2006 [INFO] Final Memory: 3M/6M [INFO] -- 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-2262) If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ
[ http://jira.codehaus.org/browse/MNG-2262?page=all ] Brett Porter closed MNG-2262: - Assign To: Brett Porter Resolution: Won't Fix snapshots get cleaned up periodically. You should be using the 2.1.3 release. > If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ > -- > > Key: MNG-2262 > URL: http://jira.codehaus.org/browse/MNG-2262 > Project: Maven 2 > Type: Bug > Components: General > Versions: 2.0.4 > Reporter: james strachan > Assignee: Brett Porter > Priority: Blocker > > > We get the following... > macstrac:/workspace/eclipse/activemq jstrachan$ mvn clean install > -Dmaven.test.skip=true > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] ActiveMQ > [INFO] ActiveMQ :: JAAS > [INFO] ActiveMQ :: Core > [INFO] ActiveCluster > [INFO] ActiveMQ :: Console > [INFO] ActiveMQ :: RA > [INFO] ActiveMQ :: RAR > [INFO] ActiveMQ :: Web > [INFO] ActiveMQ :: Web Demo > [INFO] ActiveMQ :: Optional > [INFO] ActiveMQ :: GBean Interfaces > [INFO] ActiveMQ :: GBeans > [INFO] Bundle Plugin > [INFO] ActiveMQ :: Assembly > [INFO] > > [INFO] Building ActiveMQ > [INFO]task-segment: [clean, install] > [INFO] > > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository codehaus.snapshots > (http://snapshots.maven.codehaus.org/maven2) > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository maven-csharp-plugins > (http://maven-csharp.javaforge.com/repo) > Downloading: > http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository apache.snapshots > (http://cvs.apache.org/maven-snapshot-repository) > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository codehaus-snapshot > (http://snapshots.maven.codehaus.org/maven2) > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository maven-csharp > (http://maven-csharp.javaforge.com/repo) > Downloading: > http://cvs.apache.org/repository/org.apache.maven.plugins/poms/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository apache-maven1-snapshot > (http://cvs.apache.org/repository) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.maven.plugins > ArtifactId: maven-surefire-plugin > Version: 2.1.3-SNAPSHOT > Reason: Unable to download the artifact from any repository > org.apache.maven.plugins:maven-surefire-plugin:pom:2.1.3-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > codehaus.snapshots (http://snapshots.maven.codehaus.org/maven2), > apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), > maven-csharp-plugins (http://maven-csharp.javaforge.com/repo), > codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2), > apache-maven1-snapshot (http://cvs.apache.org/repository), > maven-csharp (http://maven-csharp.javaforge.com/repo) > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time
[jira] Commented: (MNG-2262) If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ
[ http://jira.codehaus.org/browse/MNG-2262?page=comments#action_64541 ] Carlos Sanchez commented on MNG-2262: - Try removing the m1 repos from the pom (layout=legacy) and clean the repo Maven 1 repos don't work with snapshots. > If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ > -- > > Key: MNG-2262 > URL: http://jira.codehaus.org/browse/MNG-2262 > Project: Maven 2 > Type: Bug > Components: General > Versions: 2.0.4 > Reporter: james strachan > Assignee: Brett Porter > Priority: Blocker > > > We get the following... > macstrac:/workspace/eclipse/activemq jstrachan$ mvn clean install > -Dmaven.test.skip=true > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] ActiveMQ > [INFO] ActiveMQ :: JAAS > [INFO] ActiveMQ :: Core > [INFO] ActiveCluster > [INFO] ActiveMQ :: Console > [INFO] ActiveMQ :: RA > [INFO] ActiveMQ :: RAR > [INFO] ActiveMQ :: Web > [INFO] ActiveMQ :: Web Demo > [INFO] ActiveMQ :: Optional > [INFO] ActiveMQ :: GBean Interfaces > [INFO] ActiveMQ :: GBeans > [INFO] Bundle Plugin > [INFO] ActiveMQ :: Assembly > [INFO] > > [INFO] Building ActiveMQ > [INFO]task-segment: [clean, install] > [INFO] > > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository codehaus.snapshots > (http://snapshots.maven.codehaus.org/maven2) > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository maven-csharp-plugins > (http://maven-csharp.javaforge.com/repo) > Downloading: > http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository apache.snapshots > (http://cvs.apache.org/maven-snapshot-repository) > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository codehaus-snapshot > (http://snapshots.maven.codehaus.org/maven2) > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository maven-csharp > (http://maven-csharp.javaforge.com/repo) > Downloading: > http://cvs.apache.org/repository/org.apache.maven.plugins/poms/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository apache-maven1-snapshot > (http://cvs.apache.org/repository) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.maven.plugins > ArtifactId: maven-surefire-plugin > Version: 2.1.3-SNAPSHOT > Reason: Unable to download the artifact from any repository > org.apache.maven.plugins:maven-surefire-plugin:pom:2.1.3-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > codehaus.snapshots (http://snapshots.maven.codehaus.org/maven2), > apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), > maven-csharp-plugins (http://maven-csharp.javaforge.com/repo), > codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2), > apache-maven1-snapshot (http://cvs.apache.org/repository), > maven-csharp (http://maven-csharp.javaforge.com/repo) > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] T
[jira] Commented: (MNG-2262) If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ
[ http://jira.codehaus.org/browse/MNG-2262?page=comments#action_64542 ] Carlos Sanchez commented on MNG-2262: - Specially the http://maven-csharp.javaforge.com because instead of returning 404 status returns an empty page > If you zap the ~/.m2 directory then we can no longer build with m2 on ActiveMQ > -- > > Key: MNG-2262 > URL: http://jira.codehaus.org/browse/MNG-2262 > Project: Maven 2 > Type: Bug > Components: General > Versions: 2.0.4 > Reporter: james strachan > Assignee: Brett Porter > Priority: Blocker > > > We get the following... > macstrac:/workspace/eclipse/activemq jstrachan$ mvn clean install > -Dmaven.test.skip=true > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] ActiveMQ > [INFO] ActiveMQ :: JAAS > [INFO] ActiveMQ :: Core > [INFO] ActiveCluster > [INFO] ActiveMQ :: Console > [INFO] ActiveMQ :: RA > [INFO] ActiveMQ :: RAR > [INFO] ActiveMQ :: Web > [INFO] ActiveMQ :: Web Demo > [INFO] ActiveMQ :: Optional > [INFO] ActiveMQ :: GBean Interfaces > [INFO] ActiveMQ :: GBeans > [INFO] Bundle Plugin > [INFO] ActiveMQ :: Assembly > [INFO] > > [INFO] Building ActiveMQ > [INFO]task-segment: [clean, install] > [INFO] > > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository codehaus.snapshots > (http://snapshots.maven.codehaus.org/maven2) > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository maven-csharp-plugins > (http://maven-csharp.javaforge.com/repo) > Downloading: > http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository apache.snapshots > (http://cvs.apache.org/maven-snapshot-repository) > Downloading: > http://snapshots.maven.codehaus.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository codehaus-snapshot > (http://snapshots.maven.codehaus.org/maven2) > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - RETRYING > Downloading: > http://maven-csharp.javaforge.com/repo/org/apache/maven/plugins/maven-surefire-plugin/2.1.3-SNAPSHOT/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > 0b downloaded > [WARNING] *** CHECKSUM FAILED - Invalid checksum file - IGNORING > [WARNING] Unable to get resource from repository maven-csharp > (http://maven-csharp.javaforge.com/repo) > Downloading: > http://cvs.apache.org/repository/org.apache.maven.plugins/poms/maven-surefire-plugin-2.1.3-SNAPSHOT.pom > [WARNING] Unable to get resource from repository apache-maven1-snapshot > (http://cvs.apache.org/repository) > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > GroupId: org.apache.maven.plugins > ArtifactId: maven-surefire-plugin > Version: 2.1.3-SNAPSHOT > Reason: Unable to download the artifact from any repository > org.apache.maven.plugins:maven-surefire-plugin:pom:2.1.3-SNAPSHOT > from the specified remote repositories: > central (http://repo1.maven.org/maven2), > codehaus.snapshots (http://snapshots.maven.codehaus.org/maven2), > apache.snapshots (http://cvs.apache.org/maven-snapshot-repository), > maven-csharp-plugins (http://maven-csharp.javaforge.com/repo), > codehaus-snapshot (http://snapshots.maven.codehaus.org/maven2), > apache-maven1-snapshot (http://cvs.apache.org/repository), > maven-csharp (http://maven-csharp.javaforge.com/repo) > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total
[jira] Created: (CONTINUUM-678) Email notification list is duplicated at each build (and then grows exponentially)
Email notification list is duplicated at each build (and then grows exponentially) --- Key: CONTINUUM-678 URL: http://jira.codehaus.org/browse/CONTINUUM-678 Project: Continuum Type: Bug Components: Mail Notifier, Core system Versions: 1.0.3 Environment: Windows XP Reporter: Carlo Bonamico I add a maven 1 project. Then, if I manually add a mail notifier in the project config page, each time I request a build, the notifier list gets duplicated, so the number of notifications grows exponentially... Besides, the build number is incremented by two and not by one. The Maven 1 project is a multi-project. -- 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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_64546 ] Rahul Thakur commented on CONTINUUM-663: Keep in mind that the other components/libs that will be developed along with this plugin should be Eclipse (or any other IDE ) agnostic such that they can be used by clients like gnome/kde/windows applets. The applets can monitor the Continuum instance without having to run from within an IDE. > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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: (MINSTALL-20) Variables are not replaced into installed pom file
Variables are not replaced into installed pom file
--
Key: MINSTALL-20
URL: http://jira.codehaus.org/browse/MINSTALL-20
Project: Maven 2.x Install Plugin
Type: Bug
Versions: 2.0
Environment: Windows, Solaris
Maven version 2.0.4
Reporter: Laurent Dauvilaire
Variables are not replaced into installed pom file.
Here is a sample pom file
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
com.xxx.root
root
pom
${prop.version}
My Project
...
3.0.20
The installed pom is into
${localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
is the same as the project pom file but the version referenced into the
installed pom file is ${prop.version} instead of 3.0.20
which creates problem to artifacts depending of this one.
Thanks in advance
--
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: (CONTINUUM-663) Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin
[ http://jira.codehaus.org/browse/CONTINUUM-663?page=comments#action_64547 ] Rahul Thakur commented on CONTINUUM-663: Moving this proposal to: http://docs.codehaus.org/display/CONTINUUM/Continuum+Eclipse+Plugin+proposal > Google Summer Of Code 2006 proposal for Continuum Eclipse Plugin > - > > Key: CONTINUUM-663 > URL: http://jira.codehaus.org/browse/CONTINUUM-663 > Project: Continuum > Type: New Feature > Environment: Maven 2.0.x, Continuum 1.0.x, Eclipse 3.2 > Reporter: Rahul Thakur > Attachments: Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt, > Continuum-Eclipse-plugin-Google-SOC2006-proposal.txt > > Original Estimate: 8 weeks > Remaining: 8 weeks > > It is proposed for Google SOC 2006 to develop a Continuum Eclipse Plugin that > could be used by Eclipse users to manage project builds on a remote Continuum > server. -- 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-873) Upload JAI POMs
Upload JAI POMs --- Key: MAVENUPLOAD-873 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 Project: maven-upload-requests Type: Task Reporter: Joerg Schaible POMs for JAI are missing on ibiblio. Additional bundles: http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- 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-874) CoWarp 0.5 Release
CoWarp 0.5 Release -- Key: MAVENUPLOAD-874 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-874 Project: maven-upload-requests Type: Task Reporter: Carsten Ziegeler This is the latest release of CoWarp - an extension to the Apache Cocoon project. -- 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: (MAVEN-1753) Re-introduce xerces in maven's core dependencies
[ http://jira.codehaus.org/browse/MAVEN-1753?page=comments#action_64556 ] Jeff Jensen commented on MAVEN-1753: (Per Arnaud's email request: Can you tell us what you had to change to use this plugin with maven 1.1) The dependecies changed to make it work were all parser related: - Removed dependency on xercesImpl jar - Added dependency on xerces 2.4.0 jar - Upgraded Xalan dependency to 2.7.0 jar Then the last problem was: java.lang.ClassNotFoundException: org/apache/xerces/parsers/SAXParser Upgrading to m1-b3-snapshot of 4/30/06 solved that one. I'm pretty sure I was using the snapshot just before 4/30/06 that did not work. > Re-introduce xerces in maven's core dependencies > > > Key: MAVEN-1753 > URL: http://jira.codehaus.org/browse/MAVEN-1753 > Project: Maven > Type: Task > Versions: 1.1-beta-1, 1.1-beta-2 > Reporter: Arnaud Heritier > Assignee: Arnaud Heritier > Fix For: 1.1-beta-3 > > > Because maven 1.1 works only with a jdk >= 1.4 whereas maven 1.0 requires at > least the jdk 1.3, we removed xerces from the distribution (the xml parser > API implemented by crimson is available in the jdk) > The problem is that there's some bugs in crimson that are really annoying. > Particularly there are a lot of issues with entities management. > To fix them we have to readd xerces in the distribution. -- 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: (SUREFIRE-38) Surefire Maven2 Plugin fails to run EJB3 Embeddable Container (but mvn eclipse:eclipse succeeds)
[ http://jira.codehaus.org/browse/SUREFIRE-38?page=comments#action_64560 ] Dan Greening commented on SUREFIRE-38: -- I think there must have been some other improvement to Surefire or JBoss Embeddable, because I just tried recompiling my EJB3 component (now under JBoss EJB3 Embeddable version Alpha6 and -- without any changes -- it now passes all the tests. Please note, I still must use my personal copy of the EJB plugin, though I provided a patch a month ago in MEJB-6 which we all agree is good. CAN MEJB-6 PLEASE BE RESOLVED? It is marked as a "trivial" bug, but it isn't. EJB3s cannot be built properly with the official EJB plugin, however the patch I provided in MEJB-6 allows this to be done, and also retains the proper checking for EJB 2.1 (the EJB version is a pom-supplied parameter). Pretty, pretty please? > Surefire Maven2 Plugin fails to run EJB3 Embeddable Container (but mvn > eclipse:eclipse succeeds) > > > Key: SUREFIRE-38 > URL: http://jira.codehaus.org/browse/SUREFIRE-38 > Project: surefire > Type: Bug > Versions: 1.5.2 > Environment: maven 2.0.3 > Reporter: Dan Greening > Assignee: Brett Porter > Priority: Critical > Attachments: jboss-ejb3-embeddable-test-with-junit.tar.gz > > > JBoss's EJB3 embeddable container, which is very handy for unit testing EJB's > without using an application server, will not work under surefire in Maven2. > It works fine under Maven1. Furthermore, it ALSO works using the Maven2 > eclipse-plugin generated .project/.classpath in Eclipse. > Here's a complete set of instruction to reproduce it. > This is a test showing that surefire does not properly handle the JBoss EJB3 > embeddable container. > The instructions are a bit complex, because you have to download a package of > JARs from JBoss. (They make the test file too big to attach in JIRA.) > To confirm, > 1. cd /tmp > 2. Surf to > http://sourceforge.net/project/showfiles.php?group_id=22866&package_id=132063 > 3. Download jboss-EJB-3.0_Embeddable_ALPHA_5.zip. Put it in /tmp. This is >the latest EJB3 embeddable system. > 4. unzip jboss-EJB-3.0_Embeddable_ALPHA_5.zip > 5. Download jboss-ejb3-embeddable-test-with-junit.tar.gz (it is an attachment >to this JIRA ticket). > 6. tar xvfz jboss-ejb3-embeddable-test-with-junit.tar.gz > 7. cd jboss-ejb3-embeddable-test-with-junit > 8. cp -pR ../jboss-EJB-3.0_Embeddable_ALPHA_5/lib lib > 9. ./deploy-jars.perl > 10. type "mvn test". > 11. Note that the test fails. > 12. Type "mvn eclipse:eclipse" > 13. Import the jboss-ejb3-embeddable-test-with-junit directory into Eclipse > as an "existing project". > 14. Set M2_REPO build variable to your .m2/repository folder. > 15. Run the EmbeddedEjb3TestCase as a JUnit test in Eclipse. It works. -- 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-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=all ] Jared Bunting updated MEV-363: -- Attachment: spring-poms-1.2.7.zip > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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-875) Upload jaxws jars on ibiblio
Upload jaxws jars on ibiblio Key: MAVENUPLOAD-875 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-875 Project: maven-upload-requests Type: Task Reporter: Guillaume Nodet -- 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-876) Upload mx4j-tools 3.0.1
Upload mx4j-tools 3.0.1 --- Key: MAVENUPLOAD-876 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-876 Project: maven-upload-requests Type: Task Reporter: Guillaume Nodet -- 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: (MSUREFIRE-85) Surefire does not run TestNG tests with JavaDoc annotations under Java 5
[ http://jira.codehaus.org/browse/MSUREFIRE-85?page=comments#action_64562 ] Andreas Guther commented on MSUREFIRE-85: - I must admit that I can now (?) run the tests as expected as well. I created a sample project and added two TestNG classes, one ending with Test and one without. The one with Test at the end was run but the tests (two) were not executed: C:\workspace\my-app>mvn test [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 2 source files to C:\workspace\my-app\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports --- T E S T S --- Running com.mycompany.app.AppTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running com.mycompany.app.TestNgJavaOneTngTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue May 02 07:14:11 PDT 2006 [INFO] Final Memory: 4M/508M [INFO] When I use a testng configuration file the tests are executed: --- T E S T S --- Running Test with JavaDoc Annotations under Java 1.4 com.mycompany.app.JavaOneFourTngSample: beforeClass com.mycompany.app.JavaOneFourTngSample: beforeMethod com.mycompany.app.JavaOneFourTngSample: someTestMethod com.mycompany.app.JavaOneFourTngSample: beforeMethod Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.032 sec <<< FAILURE! Results : Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 [ERROR] There are test failures. It also appears that the JUnit test is not ignored. Is there only an either/or but not JUnit and TestNG together? I know, I can include JUnit tests in the TestNG file, but finding them based on a pattern and executing them both would be nice. I will attache my example project with configuration and files. > Surefire does not run TestNG tests with JavaDoc annotations under Java 5 > - > > Key: MSUREFIRE-85 > URL: http://jira.codehaus.org/browse/MSUREFIRE-85 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: Windows XP, Maven 2.0.3, Surefire plug-in, TestNG 4.7, Java 5 > Reporter: Andreas Guther > Assignee: Brett Porter > > > I have TestNG tests with Java 1.4 JavaDoc annotations. The tests are > executed with a testng.xml file. I need to be able to execute those tests > under Java 5. As it appears Surefire seems not to be able to recognize those > TestNG tests with Java 1.4 annotations and does not execute a single test > listed in the TestNG.xml test suite file. > Relevant parts of my configuration are as follows: > > org.testng > testng > 4.7 > test > jdk14 > > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.4 > 1.4 > > > > maven-surefire-plugin > > > true > > > src/test/resources/testng-xml-export.xml > > > > ... > > > apache.snapshots > > http://cvs.apache.org/maven-snapshot-repository > > > Maven Snapshots > http://snapshots.maven.codehaus.org/maven2/ >
[jira] Updated: (MSUREFIRE-85) Surefire does not run TestNG tests with JavaDoc annotations under Java 5
[ http://jira.codehaus.org/browse/MSUREFIRE-85?page=all ] Andreas Guther updated MSUREFIRE-85: Attachment: my-app.zip > Surefire does not run TestNG tests with JavaDoc annotations under Java 5 > - > > Key: MSUREFIRE-85 > URL: http://jira.codehaus.org/browse/MSUREFIRE-85 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: Windows XP, Maven 2.0.3, Surefire plug-in, TestNG 4.7, Java 5 > Reporter: Andreas Guther > Assignee: Brett Porter > Attachments: my-app.zip > > > I have TestNG tests with Java 1.4 JavaDoc annotations. The tests are > executed with a testng.xml file. I need to be able to execute those tests > under Java 5. As it appears Surefire seems not to be able to recognize those > TestNG tests with Java 1.4 annotations and does not execute a single test > listed in the TestNG.xml test suite file. > Relevant parts of my configuration are as follows: > > org.testng > testng > 4.7 > test > jdk14 > > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.4 > 1.4 > > > > maven-surefire-plugin > > > true > > > src/test/resources/testng-xml-export.xml > > > > ... > > > apache.snapshots > > http://cvs.apache.org/maven-snapshot-repository > > > Maven Snapshots > http://snapshots.maven.codehaus.org/maven2/ > > true > > > false > > > > testng.xml > > > > >name="mt.ztelligence.questionnaire.SurveyProjectXMlDataInjectorTestNg" /> > >name="mt.ztelligence.survey.util.SurveyBuilderDataExtractorTestNg"/> > > > -- 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: (MSUREFIRE-85) Surefire does not run TestNG tests with JavaDoc annotations under Java 5
[ http://jira.codehaus.org/browse/MSUREFIRE-85?page=comments#action_64564 ] Brett Porter commented on MSUREFIRE-85: --- can you please file a new bug > Surefire does not run TestNG tests with JavaDoc annotations under Java 5 > - > > Key: MSUREFIRE-85 > URL: http://jira.codehaus.org/browse/MSUREFIRE-85 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: Windows XP, Maven 2.0.3, Surefire plug-in, TestNG 4.7, Java 5 > Reporter: Andreas Guther > Assignee: Brett Porter > Attachments: my-app.zip > > > I have TestNG tests with Java 1.4 JavaDoc annotations. The tests are > executed with a testng.xml file. I need to be able to execute those tests > under Java 5. As it appears Surefire seems not to be able to recognize those > TestNG tests with Java 1.4 annotations and does not execute a single test > listed in the TestNG.xml test suite file. > Relevant parts of my configuration are as follows: > > org.testng > testng > 4.7 > test > jdk14 > > > > org.apache.maven.plugins > maven-compiler-plugin > > 1.4 > 1.4 > > > > maven-surefire-plugin > > > true > > > src/test/resources/testng-xml-export.xml > > > > ... > > > apache.snapshots > > http://cvs.apache.org/maven-snapshot-repository > > > Maven Snapshots > http://snapshots.maven.codehaus.org/maven2/ > > true > > > false > > > > testng.xml > > > > >name="mt.ztelligence.questionnaire.SurveyProjectXMlDataInjectorTestNg" /> > >name="mt.ztelligence.survey.util.SurveyBuilderDataExtractorTestNg"/> > > > -- 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: (MNGECLIPSE-116) 0.0.7 plugin will not load. Embedder related exception
[ http://jira.codehaus.org/browse/MNGECLIPSE-116?page=comments#action_64566 ] Cliff Resnick commented on MNGECLIPSE-116: -- After a little debugging I faound that Maven Embedder assumes local repository is under /.m2. Mine is not since, the network policy here limits (network replicated) user home space. Even though Embedder has a 'setLocalRepositoryDirectory', it' seems to be disregarded, as is setAlignWithUserInstallation; everything hinges on : if((new File(userHome, ".m2")).exists()) alignWithUserInstallation = true; No alignWithUserInstallation means localRepository = null; A way around this would be to launch eclipse overriding System property 'user.home' and make sure there is an .m2 dir to whereever it's set. This would solve the null local repository, but then the whole thing starts to smell. I mean, isn't the idea with aligning with user installation to get settings from $M2_HOME/conf/settings.xml? Shouldn't there be a setM2Home method on embedder, or how will it find settings.xml? Meanwhile it won't even let you set repository location. Hopefully I'm missing something since I only had time to look at it briefly, but embedder seems to still be a work in progress... > 0.0.7 plugin will not load. Embedder related exception > -- > > Key: MNGECLIPSE-116 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-116 > Project: Maven 2.x Extension for Eclipse > Type: Bug > Versions: 0.0.7 > Environment: WinXP, Eclipse 3.1.2, Maven2.0.4 > Reporter: Cliff Resnick > Assignee: Eugene Kuleshov > Fix For: 0.0.7 > > > I upgraded from 0.0.5 to 0.0.7 and the plugin fails to load. > Below is output from the workspace log file: > !MESSAGE An error occurred while automatically activating bundle > org.maven.ide.eclipse (443). > !STACK 0 > org.osgi.framework.BundleException: Exception in > org.maven.ide.eclipse.Maven2Plugin.start() of bundle org.maven.ide.eclipse. > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.startActivator(BundleContextImpl.java:1013) > at > org.eclipse.osgi.framework.internal.core.BundleContextImpl.start(BundleContextImpl.java:969) > at > org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:316) > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:264) > at > org.eclipse.core.runtime.adaptor.EclipseClassLoader.findLocalClass(EclipseClassLoader.java:116) > at > org.eclipse.osgi.framework.internal.core.BundleLoader.findLocalClass(BundleLoader.java:337) > at > org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:389) > at > org.eclipse.osgi.framework.internal.core.BundleLoader.findClass(BundleLoader.java:350) > at > org.eclipse.osgi.framework.adaptor.core.AbstractClassLoader.loadClass(AbstractClassLoader.java:78) > at java.lang.ClassLoader.loadClass(ClassLoader.java:235) > at > org.eclipse.osgi.framework.internal.core.BundleLoader.loadClass(BundleLoader.java:275) > at > org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:227) > at > org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1248) > at > org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:152) > at > org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:142) > at > org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:129) > at > org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:48) > at > org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:240) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69) > at > org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:236) > at > org.eclipse.ui.internal.dialogs.WorkbenchPreferenceNode.createPage(WorkbenchPreferenceNode.java:46) > at > org.eclipse.jface.preference.PreferenceDialog.createPage(PreferenceDialog.java:1211) > at > org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.createPage(FilteredPreferenceDialog.java:238) > at > org.eclipse.jface.preference.PreferenceDialog.showPage(PreferenceDialog.java:1114) > at > org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:351) > at > org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:638) > at > org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763) > at > org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java
[jira] Created: (MNG-2263) War packaging fails with long file names
War packaging fails with long file names Key: MNG-2263 URL: http://jira.codehaus.org/browse/MNG-2263 Project: Maven 2 Type: Bug Versions: 2.0.4 Environment: Windows Maven 2.0.4 Reporter: Laurent Dauvilaire The package action fails when file name are too long. The error does not occurs when the path of the project is shorter (ie test into C:/x) See stack trace below: [INFO] [war:war] [INFO] Exploding webapp... [INFO] Copy webapp resources to d:\Home\LDauvilaire\src\Repository\SVN\JHub\modules\display-webapp\modules\hub-internal\..\..\..\..\target\dev\3.0.20\hub-webapp-internal\hub-webapp-internal-3.0.20 [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error assembling WAR Embedded error: Could not explode webapp... d:\Home\LDauvilaire\src\Repository\SVN\JHub\modules\display-webapp\modules\hub-internal\..\..\..\..\target\dev\3.0.20\hub-webapp-internal\hub-webapp-internal-3.0.20\fceditor\editor\dialog\fck_spellerpages\spellerpages\server-scripts\spellchecker.cfm (The filename, directory name, or volume label syntax is incorrect) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling WAR at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) 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 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) Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling WAR at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:91) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) ... 16 more Caused by: org.apache.maven.plugin.MojoExecutionException: Could not explode webapp... at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:202) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:108) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:86) ... 18 more Caused by: java.io.FileNotFoundException: d:\Home\LDauvilaire\src\Repository\SVN\JHub\modules\display-webapp\modules\hub-internal\..\..\..\..\target\dev\3.0.20\hub-webapp-internal\hub-webapp-internal-3.0.20\fceditor\editor\dialog\fck_spellerpages\spellerpages\server-scripts\spellchecker.cfm (The filename, directory name, or volume label syntax is incorrect) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:179) at java.io.FileOutputStream.(FileOutputStream.java:131) at org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:821) at org.apache.maven.plugin.war.AbstractWarMojo.copyResources(AbstractWarMojo.java:230) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:196) ... 20 more -- 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-877) OpenWFE 1.7.0pre9 upload request
OpenWFE 1.7.0pre9 upload request Key: MAVENUPLOAD-877 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-877 Project: maven-upload-requests Type: Task Reporter: John Mettraux http://openwfe.org/upload/openwfe-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-applic-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-embed-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-embed-wom-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-engine-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-engine-actions-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-worklist-1.7.0pre9-bundle.jar http://openwfe.org/upload/openwfe-worklist-actions-1.7.0pre9-bundle.jar http://www.openwfe.org http://web.openwfe.org/display/openwfe/OpenWFE+people OpenWFE is an open source workflow engine under a BSD license. The main reason for this request upload is that the Magnolia team (http://www.magnolia.info) is integrating OpenWFE as the workflow engine within their CMS. As they are heavy Maven2 users... OpenWFE would then also benefit to other Maven2 users. -- 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: (MNGECLIPSE-117) Eclipse 3.2
Eclipse 3.2 --- Key: MNGECLIPSE-117 URL: http://jira.codehaus.org/browse/MNGECLIPSE-117 Project: Maven 2.x Extension for Eclipse Type: Wish Environment: Eclipse 3.2RC2 MacOSX 10.4.6 [Tiger] Intel Core Processor JDK 1.5 Reporter: Brice Robert Assigned to: Eugene Kuleshov Priority: Trivial I am a big fan of Maven2 and recently used Maven2 plugin which uses the famous mvn eclipse:eclipse. Naturally, I moved to Maven2 Extension plugin for Eclipse since it handles the M2_HOME variable appropriately. It works pretty fine at work using Eclipse 3.1.2 but since I have a mac [Intel] at home I can only use the upcoming version of Eclipse 3.2 due to SWT Shared libraries restrictions. I have gone through almost all issues in the list but didn't see anything related to Eclipse 3.2 In brief, when installing the plugin everything is Ok but I end up with manually assigning the famous M2_HOME variable in eclipse. Actually the M2_HOME variable name is more verbose the the Maven2 eclipse plugin. Any hint will be helpful. 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] Updated: (MNGECLIPSE-117) M2_HOME variable
[ http://jira.codehaus.org/browse/MNGECLIPSE-117?page=all ] Eugene Kuleshov updated MNGECLIPSE-117: --- Summary: M2_HOME variable (was: Eclipse 3.2) > M2_HOME variable > > > Key: MNGECLIPSE-117 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-117 > Project: Maven 2.x Extension for Eclipse > Type: Wish > Environment: Eclipse 3.2RC2 > MacOSX 10.4.6 [Tiger] > Intel Core Processor > JDK 1.5 > Reporter: Brice Robert > Assignee: Eugene Kuleshov > Priority: Trivial > > > I am a big fan of Maven2 and recently used Maven2 plugin which uses the > famous mvn eclipse:eclipse. Naturally, I moved to Maven2 Extension plugin for > Eclipse since it handles the M2_HOME variable appropriately. > It works pretty fine at work using Eclipse 3.1.2 but since I have a mac > [Intel] at home I can only use the upcoming version of Eclipse 3.2 due to SWT > Shared libraries restrictions. > I have gone through almost all issues in the list but didn't see anything > related to Eclipse 3.2 > In brief, when installing the plugin everything is Ok but I end up with > manually assigning the famous M2_HOME variable in eclipse. Actually the > M2_HOME variable name is more verbose the the Maven2 eclipse plugin. > Any hint will be helpful. > 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] Created: (MSUREFIRE-97) TestNG tests are not executed if invoked by */*Test.java naming pattern
TestNG tests are not executed if invoked by */*Test.java naming pattern --- Key: MSUREFIRE-97 URL: http://jira.codehaus.org/browse/MSUREFIRE-97 Project: Maven 2.x Surefire Plugin Type: Bug Environment: Windows XP, Maven 2.0.4, Surefire from snapshot server Reporter: Andreas Guther I created an example project and added two testng tests, one ending with *Test.java, one with a not Test containing name. Surefire seems to be able to find the test but does not execute the tests inside the class (one should succeed, one should fail). The console output is below. I will attach my example project in zip format to the issue report. C:\workspace\my-app>mvn test [INFO] Scanning for projects... [INFO] [INFO] Building Maven Quick Start Archetype [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] Compiling 2 source files to C:\workspace\my-app\target\test-classes [INFO] [surefire:test] [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports --- T E S T S --- Running com.mycompany.app.AppTest Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec Running com.mycompany.app.TestNgJavaOneTngTest Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec Results : Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue May 02 07:14:11 PDT 2006 [INFO] Final Memory: 4M/508M [INFO] -- 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: (MNGECLIPSE-117) M2_HOME variable
[ http://jira.codehaus.org/browse/MNGECLIPSE-117?page=all ] Eugene Kuleshov closed MNGECLIPSE-117: -- Resolution: Won't Fix Maven 2.x Extension for Eclipse (http://maven.apache.org/eclipse-plugin.html) never been using M2_HOME variable and will not be using it in the future. > M2_HOME variable > > > Key: MNGECLIPSE-117 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-117 > Project: Maven 2.x Extension for Eclipse > Type: Wish > Environment: Eclipse 3.2RC2 > MacOSX 10.4.6 [Tiger] > Intel Core Processor > JDK 1.5 > Reporter: Brice Robert > Assignee: Eugene Kuleshov > Priority: Trivial > > > I am a big fan of Maven2 and recently used Maven2 plugin which uses the > famous mvn eclipse:eclipse. Naturally, I moved to Maven2 Extension plugin for > Eclipse since it handles the M2_HOME variable appropriately. > It works pretty fine at work using Eclipse 3.1.2 but since I have a mac > [Intel] at home I can only use the upcoming version of Eclipse 3.2 due to SWT > Shared libraries restrictions. > I have gone through almost all issues in the list but didn't see anything > related to Eclipse 3.2 > In brief, when installing the plugin everything is Ok but I end up with > manually assigning the famous M2_HOME variable in eclipse. Actually the > M2_HOME variable name is more verbose the the Maven2 eclipse plugin. > Any hint will be helpful. > 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] Updated: (MSUREFIRE-97) TestNG tests are not executed if invoked by */*Test.java naming pattern
[ http://jira.codehaus.org/browse/MSUREFIRE-97?page=all ] Andreas Guther updated MSUREFIRE-97: Attachment: my-app-2.zip > TestNG tests are not executed if invoked by */*Test.java naming pattern > --- > > Key: MSUREFIRE-97 > URL: http://jira.codehaus.org/browse/MSUREFIRE-97 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: Windows XP, Maven 2.0.4, Surefire from snapshot server > Reporter: Andreas Guther > Attachments: my-app-2.zip > > > I created an example project and added two testng tests, one ending with > *Test.java, one with a not Test containing name. Surefire seems to be able > to find the test but does not execute the tests inside the class (one should > succeed, one should fail). The console output is below. I will attach my > example project in zip format to the issue report. > C:\workspace\my-app>mvn test > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Maven Quick Start Archetype > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > Compiling 2 source files to C:\workspace\my-app\target\test-classes > [INFO] [surefire:test] > [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports > --- > T E S T S > --- > Running com.mycompany.app.AppTest > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.015 sec > Running com.mycompany.app.TestNgJavaOneTngTest > Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec > Results : > Tests run: 1, Failures: 0, Errors: 0, Skipped: 0 > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 2 seconds > [INFO] Finished at: Tue May 02 07:14:11 PDT 2006 > [INFO] Final Memory: 4M/508M > [INFO] > -- 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: (MSUREFIRE-98) JUnit Tests are not executed if TestNG configuration file is used to invoke TestNG tests
JUnit Tests are not executed if TestNG configuration file is used to invoke TestNG tests Key: MSUREFIRE-98 URL: http://jira.codehaus.org/browse/MSUREFIRE-98 Project: Maven 2.x Surefire Plugin Type: Bug Environment: Windows XP, Maven 2.0.4, Java 1.4, Surefire from Snapshot server Reporter: Andreas Guther Attachments: my-app.zip I have JUnit tests and TestNG unit tests in the same project. If I use a TestNG XML configurartion file only the files (TestNG) listed in the configuration file are executed. JUnit test files are ignored. TestNG allows to include JUnit tests in the configuration, but I would expect that JUnit tests should be found based on the standard naming pattern and in addition TestNG classes as listed in the TestNG XML config file are executed as well. Expected that JUnit files are executed and in addition TestNG files. It should be possible to use different test frameworks in the same project. I will attach the example project. Output: C:\workspace\my-app>mvn test [INFO] Scanning for projects... [INFO] [INFO] Building Are JUnit Tests Ignored if TestNG Config XML is used? [INFO]task-segment: [test] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date [INFO] [surefire:test] [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports --- T E S T S --- Running Test with JavaDoc Annotations under Java 1.4 com.mycompany.app.JavaOneFourTngSample: beforeClass com.mycompany.app.JavaOneFourTngSample: beforeMethod com.mycompany.app.JavaOneFourTngSample: someTestMethod com.mycompany.app.JavaOneFourTngSample: beforeMethod Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec <<< FAILURE! Results : Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 [ERROR] There are test failures. [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Tue May 02 09:38:59 PDT 2006 [INFO] Final Memory: 4M/508M [INFO] -- 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: (MSUREFIRE-98) JUnit Tests are not executed if TestNG configuration file is used to invoke TestNG tests
[ http://jira.codehaus.org/browse/MSUREFIRE-98?page=all ] Andreas Guther updated MSUREFIRE-98: Attachment: my-app.zip > JUnit Tests are not executed if TestNG configuration file is used to invoke > TestNG tests > > > Key: MSUREFIRE-98 > URL: http://jira.codehaus.org/browse/MSUREFIRE-98 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: Windows XP, Maven 2.0.4, Java 1.4, Surefire from Snapshot server > Reporter: Andreas Guther > Attachments: my-app.zip > > > I have JUnit tests and TestNG unit tests in the same project. If I use a > TestNG XML configurartion file only the files (TestNG) listed in the > configuration file are executed. JUnit test files are ignored. TestNG > allows to include JUnit tests in the configuration, but I would expect that > JUnit tests should be found based on the standard naming pattern and in > addition TestNG classes as listed in the TestNG XML config file are executed > as well. > Expected that JUnit files are executed and in addition TestNG files. It > should be possible to use different test frameworks in the same project. > I will attach the example project. > Output: > C:\workspace\my-app>mvn test > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Are JUnit Tests Ignored if TestNG Config XML is used? > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [surefire:test] > [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports > --- > T E S T S > --- > Running Test with JavaDoc Annotations under Java 1.4 > com.mycompany.app.JavaOneFourTngSample: beforeClass > com.mycompany.app.JavaOneFourTngSample: beforeMethod > com.mycompany.app.JavaOneFourTngSample: someTestMethod > com.mycompany.app.JavaOneFourTngSample: beforeMethod > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec <<< > FAILURE! > Results : > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 > [ERROR] There are test failures. > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Tue May 02 09:38:59 PDT 2006 > [INFO] Final Memory: 4M/508M > [INFO] > -- 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: (MNGECLIPSE-118) Support for Eclipse 3.2
Support for Eclipse 3.2 --- Key: MNGECLIPSE-118 URL: http://jira.codehaus.org/browse/MNGECLIPSE-118 Project: Maven 2.x Extension for Eclipse Type: Wish Environment: Eclipse 3.2RC2 MacOSX 10.4.6 [Tiger] Intel Core Processor JDK 1.5 Reporter: Brice Robert Assigned to: Eugene Kuleshov Priority: Minor Any support for Eclipse 3.2 soon? Using Mac on intel prevents me for using Eclipse 3.1.2 Any hint will help 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: (MSUREFIRE-98) JUnit Tests are not executed if TestNG configuration file is used to invoke TestNG tests
[ http://jira.codehaus.org/browse/MSUREFIRE-98?page=comments#action_64573 ] Andreas Guther commented on MSUREFIRE-98: - Correction regarding environment: Actually the environment was not listed correctly. I am running with Java 1.5 but generate 1.4 code. TestNG is configured with JavaDoc annotations. > JUnit Tests are not executed if TestNG configuration file is used to invoke > TestNG tests > > > Key: MSUREFIRE-98 > URL: http://jira.codehaus.org/browse/MSUREFIRE-98 > Project: Maven 2.x Surefire Plugin > Type: Bug > Environment: Windows XP, Maven 2.0.4, Java 1.4, Surefire from Snapshot server > Reporter: Andreas Guther > Attachments: my-app.zip > > > I have JUnit tests and TestNG unit tests in the same project. If I use a > TestNG XML configurartion file only the files (TestNG) listed in the > configuration file are executed. JUnit test files are ignored. TestNG > allows to include JUnit tests in the configuration, but I would expect that > JUnit tests should be found based on the standard naming pattern and in > addition TestNG classes as listed in the TestNG XML config file are executed > as well. > Expected that JUnit files are executed and in addition TestNG files. It > should be possible to use different test frameworks in the same project. > I will attach the example project. > Output: > C:\workspace\my-app>mvn test > [INFO] Scanning for projects... > [INFO] > > [INFO] Building Are JUnit Tests Ignored if TestNG Config XML is used? > [INFO]task-segment: [test] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:compile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [resources:testResources] > [INFO] Using default encoding to copy filtered resources. > [INFO] [compiler:testCompile] > [INFO] Nothing to compile - all classes are up to date > [INFO] [surefire:test] > [INFO] Surefire report directory: C:\workspace\my-app\target\surefire-reports > --- > T E S T S > --- > Running Test with JavaDoc Annotations under Java 1.4 > com.mycompany.app.JavaOneFourTngSample: beforeClass > com.mycompany.app.JavaOneFourTngSample: beforeMethod > com.mycompany.app.JavaOneFourTngSample: someTestMethod > com.mycompany.app.JavaOneFourTngSample: beforeMethod > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.078 sec <<< > FAILURE! > Results : > Tests run: 2, Failures: 1, Errors: 0, Skipped: 0 > [ERROR] There are test failures. > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Tue May 02 09:38:59 PDT 2006 > [INFO] Final Memory: 4M/508M > [INFO] > -- 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: (WAGON-46) Wagon http fails when remote repo is not accessible
Wagon http fails when remote repo is not accessible --- Key: WAGON-46 URL: http://jira.codehaus.org/browse/WAGON-46 Project: wagon Type: Bug Components: wagon-http-lightweight Versions: 1.0-alpha-7 Reporter: Carlos Sanchez Seems that maven understands error codes from the http server, but not exceptions like "host doesn't exist" or "connection timeout", which make the build fail instead of going to the next one -- 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: (MNGECLIPSE-118) Support for Eclipse 3.2
[ http://jira.codehaus.org/browse/MNGECLIPSE-118?page=all ] Eugene Kuleshov closed MNGECLIPSE-118: -- Resolution: Won't Fix I am running plugin on Eclipse 3.2 without any problems. > Support for Eclipse 3.2 > --- > > Key: MNGECLIPSE-118 > URL: http://jira.codehaus.org/browse/MNGECLIPSE-118 > Project: Maven 2.x Extension for Eclipse > Type: Wish > Environment: Eclipse 3.2RC2 > MacOSX 10.4.6 [Tiger] > Intel Core Processor > JDK 1.5 > Reporter: Brice Robert > Assignee: Eugene Kuleshov > Priority: Minor > > > Any support for Eclipse 3.2 soon? > Using Mac on intel prevents me for using Eclipse 3.1.2 > Any hint will help > 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] Updated: (WAGON-46) Wagon http fails when remote repo is not accessible
[ http://jira.codehaus.org/browse/WAGON-46?page=all ] Carlos Sanchez updated WAGON-46: Fix Version: 1.0-beta-1 > Wagon http fails when remote repo is not accessible > --- > > Key: WAGON-46 > URL: http://jira.codehaus.org/browse/WAGON-46 > Project: wagon > Type: Bug > Components: wagon-http-lightweight > Versions: 1.0-alpha-7 > Reporter: Carlos Sanchez > Fix For: 1.0-beta-1 > > > Seems that maven understands error codes from the http server, but not > exceptions like "host doesn't exist" or "connection timeout", which make the > build fail instead of going to the next one -- 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: (MNGECLIPSE-20) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)
[ http://jira.codehaus.org/browse/MNGECLIPSE-20?page=comments#action_64576 ] Brian Bonner commented on MNGECLIPSE-20: I'm using 0.0.7 of MNGECLIPSE with Maven 2.0.4 and Eclipse 3.0.2 on Win Xp with JDK 1.5.0_06 and I'm still seeing the problem. I have had to disable the m2 builder because of how long it takes for this to build. XFire's pom's use dependency management for versions and use Here is the log msg: 5/2/06 1:50:41 PM EDT: [DEBUG] Profile with id: 'myprofile' has been explicitly activated. 5/2/06 1:51:22 PM EDT: Reading /paraware-webservice-gawda/pom.xml 5/2/06 1:51:22 PM EDT: [DEBUG] Found 0 components to load on start 5/2/06 1:51:22 PM EDT: [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\Brian Bonner\.m2\plugin-registry.xml' 5/2/06 1:51:22 PM EDT: [DEBUG] Building Maven global-level settings from: 'C:\eclipse\conf\settings.xml' 5/2/06 1:51:22 PM EDT: [DEBUG] Building Maven user-level settings from: 'C:\Documents and Settings\Brian Bonner\.m2\settings.xml' 5/2/06 1:51:22 PM EDT: [DEBUG] Profile with id: 'myprofile' has been explicitly activated. 5/2/06 1:51:22 PM EDT: [DEBUG] Profile with id: 'myprofile' has been explicitly activated. 5/2/06 1:51:22 PM EDT: [DEBUG] com.paraware.webservice.gawda:paraware-webservice-gawda:war:1.0 (selected for null) 5/2/06 1:51:22 PM EDT: [DEBUG] xmlunit:xmlunit:jar:1.0:test (selected for test) 5/2/06 1:51:22 PM EDT: [DEBUG] Retrieving parent-POM: org.codehaus.xfire:xfire-parent::1.1-RC1 for project: null:xfire-spring:jar:1.1-RC1 from the repository. 5/2/06 1:51:22 PM EDT: [DEBUG] org.codehaus.xfire:xfire-spring:jar:1.1-RC1:compile (selected for compile) 5/2/06 1:51:22 PM EDT: [DEBUG] junit:junit:jar:3.8.1:compile (selected for compile) 5/2/06 1:51:22 PM EDT: [DEBUG] Trying repository codehaus 5/2/06 1:51:43 PM EDT: [WARN] Unable to get resource from repository codehaus (http://dist.codehaus.org/) 5/2/06 1:51:43 PM EDT: [DEBUG] Trying repository central 5/2/06 1:52:25 PM EDT: [WARN] Unable to get resource from repository central (http://repo1.maven.org/maven2) 5/2/06 1:52:25 PM EDT: [DEBUG] Artifact not found - using stub model: Unable to download the artifact from any repository org.codehaus.xfire:xfire-annotations:pom:2.4.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus (http://dist.codehaus.org/) 5/2/06 1:52:25 PM EDT: [DEBUG] Using defaults for missing POM org.codehaus.xfire:xfire-annotations:pom:2.4.1:compile 5/2/06 1:52:25 PM EDT: [DEBUG] org.codehaus.xfire:xfire-annotations:jar:2.4.1:compile (selected for compile) 5/2/06 1:52:25 PM EDT: [DEBUG] Trying repository codehaus 5/2/06 1:52:46 PM EDT: [WARN] Unable to get resource from repository codehaus (http://dist.codehaus.org/) 5/2/06 1:52:46 PM EDT: [DEBUG] Trying repository central 5/2/06 1:53:28 PM EDT: [WARN] Unable to get resource from repository central (http://repo1.maven.org/maven2) 5/2/06 1:53:28 PM EDT: [DEBUG] Artifact not found - using stub model: Unable to download the artifact from any repository org.codehaus.xfire:xbean-spring:pom:2.3-patched-20060426 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus (http://dist.codehaus.org/) 5/2/06 1:53:28 PM EDT: [DEBUG] Using defaults for missing POM org.codehaus.xfire:xbean-spring:pom:2.3-patched-20060426:compile 5/2/06 1:53:28 PM EDT: [DEBUG] org.codehaus.xfire:xbean-spring:jar:2.3-patched-20060426:compile (selected for compile) 5/2/06 1:53:28 PM EDT: [DEBUG] Trying repository codehaus 5/2/06 1:53:50 PM EDT: [WARN] Unable to get resource from repository codehaus (http://dist.codehaus.org/) 5/2/06 1:53:50 PM EDT: [DEBUG] Trying repository central 5/2/06 1:54:32 PM EDT: [WARN] Unable to get resource from repository central (http://repo1.maven.org/maven2) 5/2/06 1:54:32 PM EDT: [DEBUG] Artifact not found - using stub model: Unable to download the artifact from any repository org.codehaus.xfire:xfire-xmlbeans:pom:2.4.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus (http://dist.codehaus.org/) 5/2/06 1:54:32 PM EDT: [DEBUG] Using defaults for missing POM org.codehaus.xfire:xfire-xmlbeans:pom:2.4.1:compile 5/2/06 1:54:32 PM EDT: [DEBUG] org.codehaus.xfire:xfire-xmlbeans:jar:2.4.1:compile (selected for compile) 5/2/06 1:54:32 PM EDT: [DEBUG] Retrieving parent-POM: org.springframework:spring-full::1.2.6 for project: null:spring:jar:1.2.6 from the repository. 5/2/06 1:54:32 PM EDT: [DEBUG] Retrieving parent-POM: org.springframework:spring-parent::1.2.6 for project: null:spring-full:pom:null from the repository. 5/2/06 1:54:32 PM EDT: [DEBUG] org.springframework:spring:jar:1.2.6:compile (selected for compile) 5/2/06 1:54:32 PM EDT: [DEBUG] commons-logging:commons-logging:jar:1.0.4:compile (selected for compile) 5/2/06 1:54:32 PM EDT: [DEBUG] log4j:log4j:jar:
[jira] Commented: (MASSEMBLY-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64578 ]
Jason Chaffee commented on MASSEMBLY-89:
I am seeing the same behavior when building the assembly plugin from the trunk.
Basically, it is interpolating all ${artifactId} in the assembly descriptor
xml and changing them to be the project.artifactId. For example, in my pom.xml
my artifactId is "packger". Let's say I have two jars in my pom, test-1.0.jar
and foo-1.0.jar. If I use ${artifactId}.${extension} for the
outputFileNameMapping I will end up with only one artifact in my bundle and it
will have the name packager.jar. If I use
${artifactId}-${version}.${extension} then I will get the correct behavior and
I will see both test-1.0.jar and foo-1.0.jar. Therefore, it seems the
interoplation isn't happening if ${version} is used which is very strange.
> outputFileNameMapping broken
>
>
> Key: MASSEMBLY-89
> URL: http://jira.codehaus.org/browse/MASSEMBLY-89
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Environment: xp
> Reporter: Dan Tran
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.1
> Attachments: bin.xml, pom.xml
>
>
> Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
> all dependency aritifacts into assembly without the version
> Here is an exmple
>
>
>
> ${artifactId}.${extension}
>
>
> After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
> a single file ${artifactId}.${extention}
--
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: (MDEP-22) copy of provided dependencies
copy of provided dependencies - Key: MDEP-22 URL: http://jira.codehaus.org/browse/MDEP-22 Project: Maven 2.x Dependency Plugin Type: Wish Environment: all Reporter: Jerome CARRE Priority: Minor create an attribute to say "don't copy 'provided' dependencies", into copy-dependencies goal. -- 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-878) Upload stax-utils 20060502
Upload stax-utils 20060502 -- Key: MAVENUPLOAD-878 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-878 Project: maven-upload-requests Type: Task Reporter: Guillaume Nodet -- 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-103) Plugin should add required classpath entry if user specified a PluginNature for a project
Plugin should add required classpath entry if user specified a PluginNature for a project - Key: MECLIPSE-103 URL: http://jira.codehaus.org/browse/MECLIPSE-103 Project: Maven 2.x Eclipse Plugin Type: New Feature Reporter: Rahul Thakur If the user specified a "org.eclipse.pde.PluginNature" in the configuration, the plugin should add a "org.eclipse.pde.core.requiredPlugins" entry to .classpath. Atleast this will enable Eclipse to recognise a PDE project. -- 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: (MECLIPSE-103) Plugin should add required classpath entry if user specified a PluginNature for a project
[ http://jira.codehaus.org/browse/MECLIPSE-103?page=all ] Rahul Thakur updated MECLIPSE-103: -- Attachment: MECLIPSE-103.patch > Plugin should add required classpath entry if user specified a PluginNature > for a project > - > > Key: MECLIPSE-103 > URL: http://jira.codehaus.org/browse/MECLIPSE-103 > Project: Maven 2.x Eclipse Plugin > Type: New Feature > Reporter: Rahul Thakur > Attachments: MECLIPSE-103.patch > > > If the user specified a "org.eclipse.pde.PluginNature" in the configuration, > the plugin should add a "org.eclipse.pde.core.requiredPlugins" entry to > .classpath. Atleast this will enable Eclipse to recognise a PDE project. -- 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-2263) War packaging fails with long file names
[ http://jira.codehaus.org/browse/MNG-2263?page=all ] Brett Porter closed MNG-2263: - Assign To: Brett Porter Resolution: Won't Fix AFAIK there is nothing we can do to solve this (can you create that file by hand? If so, then perhaps its a problem specific to Maven). If you have a solution for being able to write this, please reopen. If it is specific to WAR, please file under MWAR instead. There is nothing Maven can do about the length of that filename as it is all composed of your choice of working directory and elements from your build. > War packaging fails with long file names > > > Key: MNG-2263 > URL: http://jira.codehaus.org/browse/MNG-2263 > Project: Maven 2 > Type: Bug > Versions: 2.0.4 > Environment: Windows > Maven 2.0.4 > Reporter: Laurent Dauvilaire > Assignee: Brett Porter > > > The package action fails when file name are too long. > The error does not occurs when the path of the project is shorter (ie test > into C:/x) > See stack trace below: > [INFO] [war:war] > [INFO] Exploding webapp... > [INFO] Copy webapp resources to > d:\Home\LDauvilaire\src\Repository\SVN\JHub\modules\display-webapp\modules\hub-internal\..\..\..\..\target\dev\3.0.20\hub-webapp-internal\hub-webapp-internal-3.0.20 > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error assembling WAR > Embedded error: Could not explode webapp... > d:\Home\LDauvilaire\src\Repository\SVN\JHub\modules\display-webapp\modules\hub-internal\..\..\..\..\target\dev\3.0.20\hub-webapp-internal\hub-webapp-internal-3.0.20\fceditor\editor\dialog\fck_spellerpages\spellerpages\server-scripts\spellchecker.cfm > (The filename, directory name, or volume label syntax is incorrect) > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling WAR > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > 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 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) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling > WAR > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:91) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534) > ... 16 more > Caused by: org.apache.maven.plugin.MojoExecutionException: Could not explode > webapp... > at > org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:202) > at > org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:108) > at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:86) > ... 18 more > Caused by: java.io.FileNotFoundException: > d:\Home\LDauvilaire\src\Repository\SVN\JHub\modules\display-webapp\modules\hub-internal\..\..\..\..\target\dev\3.0.20\hub-webapp-internal\hub-webapp-internal-3.0.20\fceditor\editor\dialog\fck_spellerpages\spellerpages\server-scripts\spellchecker.cfm > (The filename, directory name, or volume label syntax is incorrect) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.(FileOutputStream.java:179) >
[jira] Commented: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64592 ] Stephen Duncan Jr commented on MEV-363: --- Jared, you still need to take into account updates to version numbers based on Carlos's link. If you tell me how to generate the md5&sha1 files, I can go through and do it, or I can tell you exactly which POMs need to change (after I search through and figure it out!), or you can figure those out too. Let me know. Thanks for your help so far! > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64593 ] Stephen Duncan Jr commented on MEV-363: --- Changes to make, all in spring-parent, all version changes: C3P0 0.9.0.4 is not available in the Maven repo. I'd recommend to leave it at C3P0 0.9.0.2 Carlos? "easymock:easymock" change from "1.2_RC2_Java1.3" to "1.2_Java1.3t" "ibatis:ibatis2-sqlmap" change from "2.1.5.582" to "2.1.7.597" "commons-httpclient:commons-httpclient" change from "3.0-rc4" to "3.0" "log4j:log4j" change from "1.2.9" to "1.2.13" "ojb:db-ojb" change from "1.0.3" to "1.0.4" "struts:struts" change from "1.2.7" to "1.2.8" (though 1.2.9 appears to the latest release) "velocity-tools:velocity-tools-view" change from "1.1" to "1.2" "velocity-tools:velocity-tools-generic" change from "1.1" to "1.2" > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (SCM-193) NullPointer in local provider update when a new file is added
NullPointer in local provider update when a new file is added - Key: SCM-193 URL: http://jira.codehaus.org/browse/SCM-193 Project: Maven SCM Type: Bug Components: maven-scm-provider-local Versions: 1.0-beta-3 Reporter: Carlos Sanchez Priority: Critical Fix For: 1.0 org.apache.maven.continuum.scm.ContinuumScmException: Error while update sources. at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.local.LocalScmProvider.update(LocalScmProvider.java:191) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:386) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:363) at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) ... 5 more Caused by: java.lang.NullPointerException at java.util.Date.getMillisOf(Date.java:938) at java.util.Date.after(Date.java:911) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:89) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55) ... 9 more -- 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: (SCM-193) NullPointer in local provider update when a new file is added
[ http://jira.codehaus.org/browse/SCM-193?page=all ] Carlos Sanchez updated SCM-193: --- Description: org.apache.maven.continuum.scm.ContinuumScmException: Error while update sources. at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.local.LocalScmProvider.update(LocalScmProvider.java:191) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:386) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:363) at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) ... 5 more Caused by: java.lang.NullPointerException at java.util.Date.getMillisOf(Date.java:938) at java.util.Date.after(Date.java:911) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:89) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55) ... 9 more was: org.apache.maven.continuum.scm.ContinuumScmException: Error while update sources. at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) at org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:595) Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM command. at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) at org.apache.maven.scm.provider.local.LocalScmProvider.update(LocalScmProvider.java:191) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:386) at org.apache.maven.scm.provider.AbstractScmProvider.update(AbstractScmProvider.java:363) at org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:242) ... 5 more Caused by: java.lang.NullPointerException at java.util.Date.getMillisOf(Date.java:938) at java.util.Date.after(Date.java:911) at org.apache.maven.scm.command.update.AbstractUpdateCommand.executeCommand(AbstractUpdateCommand.java:89) at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:55) ... 9 more Fix Version: 1.0 File is copied anyway although the exception is thrown > NullPointer in local provider update when a new file is added > - > > Key: SCM-193 > URL: http://jira.codehaus.org/browse/SCM-193 > Project: Maven SCM > Type: Bug > Components: maven-scm-provider-local > Versions: 1.0-beta-3 > Reporter: Carlos Sanchez > Priority: Critical > Fix For: 1.0 > > > org.apache.maven.continuum.scm.ContinuumScmException: Error while update > sources. > at > org.apache.maven.continuum.scm.DefaultContinuumScm.updateProject(DefaultContinuumScm.java:272) > at > org.apache.maven.continuum.core.action.UpdateWorkingDirectoryFromScmContinuumAction.execute(UpdateWorkingDirectoryFromScmContinuumAction.java:58) > at > org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:166) > at > org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) > at > org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) > at java.lang.Thread.run(Thread.java:595) > Caused by: org.apache.maven.scm.ScmException: Exception while executing SCM > command. > at > org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:59) > at > org.
[jira] Commented: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64595 ] Stephen Duncan Jr commented on MEV-363: --- Note that it should be (without the the 't' in the version #): "easymock:easymock" change from "1.2_RC2_Java1.3" to "1.2_Java1.3" > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (SCM-194) local provider doesn't trigger build when a file is edited
local provider doesn't trigger build when a file is edited -- Key: SCM-194 URL: http://jira.codehaus.org/browse/SCM-194 Project: Maven SCM Type: Bug Components: maven-scm-provider-local Versions: 1.0-beta-3 Reporter: Carlos Sanchez -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64596 ] Carlos Sanchez commented on MEV-363: If it builds with C3P0 0.9.0.4 it has to depend on it. It needs to be uploaded > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MPIR-2) Dependencies report throws NullPointerException when a transitive dependency has system scope
[ http://jira.codehaus.org/browse/MPIR-2?page=comments#action_64597 ]
Julian Wood commented on MPIR-2:
I'm still seeing this issue as of maven 2.0.4, May 2nd, 2006. So still can't
make a dependency report if there is a system-scoped dep.
> Dependencies report throws NullPointerException when a transitive dependency
> has system scope
> -
>
> Key: MPIR-2
> URL: http://jira.codehaus.org/browse/MPIR-2
> Project: Maven 2.x Project Info Reports Plugin
> Type: Bug
> Versions: 2.0-beta-3
> Reporter: Carlos Sanchez
> Assignee: Vincent Siveton
> Fix For: 2.0
>
>
> DependenciesReport.java, inside getMavenProjectFromRepository( Artifact
> artifact, ArtifactRepository localRepository )
> projectArtifact.file is always null, and when calling
> mavenProjectBuilder.buildFromRepository causes
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:377)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:343)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:373)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:297)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> I've made a quick fix ignoring system dependencies, not sure if we want to
> change it
> Inside renderBody
> if ( Artifact.SCOPE_SYSTEM.equals( artifact.getScope() ) )
> {
> continue;
> }
--
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: (MPIR-24) Possible NPE in DefaultArtifactResolver
[ http://jira.codehaus.org/browse/MPIR-24?page=comments#action_64598 ] Julian Wood commented on MPIR-24: - Still not fixed as of maven 2.0.4, and yet all this issue and all its duplicates are closed, AFAICT. > Possible NPE in DefaultArtifactResolver > --- > > Key: MPIR-24 > URL: http://jira.codehaus.org/browse/MPIR-24 > Project: Maven 2.x Project Info Reports Plugin > Type: Bug > Versions: 2.0-beta-3 > Environment: Ubuntu /Windows 2000 > Reporter: Bernd Bohmann > Assignee: Carlos Sanchez > Attachments: DefaultArtifactResolver.java.patch > > > With mvn site:site we got a NPE at > org.apache.maven.aritfact.resolver.DefaultArtifactResolver.java Line 82 -- 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: (MPIR-2) Dependencies report throws NullPointerException when a transitive dependency has system scope
[ http://jira.codehaus.org/browse/MPIR-2?page=comments#action_64599 ]
Carlos Sanchez commented on MPIR-2:
---
You need to use the 2.0 version of the maven-project-info-report plugin, that
will be released in the following days
> Dependencies report throws NullPointerException when a transitive dependency
> has system scope
> -
>
> Key: MPIR-2
> URL: http://jira.codehaus.org/browse/MPIR-2
> Project: Maven 2.x Project Info Reports Plugin
> Type: Bug
> Versions: 2.0-beta-3
> Reporter: Carlos Sanchez
> Assignee: Vincent Siveton
> Fix For: 2.0
>
>
> DependenciesReport.java, inside getMavenProjectFromRepository( Artifact
> artifact, ArtifactRepository localRepository )
> projectArtifact.file is always null, and when calling
> mavenProjectBuilder.buildFromRepository causes
> java.lang.NullPointerException
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:82)
> at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:377)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:343)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.getMavenProjectFromRepository(DependenciesReport.java:373)
> at
> org.apache.maven.report.projectinfo.DependenciesReport$DependenciesRenderer.renderBody(DependenciesReport.java:297)
> at
> org.apache.maven.reporting.AbstractMavenReportRenderer.render(AbstractMavenReportRenderer.java:65)
> I've made a quick fix ignoring system dependencies, not sure if we want to
> change it
> Inside renderBody
> if ( Artifact.SCOPE_SYSTEM.equals( artifact.getScope() ) )
> {
> continue;
> }
--
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: (MPXDOC-17) xdoc with XML entities goes wierd
[ http://jira.codehaus.org/browse/MPXDOC-17?page=all ] Lukas Theussl closed MPXDOC-17: --- Assign To: Lukas Theussl Resolution: Fixed Fix Version: 1.10 This works in Maven 1.1 with jsl:copyOf instead of jsl:copy. I hope this doesn't break anything else though... > xdoc with XML entities goes wierd > - > > Key: MPXDOC-17 > URL: http://jira.codehaus.org/browse/MPXDOC-17 > Project: maven-xdoc-plugin > Type: Bug > Environment: windows xp, JDK 1.4.1 > Reporter: Howard M. Lewis Ship > Assignee: Lukas Theussl > Priority: Minor > Fix For: 1.10 > > > I'm having a problem using XML entities inside xdoc files. > I like to create XML entities for my XML documentation for common things like > links to API docs, or to descriptions of my schemas. > So, I have a file, services.xml, which begins: > > > %common-links; > ]> > Inside common/links.xml I have stuff like: > > &_module;'> > And that works properly in my docs; appears as a link when I use > &module; in the document. > However, if you do something *simpler* it fails: > > Appears in the output as a blank space. > > Appears as: > > Appears as: ] > href="apidocs/org/apache/commons/hivemind/IFactory.html">IFactory'> > Appears as: > > tory > > Something appears screwed up in the xdoc processing pipeline. Does this all > sound familiar? > Alternately, is there another way to accomplish my goals (using some kind of > Velocity markup?) -- 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-89) outputFileNameMapping broken
[ http://jira.codehaus.org/browse/MASSEMBLY-89?page=comments#action_64601 ]
Jason Chaffee commented on MASSEMBLY-89:
I just reviewed the added unit tests and they do not use an
InterpolationFilterReader to load the assembly descriptors as the
AbstractAssemblyMojo does. See the filterFile(File) method.
> outputFileNameMapping broken
>
>
> Key: MASSEMBLY-89
> URL: http://jira.codehaus.org/browse/MASSEMBLY-89
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Versions: 2.1
> Environment: xp
> Reporter: Dan Tran
> Assignee: John Casey
> Priority: Critical
> Fix For: 2.1
> Attachments: bin.xml, pom.xml
>
>
> Prior to MASSEMBLY-40, I am able to outputFileNameMapping feature to place
> all dependency aritifacts into assembly without the version
> Here is an exmple
>
>
>
> ${artifactId}.${extension}
>
>
> After MASSEMBLY40, All artifact inside a set of dependencySet is mapped to
> a single file ${artifactId}.${extention}
--
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: (MPXDOC-179) Can't use relative links for external entities
[ http://jira.codehaus.org/browse/MPXDOC-179?page=comments#action_64602 ] Lukas Theussl commented on MPXDOC-179: -- Confirming that this works with my upgraded dom4j build, see the recent comments at MAVEN-1345. So the problem is not in the xdoc plugin but in the core. > Can't use relative links for external entities > -- > > Key: MPXDOC-179 > URL: http://jira.codehaus.org/browse/MPXDOC-179 > Project: maven-xdoc-plugin > Type: Bug > Versions: 1.10, 1.9.1, 1.9.2, 1.9 > Environment: maven-1.1 beta 3 from SVN > Reporter: Arnaud Heritier > > > Actually we can't use a relative path in xdocs to declare external entities > For exemple in plugins\trunk\xdoc\xdocs\reference\xdocs.xml we reference > escapeXml.xml like this with an absolute path from where maven is generally > called (in the xdoc plugin root directory) > > ]> > Thus if we use a multiproject the site fails. For example : > plugins\trunk>maven -Dgoal=site > -Dmaven.multiproject.includes=xdoc/project.xml multiproject:goal > gives : > LA CONSTRUCTION A ╚CHOU╚ > Fichier... > D:\Data\maven-1\cache\maven-multiproject-plugin-1.5-SNAPSHOT\plugin.jelly > ╚lement... maven:reactor > Ligne. 226 > Colonne... -1 > Unable to obtain goal [site] -- > D:\Data\maven-1\cache\maven-xdoc-plugin-1.10-SNAPSHOT\plugin.jelly:490:-1: > xdocs\reference\escapeX > ml.xml (The system cannot find the path specified) Nested exception: > xdocs\reference\escapeXml.xml (The system cannot find the path specifie > d) > If I use a relative path : > > ]> > With the same command as previously I receive a similar error : > Fichier... > D:\Data\maven-1\cache\maven-multiproject-plugin-1.5-SNAPSHOT\plugin.jelly > ╚lement... maven:reactor > Ligne. 226 > Colonne... -1 > Unable to obtain goal [site] -- > D:\Data\maven-1\cache\maven-xdoc-plugin-1.10-SNAPSHOT\plugin.jelly:490:-1: > Error on line 3 of docu > ment : URI relative "file:escapeXml.xml"; ne peut Ûtre rÚsolue sans URI de > base. Nested exception: URI relative "file:escapeXml.xml"; ne pe > ut Ûtre rÚsolue sans URI de base. > It seems to be a problem with dom4j 1.4 -- 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-2264) [PATCH] Ant tasks should allow you to specify a custom location for settings.xml
[PATCH] Ant tasks should allow you to specify a custom location for settings.xml Key: MNG-2264 URL: http://jira.codehaus.org/browse/MNG-2264 Project: Maven 2 Type: Improvement Components: Ant tasks Versions: 2.0.4 Reporter: Dan Fabulich Attachments: patch.txt On my official build system, I'm not allowed to leave files in ~ (user.home). That means that I need to pass in custom settings directly in my Ant script. The attached patch creates a setter lets you specify the location of a settings.xml 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] Commented: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64603 ] Jared Bunting commented on MEV-363: --- I can make these changes tomorrow, probably early afternoon. I used a basic ant script to generate the checksums - something like this... > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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] Moved: (MECLIPSE-104) Add the ability to specify source exclusions
[ http://jira.codehaus.org/browse/MECLIPSE-104?page=all ] Lukas Theussl moved MPECLIPSE-117 to MECLIPSE-104: -- Workflow: Maven New (was: jira) Key: MECLIPSE-104 (was: MPECLIPSE-117) Project: Maven 2.x Eclipse Plugin (was: maven-eclipse-plugin) > Add the ability to specify source exclusions > > > Key: MECLIPSE-104 > URL: http://jira.codehaus.org/browse/MECLIPSE-104 > Project: Maven 2.x Eclipse Plugin > Type: New Feature > Reporter: James Mitchell > Priority: Minor > Attachments: srcExclusions-patch.zip > > > When source files contain scm information (**/.svn/** or **/CVS/**), which is > pretty much a given, there's currently no way to specify that those > directories be excluded except through the GUI. This isn't so much of a > problem except that the next time a change is needed and this plugin is ran, > it will overwrite this exclusion and will force me to exclude it, by hand, > again. > The above case is the driving reason why I decided to get involved and help > out. So, I have written everything (I think) that is needed for this > enhancement including, adding to the javadoc, creating a new test that > verifies this enhancement, and fully testing this with my own projects (many > of them @ Struts). If there is anything else I need to do as far as site > documentation, please tell me where it is and I'll add it. > This is my first patch to Maven. If this sucks, please don't ignore it, just > say 'it sucks, no thanks" and I'll go about working on something else. > Thanks so much for your attention. > -- > James Mitchell -- 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] Reopened: (MASSEMBLY-14) assembly plugin does not include dependencies for all artifacts in reactor.
[ http://jira.codehaus.org/browse/MASSEMBLY-14?page=all ] Kenney Westerhof reopened MASSEMBLY-14: --- There are some major issues with this commit (revision 327855). The only way to run the assembly plugin in a reactor is to bind it to the lifecycle of some pom. If you're not interested in ALL modules and ALL dependencies, but for instance, you use the assembly plugin to create an artifact in a submodule somewhere, all modules and all dependencies of them end up in that assembly. Example: root/pom.xml, define moda and modb moda/pom.xml, depend on X modb/pom.xml, depend on Y, declare assembly then root/modb/target/... contains moda.jar, modb.jar, X.jar and Y.jar. I'm sure that that's not what's intended. I think this can be easily resolved by only considering child modules of the current pom. I find it strange that this wasn't tested in a reactor environment, since that's the only way to test this patch. > assembly plugin does not include dependencies for all artifacts in reactor. > --- > > Key: MASSEMBLY-14 > URL: http://jira.codehaus.org/browse/MASSEMBLY-14 > Project: Maven 2.x Assembly Plugin > Type: Bug > Reporter: Erick Dovale > Assignee: Edwin Punzalan > Attachments: MNG-1206-maven-assembly-plugin.patch, test-assembly-m2.zip > > > When trying to create an archive using maven-assembly-plugin the dependencies > for the artifacts in the reactor are not added to the archive. > attached is a whole project structure that can be used to reproduce this > issue. -- 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-14) assembly plugin does not include dependencies for all artifacts in reactor.
[ http://jira.codehaus.org/browse/MASSEMBLY-14?page=comments#action_64608 ]
Edwin Punzalan commented on MASSEMBLY-14:
-
I see what's happening... ${reactorProects} contain all projects in the
reactor. So I'll have to check first if the project is a module of the
executedProject before adding its dependencies.
> assembly plugin does not include dependencies for all artifacts in reactor.
> ---
>
> Key: MASSEMBLY-14
> URL: http://jira.codehaus.org/browse/MASSEMBLY-14
> Project: Maven 2.x Assembly Plugin
> Type: Bug
> Reporter: Erick Dovale
> Assignee: Edwin Punzalan
> Attachments: MNG-1206-maven-assembly-plugin.patch, test-assembly-m2.zip
>
>
> When trying to create an archive using maven-assembly-plugin the dependencies
> for the artifacts in the reactor are not added to the archive.
> attached is a whole project structure that can be used to reproduce this
> issue.
--
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: (MPIR-45) Some french translations are missing
[ http://jira.codehaus.org/browse/MPIR-45?page=all ] Vincent Siveton closed MPIR-45: --- Assign To: Vincent Siveton Resolution: Fixed Fix Version: 2.0 Applied. Thanks! Please check the maven site for instructions on how to create a patch: http://maven.apache.org/contributing/patches.html > Some french translations are missing > > > Key: MPIR-45 > URL: http://jira.codehaus.org/browse/MPIR-45 > Project: Maven 2.x Project Info Reports Plugin > Type: Bug > Reporter: Alexandre Poitras > Assignee: Vincent Siveton > Priority: Minor > Fix For: 2.0 > Attachments: project-info-report_fr.properties > > > French translations are missing for the dependency graph and project summary > entries. -- 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-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=all ] Jared Bunting updated MEV-363: -- Attachment: spring-poms-1.2.7.zip > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip, spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MSITE-115) Provide a default value for a staging directory
[ http://jira.codehaus.org/browse/MSITE-115?page=comments#action_64612 ] Vincent Siveton commented on MSITE-115: --- Seting a default staging directory doesn't work in multi project case. Seting a default staging URL create an other directory. I will revert > Provide a default value for a staging directory > --- > > Key: MSITE-115 > URL: http://jira.codehaus.org/browse/MSITE-115 > Project: Maven 2.x Site Plugin > Type: Improvement > Reporter: Jason van Zyl > Fix For: 2.0-beta-5 > > > We'll append a /staging to the distribution management. At this point it > doesn't create a self-contained tree but no different then an arbitrary > my-whatever-place/site and you don't have to provide an URL as long as your > arm on the CLI. -- 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: (MEV-363) Spring 1.2.7 POMs Missing
[ http://jira.codehaus.org/browse/MEV-363?page=comments#action_64616 ] Stephen Duncan Jr commented on MEV-363: --- Well, I put in an issue at the c3p0 site to do the upload: http://sourceforge.net/tracker/index.php?func=detail&aid=1480831&group_id=25357&atid=383691 > Spring 1.2.7 POMs Missing > - > > Key: MEV-363 > URL: http://jira.codehaus.org/browse/MEV-363 > Project: Maven Evangelism > Type: Bug > Components: Missing POM > Reporter: Stephen Duncan Jr > Attachments: spring-poms-1.2.7.zip, spring-poms-1.2.7.zip > > > All Spring 1.2.7 jars need POMs added. POMs should be duplicates of Spring > 1.2.6 but with the following other MEV issues taken into account: > http://jira.codehaus.org/browse/MEV-316 and > http://jira.codehaus.org/browse/MEV-277 -- 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: (MAVENUPLOAD-878) Upload stax-utils 20060502
[ http://jira.codehaus.org/browse/MAVENUPLOAD-878?page=all ] Carlos Sanchez closed MAVENUPLOAD-878: -- Assign To: Carlos Sanchez Resolution: Fixed Added to net.java.dev.stax-utils, with dependency to RI > Upload stax-utils 20060502 > -- > > Key: MAVENUPLOAD-878 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-878 > Project: maven-upload-requests > Type: Task > Reporter: Guillaume Nodet > Assignee: Carlos Sanchez > > -- 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: (MAVENUPLOAD-870) cas-extend-client-java version 2.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-870?page=all ] Carlos Sanchez closed MAVENUPLOAD-870: -- Assign To: Carlos Sanchez Resolution: Fixed > cas-extend-client-java version 2.2 > -- > > Key: MAVENUPLOAD-870 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-870 > Project: maven-upload-requests > Type: Task > Reporter: Tim O'Brien > Assignee: Carlos Sanchez > > > New release of the cas-extend client -- 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: (MAVENUPLOAD-872) JCommon 1.0.4
[ http://jira.codehaus.org/browse/MAVENUPLOAD-872?page=all ] Carlos Sanchez closed MAVENUPLOAD-872: -- Assign To: Carlos Sanchez Resolution: Fixed > JCommon 1.0.4 > - > > Key: MAVENUPLOAD-872 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-872 > Project: maven-upload-requests > Type: Task > Reporter: Takayoshi Kimura > Assignee: Carlos Sanchez > Attachments: jcommon-1.0.4-bundle.jar, jcommon-1.0.4.jar > > > http://www.jfree.org/jcommon/ -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs
[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64618 ] Carlos Sanchez commented on MAVENUPLOAD-873: groupid should be com.sun.media for consistency (only three levels) you need to add the distributionManagement section to point where it can be hand downloaded eg. http://ftpna2.bea.com/pub/downloads/jsr173.jar > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 > Project: maven-upload-requests > Type: Task > Reporter: Joerg Schaible > > > POMs for JAI are missing on ibiblio. > Additional bundles: > http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar > http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-874) CoWarp 0.5 Release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-874?page=comments#action_64619 ] Carlos Sanchez commented on MAVENUPLOAD-874: you have dependencies in snapshots. Releases shouldn't, they are not reproducible > CoWarp 0.5 Release > -- > > Key: MAVENUPLOAD-874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-874 > Project: maven-upload-requests > Type: Task > Reporter: Carsten Ziegeler > > > This is the latest release of CoWarp - an extension to the Apache Cocoon > project. -- 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: (MEJB-9) test ejb plugin using plugin testing harness
[ http://jira.codehaus.org/browse/MEJB-9?page=all ] John Tolentino closed MEJB-9: - Assign To: Marvin King (was: John Tolentino) Resolution: Fixed Fix Version: 2.1 Patch applied > test ejb plugin using plugin testing harness > > > Key: MEJB-9 > URL: http://jira.codehaus.org/browse/MEJB-9 > Project: Maven 2.x Ejb Plugin > Type: Test > Reporter: John Tolentino > Assignee: Marvin King > Fix For: 2.1 > Attachments: MEJB-9-unit_test.patch > > -- 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: (MAVENUPLOAD-875) Upload jaxws jars on ibiblio
[ http://jira.codehaus.org/browse/MAVENUPLOAD-875?page=all ] Carlos Sanchez closed MAVENUPLOAD-875: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload jaxws jars on ibiblio > > > Key: MAVENUPLOAD-875 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-875 > Project: maven-upload-requests > Type: Task > Reporter: Guillaume Nodet > Assignee: Carlos Sanchez > > -- 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: (MAVENUPLOAD-876) Upload mx4j-tools 3.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-876?page=all ] Carlos Sanchez closed MAVENUPLOAD-876: -- Assign To: Carlos Sanchez Resolution: Fixed > Upload mx4j-tools 3.0.1 > --- > > Key: MAVENUPLOAD-876 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-876 > Project: maven-upload-requests > Type: Task > Reporter: Guillaume Nodet > Assignee: Carlos Sanchez > > -- 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: (MAVENUPLOAD-876) Upload mx4j-tools 3.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-876?page=all ] Carlos Sanchez updated MAVENUPLOAD-876: --- Attachment: dep.xml > Upload mx4j-tools 3.0.1 > --- > > Key: MAVENUPLOAD-876 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-876 > Project: maven-upload-requests > Type: Task > Reporter: Guillaume Nodet > Assignee: Carlos Sanchez > Attachments: dep.png, dep.xml > > -- 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: (MAVENUPLOAD-876) Upload mx4j-tools 3.0.1
[ http://jira.codehaus.org/browse/MAVENUPLOAD-876?page=all ] Carlos Sanchez updated MAVENUPLOAD-876: --- Attachment: dep.png > Upload mx4j-tools 3.0.1 > --- > > Key: MAVENUPLOAD-876 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-876 > Project: maven-upload-requests > Type: Task > Reporter: Guillaume Nodet > Assignee: Carlos Sanchez > Attachments: dep.png, dep.xml > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs
[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64622 ] Joerg Schaible commented on MAVENUPLOAD-873: > groupid should be com.sun.media for consistency (only three levels) OK. Although Sun often replaces the "javax." part with "com.sun." and so we're losing one level. > you need to add the distributionManagement section to point where it can be > hand downloaded Well, how? You can donwload from Sun only after accepting the license agreement. All you get then is a download URL with a link to an archive that contains the jar. So there's no direct link. > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 > Project: maven-upload-requests > Type: Task > Reporter: Joerg Schaible > > > POMs for JAI are missing on ibiblio. > Additional bundles: > http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar > http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- 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: (MAVENUPLOAD-877) OpenWFE 1.7.0pre9 upload request
[ http://jira.codehaus.org/browse/MAVENUPLOAD-877?page=all ] Carlos Sanchez closed MAVENUPLOAD-877: -- Assign To: Carlos Sanchez Resolution: Fixed > OpenWFE 1.7.0pre9 upload request > > > Key: MAVENUPLOAD-877 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-877 > Project: maven-upload-requests > Type: Task > Reporter: John Mettraux > Assignee: Carlos Sanchez > > > http://openwfe.org/upload/openwfe-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-applic-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-embed-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-embed-wom-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-engine-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-engine-actions-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-worklist-1.7.0pre9-bundle.jar > http://openwfe.org/upload/openwfe-worklist-actions-1.7.0pre9-bundle.jar > http://www.openwfe.org > http://web.openwfe.org/display/openwfe/OpenWFE+people > OpenWFE is an open source workflow engine under a BSD license. > The main reason for this request upload is that the Magnolia team > (http://www.magnolia.info) is integrating OpenWFE as the workflow engine > within their CMS. As they are heavy Maven2 users... > OpenWFE would then also benefit to other Maven2 users. -- 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: (MNG-2261) Profiles ignored when working with non-projects (such as archetype:create)
[ http://jira.codehaus.org/browse/MNG-2261?page=all ] Carlos Sanchez updated MNG-2261: Attachment: MNG-2261-2.patch > Profiles ignored when working with non-projects (such as archetype:create) > -- > > Key: MNG-2261 > URL: http://jira.codehaus.org/browse/MNG-2261 > Project: Maven 2 > Type: Bug > Components: General > Versions: 2.0.4 > Reporter: Joakim Erdfelt > Fix For: 2.0.5 > Attachments: MNG-2261-2.patch, MNG-2261.patch > > > Several conditions have to be met to show this bug. > 1) Be in an environment that does not have access to repo1.maven.org, (such > as a corporate environment) > 2) Have no content in your local repository (a fresh install of maven 2.0.4) > 3) Attempt to use a plugin that has no project requirement (such as > archetype:create) > The plugin fails because access to repo1.maven.org cannot be accessed. > Recommended solution: > Create a settings.xml profile that changes the location of the 'central' > repository to point to an internal resource (such as a maven-proxy > installation). > > > > use_internal > > > central > Internal Central Repository > http://repo.internal.com/maven2 > > true > > > true > > > > > > central > Internal Central Repository > http://repo.internal.com/maven2 > > true > > > true > > > > > > > use_internal > > > Try again. > Still fails. > The reason is that the default behaviour for non-project execution is to use > the maven super pom, however there is a bug with that flow that does not > allow for the merging of the settings.xml 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] Commented: (MAVENUPLOAD-873) Upload JAI POMs
[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64626 ] Joerg Schaible commented on MAVENUPLOAD-873: BTW: Sun refers both versions as 1.1.2_01 and 1.0_01. Should I adjust this also? If yes, is it enough to update the POMs in the bundles or doi I have to publish new URLs for the bundles also? > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 > Project: maven-upload-requests > Type: Task > Reporter: Joerg Schaible > > > POMs for JAI are missing on ibiblio. > Additional bundles: > http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar > http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs
[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64627 ] Carlos Sanchez commented on MAVENUPLOAD-873: 1.1.2_01 and 1.0_01 would be better updating bundles is ok > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 > Project: maven-upload-requests > Type: Task > Reporter: Joerg Schaible > > > POMs for JAI are missing on ibiblio. > Additional bundles: > http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar > http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-874) CoWarp 0.5 Release
[ http://jira.codehaus.org/browse/MAVENUPLOAD-874?page=comments#action_64628 ] Carsten Ziegeler commented on MAVENUPLOAD-874: -- Yes, I know - but there is no Cocoon 2.2 release and there won't be any for the next months I guess. The dependencies are very minimal and the api it depends on should not change in Cocoon :) Will you upload the release nevertheless? > CoWarp 0.5 Release > -- > > Key: MAVENUPLOAD-874 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-874 > Project: maven-upload-requests > Type: Task > Reporter: Carsten Ziegeler > > > This is the latest release of CoWarp - an extension to the Apache Cocoon > project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MAVENUPLOAD-873) Upload JAI POMs
[ http://jira.codehaus.org/browse/MAVENUPLOAD-873?page=comments#action_64631 ] Joerg Schaible commented on MAVENUPLOAD-873: OK. All bundles are updated and contain _0x version scheme, distributionManagement with URLs to the latest page, that does not enforces a session and I've added a licenses section - again with the URL to the latest page, that does not enforce a session. > Upload JAI POMs > --- > > Key: MAVENUPLOAD-873 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-873 > Project: maven-upload-requests > Type: Task > Reporter: Joerg Schaible > > > POMs for JAI are missing on ibiblio. > Additional bundles: > http://people.apache.org/~joehni/jai_codec-1.1.2.1-bundle.jar > http://people.apache.org/~joehni/jai_imageio-1.0.1-bundle.jar -- 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-879) Upload acrobat-viewer-bean from Adobe
Upload acrobat-viewer-bean from Adobe - Key: MAVENUPLOAD-879 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-879 Project: maven-upload-requests Type: Task Reporter: Joerg Schaible This bundle contains the free acrobat-viewer-bean from Adobe (see project URL). POM contains licenses section and dirstibutionManagement section. Note, the POM has also a dependency to mrj:MRJToolkitStubs:1.1. This artifact is already on ibiblio (inherited from M1), but its groupId should possibly relocated to com.apple.mrj ... -- 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
