[jira] Commented: (MNGECLIPSE-124) Plugin fail to initialize when default maven repository folder is not available
[ http://jira.codehaus.org/browse/MNGECLIPSE-124?page=comments#action_74435
]
Tim Hedger commented on MNGECLIPSE-124:
---
Having just come across the same problem I can see where both Phillipe and
Martin are coming from on this issue. The plugin does work fine; you can use a
local repository, but the problem is you have to put the settings.xml config
file for Maven in a specific place (the location specified by the property
${user.home}/.m2/settings.xml) before you can run the plugin in Eclipse to
specify where you want the repository to be. The issue from a maven
perspective being that the master configuration for maven is in the conf
subdirectory under the maven installation. So if, as I do, you have your
configuration for your repository and proxy etc in that file (e.g.
c:\maven-2.0.4\conf\settings.xml) the Eclipse plugin doesn't look there - it
insists that the settings.xml file in under ${user.home} - so in my case I have
to duplicate it. When I do that it works fine.
I think a worthwhile enhancement to the plugin would be to look for a
settings.xml file in the conf directory under the maven installation and use
that in preference - as maven itself does.
> Plugin fail to initialize when default maven repository folder is not
> available
> ---
>
> Key: MNGECLIPSE-124
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-124
> Project: Maven 2.x Extension for Eclipse
> Issue Type: Bug
>Affects Versions: 0.0.7
> Environment: Windows XP Professional SP2
> JSE v1.5.0-06
> Eclipse 3.2RC4
>Reporter: Douglas WF Acheson
> Attachments: .log
>
>
> This is this error when I try to go to the Maven2 preferences :
> Plug-in org.maven.ide.eclipse was unable to load class
> org.maven.ide.eclipse.preferences.Maven2PreferencePage.
> As well, I an not able to associate a project with maven2 when using the RMB
> context menu for a project . I get a popup window with the following
> The chosen operation is not currently available
--
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-2554) Maven 2.1 trunk does not activate debug logging with the -X/--debug command line options.
Maven 2.1 trunk does not activate debug logging with the -X/--debug command line options. - Key: MNG-2554 URL: http://jira.codehaus.org/browse/MNG-2554 Project: Maven 2 Issue Type: Bug Components: Logging Affects Versions: 2.0.4 Reporter: Binyan Attachments: MNG-2554-maven-core.patch It is not possible to get the maven 2.1 source on the trunk to produce debug output. The reason is because the mojo logger instance does not have its threshold logging level updated from info to debug in the request passed to the Maven.execute() method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-2554) Maven 2.1 trunk does not activate debug logging with the -X/--debug command line options.
[ http://jira.codehaus.org/browse/MNG-2554?page=all ] Binyan updated MNG-2554: Attachment: MNG-2554-maven-core.patch Patch that restores debug logging to the mojos. > Maven 2.1 trunk does not activate debug logging with the -X/--debug command > line options. > - > > Key: MNG-2554 > URL: http://jira.codehaus.org/browse/MNG-2554 > Project: Maven 2 > Issue Type: Bug > Components: Logging >Affects Versions: 2.0.4 >Reporter: Binyan > Attachments: MNG-2554-maven-core.patch > > > It is not possible to get the maven 2.1 source on the trunk to produce debug > output. The reason is because the mojo logger instance does not have its > threshold logging level updated from info to debug in the request passed to > the Maven.execute() method. -- 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-2554) Maven 2.1 trunk does not activate debug logging with the -X/--debug command line options.
[ http://jira.codehaus.org/browse/MNG-2554?page=comments#action_74422 ] Binyan commented on MNG-2554: - This patch actually is for 2.1 trunk, not 2.0.4. > Maven 2.1 trunk does not activate debug logging with the -X/--debug command > line options. > - > > Key: MNG-2554 > URL: http://jira.codehaus.org/browse/MNG-2554 > Project: Maven 2 > Issue Type: Bug > Components: Logging >Affects Versions: 2.0.4 >Reporter: Binyan > Attachments: MNG-2554-maven-core.patch > > > It is not possible to get the maven 2.1 source on the trunk to produce debug > output. The reason is because the mojo logger instance does not have its > threshold logging level updated from info to debug in the request passed to > the Maven.execute() method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-36) Examples in how to have wrong groupId
Examples in how to have wrong groupId - Key: MDEP-36 URL: http://jira.codehaus.org/browse/MDEP-36 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0 Reporter: Jimisola Laursen I believe that the How to on http://maven.apache.org/plugins/maven-dependency-plugin/howto.html have the wrong groupId. It is org.apache.maven.plugin instead of org.apache.maven.plugins (notice the "s" in "plugins"). Which differs with the project summary page: http://maven.apache.org/plugins/maven-dependency-plugin/project-summary.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: (MDEP-36) Examples in how to have wrong groupId
[ http://jira.codehaus.org/browse/MDEP-36?page=all ] Dennis Lundberg closed MDEP-36. --- Resolution: Duplicate > Examples in how to have wrong groupId > - > > Key: MDEP-36 > URL: http://jira.codehaus.org/browse/MDEP-36 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Affects Versions: 2.0 >Reporter: Jimisola Laursen > > I believe that the How to on > http://maven.apache.org/plugins/maven-dependency-plugin/howto.html have the > wrong groupId. > It is > org.apache.maven.plugin > instead of > org.apache.maven.plugins > (notice the "s" in "plugins"). Which differs with the project summary page: > http://maven.apache.org/plugins/maven-dependency-plugin/project-summary.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] Commented: (MANTLR-8) Review plugin documentation
[ http://jira.codehaus.org/browse/MANTLR-8?page=comments#action_74439 ] Vincent Siveton commented on MANTLR-8: -- Staging site http://people.apache.org/~vsiveton/maven-antlr-plugin/ > Review plugin documentation > --- > > Key: MANTLR-8 > URL: http://jira.codehaus.org/browse/MANTLR-8 > Project: Maven 2.x Antlr Plugin > Issue Type: Task >Reporter: Vincent Siveton > Assigned To: Vincent Siveton > > See http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation -- 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: (MANTLR-3) ANTLR plugin does not reorder grammars connected by importVocab/exportVocab dependencies
[ http://jira.codehaus.org/browse/MANTLR-3?page=all ] Vincent Siveton closed MANTLR-3. Resolution: Duplicate as MANTLR-1 > ANTLR plugin does not reorder grammars connected by importVocab/exportVocab > dependencies > > > Key: MANTLR-3 > URL: http://jira.codehaus.org/browse/MANTLR-3 > Project: Maven 2.x Antlr Plugin > Issue Type: Bug > Environment: Win-XP >Reporter: Sergey Kalinichenko >Priority: Minor > Attachments: bug.zip > > > When ANTLR parsers (e.g. the text parser and the tree parser) share token > vocabularies through the importVocab/exportVocab options, ANTLR plugin does > not reorder grammars sent to the antlr. As the result, a compile will fail if > the grammar names are not sorted manually. A work-around is to sort the > grammars manually is usually an easy fix, but if this is something that could > be automated it would be a preferred solution to the problem. > See http://www.antlr.org/doc/vocab.html for information on > importVocab/exportVocab. > Steps to reproduce the bug: > 1. Create a maven project > 2. Unzip the attached file into the src/main directory. This will create > antlr directory with two files, bug.g and bugtree.g, in it. > 3. Add maven-antlr-plugin to the POM with > bugtree.g,bug.g > 4. Run mvn compile. Note that the compile fails because the import vocabulary > referenced by bugtree.g does not exist. > 5. Run mvn compile again. Note that this time the compile succeeds. > Expected behavior: > Ideally, the plugin should recognize that the import vocabulary required by > the grammar mentioned earlier in the list is produced by the grammar > mentioned later in the list, and re-order the grammars based on this > knowledge. I understand that this would require a lot more "parsing" than is > currently going on in the plugin, but doing so would eliminate some very > subtle errors (my co-worker spent a lot of time trying to figure out a > similar problem in our ant-based build scripts). -- 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: (MANTLR-3) ANTLR plugin does not reorder grammars connected by importVocab/exportVocab dependencies
[ http://jira.codehaus.org/browse/MANTLR-3?page=all ] Vincent Siveton reopened MANTLR-3: -- my mistake > ANTLR plugin does not reorder grammars connected by importVocab/exportVocab > dependencies > > > Key: MANTLR-3 > URL: http://jira.codehaus.org/browse/MANTLR-3 > Project: Maven 2.x Antlr Plugin > Issue Type: Bug > Environment: Win-XP >Reporter: Sergey Kalinichenko >Priority: Minor > Attachments: bug.zip > > > When ANTLR parsers (e.g. the text parser and the tree parser) share token > vocabularies through the importVocab/exportVocab options, ANTLR plugin does > not reorder grammars sent to the antlr. As the result, a compile will fail if > the grammar names are not sorted manually. A work-around is to sort the > grammars manually is usually an easy fix, but if this is something that could > be automated it would be a preferred solution to the problem. > See http://www.antlr.org/doc/vocab.html for information on > importVocab/exportVocab. > Steps to reproduce the bug: > 1. Create a maven project > 2. Unzip the attached file into the src/main directory. This will create > antlr directory with two files, bug.g and bugtree.g, in it. > 3. Add maven-antlr-plugin to the POM with > bugtree.g,bug.g > 4. Run mvn compile. Note that the compile fails because the import vocabulary > referenced by bugtree.g does not exist. > 5. Run mvn compile again. Note that this time the compile succeeds. > Expected behavior: > Ideally, the plugin should recognize that the import vocabulary required by > the grammar mentioned earlier in the list is produced by the grammar > mentioned later in the list, and re-order the grammars based on this > knowledge. I understand that this would require a lot more "parsing" than is > currently going on in the plugin, but doing so would eliminate some very > subtle errors (my co-worker spent a lot of time trying to figure out a > similar problem in our ant-based build scripts). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-529) Modules (child) scm connection URLs are not constructed correctly
[ http://jira.codehaus.org/browse/CONTINUUM-529?page=comments#action_74442
]
Joakim Erdfelt commented on CONTINUUM-529:
--
This problem can be reproduced with the plexus-security components.
https://svn.codehaus.org/plexus/trunk/plexus-sandbox/plexus-components/plexus-security/
> Modules (child) scm connection URLs are not constructed correctly
> -
>
> Key: CONTINUUM-529
> URL: http://jira.codehaus.org/browse/CONTINUUM-529
> Project: Continuum
> Issue Type: Bug
> Components: Core system, SCM
>Affects Versions: 1.0.2
>Reporter: Grégory Joseph
> Fix For: 1.1
>
>
> It *seems* to me that, when adding a parent pom to continuum, which has
> defined, but the scm url only defined in the parent, it gets and
> parses the child poms correctly, but their scm URLs are build as
> ${parentScmUrl}/${childArtifactId} , while I think they should rather be
> ${parentScmUrl}/${modulePath}
> Maybe this is a maven inheritance issue, though ?
--
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: (CONTINUUM-529) Modules (child) scm connection URLs are not constructed correctly
[ http://jira.codehaus.org/browse/CONTINUUM-529?page=all ]
Joakim Erdfelt updated CONTINUUM-529:
-
Priority: Critical (was: Major)
> Modules (child) scm connection URLs are not constructed correctly
> -
>
> Key: CONTINUUM-529
> URL: http://jira.codehaus.org/browse/CONTINUUM-529
> Project: Continuum
> Issue Type: Bug
> Components: Core system, SCM
>Affects Versions: 1.0.2
>Reporter: Grégory Joseph
>Priority: Critical
> Fix For: 1.1
>
>
> It *seems* to me that, when adding a parent pom to continuum, which has
> defined, but the scm url only defined in the parent, it gets and
> parses the child poms correctly, but their scm URLs are build as
> ${parentScmUrl}/${childArtifactId} , while I think they should rather be
> ${parentScmUrl}/${modulePath}
> Maybe this is a maven inheritance issue, though ?
--
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: (MANTLR-8) Review plugin documentation
Review plugin documentation --- Key: MANTLR-8 URL: http://jira.codehaus.org/browse/MANTLR-8 Project: Maven 2.x Antlr Plugin Issue Type: Task Reporter: Vincent Siveton Assigned To: Vincent Siveton See http://docs.codehaus.org/display/MAVEN/Maven+Plugin+Documentation -- 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: (MRM-166) ability to have multiple reports
[ http://jira.codehaus.org/browse/MRM-166?page=all ] Brett Porter closed MRM-166. Resolution: Fixed > ability to have multiple reports > > > Key: MRM-166 > URL: http://jira.codehaus.org/browse/MRM-166 > Project: Archiva > Issue Type: New Feature > Components: reporting, web application >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > > currently the reports are all aggregated into one representation and > execution. It should be possible to have separate groups, with just the > health ones tied to the indexing and the others run on demand. -- 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: (MRM-162) implement "quick fix" capabilities in reports
[ http://jira.codehaus.org/browse/MRM-162?page=comments#action_7 ] Brett Porter commented on MRM-162: -- the following capabilities are needed: - forward to relocation action page - delete (including corresponding checksums, POM and metadata) - correct checksum - correct metadata > implement "quick fix" capabilities in reports > - > > Key: MRM-162 > URL: http://jira.codehaus.org/browse/MRM-162 > Project: Archiva > Issue Type: Task > Components: reporting >Reporter: Brett Porter > Assigned To: Brett Porter > Fix For: 1.0-beta-1 > > > see the white site - checksums need to be generated/corrected, duplicate > files might be removed or relocated, etc. -- 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: (MDEP-35) Plugin documentation doesn't agree with what's actually deployed
[ http://jira.codehaus.org/browse/MDEP-35?page=comments#action_74446 ] kristian meier commented on MDEP-35: what about: http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-dependency-plugin/2.0-SNAPSHOT/maven-dependency-plugin-2.0-20060906.165246-1.jar after a brief check I think that will solve your issue. but I can not state anything about the stability of that snapshot. Personnaly I am using a subversion snapshot from two month ago. > Plugin documentation doesn't agree with what's actually deployed > > > Key: MDEP-35 > URL: http://jira.codehaus.org/browse/MDEP-35 > Project: Maven 2.x Dependency Plugin > Issue Type: Bug >Affects Versions: 1.0 >Reporter: Matthew Beermann >Priority: Blocker > > Compare: > http://www.ibiblio.org/maven2/org/codehaus/mojo/dependency-maven-plugin/1.0/dependency-maven-plugin-1.0.jar > With: > http://maven.apache.org/plugins/maven-dependency-plugin/copy-dependencies-mojo.html > In particular, look inside the "plugin.xml" file and see that the vast > majority of the parameters are missing. The result is that the documentation > page is pure fiction - the vast majority of those parameters won't work at > all. I don't know if I can convince the project owner(s) to move up the next > release at all, but if you could, we'd really, _really_ appreciate it... the > dependency plugin is almost useless to us without the additional > configuration parameters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MDEP-37) setting type in config causes NullPointerException
setting type in config causes NullPointerException -- Key: MDEP-37 URL: http://jira.codehaus.org/browse/MDEP-37 Project: Maven 2.x Dependency Plugin Issue Type: Bug Affects Versions: 2.0 Environment: suse10.0, java 1.4.2_11-b06,Maven version: 2.0.4 , latest subverion trunk Reporter: kristian meier Attachments: patch class does not set instacne variable factory -- 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: (MDEP-24) Sort the dependency:resolve output alphabetically
[ http://jira.codehaus.org/browse/MDEP-24?page=comments#action_74447 ] kristian meier commented on MDEP-24: patch works for me > Sort the dependency:resolve output alphabetically > - > > Key: MDEP-24 > URL: http://jira.codehaus.org/browse/MDEP-24 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Affects Versions: 1.0 >Reporter: Brian Fox >Priority: Trivial > Attachments: sorted-output.diff > > > Output looks like this: > [INFO] Resolved: fdf-toolkit-1.0.jar > [INFO] Resolved: activation-1.0.2.jar > [INFO] Resolved: sqlline-1.0.jar > [INFO] Resolved: struts-legacy-1.1.jar > [INFO] Resolved: jdo-1.0.2.jar > [INFO] Resolved: xalan-2.5.1.jar > [INFO] Resolved: dom4j-1.5.2.jar > [INFO] Resolved: xpp3-1.1.3.3.jar > [INFO] Resolved: qdox-1.5.jar > [INFO] Resolved: kodo-jdo-3.3.4.jar > Would be better sorted. -- 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: (CONTINUUM-856) Create add/edit/delete user group pages
[ http://jira.codehaus.org/browse/CONTINUUM-856?page=all ] Carlos Sanchez updated CONTINUUM-856: - Fix Version/s: 1.1 > Create add/edit/delete user group pages > --- > > Key: CONTINUUM-856 > URL: http://jira.codehaus.org/browse/CONTINUUM-856 > Project: Continuum > Issue Type: New Feature > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Fix For: 1.1 > > > Same as user pages, we need the screens to add/edit/delete user groups -- 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: (CONTINUUM-856) Create add/edit/delete user group pages
Create add/edit/delete user group pages --- Key: CONTINUUM-856 URL: http://jira.codehaus.org/browse/CONTINUUM-856 Project: Continuum Issue Type: New Feature Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Fix For: 1.1 Same as user pages, we need the screens to add/edit/delete user groups -- 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: (CONTINUUM-857) Allow several groups per user
Allow several groups per user - Key: CONTINUUM-857 URL: http://jira.codehaus.org/browse/CONTINUUM-857 Project: Continuum Issue Type: New Feature Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Fix For: 1.1 An user may belong to several groups -- 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: (CONTINUUM-857) Allow several groups per user
[ http://jira.codehaus.org/browse/CONTINUUM-857?page=all ] Carlos Sanchez updated CONTINUUM-857: - Fix Version/s: 1.1 Component/s: (was: Web interface) Core system > Allow several groups per user > - > > Key: CONTINUUM-857 > URL: http://jira.codehaus.org/browse/CONTINUUM-857 > Project: Continuum > Issue Type: New Feature > Components: Core system >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Fix For: 1.1 > > > An user may belong to several groups -- 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: (CONTINUUM-858) Move role add/edit/delete form to user group edit page
Move role add/edit/delete form to user group edit page -- Key: CONTINUUM-858 URL: http://jira.codehaus.org/browse/CONTINUUM-858 Project: Continuum Issue Type: Bug Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez The form is currently in edit user page -- 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: (MDEP-29) Make (sure) dependency:resolve outputs absolute filename (or at least make it configurable)
[ http://jira.codehaus.org/browse/MDEP-29?page=comments#action_74449 ] Jimisola Laursen commented on MDEP-29: -- I'm working on a patch for this issue. Stay tuned. > Make (sure) dependency:resolve outputs absolute filename (or at least make it > configurable) > --- > > Key: MDEP-29 > URL: http://jira.codehaus.org/browse/MDEP-29 > Project: Maven 2.x Dependency Plugin > Issue Type: Improvement >Affects Versions: 1.1, 2.0 >Reporter: Jimisola Laursen > > I haven't used 1.1/2.0 yet myself, but from Brian Fox's comment > (http://jira.codehaus.org/browse/MDEP-24#action_69078) it's uncertain whether > dependency:resolve outputs the absolute filename at all times. > Being able to specify whether the output should be filename onlhy or > absolute filename would be very useful. -- 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: (CONTINUUM-859) improve display of project group permissions page
improve display of project group permissions page - Key: CONTINUUM-859 URL: http://jira.codehaus.org/browse/CONTINUUM-859 Project: Continuum Issue Type: Improvement Components: Web interface Affects Versions: 1.1 Reporter: Carlos Sanchez Use extremecomponents table or other method to display the content -- 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: (CONTINUUM-859) improve display of project group permissions page
[ http://jira.codehaus.org/browse/CONTINUUM-859?page=all ] Carlos Sanchez updated CONTINUUM-859: - Fix Version/s: 1.1 > improve display of project group permissions page > - > > Key: CONTINUUM-859 > URL: http://jira.codehaus.org/browse/CONTINUUM-859 > Project: Continuum > Issue Type: Improvement > Components: Web interface >Affects Versions: 1.1 >Reporter: Carlos Sanchez > Assigned To: Teodoro Cue Jr. > Fix For: 1.1 > > > Use extremecomponents table or other method to display the content -- 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-1121) Jericho HTML Parser 2.3
Jericho HTML Parser 2.3 --- Key: MAVENUPLOAD-1121 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1121 Project: maven-upload-requests Issue Type: Task Reporter: Martin Jericho Jericho HTML Parser is a simple but powerful java library allowing analysis and manipulation of parts of an HTML document, including some common server-side tags, while reproducing verbatim any unrecognised or invalid HTML. Also provides useful HTML form utilities. -- 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
