[jira] Commented: (MAVENUPLOAD-1932) Update j2ssh-common and j2ssh-core
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126615 ] Carlos Sanchez commented on MAVENUPLOAD-1932: - If you are not using maven as your build system but want something uploaded to the Central Repository then you just need to make a JAR (using the jar executable, not zip , pkzip or equivalent) with the following content: pom.xml foo-1.0.jar (or whatever artifact is referred to in the pom.xml) foo-1.0-sources.jar (optional, jar containing java sources) foo-1.0-javadoc.jar (optional, jar containing javadocs) Note that the bundle will be read by a script, so it must follow the above format. > Update j2ssh-common and j2ssh-core > -- > > Key: MAVENUPLOAD-1932 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1932 > Project: maven-upload-requests > Issue Type: Wish >Reporter: Henri Dupre >Assignee: Carlos Sanchez > Attachments: sshtools-0.2.9.zip > > -- 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-3453) Avoid references to the deprecated expression "${project.build.resources}"
Avoid references to the deprecated expression "${project.build.resources}"
--
Key: MNG-3453
URL: http://jira.codehaus.org/browse/MNG-3453
Project: Maven 2
Issue Type: Improvement
Components: Documentation: General
Reporter: Benjamin Bentmann
Priority: Trivial
Attachments: project-resources-expression.patch
The [Mojo API
Spec|http://maven.apache.org/developers/mojo-api-specification.html#The_Descriptor_and_Annotations]
contains a reference to the expression "${project.build.resources}" which has
been deprecated as of MNG-715. The docs should be updated to use the
recommended expression "${project.resources}".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MPLUGIN-82) Fix test for javadoc tools
[ http://jira.codehaus.org/browse/MPLUGIN-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MPLUGIN-82. -- Resolution: Fixed Apply > Fix test for javadoc tools > -- > > Key: MPLUGIN-82 > URL: http://jira.codehaus.org/browse/MPLUGIN-82 > Project: Maven 2.x Plugin Tools > Issue Type: Task >Reporter: Benjamin Bentmann >Assignee: Vincent Siveton >Priority: Trivial > Fix For: 2.4 > > Attachments: > org.apache.maven.tools.plugin.javadoc.JavadocReportTest.txt, > resource-filtering-encoding.patch, taglet-test.patch, taglet-test.patch > > > The POM javadoc-plugin-config.xml for the taglets test is hardcoded to use > 1.0 of the maven-plugin-tools-javadoc. For now, i.e. before the artifact is > available on central, the test simply fails. In the long term, you are > testing the wrong artifact. > Patch uses resource filtering to use current project version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3395) Default core plugin versions in the superpom.
[ http://jira.codehaus.org/browse/MNG-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126624 ] Paul Benedict commented on MNG-3395: I'd also like to see added: maven-archetype-plugin maven-resources-plugin maven-help-plugin > Default core plugin versions in the superpom. > - > > Key: MNG-3395 > URL: http://jira.codehaus.org/browse/MNG-3395 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.9 > > Attachments: default-plugin-versions.patch > > > We should define the plugin versions for core and other common plugins (the > apache plugins is a good place to start) in the super pom in 2.0.x to help > with stability. > See here for more info. > http://www.nabble.com/Plugin-Versions-in-the-Super-pom-to15367074s177.html#a15367074 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3395) Default core plugin versions in the superpom.
[ http://jira.codehaus.org/browse/MNG-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126627 ] Brian Fox commented on MNG-3395: Resources is in there, or it should be. IMO, archetype is evolving too quickly to lock it down. Since it is primarily used from the command line, this won't hurt repeatability of builds. Locking down help doesn't seem to provide any benefit either. > Default core plugin versions in the superpom. > - > > Key: MNG-3395 > URL: http://jira.codehaus.org/browse/MNG-3395 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.9 > > Attachments: default-plugin-versions.patch > > > We should define the plugin versions for core and other common plugins (the > apache plugins is a good place to start) in the super pom in 2.0.x to help > with stability. > See here for more info. > http://www.nabble.com/Plugin-Versions-in-the-Super-pom-to15367074s177.html#a15367074 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-3395) Default core plugin versions in the superpom.
[ http://jira.codehaus.org/browse/MNG-3395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126635 ] Paul Benedict commented on MNG-3395: Brian, you were right about resources plugin. I missed it because it wasn't in alphabetical order. > Default core plugin versions in the superpom. > - > > Key: MNG-3395 > URL: http://jira.codehaus.org/browse/MNG-3395 > Project: Maven 2 > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 2.0.8 >Reporter: Brian Fox >Assignee: Brian Fox > Fix For: 2.0.9 > > Attachments: default-plugin-versions.patch > > > We should define the plugin versions for core and other common plugins (the > apache plugins is a good place to start) in the super pom in 2.0.x to help > with stability. > See here for more info. > http://www.nabble.com/Plugin-Versions-in-the-Super-pom-to15367074s177.html#a15367074 -- 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: (MEAR-35) Generate id for modules in application.xml
[ http://jira.codehaus.org/browse/MEAR-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Jensen updated MEAR-35: Attachment: ear-module-id.patch The attached patch allows the module ID to be supplied explicitly through a "moduleId" configuration parameter; if none is supplied, "TYPE_groupId.artifactId[-classifier]" is used by default, where TYPE is the artifact type converted to uppercase (such as "WAR") and [-classifier] is included if the artifact has a classifier. Module ID support has been added to the EJB, JAR, and Web module types only. > Generate id for modules in application.xml > -- > > Key: MEAR-35 > URL: http://jira.codehaus.org/browse/MEAR-35 > Project: Maven 2.x Ear Plugin > Issue Type: Improvement >Reporter: Manikandan Balasubramanian >Priority: Minor > Fix For: 2.3.2 > > Attachments: ear-module-id.patch, MEAR-35-maven-ear-plugin-2.patch, > MEAR-35-maven-ear-plugin.patch > > > When the ear plugin generates application.xml, it should generate an "id" > with each module. This "id" is according to application.xml schema. > This would help eclipse plugin to generate correct eclipse metedata. -- 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: (DOXIA-75) XhtmlSink#figureCaption() writes an "alt" attribute, but a "title" attribute would also be appropriate
[ http://jira.codehaus.org/browse/DOXIA-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lukas Theussl closed DOXIA-75. -- Assignee: Lukas Theussl (was: Fabrice BELLINGARD) Resolution: Won't Fix Fix Version/s: (was: 1.0-beta-2) r635336 adjusted the figure handling according to my comments above. Any attributes like 'title' or 'alt' can now be passed in via SinkEventAttributeSets, see DOXIA-204. The old figure methods (without SinkEventAttributeSets) are kept unchanged for backward compatibility. > XhtmlSink#figureCaption() writes an "alt" attribute, but a "title" attribute > would also be appropriate > -- > > Key: DOXIA-75 > URL: http://jira.codehaus.org/browse/DOXIA-75 > Project: Maven Doxia > Issue Type: Improvement > Components: Core >Affects Versions: 1.0-alpha-8 >Reporter: Fabrice BELLINGARD >Assignee: Lukas Theussl >Priority: Trivial > > It's nice to see the figure caption in a tooltip, so maybe both "alt" and > "title" should be written. -- 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-530) Broken checksum for org/apache/maven/maven/2.0.6/maven-2.0.6.pom
[ http://jira.codehaus.org/browse/MEV-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126655 ] Jonathan Carr commented on MEV-530: --- I'll second that - I'm getting the same warning as Peter. > Broken checksum for org/apache/maven/maven/2.0.6/maven-2.0.6.pom > > > Key: MEV-530 > URL: http://jira.codehaus.org/browse/MEV-530 > Project: Maven Evangelism > Issue Type: Bug >Reporter: Max Bowsher >Assignee: Jason van Zyl > > org/apache/maven/maven/2.0.6/maven-2.0.6.pom has bad md5 and sha1 -- 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-395) Plugin tests are failing due to a wrong local repository path.
[
http://jira.codehaus.org/browse/MECLIPSE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier updated MECLIPSE-395:
-
Fix Version/s: (was: 2.5)
> Plugin tests are failing due to a wrong local repository path.
> --
>
> Key: MECLIPSE-395
> URL: http://jira.codehaus.org/browse/MECLIPSE-395
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.5
>Reporter: Arnaud Heritier
>Assignee: Arnaud Heritier
>
> In a corporate environment, we have the local repository not located in the
> standard location (${user.home}/.m2/repository).
> This is set in settings passed to maven with properties
> org.apache.maven.user-settings and org.apache.maven.global-settings (our
> settings are also not located in the standard locations
> ${user.home}/.m2/settings.xml and ${maven.home}/conf/settings.xml).
> Instead of using my local repository defined in our global settings, eclipse
> integration tests are using ${user.home}/.m2/repository, thus don't find
> dependencies. For example :
> {code}
> Error getting POM for ...
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2),
> testing.mainLocalAsRemote (file:/C:/Documents and
> Settings//.m2/repository)
> {code}
--
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: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126656 ] Arnaud Heritier commented on MECLIPSE-344: -- This last issue is reported in MECLIPSE-397 but I'm not surethat it is related to this one. You didn't have this problem with 2.4 ? > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Core : Dependencies resolution and build path >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, > MECLIPSE-344.patch, MECLIPSE-344.tgz, workspace-new-files.tgz, > workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-344. Resolution: Fixed I think we solved all problems discussed on the mailing list. I close the issue. Please open new ones if necessary > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Core : Dependencies resolution and build path >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, > MECLIPSE-344.patch, MECLIPSE-344.tgz, workspace-new-files.tgz, > workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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: (SUREFIRE-422) Strip "Maven" from report title
[ http://jira.codehaus.org/browse/SUREFIRE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed SUREFIRE-422. -- Resolution: Fixed fixed in r635366 thanks > Strip "Maven" from report title > --- > > Key: SUREFIRE-422 > URL: http://jira.codehaus.org/browse/SUREFIRE-422 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Benjamin Bentmann >Priority: Trivial > Fix For: 2.x > > Attachments: report-title.patch > > > Currently, the plugin generates a report named "Maven Surefire Report". I > consider "Maven" boilerplate text here that should be removed (of course it's > Maven, what else?). All other reporing plugins I have come along so far do > not use "Maven" in their title neither. -- 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: (SUREFIRE-422) Strip "Maven" from report title
[ http://jira.codehaus.org/browse/SUREFIRE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated SUREFIRE-422: --- Fix Version/s: (was: 2.x) 2.5 > Strip "Maven" from report title > --- > > Key: SUREFIRE-422 > URL: http://jira.codehaus.org/browse/SUREFIRE-422 > Project: Maven Surefire > Issue Type: Improvement >Affects Versions: 2.3 >Reporter: Benjamin Bentmann >Assignee: Herve Boutemy >Priority: Trivial > Fix For: 2.5 > > Attachments: report-title.patch > > > Currently, the plugin generates a report named "Maven Surefire Report". I > consider "Maven" boilerplate text here that should be removed (of course it's > Maven, what else?). All other reporing plugins I have come along so far do > not use "Maven" in their title neither. -- 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: (SUREFIRE-426) Add german translation
[ http://jira.codehaus.org/browse/SUREFIRE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy closed SUREFIRE-426. -- Assignee: Herve Boutemy Resolution: Fixed Fix Version/s: (was: 2.x) 2.5 fixed in r635369 thanks > Add german translation > -- > > Key: SUREFIRE-426 > URL: http://jira.codehaus.org/browse/SUREFIRE-426 > Project: Maven Surefire > Issue Type: Improvement > Components: report plugin >Affects Versions: 2.3 >Reporter: Benjamin Bentmann >Assignee: Herve Boutemy >Priority: Minor > Fix For: 2.5 > > Attachments: i18n-de.patch > > > Teaching the report another language. -- 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: (MECLIPSE-392) Output is written to src/main/webapp instead of target
[
http://jira.codehaus.org/browse/MECLIPSE-392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arnaud Heritier closed MECLIPSE-392.
Resolution: Fixed
Fix Version/s: 2.5
The manifest parameter is now correctly used to generate the file. You can test
the version maven-eclipse-plugin-2.5-20080309.224617-25 deployed on the
snapshots repository.
> Output is written to src/main/webapp instead of target
> --
>
> Key: MECLIPSE-392
> URL: http://jira.codehaus.org/browse/MECLIPSE-392
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Improvement
> Components: WTP support
>Affects Versions: 2.5
> Environment: Maven 2.0.7 on Linux, WTP 2.0
>Reporter: Martin Höller
>Assignee: Arnaud Heritier
>Priority: Minor
> Fix For: 2.5
>
>
> When using wtp 2.0 support MANIFEST.MF file is written to
> {{src/main/webapp/META-INF/MANIFEST.MF}} for webapplications (packaging WAR).
> According to the documentation this location is configurable using
> {{}}, which is silently ignored. The issues I have with this is a)
> that output is written to {{src/main}} (which is IMHO against maven
> conventions) and b) that the output location should be configurable according
> to docs, but is not.
> My configuration in the {{pom.xml}} is like this:
> {code}
>
> org.apache.maven.plugins
> maven-eclipse-plugin
> 2.5-SNAPSHOT
>
> 2.0
> true
>
>
> {code}
> For some discussion see also [this thread on
> nabble|http://www.nabble.com/maven-eclipse-plugin-writes-to-src-main-webapp-to15592874s177.html].
> A related issue to this one is
> [MECLIPSE-389|http://jira.codehaus.org/browse/MECLIPSE-389].
--
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-1958) a fix for jgroups 2.4.1
a fix for jgroups 2.4.1 --- Key: MAVENUPLOAD-1958 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1958 Project: maven-upload-requests Issue Type: Wish Reporter: pierre monestie Attachments: jgroups-all-2.4.1-bundle.jar I do not own this project however the maven repository for it is broken, as it refers to a non existing bsf. The attachement contains the correct pom.xml+jar for jgroups 2.4.1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (ARCHETYPE-147) Cannot create a new project from an exist project
Cannot create a new project from an exist project - Key: ARCHETYPE-147 URL: http://jira.codehaus.org/browse/ARCHETYPE-147 Project: Maven Archetype Issue Type: Bug Components: Archetypes Affects Versions: 2.0-alpha-2 Reporter: chenliang 1:run mvn:create-from-project in an existing project d:\workspace\myArchetype 2:run mvn:install in d:\workspace\myArchetype\target\archetype All the command run success But after that, i move to d:\workspace and try run mvn archetype:create. It fails. The log is here: Downloading: http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom Downloading: http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom [INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexu .velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on => 'false'. [INFO] Setting property: resource.loader => 'classpath'. [INFO] Setting property: resource.manager.logwhenfound => 'false'. [INFO] [archetype:create] [INFO] Defaulting package to group ID: com.ncs.iconnect.testproject [INFO] --- [INFO] Using following parameters for creating OldArchetype: iframe-blank:1.0-S APSHOT [INFO] --- [INFO] Parameter: groupId, Value: com.ncs.iconnect.testproject [INFO] Parameter: packageName, Value: com.ncs.iconnect.testproject [INFO] Parameter: basedir, Value: D:\workspace\testProject [INFO] Parameter: package, Value: com.ncs.iconnect.testproject [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] Parameter: artifactId, Value: myproject [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 5 seconds [INFO] Finished at: Mon Mar 10 09:57:06 GMT+08:00 2008 [INFO] Final Memory: 7M/14M [INFO] Cannot use mvn:create to create a new project from an archetype which install by mvn:create-from-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: (ARCHETYPE-147) Cannot create a new project from an exist project
[ http://jira.codehaus.org/browse/ARCHETYPE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126670 ] chenliang commented on ARCHETYPE-147: - The structure of the jar of create-from-project is: META-INF -maven -archetype.xml -archetype-metadata.xml archetype-resources -src -pom.xml > Cannot create a new project from an exist project > - > > Key: ARCHETYPE-147 > URL: http://jira.codehaus.org/browse/ARCHETYPE-147 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 2.0-alpha-2 >Reporter: chenliang > > 1:run mvn:create-from-project in an existing project d:\workspace\myArchetype > 2:run mvn:install in d:\workspace\myArchetype\target\archetype > All the command run success > But after that, i move to d:\workspace and try run mvn archetype:create. It > fails. The log is here: > Downloading: > http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h > tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom > Downloading: > http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h > tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom > [INFO] Setting property: classpath.resource.loader.class => > 'org.codehaus.plexu > .velocity.ContextClassLoaderResourceLoader'. > [INFO] Setting property: velocimacro.messages.on => 'false'. > [INFO] Setting property: resource.loader => 'classpath'. > [INFO] Setting property: resource.manager.logwhenfound => 'false'. > [INFO] [archetype:create] > [INFO] Defaulting package to group ID: com.ncs.iconnect.testproject > [INFO] > > --- > [INFO] Using following parameters for creating OldArchetype: > iframe-blank:1.0-S > APSHOT > [INFO] > > --- > [INFO] Parameter: groupId, Value: com.ncs.iconnect.testproject > [INFO] Parameter: packageName, Value: com.ncs.iconnect.testproject > [INFO] Parameter: basedir, Value: D:\workspace\testProject > [INFO] Parameter: package, Value: com.ncs.iconnect.testproject > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Parameter: artifactId, Value: myproject > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error creating from archetype > Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 5 seconds > [INFO] Finished at: Mon Mar 10 09:57:06 GMT+08:00 2008 > [INFO] Final Memory: 7M/14M > [INFO] > > Cannot use mvn:create to create a new project from an archetype which install > by mvn:create-from-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] Issue Comment Edited: (ARCHETYPE-147) Cannot create a new project from an exist project
[ http://jira.codehaus.org/browse/ARCHETYPE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126670 ] chenliang edited comment on ARCHETYPE-147 at 3/9/08 9:13 PM: - The structure of the jar of create-from-project is: META-INF -maven -archetype.xml -archetype-metadata.xml archetype-resources -src -pom.xml was (Author: chenliang): The structure of the jar of create-from-project is: META-INF -maven -archetype.xml -archetype-metadata.xml archetype-resources -src -pom.xml > Cannot create a new project from an exist project > - > > Key: ARCHETYPE-147 > URL: http://jira.codehaus.org/browse/ARCHETYPE-147 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 2.0-alpha-2 >Reporter: chenliang > > 1:run mvn:create-from-project in an existing project d:\workspace\myArchetype > 2:run mvn:install in d:\workspace\myArchetype\target\archetype > All the command run success > But after that, i move to d:\workspace and try run mvn archetype:create. It > fails. The log is here: > Downloading: > http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h > tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom > Downloading: > http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h > tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom > [INFO] Setting property: classpath.resource.loader.class => > 'org.codehaus.plexu > .velocity.ContextClassLoaderResourceLoader'. > [INFO] Setting property: velocimacro.messages.on => 'false'. > [INFO] Setting property: resource.loader => 'classpath'. > [INFO] Setting property: resource.manager.logwhenfound => 'false'. > [INFO] [archetype:create] > [INFO] Defaulting package to group ID: com.ncs.iconnect.testproject > [INFO] > > --- > [INFO] Using following parameters for creating OldArchetype: > iframe-blank:1.0-S > APSHOT > [INFO] > > --- > [INFO] Parameter: groupId, Value: com.ncs.iconnect.testproject > [INFO] Parameter: packageName, Value: com.ncs.iconnect.testproject > [INFO] Parameter: basedir, Value: D:\workspace\testProject > [INFO] Parameter: package, Value: com.ncs.iconnect.testproject > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Parameter: artifactId, Value: myproject > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error creating from archetype > Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 5 seconds > [INFO] Finished at: Mon Mar 10 09:57:06 GMT+08:00 2008 > [INFO] Final Memory: 7M/14M > [INFO] > > Cannot use mvn:create to create a new project from an archetype which install > by mvn:create-from-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] Issue Comment Edited: (ARCHETYPE-147) Cannot create a new project from an exist project
[ http://jira.codehaus.org/browse/ARCHETYPE-147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126670 ] chenliang edited comment on ARCHETYPE-147 at 3/9/08 9:28 PM: - The structure of the jar of create-from-project is: -META-INF --maven ---archetype.xml ---archetype-metadata.xml -archetype-resources --src --pom.xml I also tried mvn archetype:generate. But only create a POM file, all the src and other files are missing. was (Author: chenliang): The structure of the jar of create-from-project is: META-INF -maven -archetype.xml -archetype-metadata.xml archetype-resources -src -pom.xml > Cannot create a new project from an exist project > - > > Key: ARCHETYPE-147 > URL: http://jira.codehaus.org/browse/ARCHETYPE-147 > Project: Maven Archetype > Issue Type: Bug > Components: Archetypes >Affects Versions: 2.0-alpha-2 >Reporter: chenliang > > 1:run mvn:create-from-project in an existing project d:\workspace\myArchetype > 2:run mvn:install in d:\workspace\myArchetype\target\archetype > All the command run success > But after that, i move to d:\workspace and try run mvn archetype:create. It > fails. The log is here: > Downloading: > http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h > tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom > Downloading: > http://repo1.maven.org/maven2/com/ncs/iconnect/testproject/wagon-h > tp-shared/1.0-beta-2/wagon-http-shared-1.0-beta-2.pom > [INFO] Setting property: classpath.resource.loader.class => > 'org.codehaus.plexu > .velocity.ContextClassLoaderResourceLoader'. > [INFO] Setting property: velocimacro.messages.on => 'false'. > [INFO] Setting property: resource.loader => 'classpath'. > [INFO] Setting property: resource.manager.logwhenfound => 'false'. > [INFO] [archetype:create] > [INFO] Defaulting package to group ID: com.ncs.iconnect.testproject > [INFO] > > --- > [INFO] Using following parameters for creating OldArchetype: > iframe-blank:1.0-S > APSHOT > [INFO] > > --- > [INFO] Parameter: groupId, Value: com.ncs.iconnect.testproject > [INFO] Parameter: packageName, Value: com.ncs.iconnect.testproject > [INFO] Parameter: basedir, Value: D:\workspace\testProject > [INFO] Parameter: package, Value: com.ncs.iconnect.testproject > [INFO] Parameter: version, Value: 1.0-SNAPSHOT > [INFO] Parameter: artifactId, Value: myproject > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error creating from archetype > Embedded error: The META-INF/maven/archetype.xml descriptor cannot be found. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 5 seconds > [INFO] Finished at: Mon Mar 10 09:57:06 GMT+08:00 2008 > [INFO] Final Memory: 7M/14M > [INFO] > > Cannot use mvn:create to create a new project from an archetype which install > by mvn:create-from-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] Issue Comment Edited: (MNG-2807) ciManagement from parent is not merging with children
[ http://jira.codehaus.org/browse/MNG-2807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_124607 ] paul4christ79 edited comment on MNG-2807 at 3/9/08 10:00 PM: - This would greatly help when submodules are ran by different developers. The software engineers can be placed in the parent POM, and additional developers notified via the children POM. In the company I work for, we aren't allowed to have custom mailing lists -- so we have to list people (i.e., developers) individually in the POM. A pain, yes, but if this element was inheritable, it would be easier to deal with our constraint. was (Author: paul4christ79): This would greatly help when submodules are ran by different developers. The software engineers can be placed in the parent POM, and additional developers notified via the children POM. > ciManagement from parent is not merging with children > - > > Key: MNG-2807 > URL: http://jira.codehaus.org/browse/MNG-2807 > Project: Maven 2 > Issue Type: Bug > Components: Inheritance and Interpolation >Affects Versions: 2.0.4 > Environment: linux jdk1.5.0_10 amd64 >Reporter: Kelly Davis > Fix For: Reviewed Pending Version Assignment > > > If I define the following in my parent pom: > > continuum > http://blah > > and then in the child pom I have the following: > > > mail > > blah > > > The ciManagement for the effective pom lacks the system and url properties > from the parent pom. Seems like it should be merging them but isn't. This > would helpful for reducing code duplication. -- 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
