[jira] Created: (CONTINUUM-774) Better support for multiprojects
Better support for multiprojects Key: CONTINUUM-774 URL: http://jira.codehaus.org/browse/CONTINUUM-774 Project: Continuum Type: Improvement Reporter: Tomasz Pik Priority: Minor Currently when multiproject is being added to continuum, then top project is being registered as 'non-recursive' and all submodules are being added as separate projects. It will be nice to have the possibility to define (during initiial POM loading) if project should be treat that way or as a multiproject with full recursive build and without adding subprojects. I'm doing that manually, by redefining build section for top project and removing subprojects. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-428) Incorrect version for groovy-1.0-jsr-06
Incorrect version for groovy-1.0-jsr-06 --- Key: MEV-428 URL: http://jira.codehaus.org/browse/MEV-428 Project: Maven Evangelism Issue Type: Improvement Components: Invalid POM Reporter: Tomasz Pik currently pom (http://www.ibiblio.org/maven2/groovy/groovy-1.0-jsr/06/groovy-1.0-jsr-06.pom) has: groovy groovy groovy 1.0-jsr-06 but is located as groovy/groovy-1.0-jsr/06/groovy-1.0-jsr-06.pom so it should be groovy groovy groovy-1.0-jsr 06 The same problem for versions 01 and 02, versions 03, 04 and 05 looks OK Also version 06 referencing xpp3:xpp3:jar:1.1.3.4-RC8_min, which is not existing at ibiblio. -- 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-428) Incorrect version for groovy-1.0-jsr-06
[ http://jira.codehaus.org/browse/MEV-428?page=comments#action_71094 ] Tomasz Pik commented on MEV-428: Correction, it should be: groovy groovy-1.0-jsr groovy 06 > Incorrect version for groovy-1.0-jsr-06 > --- > > Key: MEV-428 > URL: http://jira.codehaus.org/browse/MEV-428 > Project: Maven Evangelism > Issue Type: Improvement > Components: Invalid POM >Reporter: Tomasz Pik > > currently pom > (http://www.ibiblio.org/maven2/groovy/groovy-1.0-jsr/06/groovy-1.0-jsr-06.pom) > has: > groovy > groovy > groovy > 1.0-jsr-06 > but is located as groovy/groovy-1.0-jsr/06/groovy-1.0-jsr-06.pom > so it should be > groovy > groovy > groovy-1.0-jsr > 06 > The same problem for versions 01 and 02, versions 03, 04 and 05 looks OK > Also version 06 referencing xpp3:xpp3:jar:1.1.3.4-RC8_min, which is not > existing at ibiblio. -- 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: (MWAR-67) webResource filtering needs filter
webResource filtering needs filter -- Key: MWAR-67 URL: http://jira.codehaus.org/browse/MWAR-67 Project: Maven 2.x War Plugin Issue Type: Bug Reporter: Tomasz Pik Priority: Minor Filtering of webResources works only, if there's at least one path/to/properties defined in pom. So without such a configuration there's no possiblity to build war file with filtering using values specified during build invocation, with -D options (System properties are ignored). Adding reference to (even empty) file using element 'solves' the problem and properties defined using -D are used. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-20) clean up bad IDs in the repository
[ http://jira.codehaus.org/browse/MEV-20?page=comments#action_73904 ] Tomasz Pik commented on MEV-20: --- What about rhino : js, shouldn't it be org.mozilla.javascript : js ? > clean up bad IDs in the repository > -- > > Key: MEV-20 > URL: http://jira.codehaus.org/browse/MEV-20 > Project: Maven Evangelism > Issue Type: Task >Reporter: Brett Porter > > some projects seem to have been filed with the wrong/multiple artifact and > group IDs. > This is to track what they are and get them in order. Document correct IDs, > but leave the old ones alone so as not to break builds. A richer repository > may later be able to give deprecation warnings on requesting the old JARs. > This will also assist in making a future transition to a new layout easier. -- 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-1128) Rhino js-1.5R3
Rhino js-1.5R3 -- Key: MAVENUPLOAD-1128 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1128 Project: maven-upload-requests Issue Type: New Feature Reporter: Tomasz Pik Rhino Java Script interpreter, with org.mozilla.javascript as groupId -- 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-1129) Rhino js-1.5R4-RC3
Rhino js-1.5R4-RC3 -- Key: MAVENUPLOAD-1129 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1129 Project: maven-upload-requests Issue Type: New Feature Reporter: Tomasz Pik Rhino Java Script interpreter. This is the same jar as in http://www.ibiblio.org/maven2/rhino/js/1.5R4-RC3/ but with org.mozilla.javascript as groupId and improved pom 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] Created: (MAVENUPLOAD-1130) Rhino js-1.5R4.1
Rhino js-1.5R4.1 Key: MAVENUPLOAD-1130 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1130 Project: maven-upload-requests Issue Type: New Feature Reporter: Tomasz Pik Rhino Java Script interpreter. Those are the same jars as in http://www.ibiblio.org/maven2/rhino/js/1.5R4.1/ (and http://www.ibiblio.org/maven2/rhino/rhino/1.5R4.1/) but with org.mozilla.javascript as groupId and improved pom 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: (MAVENUPLOAD-1128) Rhino js-1.5R3
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1128?page=comments#action_75057 ] Tomasz Pik commented on MAVENUPLOAD-1128: - yes, but both of them do not contain 1.5R3 (other versions do not work under BSF2.3.0) and also there's an overlap and 1.5R4.1 is in both rhino:rhino and rhino:js. the idea of this issue (and some other) is to put rhino under org.mozilla.javascript as package name suggests and relocate current rhino:rhino and rhino:js. > Rhino js-1.5R3 > -- > > Key: MAVENUPLOAD-1128 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1128 > Project: maven-upload-requests > Issue Type: New Feature >Reporter: Tomasz Pik > > Rhino Java Script interpreter, with org.mozilla.javascript as groupId -- 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: (MWAR-104) handle zip dependencies in war plugin
[ http://jira.codehaus.org/browse/MWAR-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108537 ] Tomasz Pik commented on MWAR-104: - Would it be also possible to provide a way for 'relocating' zip into given subdirectory during embedding into war file? Say: there's a zip file containing files directly in root of archive and there's a way to put them into 'scripts' directory of war file. This should be configurable - probably similar to http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-context-root.html > handle zip dependencies in war plugin > - > > Key: MWAR-104 > URL: http://jira.codehaus.org/browse/MWAR-104 > Project: Maven 2.x War Plugin > Issue Type: Improvement > Environment: all >Reporter: Olivier Lamy >Assignee: Stephane Nicoll > Fix For: 2.1-alpha-1 > > Attachments: foobar.zip, MWAR-104 > > > As MNG-1683 has been applied, the zip artifact must be handled in the war > plugin. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (SCM-348) missing scm:bootstrap in overview
missing scm:bootstrap in overview - Key: SCM-348 URL: http://jira.codehaus.org/browse/SCM-348 Project: Maven SCM Issue Type: Improvement Components: documentation Reporter: Tomasz Pik Overview on http://maven.apache.org/scm/plugins/index.html page lists most of mojos but list do not include scm:bootstrap. Please, add bootstrap to list. -- 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: (MWAR-122) tests failing in trunk on windows
tests failing in trunk on windows
-
Key: MWAR-122
URL: http://jira.codehaus.org/browse/MWAR-122
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Environment: WindowsXP
Reporter: Tomasz Pik
Two tests from trunk failing on windows:
Failed tests:
testOverlaysIncludesExcludesWithMultipleDefinitions(org.apache.maven.plugin.war.WarOverlaysTest)
testOverlaysIncludesExcludesWithMultipleDefinitions2(org.apache.maven.plugin.war.WarOverlaysTest)
this is causes by hardcoded META-INF/MAINFEST.MF paths in tests.
File.separator should be used instead of "/" :
-final FileFilter filter = new FileFilterImpl( webAppDirectory, new
String[]{"META-INF/MANIFEST.MF"} );
+ final FileFilter filter = new FileFilterImpl( webAppDirectory, new
String[]{"META-INF" + File.separator + "MANIFEST.MF"} );
--
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: (MWAR-123) filtering with @ is working randomly
filtering with @ is working randomly
Key: MWAR-123
URL: http://jira.codehaus.org/browse/MWAR-123
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-1
Reporter: Tomasz Pik
Attachments: filters.patch
Attached patch adding testing for filtering using @...@ (in parallel with
filtering using ${..}) tokens.
However, if you'll change
# this is comment created by author at somewhere
to
# this is comment created by [EMAIL PROTECTED]"
then test case will fall.
As far as I know this problem has a root in plexus utils but this is very
important for filtering jsp files (and so - for maven-war-plugin) because @
character has a special meaning in jsp.
So adding a directive like <%@ page import="package" %> will effectively
'disable' filtering.
--
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-1771) sync script for aislib
sync script for aislib -- Key: MAVENUPLOAD-1771 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1771 Project: maven-upload-requests Issue Type: Wish Reporter: Tomasz Pik Please, setup a sync process for aislib.sf.net set of projects. aislib is a set of OS tools and libraries created by AIS.PL (www.ais.pl) Here's a script: #!/bin/sh CONTACTS="Tomasz Pik <[EMAIL PROTECTED]>" MODE=rsync_ssh [EMAIL PROTECTED]:/home/groups/a/ai/aislib/htdocs/repos/sync GROUP_DIR=net/sf/aislib/ -- 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: (MENFORCER-51) build failure in case of available updates
[ http://jira.codehaus.org/browse/MENFORCER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147357#action_147357 ] Tomasz Pik commented on MENFORCER-51: - I agree that having it in enforcer is a better idea, then having it in versions plugin. Any chance that it can be included in roadmap for 1.0? > build failure in case of available updates > -- > > Key: MENFORCER-51 > URL: http://jira.codehaus.org/browse/MENFORCER-51 > Project: Maven 2.x Enforcer Plugin > Issue Type: Wish >Reporter: Tomasz Pik > > It would be useful to have a possibility to fail build if there's an update > of given dependency. > In some way it would 'solve' problem of 'how to depend of latest stable > version of my company parent pom' problem - build would just not pass > if there's an update. -- 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-1410) please could somebody correct castor-1.0, or give a hint how to use it?
[ http://jira.codehaus.org/browse/MAVENUPLOAD-1410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90128 ] Tomasz Pik commented on MAVENUPLOAD-1410: - maybe you may use versions newer then 1.0, it looks that they have correct poms: http://repo1.maven.org/maven2/org/codehaus/castor/castor/ (note change of groupId)? > please could somebody correct castor-1.0, or give a hint how to use it? > --- > > Key: MAVENUPLOAD-1410 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1410 > Project: maven-upload-requests > Issue Type: Task >Reporter: THURNER rupert > Assigned To: Carlos Sanchez > > http://repo1.maven.org/maven2/castor/castor/1.0/ does not have a pom file. is > there a special maven version which can read such artefacts or the upload > somehow was wrong? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MEV-517) incomplete maven-scm-plugin 1.0-rc1
incomplete maven-scm-plugin 1.0-rc1 --- Key: MEV-517 URL: http://jira.codehaus.org/browse/MEV-517 Project: Maven Evangelism Issue Type: Bug Components: Missing POM Reporter: Tomasz Pik there's only jar file for maven-scm-plugin 1.0-rc1, there's no pom file and maven-metadata do not list 1.0-rc1. it looks that sync from http://people.apache.org/~evenisse/stage/repo/org/apache/maven/plugins/maven-scm-plugin/ is incomplete -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-690) using undefined appserver.base
using undefined appserver.base
--
Key: MRM-690
URL: http://jira.codehaus.org/browse/MRM-690
Project: Archiva
Issue Type: Bug
Components: system
Affects Versions: 1.0.1
Reporter: Tomasz Pik
Archiva while first startup creates repositories using ${appserver.base}/data
as a root directory.
But setup guide does not inform, that such property should be set up for tomcat
during startup,
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-689) Incorrect war name in example for tomcat
Incorrect war name in example for tomcat Key: MRM-689 URL: http://jira.codehaus.org/browse/MRM-689 Project: Archiva Issue Type: Bug Components: documentation Affects Versions: 1.0.1 Reporter: Tomasz Pik Priority: Minor Page with tomcat configuration shows configuration for archiva-webapp-1.0.war while file is distributed as apache-archiva-1.0.1.war -- 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: (MENFORCER-37) 'noSnapshots' rule do not check version of parent
'noSnapshots' rule do not check version of parent - Key: MENFORCER-37 URL: http://jira.codehaus.org/browse/MENFORCER-37 Project: Maven 2.x Enforcer Plugin Issue Type: Bug Components: Standard Rules Affects Versions: 1.0-alpha-3 Reporter: Tomasz Pik Assignee: Brian Fox 'noSnapshots' is passing when parent is defined to be SNAPSHOT, IMHO parent is also a dependency so it should be checked and rule should throw an error if parent is a SNAPSHOT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MPLUGIN-91) misleading icon on list of goals
misleading icon on list of goals Key: MPLUGIN-91 URL: http://jira.codehaus.org/browse/MPLUGIN-91 Project: Maven 2.x Plugin Tools Issue Type: Bug Components: Plugin Plugin Reporter: Tomasz Pik Priority: Minor There's a column on 'list of goals' report page, indicating if given goal is a report of not. And for those, that are not a report 'red alert' icon is used. This will lead users to confusion because this page generated for plugin providing many mojos that are not reports will look like JUnit report with many failures. Please, change it to something different. Maybe, instead of "report: yes/no" this column should be named 'mojo type' and current 'green' mojos will have 'report' there while current 'red' mojos will have 'executable' there? -- 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: (MWAR-88) typos in documentation
typos in documentation -- Key: MWAR-88 URL: http://jira.codehaus.org/browse/MWAR-88 Project: Maven 2.x War Plugin Issue Type: Bug Reporter: Tomasz Pik Priority: Trivial Attachments: adding-filtering-webresources.apt.diff http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html contains typos in examples (related to excludes). Patch attached -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MASSEMBLY-175) MANIFEST entries are not preserved during assemby
MANIFEST entries are not preserved during assemby - Key: MASSEMBLY-175 URL: http://jira.codehaus.org/browse/MASSEMBLY-175 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Tomasz Pik "jar-with-dependencies" assembly should preserve MANIFEST entries from project main result (so configuration for this will be inherited from maven-jar-plugin). This is especially important in case for parameter. -- 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-2762) warning during tar unpackaging
warning during tar unpackaging -- Key: MNG-2762 URL: http://jira.codehaus.org/browse/MNG-2762 Project: Maven 2 Issue Type: Bug Components: Bootstrap & Build Reporter: Tomasz Pik Priority: Minor Using tar distribution, during upackaging I'm getting: tar: A lone zero block at 4174 warning message in output. Archive is being untarred correctly but this message may worry users that archive is corrupted -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MINVOKER-2) Failures are incorrectly counted
[ http://jira.codehaus.org/browse/MINVOKER-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tomasz Pik updated MINVOKER-2: -- Attachment: invoker.diff diff for InvokerMojo.java > Failures are incorrectly counted > > > Key: MINVOKER-2 > URL: http://jira.codehaus.org/browse/MINVOKER-2 > Project: Maven 2.x Invoker Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Tomasz Pik > Assigned To: John Casey >Priority: Minor > Attachments: invoker.diff > > > When build hook scripts returns false projects are counted two times as > failures - first time at script execution methods and second time in runBuild > methods. > This leads to results like this: > --- > Execution Summary: > Builds Passing: -1 > Builds Failing: 2 > --- > The following builds failed: > * test1\pom.xml > * test1\pom.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] Created: (MINVOKER-2) Failures are incorrectly counted
Failures are incorrectly counted Key: MINVOKER-2 URL: http://jira.codehaus.org/browse/MINVOKER-2 Project: Maven 2.x Invoker Plugin Issue Type: Bug Affects Versions: 1.0 Reporter: Tomasz Pik Assigned To: John Casey Priority: Minor Attachments: invoker.diff When build hook scripts returns false projects are counted two times as failures - first time at script execution methods and second time in runBuild methods. This leads to results like this: --- Execution Summary: Builds Passing: -1 Builds Failing: 2 --- The following builds failed: * test1\pom.xml * test1\pom.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] Created: (SCM-280) santiizing CVS tag in 'tag' mojo
santiizing CVS tag in 'tag' mojo
Key: SCM-280
URL: http://jira.codehaus.org/browse/SCM-280
Project: Maven SCM
Issue Type: Improvement
Components: maven-plugin
Affects Versions: 1.0-beta-4
Reporter: Tomasz Pik
'tag' mojo should sanitize CVS tag name so tags based on numbers with dots may
be used (and mojo will map them to acceptable form).
For example this will then work:
maven-scm-plugin
SNAPSHOT_${project.artifact.version}
deploy
tag
for SNAPSHOT deployments for those, who needs SNAPSHOTs recored in CVS as tags.
--
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-280) santiizing CVS tag in 'tag' mojo
[
http://jira.codehaus.org/browse/SCM-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Pik updated SCM-280:
---
Attachment: tag.diff
diff provided by richvdh on irc, verified - works as expected and solving
problem.
> santiizing CVS tag in 'tag' mojo
>
>
> Key: SCM-280
> URL: http://jira.codehaus.org/browse/SCM-280
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-plugin
>Affects Versions: 1.0-beta-4
>Reporter: Tomasz Pik
> Attachments: tag.diff
>
>
> 'tag' mojo should sanitize CVS tag name so tags based on numbers with dots
> may be used (and mojo will map them to acceptable form).
> For example this will then work:
>
> maven-scm-plugin
>
> SNAPSHOT_${project.artifact.version}
>
>
>
> deploy
>
> tag
>
>
>
>
> for SNAPSHOT deployments for those, who needs SNAPSHOTs recored in CVS as
> tags.
--
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-2307) Link to SCM plugin
Link to SCM plugin -- Key: MNG-2307 URL: http://jira.codehaus.org/browse/MNG-2307 Project: Maven 2 Type: Improvement Components: Documentation: General Reporter: Tomasz Pik There should be a link to maven-scm-plugin (http://maven.apache.org/scm/plugins/index.html) on http://maven.apache.org/plugins/ -- 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
