[jira] Commented: (MAVENUPLOAD-1869) netbeans ant tasks for creating netbeans modules (as shipped with netbeans 6.0)
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118513 ] Milos Kleint commented on MAVENUPLOAD-1869: --- ok, I will consider that for the future. So far I've needed just this one jar file as it's used by the nbm-maven-plugin and it's pain in the ass to have plugin depend on something not in the central repo. > netbeans ant tasks for creating netbeans modules (as shipped with netbeans > 6.0) > --- > > Key: MAVENUPLOAD-1869 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1869 > Project: maven-upload-requests > Issue Type: Task >Reporter: Milos Kleint >Assignee: Carlos Sanchez > > netbeans ant tasks to create netbeans modules. > the jar is coming straight from the netbeans binary download of NetBeans 6.0 > FCS. The jar is located at netbeans/harness/tasks.jar in the binary distro. > relates tasks for previous versions. > http://jira.codehaus.org/browse/MAVENUPLOAD-1388 > released under dual license CDDL 1.0 + GPL 2.0 with classpath exception > I'm technically not a developer of the ant tasks, but I'm a Netbeans.org > contributor for 6 years , employed by Sun Microsystems. -- 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-2363) does not work in a multi-project build
[
http://jira.codehaus.org/browse/MNG-2363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118517
]
chenliang commented on MNG-2363:
I have the same issue.
I also have tried another way: to set a varible "needRun" to make sure whether
the sub module need to run the profile. Buf unfortunately, the activation does
not support the varible which defined in the POM. It only recognize the Command
Line Varible, such : mvn -DneedRun=true
Is there any solutions?
> does not work in a multi-project build
> ---
>
> Key: MNG-2363
> URL: http://jira.codehaus.org/browse/MNG-2363
> Project: Maven 2
> Issue Type: Bug
> Components: Profiles
>Reporter: David Boden
>Priority: Critical
> Fix For: 2.1
>
> Attachments: problemactivation.zip, screenshot-1.jpg
>
>
> I would expect each subproject to have the profile turned on or off depending
> on whether ${basedir}/file-to-check-for exists.
> Instead, during a multi-project build the profile is either on or off
> depending on whether the file exists relative to the *aggregator pom*. The
> decision is made once.
> Variable substitution doesn't work, so I can't explicitly use
> ${basedir}/file-to-check-for or any variation on this theme
> to workaround the bug.
> Some background to my particular problem. I have 10 modules to build. Some of
> them are GUI modules and contain a file called plugin.xml in the subproject
> directory. I want to package these up specially and sign them, ready for
> deployment to webstart. The other modules are shared and server code and I
> don't want these packaged in the same way. So, I've got a dependency in my
> *parent* pom file which activates a profile called "guibundle" if a
> plugin.xml file exists in the subproject directory.
--
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-835) Default profile in pom.xml not activated
[
http://jira.codehaus.org/browse/MNG-835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118519
]
Jake MacMullin commented on MNG-835:
Actually the syntax needed is:
test
true
...
That is *activeByDefault* not, activatedByDefault.
> Default profile in pom.xml not activated
>
>
> Key: MNG-835
> URL: http://jira.codehaus.org/browse/MNG-835
> Project: Maven 2
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 2.0-alpha-3
>Reporter: Vincent Massol
>Assignee: John Casey
> Fix For: 2.0-beta-1
>
> Original Estimate: 3 hours
> Time Spent: 3 hours
> Remaining Estimate: 0 minutes
>
> Pasted email from mailing list explaining the problem. I've also ran "m2
> projecthelp:active-profiles" and it doesn't show the profile as active.
> ---
> Hi,
> I want to allow cargo build users to override a plugin property. I have seen
> that using a element is not allowed in a settings.xml file and Brett
> has suggested I use a element instead. However I also need to
> define a default value for the property that can be overridden.
> Thus I have defined the following in my project's pom.xml:
> [...]
>
>
>
> maven-surefire-plugin
>
>
>
> cargo.containers
> ${cargo.containers}
>
> [...]
>
>
>
>
>
>
>
> default
>
> jetty4xEmbedded
>
>
>
>
> I want cargo build users to be able to create a settings.xml file with the
> following for example:
>
>
>
> user-vmassol
>
> resin3x
>
>
>
>
> user-vmassol
>
>
> Is that the correct way to implement my use case?
> So far, the issue I've had is that the default profile created in pom.xml is
> not used when I issue a "m2 install" command. I've read on
> http://docs.codehaus.org/display/MAVEN/Build+Profiles that naming a profile
> "default" will automatically activate it. Isn't that so?
> If not how can I activate a profile defined in pom.xml by default?
> Thanks a lot
> -Vincent
--
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: (MAVENUPLOAD-1859) Upload of NekoHTML 1.9.6
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez reopened MAVENUPLOAD-1859: - Assignee: (was: Carlos Sanchez) provide a bundle with the correct things and i'll put just the sources > Upload of NekoHTML 1.9.6 > > > Key: MAVENUPLOAD-1859 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1859 > Project: maven-upload-requests > Issue Type: Task >Reporter: Marc Guillemot > > htmlunit.sf.net/tmp/nekohtml-1.9.6-bundle.jar > http://nekohtml.sourceforge.net/ > Upload of new version of NekoHTML to allow it to be used by HtmlUnit. > (Version 1.9.6 is normal: version number has been boosted to denote project's > maturity) -- 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-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118540 ] Martin Zeltner commented on MECLIPSE-333: - I've now tried it with the Eclipse Europe 3.3.1.1 (eclipse-jee-europa-fall2-win32.zip) and the message doesn't appear. So all well. Happy New Year! Martin > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Multi-projects, WTP support >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: Eclipse-3.3.0-about.png, > Eclipse-3.3.0-project-upgrade.png, maven-eclipse-plugin_only_new.tar.gz, > maven-eclipse-plugin_only_new_2.tar.tgz, > wtp-2.0-and-more-2.5-SNAPSHOT-2.patch, wtp-2.0-and-more-2.5-SNAPSHOT-3.patch, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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-3282) maven only tries the first repo that contains an artifact
[ http://jira.codehaus.org/browse/MNG-3282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118558 ] Ken in nashua commented on MNG-3282: This is a pain in the neck. I receive the same thin with maven 2.0.6 org.apache.maven.artifact.resolver.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'com.gargoyle.test:gbase:jar': Error getting POM for 'com.gargoyle.test:gbase' from the repository: Error transferring file com.gargoyle.test:gbase:pom:2.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), trails.codehaus.org (http://trails.codehaus.org/repository), howardlewisship.com (http://howardlewisship.com/repository), localhost.repository (file:///C:\Tomcat-5.5.17/webapps/m2.repository) com.gargoyle.test:gbase:jar:2.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), trails.codehaus.org (http://trails.codehaus.org/repository), howardlewisship.com (http://howardlewisship.com/repository), localhost.repository (file:///C:\Tomcat-5.5.17/webapps/m2.repository) Path to dependency: 1) org.trailsframework.examples:realty:war:1.2-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:297) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:67) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:223) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:211) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:192) at org.apache.maven.project.DefaultMavenProjectBuilder.buildWithDependencies(DefaultMavenProjectBuilder.java:342) at org.apache.maven.project.DefaultMavenProjectBuilder.buildWithDependencies(DefaultMavenProjectBuilder.java:289) at org.apache.maven.embedder.MavenEmbedder.readProjectWithDependencies(MavenEmbedder.java:277) at org.maven.ide.eclipse.Maven2Executor.main(Maven2Executor.java:53) Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'com.gargoyle.test:gbase:jar': Error getting POM for 'com.gargoyle.test:gbase' from the repository: Error transferring file com.gargoyle.test:gbase:pom:2.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), trails.codehaus.org (http://trails.codehaus.org/repository), howardlewisship.com (http://howardlewisship.com/repository), localhost.repository (file:///C:\Tomcat-5.5.17/webapps/m2.repository) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:131) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:275) ... 8 more Caused by: org.apache.maven.project.ProjectBuildingException: Error getting POM for 'com.gargoyle.test:gbase' from the repository: Error transferring file com.gargoyle.test:gbase:pom:2.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), trails.codehaus.org (http://trails.codehaus.org/repository), howardlewisship.com (http://howardlewisship.com/repository), localhost.repository (file:///C:\Tomcat-5.5.17/webapps/m2.repository) at org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:501) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.java:225) at org.apache.maven.project.artifact.MavenMetadataSource.retrieve(MavenMetadataSource.java:102) ... 9 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transferring file com.gargoyle.test:gbase:pom:2.0.1 from the specified remote repositories: central (http://repo1.maven.org/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), trails.codehaus.org (http://trails.codehaus.org/repository), howardlewisship.com (http://howardlewisship.com/repository), localhost.repository (file:///C:\Tomcat-5.5.17/webapps/m2.repository) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:140) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:63)
[jira] Created: (MNG-3347) Broken links to maven source javadocs: http://maven.apache.org/guides/index.html
Broken links to maven source javadocs: http://maven.apache.org/guides/index.html Key: MNG-3347 URL: http://jira.codehaus.org/browse/MNG-3347 Project: Maven 2 Issue Type: Bug Components: Documentation: General Affects Versions: 2.0.8 Reporter: Graham Leggett When scrolling to the bottom of the following page, links are provided to the javadocs of the major maven APIs: http://maven.apache.org/guides/index.html All the links to these javadocs are currently broken. Following the links to http://maven.apache.org/ref/current/, none of the documentation sites include the maven reports section, which I suspect is the reason for the javadocs being missing. -- 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-3341) Bash auto-completion script in mini guide contains syntax error
[
http://jira.codehaus.org/browse/MNG-3341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MNG-3341.
-
Assignee: Olivier Lamy
Resolution: Fixed
fixed in rev 608553.
Thanks.
> Bash auto-completion script in mini guide contains syntax error
> ---
>
> Key: MNG-3341
> URL: http://jira.codehaus.org/browse/MNG-3341
> Project: Maven 2
> Issue Type: Bug
> Components: Documentation: Guides
>Affects Versions: 2.0.8
>Reporter: Daniel Harvey
>Assignee: Olivier Lamy
>Priority: Trivial
>
> The Mini Guide "Guide to Maven 2.x auto completion using BASH" at
> http://maven.apache.org/guides/mini/guide-bash-m2-completion.html contains an
> extra space in one line of the script which caused it to fail.
> The line
> {code}
> cur=${ COMP_WORDS[COMP_CWORD]}
> {code}
> should be
> {code}
> cur=${COMP_WORDS[COMP_CWORD]}
> {code}
> i.e. no space between "${" and "COMP_WORDS"
> Works perfectly otherwise! 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: (NMAVEN-102) nmaven doesn't clean up compilation staging directories when source is deleted/renamed
[ http://jira.codehaus.org/browse/NMAVEN-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118577 ] Shane Isbell commented on NMAVEN-102: - I'm thinking we should create a build-sources/generated-sources directory. Then the source processor can ignore anything under that single directory. This takes care of the general case. Specifically, for assembly info we would have: build-sources/generated-sources/META-INF/AssemblyInfo.cs. This patch creates a divergence with how Maven handles source processing, so I want to highlight the behavior in the docs. Also it would be a good idea to outline the reasons for the delta within this JIRA, otherwise we may have to keep revisiting the issue. > nmaven doesn't clean up compilation staging directories when source is > deleted/renamed > -- > > Key: NMAVEN-102 > URL: http://jira.codehaus.org/browse/NMAVEN-102 > Project: NMaven > Issue Type: Bug >Affects Versions: 0.15 > Environment: windows xp > maven version 2.0.7 >Reporter: zak jacobson >Priority: Minor > Attachments: synchronizeBuildSources.patch > > > If a file is renamed or deleted from sourceDirectory or testSourceDirectory, > it remains in the staging directory until a clean. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRELEASE-294) Generated release-pom.xml does not contain plugins configured in a super pom.
[
http://jira.codehaus.org/browse/MRELEASE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118589
]
Alex Deschapelles commented on MRELEASE-294:
This is still broken in 2.0-beta-7.
Would be REAL nice to get this fixed soon!
> Generated release-pom.xml does not contain plugins configured in a super pom.
> -
>
> Key: MRELEASE-294
> URL: http://jira.codehaus.org/browse/MRELEASE-294
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
>Affects Versions: 2.0-beta-6
>Reporter: Reinhard Nägele
> Attachments: patch.txt
>
>
> Finally, since 2.0-beta-6 it has been possible to generate release poms.
> Unfortunately, plugins configured in a super pom don't make it into the
> {{release-pom.xml}}.
> We have a multi-module project. Each module inherits from a super pom that
> also defines the modules. The super pom, amongst others, configures the
> compiler plugin for {{source}} and {{target 1.5}}. Since these plugin
> configurations only make it into the release pom of the super pom, but not
> into the release poms of the modules, the modules fail to build using the
> release plugin.
> {{generics are not supported in -source 1.3 (try -source 1.5 to enable
> generics)}}
> {{annotations are not supported in -source 1.3 (try -source 1.5 to enable
> annotations) @Override}}
> So, we still have to set {{generateReleasePoms}} to {{false}}.
--
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: (MJAR-82) Class-Path manifest entry should support maven repository layout
[ http://jira.codehaus.org/browse/MJAR-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118597 ] Geoffrey De Smet commented on MJAR-82: -- I 've tested it and it looks ok. I haven't been able to test it with the assembly plugin combined with java -jar, because of our hack for MJAR-28 which needs a , so we can't use a . I am unsure if the Class-path is taken from the current working directory or from the directory of the jar. In the second case that might mean that all entry's should be prefixed with "../../", depending on the number of dots in the groupId of the jar. I 'll create another issue and reference it here if that's the case. > Class-Path manifest entry should support maven repository layout > > > Key: MJAR-82 > URL: http://jira.codehaus.org/browse/MJAR-82 > Project: Maven 2.x Jar Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Geoffrey De Smet >Assignee: Olivier Lamy > Fix For: 2.2 > > > The assembly plugin supports outputting all dependencies in a repository > layout. > The jar plugin should support adding the classpath manifest entry based on > the repository layout. > The combination of the two makes it easy to write a script to run the app: > "java -jar org/domain/project/projectApp.jar" at the base of the repository > layout. > Example of a Class-Path entry: > ClassPath: > org/springframework/spring-core/2.0/spring-core-2.0.jar;org/drools/drools-core/4.0/drools-core-4.0.jar;org/domain/project/projectApp.jar > Also see maven user mailing list "maven-jar-plugin: how to avoid conflicts in > " -- 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-363) Perforce Provider ignores p4 errors from stderr
Perforce Provider ignores p4 errors from stderr --- Key: SCM-363 URL: http://jira.codehaus.org/browse/SCM-363 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-perforce Reporter: Brian Jackson Attachments: stderrChecking.patch All of the perforce commands are implemented to only check stdout for errors when the errors are actually written to stderr. Attached is a patch for a subset of the commands. -- 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: (CONTINUUM-1613) Add setting JAVA_HOME to the getting started documentation
[ http://jira.codehaus.org/browse/CONTINUUM-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivier Lamy closed CONTINUUM-1613. --- Assignee: Olivier Lamy Resolution: Fixed Fix Version/s: 1.1.x fix in rev 608614. > Add setting JAVA_HOME to the getting started documentation > -- > > Key: CONTINUUM-1613 > URL: http://jira.codehaus.org/browse/CONTINUUM-1613 > Project: Continuum > Issue Type: Improvement > Components: Documentation >Affects Versions: 1.1 > Environment: All >Reporter: Jon Stockdill >Assignee: Olivier Lamy > Fix For: 1.1.x > > > http://maven.apache.org/continuum/documentation/1_1/installation/standalone.html > should mention setting JAVA_HOME for all environments. -- 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: (SCM-321) bootstrap does duplicate checkout
[ http://jira.codehaus.org/browse/SCM-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-321. Assignee: Dan Tran Resolution: Fixed Fix Version/s: 1.x fixed at rev 608636 by having boostrap mojo to skip its checkout and check for the result stored in checkout mojo > bootstrap does duplicate checkout > - > > Key: SCM-321 > URL: http://jira.codehaus.org/browse/SCM-321 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.x > Environment: All >Reporter: Wouter Hermeling >Assignee: Dan Tran > Fix For: 1.x > > Attachments: BootstrapMojo.java, CheckoutMojo.java > > > A duplicate checkout is performed when executing scm:bootstrap. I checked the > sources of the plugin. In BoostrapMojo#execute() the following causes problem: > super.execute(); > CheckOutScmResult result = checkout(); > The super.execute() will perform a checkout since the class inherits from > CheckoutMojo. And the checkout() method will of course also perform a > checkout. -- 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: (SCM-341) tag is not required for an scm:tag operation
[ http://jira.codehaus.org/browse/SCM-341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-341. Assignee: Dan Tran Resolution: Won't Fix wrong configuration use -Dtag=tagname tagName in pom > tag is not required for an scm:tag operation > > > Key: SCM-341 > URL: http://jira.codehaus.org/browse/SCM-341 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin >Affects Versions: 1.0 >Reporter: Mykel Alvis >Assignee: Dan Tran > > When performing an scm:tag operation, neither passing the tag parameter to > the plugin nor configuring the tag in the pom actually fills in the tag info, > resulting in a missing parameter. > --- Copied from my original email > With maven 2.0.7, a working subversion SCM url and a build plugin as > > maven-scm-plugin > > tag > > > [EMAIL PROTECTED] MEFoundation-1.0.x]$ mvn scm:tag > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > WAGON_VERSION: 1.0-beta-2 > [INFO] > > [INFO] Building DSTHS MEFoundation EJB > [INFO]task-segment: [scm:tag] (aggregator-style) > [INFO] > > [INFO] [scm:tag] > [INFO] Final Tag Name: 'null' > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Cannot run tag command : > Embedded error: Exception while executing SCM command. > Missing parameter: 'tagName'. > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 3 seconds > [INFO] Finished at: Thu Sep 06 13:27:52 CDT 2007 > [INFO] Final Memory: 6M/127M > [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: (SCM-353) maven-scm-plugin configuration is ignored if executions present
[ http://jira.codehaus.org/browse/SCM-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran closed SCM-353. Assignee: Dan Tran Resolution: Won't Fix missing configuration. First you need set your to 'checkout' then set a phase to each execute. Best to query your quest with maven list first when in doubt about maven configration, likely you have a quick answer it works for me. > maven-scm-plugin configuration is ignored if executions present > --- > > Key: SCM-353 > URL: http://jira.codehaus.org/browse/SCM-353 > Project: Maven SCM > Issue Type: Bug > Components: maven-plugin > Environment: Maven version: 2.0.7 > Java version: 1.6.0_01 >Reporter: jason harrop >Assignee: Dan Tran >Priority: Minor > > If I don't use the element, the embedded configuration is used. > > org.apache.maven.plugins > maven-scm-plugin > 1.0 > > > > scm:svn:http://dev.plutext.org/svn/docx4j/trunk/docx4j > > docx4j > validate > > > However, I would like to checkout 2 modules from each of 2 different > repositories. > If I introduce , the plugin doesn't read the embedded > configuration. Instead, it falls back to what is defined in the > element (or if none exists, the super pom). > Here is what I have trying: > > org.apache.maven.plugins > maven-scm-plugin > 1.0 > > > > > > checkout-docx4j > > > > scm:svn:http://dev.plutext.org/svn/docx4j/trunk/docx4j > > > docx4j > > > validate > > > > checkout-jackrabbit-webapp > > > > scm:svn:http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-webapp > > > jackrabbit-webapp > > > > validate > > > > -- 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-3323) Publish the reference docs for 2.0.8
[ http://jira.codehaus.org/browse/MNG-3323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed MNG-3323. Resolution: Fixed Fix Version/s: 2.0.8 re-published with: mvn site-deploy -Preporting > Publish the reference docs for 2.0.8 > > > Key: MNG-3323 > URL: http://jira.codehaus.org/browse/MNG-3323 > Project: Maven 2 > Issue Type: Task > Components: Documentation: General >Affects Versions: 2.0.8 >Reporter: Wendy Smoak >Assignee: Wendy Smoak > Fix For: 2.0.8 > > > The reference docs for Maven 2.0.8 are missing, for example > http://maven.apache.org/ref/2.0.8/maven-model/maven.html -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-3347) Broken links to maven source javadocs: http://maven.apache.org/guides/index.html
[ http://jira.codehaus.org/browse/MNG-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed MNG-3347. Assignee: Wendy Smoak Resolution: Fixed Fix Version/s: 2.0.8 I re-published docs from the 2.0.8 tag with 'mvn site-deploy -Preporting'. (Site will take ~1 hour to sync.) Thanks for reporting it! > Broken links to maven source javadocs: > http://maven.apache.org/guides/index.html > > > Key: MNG-3347 > URL: http://jira.codehaus.org/browse/MNG-3347 > Project: Maven 2 > Issue Type: Bug > Components: Documentation: General >Affects Versions: 2.0.8 >Reporter: Graham Leggett >Assignee: Wendy Smoak > Fix For: 2.0.8 > > > When scrolling to the bottom of the following page, links are provided to the > javadocs of the major maven APIs: > http://maven.apache.org/guides/index.html > All the links to these javadocs are currently broken. > Following the links to http://maven.apache.org/ref/current/, none of the > documentation sites include the maven reports section, which I suspect is the > reason for the javadocs being missing. -- 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-366) Test file(s) for Multi-project sample is missing
[ http://jira.codehaus.org/browse/MECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118637 ] Simon Crossley commented on MECLIPSE-366: - In the meantime you can download the file from SVN at http://svn.apache.org/viewvc/maven/plugins/trunk/maven-eclipse-plugin/src/site/resources/j2ee-simple.tar.gz?view=co I had to specify the 2.5-SNAPSHOT version of the maven-eclipse-plugin in the pom (and use the snapshot repository), but then the example worked very nicely. > Test file(s) for Multi-project sample is missing > > > Key: MECLIPSE-366 > URL: http://jira.codehaus.org/browse/MECLIPSE-366 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.4 > Environment: Web, reading the documentation on > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html >Reporter: Anders Domeij >Priority: Minor > > In the multi-module project description the following is on the web page > The Example project > This project is an example of a multi-module projects, containing some JAR-, > a WAR- and an EAR-project. You can download it from here. The project is > based on the j2ee-simple archetype. > , with 'here' as a link to > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/j2ee-simple.tar.gz. > Unfortumnately that file is missing. -- 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: (MANTRUN-53) add ant optional task support
[
http://jira.codehaus.org/browse/MANTRUN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118644
]
Khai Do commented on MANTRUN-53:
The link points to a blank web page. How can I add optional jars to the
classpath? I want to run the ant FTP task from maven but I keep getting an
error that says the task is not recognized.
> add ant optional task support
> -
>
> Key: MANTRUN-53
> URL: http://jira.codehaus.org/browse/MANTRUN-53
> Project: Maven 2.x Antrun Plugin
> Issue Type: Improvement
>Affects Versions: 1.2
> Environment: windows 2000,java 1.4.2
>Reporter: bingwuli
>Assignee: Carlos Sanchez
>
> I use maven-antrun-plugin for my project recently. Althought this plugin give
> me some convenience, I find it doesn't support ant optional task. In my
> project ,I need to use native2ascii to convert my messages. When I put such
> ant segment dest="${project.build.outputDirectory}" includes="**/*.txt" ext =
> ".properties"/> into plugin's configuration, it doesn't work.
> After I carefully study plugin's docment ,I find the plugin doesn't depend on
> ant optional jar .After I add ant-optional jar into dependency path ,and
> rewrite ant segent as such ,it does work for me.
> classname="org.apache.tools.ant.taskdefs.optional.Native2Ascii" classpathref
> = "maven.compile.classpath" /> src="src/main/conf/message"dest="${project.build.outputDirectory}"
> includes="**/*.txt" ext = ".properties"/>
> I think it good idea that this plugin will support ant optional task.
--
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-366) Test file(s) for Multi-project sample is missing
[ http://jira.codehaus.org/browse/MECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118656 ] Arnaud Heritier commented on MECLIPSE-366: -- I don't know why Brian deployed this new version of the web site. It was not yet completely finalized and more important it is dedicated for the 2.5 release which isn't yet out. > Test file(s) for Multi-project sample is missing > > > Key: MECLIPSE-366 > URL: http://jira.codehaus.org/browse/MECLIPSE-366 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.4 > Environment: Web, reading the documentation on > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html >Reporter: Anders Domeij >Priority: Minor > > In the multi-module project description the following is on the web page > The Example project > This project is an example of a multi-module projects, containing some JAR-, > a WAR- and an EAR-project. You can download it from here. The project is > based on the j2ee-simple archetype. > , with 'here' as a link to > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/j2ee-simple.tar.gz. > Unfortumnately that file is missing. -- 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-366) Test file(s) for Multi-project sample is missing
[ http://jira.codehaus.org/browse/MECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-366: - Assignee: Arnaud Heritier Affects Version/s: (was: 2.4) 2.5 Fix Version/s: 2.5 > Test file(s) for Multi-project sample is missing > > > Key: MECLIPSE-366 > URL: http://jira.codehaus.org/browse/MECLIPSE-366 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5 > Environment: Web, reading the documentation on > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html >Reporter: Anders Domeij >Assignee: Arnaud Heritier >Priority: Minor > Fix For: 2.5 > > > In the multi-module project description the following is on the web page > The Example project > This project is an example of a multi-module projects, containing some JAR-, > a WAR- and an EAR-project. You can download it from here. The project is > based on the j2ee-simple archetype. > , with 'here' as a link to > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/j2ee-simple.tar.gz. > Unfortumnately that file is missing. -- 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-365) eclipse:eclipse should have a possibility to add linked resources to generatd .project file and use it in .classpath file
[ http://jira.codehaus.org/browse/MECLIPSE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-365: - Component/s: (was: M2Eclipse support) Dependencies resolution and build path > eclipse:eclipse should have a possibility to add linked resources to generatd > .project file and use it in .classpath file > - > > Key: MECLIPSE-365 > URL: http://jira.codehaus.org/browse/MECLIPSE-365 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Dependencies resolution and build path >Reporter: ddd >Priority: Critical > > I have a multi project which is deployed as WAR. For testing purposes I would > like to deploy expanded WAR on Tomcat deploy directory and then set the > project (on eclipse) to generate the compiled files on that dir, which in > turn would need to be a linked resource in my project. > When I set up projects manually .project and .classpath files look like this: > > project > > > > > > org.eclipse.jdt.core.javabuilder > > > > > > org.eclipse.jdt.core.javanature > > > > TARGET_DIR > 2 > TARGET_DIR > > > TARGET_DIR_TEST > 2 > TARGET_DIR_TEST > > > > > >path="src/test/java"/> >path="org.eclipse.jdt.launching.JRE_CONTAINER"/> > > > Currently my linked resources are pointing to workspace linked resources and > it would be nice to have a way to add workspace linked resources too, if that > is not too complicated. > And of course for multiproject purposes this settings should be inherited > from parent pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-365) eclipse:eclipse should have a possibility to add linked resources to generatd .project file and use it in .classpath file
[ http://jira.codehaus.org/browse/MECLIPSE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118658 ] Arnaud Heritier commented on MECLIPSE-365: -- Did you try to use WTP to launch your webapp in tomcat from eclipse. With WTP you have access to a step by step debugger and I think (I have to check) that it works also in JSPs without having to play with linked resources ? > eclipse:eclipse should have a possibility to add linked resources to generatd > .project file and use it in .classpath file > - > > Key: MECLIPSE-365 > URL: http://jira.codehaus.org/browse/MECLIPSE-365 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Dependencies resolution and build path >Reporter: ddd >Priority: Critical > > I have a multi project which is deployed as WAR. For testing purposes I would > like to deploy expanded WAR on Tomcat deploy directory and then set the > project (on eclipse) to generate the compiled files on that dir, which in > turn would need to be a linked resource in my project. > When I set up projects manually .project and .classpath files look like this: > > project > > > > > > org.eclipse.jdt.core.javabuilder > > > > > > org.eclipse.jdt.core.javanature > > > > TARGET_DIR > 2 > TARGET_DIR > > > TARGET_DIR_TEST > 2 > TARGET_DIR_TEST > > > > > >path="src/test/java"/> >path="org.eclipse.jdt.launching.JRE_CONTAINER"/> > > > Currently my linked resources are pointing to workspace linked resources and > it would be nice to have a way to add workspace linked resources too, if that > is not too complicated. > And of course for multiproject purposes this settings should be inherited > from parent pom. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MECLIPSE-366) Test file(s) for Multi-project sample is missing
[ http://jira.codehaus.org/browse/MECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier updated MECLIPSE-366: - Component/s: Documentation > Test file(s) for Multi-project sample is missing > > > Key: MECLIPSE-366 > URL: http://jira.codehaus.org/browse/MECLIPSE-366 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Documentation, WTP support >Affects Versions: 2.5 > Environment: Web, reading the documentation on > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html >Reporter: Anders Domeij >Assignee: Arnaud Heritier >Priority: Minor > Fix For: 2.5 > > > In the multi-module project description the following is on the web page > The Example project > This project is an example of a multi-module projects, containing some JAR-, > a WAR- and an EAR-project. You can download it from here. The project is > based on the j2ee-simple archetype. > , with 'here' as a link to > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/j2ee-simple.tar.gz. > Unfortumnately that file is missing. -- 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-366) Test file(s) for Multi-project sample is missing
[ http://jira.codehaus.org/browse/MECLIPSE-366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MECLIPSE-366. Resolution: Fixed New site deployed. Will be sync in a few time... > Test file(s) for Multi-project sample is missing > > > Key: MECLIPSE-366 > URL: http://jira.codehaus.org/browse/MECLIPSE-366 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: Documentation, WTP support >Affects Versions: 2.5 > Environment: Web, reading the documentation on > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/multi-module-projects.html >Reporter: Anders Domeij >Assignee: Arnaud Heritier >Priority: Minor > Fix For: 2.5 > > > In the multi-module project description the following is on the web page > The Example project > This project is an example of a multi-module projects, containing some JAR-, > a WAR- and an EAR-project. You can download it from here. The project is > based on the j2ee-simple archetype. > , with 'here' as a link to > http://maven.apache.org/plugins/maven-eclipse-plugin/examples/j2ee-simple.tar.gz. > Unfortumnately that file is missing. -- 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
