[jira] Updated: (MJAVADOC-36) Would like a way to get default javadoc behavior
[ http://jira.codehaus.org/browse/MJAVADOC-36?page=all ] Maria Odea Ching updated MJAVADOC-36: - Attachment: MJAVADOC-36-maven-javadoc-plugin.patch Would like a way to get default javadoc behavior Key: MJAVADOC-36 URL: http://jira.codehaus.org/browse/MJAVADOC-36 Project: Maven 2.x Javadoc Plugin Type: Wish Environment: Windows XP Reporter: Martin Desruisseaux Priority: Minor Fix For: 2.0-beta-4 Attachments: MJAVADOC-36-maven-javadoc-plugin.patch, no_default_stylesheet.diff The javadoc plugin overrides some Sun's javadoc default options with its own default. This is quite nice for options like -bottom, since Maven has informations that Sun's javadoc doesn't have. The -package option (which default to 'true' in maven-javadoc-plugin, while the default was 'false' in Sun's javadoc) sound a little bit more surprising to me, since it lead us to a situation where we have two set of default values to keep in mind: the Sun's ones, and the Maven ones. It is not a real problem for options like -package and -use. It is a little bit more disturbing for -stylesheet, since it seems hard to tell to Maven to not use the Maven's stylesheet, but to keep the Sun's default stylesheet instead. I understand that we can provide our own stylesheet with the stylesheet parameter, but in this case I have no file to point; I would just like to keep Sun's default stylesheet. I would like a way to disable completly the -stylesheet option in the javadoc plugin. Or alternatively, the plugin may use the Maven's stylesheet only when explicitly required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAVADOC-36) Would like a way to get default javadoc behavior
[ http://jira.codehaus.org/browse/MJAVADOC-36?page=comments#action_60326 ] Maria Odea Ching commented on MJAVADOC-36: -- By the way, if no stylesheet parameter is specified, the default stylesheet used is java's default stylesheet. Would like a way to get default javadoc behavior Key: MJAVADOC-36 URL: http://jira.codehaus.org/browse/MJAVADOC-36 Project: Maven 2.x Javadoc Plugin Type: Wish Environment: Windows XP Reporter: Martin Desruisseaux Assignee: Maria Odea Ching Priority: Minor Fix For: 2.0-beta-4 Attachments: MJAVADOC-36-maven-javadoc-plugin.patch, no_default_stylesheet.diff The javadoc plugin overrides some Sun's javadoc default options with its own default. This is quite nice for options like -bottom, since Maven has informations that Sun's javadoc doesn't have. The -package option (which default to 'true' in maven-javadoc-plugin, while the default was 'false' in Sun's javadoc) sound a little bit more surprising to me, since it lead us to a situation where we have two set of default values to keep in mind: the Sun's ones, and the Maven ones. It is not a real problem for options like -package and -use. It is a little bit more disturbing for -stylesheet, since it seems hard to tell to Maven to not use the Maven's stylesheet, but to keep the Sun's default stylesheet instead. I understand that we can provide our own stylesheet with the stylesheet parameter, but in this case I have no file to point; I would just like to keep Sun's default stylesheet. I would like a way to disable completly the -stylesheet option in the javadoc plugin. Or alternatively, the plugin may use the Maven's stylesheet only when explicitly required. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2134) Population problem when ${project.organization.name} is used in pom, e.g. in plugin configuration.
Population problem when ${project.organization.name} is used in pom, e.g. in
plugin configuration.
--
Key: MNG-2134
URL: http://jira.codehaus.org/browse/MNG-2134
Project: Maven 2
Type: Bug
Components: POM
Versions: 2.0.3
Reporter: Maria Odea Ching
The value set is the project name instead of the organization name.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MJAVADOC-57) empty target/site/apidocs/apidocs/index.html created
[ http://jira.codehaus.org/browse/MJAVADOC-57?page=all ] Maria Odea Ching updated MJAVADOC-57: - Attachment: MJAVADOC-57-maven-javadoc-plugin.patch empty target/site/apidocs/apidocs/index.html created Key: MJAVADOC-57 URL: http://jira.codehaus.org/browse/MJAVADOC-57 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 2.0-beta-4 Attachments: MJAVADOC-57-maven-javadoc-plugin.patch this seems to be because of the getOutputName(), but setting that to index would likely overwrite the correct version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MJAVADOC-55) offline links not generated when offline
[ http://jira.codehaus.org/browse/MJAVADOC-55?page=all ]
Maria Odea Ching updated MJAVADOC-55:
-
Attachment: MJAVADOC-55-maven-javadoc-plugin.patch
offline links not generated when offline
Key: MJAVADOC-55
URL: http://jira.codehaus.org/browse/MJAVADOC-55
Project: Maven 2.x Javadoc Plugin
Type: Bug
Environment: maven 2.0.2
javadoc plugin (beta-3)
Reporter: David DIDIER
Assignee: Maria Odea Ching
Fix For: 2.0-beta-4
Attachments: MJAVADOC-55-maven-javadoc-plugin.patch
The javadoc plugin (beta-3) in offline mode doesn't take into account the
offlineLinks parameter.
In JavadocReport.java, line 829:
if ( !isOffline )
{
addLinkArguments( arguments );
addLinkofflineArguments( arguments );
...
}
Shouldn't addLinkofflineArguments be outside the if block ?
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-2122) Update web access and svn checkout URLS in source repository page of maven-javadoc-plugin
Update web access and svn checkout URLS in source repository page of maven-javadoc-plugin - Key: MNG-2122 URL: http://jira.codehaus.org/browse/MNG-2122 Project: Maven 2 Type: Task Components: Sites Reporting Versions: 2.0.3 Reporter: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAVADOC-51) Wrong source url on website
[ http://jira.codehaus.org/browse/MJAVADOC-51?page=comments#action_60193 ] Maria Odea Ching commented on MJAVADOC-51: -- Already fixed in svn, the maven website just needs to be updated. Wrong source url on website --- Key: MJAVADOC-51 URL: http://jira.codehaus.org/browse/MJAVADOC-51 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Web browser Reporter: Keith E Campbell Assignee: Maria Odea Ching Fix For: 2.0-beta-4 The website http://maven.apache.org/plugins/maven-javadoc-plugin/source-repository.html lists the web access as: http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-plugins/maven-javadoc-plugin and the svn checkout as: svn checkout http://svn.apache.org/repos/asf/maven/components/trunk/maven-plugins/maven-javadoc-plugin maven-javadoc-plugin These don't work resulting errors such as: svn: URL 'http://svn.apache.org/repos/asf/maven/components/trunk/maven-plugins/maven-javadoc-plugin' doesn't exist The correct URLs (found via trial and error) should probably be: http://svn.apache.org/viewcvs.cgi/maven/plugins/trunk/maven-javadoc-plugin/ and svn checkout http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-javadoc-plugin maven-javadoc-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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAVADOC-46) Allow -docletpath to be specified as an artifact
[ http://jira.codehaus.org/browse/MJAVADOC-46?page=comments#action_60036 ] Maria Odea Ching commented on MJAVADOC-46: -- Tested and verified the submitted patch. Allow -docletpath to be specified as an artifact Key: MJAVADOC-46 URL: http://jira.codehaus.org/browse/MJAVADOC-46 Project: Maven 2.x Javadoc Plugin Type: New Feature Reporter: Wendy Smoak Priority: Minor Fix For: 2.0-beta-4 Attachments: javadoc-docletArtifact.diff As suggested (and written!) by Brett Porter on [EMAIL PROTECTED], in this thread: http://marc.theaimsgroup.com/?l=turbine-maven-devm=113694865002748w=2 Allow the doclet path to be specified as an artifact with docletArtifact. Currently the only option is docletPath which must be the local path to the jar file and is not portable. Comments welcome, I'm happy to rework it if necessary. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MJAVADOC-40) javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
[ http://jira.codehaus.org/browse/MJAVADOC-40?page=all ]
Maria Odea Ching updated MJAVADOC-40:
-
Attachment: (was: MJAVADOC-40-maven-javadoc-plugin.patch)
javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
--
Key: MJAVADOC-40
URL: http://jira.codehaus.org/browse/MJAVADOC-40
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Brian Fox
Assignee: Maria Odea Ching
Fix For: 2.0-beta-4
Attachments: javadoc-jar.patch
The following configuration will cause jar to fail. This is major because it
stops release:perform from completing on what otherwise should be a valid
config
build
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
source1.4/source
destDir${project.build.directory}/site/javadoc/destDir
/configuration
/plugin
/plugins
/build
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MJAVADOC-40) javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
[ http://jira.codehaus.org/browse/MJAVADOC-40?page=all ]
Maria Odea Ching updated MJAVADOC-40:
-
Attachment: MJAVADOC-40-maven-javadoc-plugin.patch
javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
--
Key: MJAVADOC-40
URL: http://jira.codehaus.org/browse/MJAVADOC-40
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Brian Fox
Assignee: Maria Odea Ching
Fix For: 2.0-beta-4
Attachments: MJAVADOC-40-maven-javadoc-plugin.patch, javadoc-jar.patch
The following configuration will cause jar to fail. This is major because it
stops release:perform from completing on what otherwise should be a valid
config
build
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
source1.4/source
destDir${project.build.directory}/site/javadoc/destDir
/configuration
/plugin
/plugins
/build
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MJAVADOC-47) Javadoc plugin ignores destDir when used in reporting section
[ http://jira.codehaus.org/browse/MJAVADOC-47?page=all ]
Maria Odea Ching updated MJAVADOC-47:
-
Attachment: MJAVADOC-47-maven-javadoc-plugin.patch
Javadoc plugin ignores destDir when used in reporting section
-
Key: MJAVADOC-47
URL: http://jira.codehaus.org/browse/MJAVADOC-47
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Wendy Smoak
Assignee: Maria Odea Ching
Fix For: 2.0-beta-4
Attachments: MJAVADOC-47-maven-javadoc-plugin.patch
When used in the reporting section of the pom and 'mvn site', output always
goes to target/apidocs, even if you specify an outputDir.
Having outputDir work correctly would by useful with alternate doclets, for
example sending the output of the UMLGraph doclet to target/uml so that it
can be further transformed.
This seems to be the code that's doing it:
if ( !javadocDirectory.getAbsolutePath().equals( getOutputDirectory()
) )
{
// we're in site-embedded report mode, so Doxia has set the
// reportOutputDirectory to the basedir of the site.
// Append 'apidocs'.
javadocDirectory = new File( javadocDirectory, apidocs );
}
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-99) Use RepositoryIndexSearchLayer for searching in Packages
[ http://jira.codehaus.org/browse/MRM-99?page=all ] Maria Odea Ching updated MRM-99: Attachment: MRM-99-maven-repository-webapp.patch Use RepositoryIndexSearchLayer for searching in Packages Key: MRM-99 URL: http://jira.codehaus.org/browse/MRM-99 Project: Maven Repository Manager Type: Bug Components: web application Versions: 1.0-alpha-1 Reporter: John Tolentino Attachments: MRM-99-maven-repository-webapp.patch Time Spent: 30 minutes Remaining: 0 minutes Update PackageSearchAction to use RepositoryIndexSearchLayer and change search result page to use SearchResult class. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-32) Repository Indexing
[ http://jira.codehaus.org/browse/MRM-32?page=all ] Maria Odea Ching closed MRM-32: --- Resolution: Fixed Lucene index was already created. All sub-tasks of this issue are already finished. Repository Indexing --- Key: MRM-32 URL: http://jira.codehaus.org/browse/MRM-32 Project: Maven Repository Manager Type: New Feature Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Create a repository indexer using Lucene -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MJAVADOC-40) javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
[ http://jira.codehaus.org/browse/MJAVADOC-40?page=all ]
Maria Odea Ching updated MJAVADOC-40:
-
Attachment: MJAVADOC-40-maven-javadoc-plugin.patch
javadoc:jar doesn't work if destDir was changed in javadoc:javadoc
--
Key: MJAVADOC-40
URL: http://jira.codehaus.org/browse/MJAVADOC-40
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Brian Fox
Assignee: Maria Odea Ching
Fix For: 2.0-beta-4
Attachments: MJAVADOC-40-maven-javadoc-plugin.patch, javadoc-jar.patch
The following configuration will cause jar to fail. This is major because it
stops release:perform from completing on what otherwise should be a valid
config
build
plugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
source1.4/source
destDir${project.build.directory}/site/javadoc/destDir
/configuration
/plugin
/plugins
/build
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-42) discover repository metadata
[ http://jira.codehaus.org/browse/MRM-42?page=all ] Maria Odea Ching reopened MRM-42: - There was a bug found when integrated with the scheduler and indexer. discover repository metadata Key: MRM-42 URL: http://jira.codehaus.org/browse/MRM-42 Project: Maven Repository Manager Type: Task Components: discovery Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-42-repository-manager-discovery.patch, MRM-42-repository-manager-discovery.patch Original Estimate: 18 hours Time Spent: 18 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-42) discover repository metadata
[ http://jira.codehaus.org/browse/MRM-42?page=all ] Maria Odea Ching updated MRM-42: Attachment: MRM-42-maven-repository-discovery.patch discover repository metadata Key: MRM-42 URL: http://jira.codehaus.org/browse/MRM-42 Project: Maven Repository Manager Type: Task Components: discovery Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-42-maven-repository-discovery.patch, MRM-42-repository-manager-discovery.patch, MRM-42-repository-manager-discovery.patch Original Estimate: 18 hours Time Spent: 18 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-36) integration with discovery and scheduling
[ http://jira.codehaus.org/browse/MRM-36?page=all ] Maria Odea Ching updated MRM-36: Attachment: MRM-36-maven-repository-webapp.patch integration with discovery and scheduling - Key: MRM-36 URL: http://jira.codehaus.org/browse/MRM-36 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-36-maven-repository-webapp.patch Original Estimate: 15 hours Time Spent: 7 hours Remaining: 8 hours I presume the regular indexer will process an individual file and add it to the index, or remove a file from the index. This should integrated with the discovery mechanism so that it can trigger the indexing of files (or removal - though this is not currently in the discovery mechanism). As for scheduling, it may be that the index updates are processed on a scheduled interval so that integration might be needed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MJAVADOC-52) locale error
[ http://jira.codehaus.org/browse/MJAVADOC-52?page=comments#action_59870 ] Maria Odea Ching commented on MJAVADOC-52: -- Also, change the localezh_CN.UTF8/locale to localezh_CN/locale in the plugin configuration specified on the issue's description because a Malformed locale name error occurs. locale error Key: MJAVADOC-52 URL: http://jira.codehaus.org/browse/MJAVADOC-52 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: windows 2000 maven 2.01 Reporter: pinghe Priority: Critical Attachments: javadoc-locale.diff plugin artifactIdmaven-javadoc-plugin/artifactId configuration localezh_CN.UTF8/locale encodingUTF-8/encoding charsetUTF-8/charset docencodingUTF-8/docencoding /configuration /plugin output: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error has occurred in JavaDocs report generation. Embedded error: Exit code: 1 - javadoc: option -locale must be first on the command line. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-57) ability to retrieve matched portion of classes, packages and files fields
[ http://jira.codehaus.org/browse/MRM-57?page=all ] Maria Odea Ching updated MRM-57: Attachment: MRM-57-maven-repository-indexer.patch ability to retrieve matched portion of classes, packages and files fields - Key: MRM-57 URL: http://jira.codehaus.org/browse/MRM-57 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-57-maven-repository-indexer.patch, MRM-57-maven-repository-indexing.patch Time Spent: 21 hours Remaining: 0 minutes If searching by org.apache, it would be good to just obtain the portions of the field that matched. This might require indexing one record per class. Need to investigate some more, and determine whether we are using that or can do something else. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-88) search by filename
[ http://jira.codehaus.org/browse/MRM-88?page=all ] Maria Odea Ching closed MRM-88: --- Resolution: Fixed The searcher is already capable of this. search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 2 hours Remaining: 2 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-57) ability to retrieve matched portion of classes, packages and files fields
[ http://jira.codehaus.org/browse/MRM-57?page=all ] Maria Odea Ching updated MRM-57: Attachment: MRM-57-maven-repository-indexing.patch ability to retrieve matched portion of classes, packages and files fields - Key: MRM-57 URL: http://jira.codehaus.org/browse/MRM-57 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-57-maven-repository-indexing.patch Time Spent: 12 hours Remaining: 9 hours If searching by org.apache, it would be good to just obtain the portions of the field that matched. This might require indexing one record per class. Need to investigate some more, and determine whether we are using that or can do something else. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-36) integration with discovery and scheduling
[ http://jira.codehaus.org/browse/MRM-36?page=comments#action_58581 ] Maria Odea Ching commented on MRM-36: - This issue is related to MRM-38. A Job that invokes the discoverer and indexer should be created and then scheduled to be executed. integration with discovery and scheduling - Key: MRM-36 URL: http://jira.codehaus.org/browse/MRM-36 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 15 hours Remaining: 15 hours I presume the regular indexer will process an individual file and add it to the index, or remove a file from the index. This should integrated with the discovery mechanism so that it can trigger the indexing of files (or removal - though this is not currently in the discovery mechanism). As for scheduling, it may be that the index updates are processed on a scheduled interval so that integration might be needed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-57) ability to retrieve matched portion of classes, packages and files fields
[ http://jira.codehaus.org/browse/MRM-57?page=all ] Maria Odea Ching closed MRM-57: --- Resolution: Fixed The current searcher already handles this type of search. ability to retrieve matched portion of classes, packages and files fields - Key: MRM-57 URL: http://jira.codehaus.org/browse/MRM-57 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 12 hours Remaining: 0 minutes If searching by org.apache, it would be good to just obtain the portions of the field that matched. This might require indexing one record per class. Need to investigate some more, and determine whether we are using that or can do something else. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-57) ability to retrieve matched portion of classes, packages and files fields
[ http://jira.codehaus.org/browse/MRM-57?page=all ] Maria Odea Ching reopened MRM-57: - When org.apache is searched in query everything, and a match was found in a package name, the search results should know that it was a package that was found. ability to retrieve matched portion of classes, packages and files fields - Key: MRM-57 URL: http://jira.codehaus.org/browse/MRM-57 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 12 hours Remaining: 0 minutes If searching by org.apache, it would be good to just obtain the portions of the field that matched. This might require indexing one record per class. Need to investigate some more, and determine whether we are using that or can do something else. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-57) ability to retrieve matched portion of classes, packages and files fields
[ http://jira.codehaus.org/browse/MRM-57?page=all ] Maria Odea Ching updated MRM-57: Due Date: 16/Feb/06 Remaining Estimate: 9 hours (was: 0 minutes) ability to retrieve matched portion of classes, packages and files fields - Key: MRM-57 URL: http://jira.codehaus.org/browse/MRM-57 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 12 hours Remaining: 9 hours If searching by org.apache, it would be good to just obtain the portions of the field that matched. This might require indexing one record per class. Need to investigate some more, and determine whether we are using that or can do something else. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-58) create a search result class for returning from search
[ http://jira.codehaus.org/browse/MRM-58?page=all ] Maria Odea Ching updated MRM-58: Due Date: 17/Feb/06 (was: 15/Feb/06) create a search result class for returning from search -- Key: MRM-58 URL: http://jira.codehaus.org/browse/MRM-58 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 6 hours Remaining: 6 hours instead of returning artifacts, return a search result class including artifact, classes, packages and 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-36) integration with discovery and scheduling
[ http://jira.codehaus.org/browse/MRM-36?page=comments#action_58412 ] Maria Odea Ching commented on MRM-36: - The discoverer will be scheduled to execute using the plexus-quartz scheduler. Since the discoverer will have a complete list of all the artifacts/metadata in the repository, we can call the indexer and index the artifact/metadata as we iterate through this list. Please note that the indexer checks first whether the artifact/metadata already exists in the index before indexing the given artifact/metadata to assure that there will be no duplicates. integration with discovery and scheduling - Key: MRM-36 URL: http://jira.codehaus.org/browse/MRM-36 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 15 hours Remaining: 15 hours I presume the regular indexer will process an individual file and add it to the index, or remove a file from the index. This should integrated with the discovery mechanism so that it can trigger the indexing of files (or removal - though this is not currently in the discovery mechanism). As for scheduling, it may be that the index updates are processed on a scheduled interval so that integration might be needed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Attachment: MRM-69-maven-repository-indexer.patch Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Attachments: MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch Original Estimate: 15 hours Time Spent: 13 hours Remaining: 2 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Attachment: MRM-69-maven-repository-indexer.patch Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Attachments: MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch Original Estimate: 15 hours Time Spent: 13 hours Remaining: 2 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Attachment: (was: MRM-69-maven-repository-indexer.patch) Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Attachments: MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch Original Estimate: 15 hours Time Spent: 13 hours Remaining: 2 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Attachment: MRM-69-maven-repository-indexer.patch Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Attachments: MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch, MRM-69-maven-repository-indexer.patch Original Estimate: 15 hours Time Spent: 13 hours Remaining: 2 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-68) Accomodate query everything in the index
[ http://jira.codehaus.org/browse/MRM-68?page=all ] Maria Odea Ching closed MRM-68: --- Resolution: Fixed The resolution is included in the patch file attached in MRM-69. Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 20 hours Time Spent: 17 hours, 30 minutes Remaining: 2 hours, 30 minutes Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Attachment: MRM-69-maven-repository-indexer.patch Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Attachments: MRM-69-maven-repository-indexer.patch Original Estimate: 15 hours Time Spent: 8 hours Remaining: 7 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-68) Accomodate query everything in the index
[ http://jira.codehaus.org/browse/MRM-68?page=all ] Maria Odea Ching updated MRM-68: Due Date: 10/Feb/06 Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 20 hours Remaining: 20 hours Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Due Date: 10/Feb/06 Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 15 hours Remaining: 15 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching closed MRM-61: --- Resolution: Fixed Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 13 hours Time Spent: 13 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-66) Repository configuration
[ http://jira.codehaus.org/browse/MRM-66?page=all ] Maria Odea Ching updated MRM-66: Summary: Repository configuration (was: Repoitory configuration) Repository configuration Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching closed MRM-52: --- Resolution: Fixed integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 10 hours Remaining: 10 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-66) Repoitory configuration
Repoitory configuration --- Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-66) Repoitory configuration
[ http://jira.codehaus.org/browse/MRM-66?page=all ] Maria Odea Ching updated MRM-66: Remaining Estimate: 1 day Original Estimate: 1 day Repoitory configuration --- Key: MRM-66 URL: http://jira.codehaus.org/browse/MRM-66 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day A configuration file will be retrieved and read by the Administration module. Then the values will be set on the specific class(es) that will use this configuration. Configurable fields: repositories, location of local cache and if repositories are browsable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-67) Index maintenance
Index maintenance - Key: MRM-67 URL: http://jira.codehaus.org/browse/MRM-67 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Update of index is triggered by discovery, which is a scheduled task. A configuration file that contains the execution schedule of the discoverer will be retrieved and read. These values will be passed/set on the scheduler. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-67) Index maintenance
[ http://jira.codehaus.org/browse/MRM-67?page=all ] Maria Odea Ching updated MRM-67: Remaining Estimate: 1 day Original Estimate: 1 day Index maintenance - Key: MRM-67 URL: http://jira.codehaus.org/browse/MRM-67 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 1 day Remaining: 1 day Update of index is triggered by discovery, which is a scheduled task. A configuration file that contains the execution schedule of the discoverer will be retrieved and read. These values will be passed/set on the scheduler. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-68) Accomodate query everything in the index
Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-68) Accomodate query everything in the index
[ http://jira.codehaus.org/browse/MRM-68?page=all ] Maria Odea Ching updated MRM-68: Remaining Estimate: 20 hours Original Estimate: 20 hours Accomodate query everything in the index -- Key: MRM-68 URL: http://jira.codehaus.org/browse/MRM-68 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 20 hours Remaining: 20 hours Index must accomodate google-like search wherein the keyword or term can be searched on all the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-69) Simple query everything search
Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-69) Simple query everything search
[ http://jira.codehaus.org/browse/MRM-69?page=all ] Maria Odea Ching updated MRM-69: Remaining Estimate: 15 hours Original Estimate: 15 hours Simple query everything search Key: MRM-69 URL: http://jira.codehaus.org/browse/MRM-69 Project: Maven Repository Manager Type: Task Reporter: Maria Odea Ching Original Estimate: 15 hours Remaining: 15 hours Search keyword/term in any of the fields in the index. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-88) search by filename
search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-88) search by filename
[ http://jira.codehaus.org/browse/MRM-88?page=all ] Maria Odea Ching updated MRM-88: Assign To: Maria Odea Ching Remaining Estimate: 2 hours Original Estimate: 2 hours search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 2 hours Remaining: 2 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-88) search by filename
[ http://jira.codehaus.org/browse/MRM-88?page=comments#action_57705 ] Maria Odea Ching commented on MRM-88: - The resolution for this issue is included in the patch file attached to issue MRM-44. search by filename -- Key: MRM-88 URL: http://jira.codehaus.org/browse/MRM-88 Project: Maven Repository Manager Type: Sub-task Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 2 hours Remaining: 2 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching reopened MRM-61: - Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching updated MRM-61: Remaining Estimate: 13 hours Original Estimate: 13 hours Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching Original Estimate: 13 hours Remaining: 13 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching reopened MRM-52: - integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=comments#action_57713 ] Maria Odea Ching commented on MRM-52: - MRM-69 still needs to be done and integrated with indexing. integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching updated MRM-52: Remaining Estimate: 10 hours Original Estimate: 10 hours integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Original Estimate: 10 hours Remaining: 10 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-36) integration with discovery and scheduling
[ http://jira.codehaus.org/browse/MRM-36?page=all ] Maria Odea Ching updated MRM-36: Remaining Estimate: 15 hours Original Estimate: 15 hours integration with discovery and scheduling - Key: MRM-36 URL: http://jira.codehaus.org/browse/MRM-36 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Fix For: 1.0-alpha-1 Original Estimate: 15 hours Remaining: 15 hours I presume the regular indexer will process an individual file and add it to the index, or remove a file from the index. This should integrated with the discovery mechanism so that it can trigger the indexing of files (or removal - though this is not currently in the discovery mechanism). As for scheduling, it may be that the index updates are processed on a scheduled interval so that integration might be needed. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-1593) Typo in settings doc
[ http://jira.codehaus.org/browse/MNG-1593?page=comments#action_57388 ] Maria Odea Ching commented on MNG-1593: --- This has already been updated in SVN. An xdoc must be generated and included in the maven settings site. Typo in settings doc Key: MNG-1593 URL: http://jira.codehaus.org/browse/MNG-1593 Project: Maven 2 Type: Bug Components: Documentation: General Versions: 2.0 Reporter: Carlos Sanchez Assignee: Maria Odea Ching Priority: Minor Fix For: documentation http://maven.apache.org/maven-settings/settings.html under repository and pluginRepository release should be releases snapshot should be snapshots -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1268) Complete the Introduction to the POM page
[ http://jira.codehaus.org/browse/MNG-1268?page=all ] Maria Odea Ching updated MNG-1268: -- Attachment: MNG-1268-documentation-instroductions.patch Complete the Introduction to the POM page - Key: MNG-1268 URL: http://jira.codehaus.org/browse/MNG-1268 Project: Maven 2 Type: Task Components: documentation - introductions Reporter: Srepfler Srgjan Assignee: Maria Odea Ching Priority: Minor Fix For: documentation Attachments: MNG-1268-documentation-instroductions.patch The Introduction to the POM page is there but empty. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-1953) src/main/webapp should be added to Introduction to the Standard Directory Layout page
[ http://jira.codehaus.org/browse/MNG-1953?page=all ] Maria Odea Ching updated MNG-1953: -- Attachment: MNG-1953-documentation-introductions.patch src/main/webapp should be added to Introduction to the Standard Directory Layout page --- Key: MNG-1953 URL: http://jira.codehaus.org/browse/MNG-1953 Project: Maven 2 Type: Bug Components: documentation - introductions Reporter: Stephen Duncan Jr Assignee: Maria Odea Ching Priority: Minor Fix For: documentation Attachments: MNG-1953-documentation-introductions.patch Introduction to the Standard Directory Layout at http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html should add an entry for src/main/webapp as the standard for web app sources. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-55) don't add duplicates to the index
[ http://jira.codehaus.org/browse/MRM-55?page=all ] Maria Odea Ching updated MRM-55: Attachment: MRM-55-maven-repository-indexer.patch don't add duplicates to the index - Key: MRM-55 URL: http://jira.codehaus.org/browse/MRM-55 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-55-maven-repository-indexer.patch currently indexing an artifact that is already in the index will add it again. It should recognise its existence and update the existing record. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-55) don't add duplicates to the index
[ http://jira.codehaus.org/browse/MRM-55?page=all ] Maria Odea Ching updated MRM-55: Attachment: MRM-55-maven-repository-indexer.patch don't add duplicates to the index - Key: MRM-55 URL: http://jira.codehaus.org/browse/MRM-55 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-55-maven-repository-indexer.patch, MRM-55-maven-repository-indexer.patch Time Spent: 9 hours Remaining: 0 minutes currently indexing an artifact that is already in the index will add it again. It should recognise its existence and update the existing record. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-56) ability to delete documents from the index
[ http://jira.codehaus.org/browse/MRM-56?page=all ] Maria Odea Ching updated MRM-56: Attachment: MRM-56-maven-repository-indexer.patch ability to delete documents from the index -- Key: MRM-56 URL: http://jira.codehaus.org/browse/MRM-56 Project: Maven Repository Manager Type: Bug Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-56-maven-repository-indexer.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching closed MRM-35: --- Resolution: Fixed add repository metadata indexer --- Key: MRM-35 URL: http://jira.codehaus.org/browse/MRM-35 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-35-maven-repository-indexer.patch, MRM-35-maven-repository-indexer.patch Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-61) Searcher for metadata index
[ http://jira.codehaus.org/browse/MRM-61?page=all ] Maria Odea Ching closed MRM-61: --- Resolution: Fixed Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assignee: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching updated MRM-35: Attachment: MRM-35-maven-repository-indexer.patch add repository metadata indexer --- Key: MRM-35 URL: http://jira.codehaus.org/browse/MRM-35 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-35-maven-repository-indexer.patch, MRM-35-maven-repository-indexer.patch Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-35) add repository metadata indexer
[ http://jira.codehaus.org/browse/MRM-35?page=all ] Maria Odea Ching updated MRM-35: Attachment: MRM-35-maven-repository-indexer.patch add repository metadata indexer --- Key: MRM-35 URL: http://jira.codehaus.org/browse/MRM-35 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-35-maven-repository-indexer.patch Original Estimate: 8 hours Remaining: 8 hours -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MRM-61) Searcher for metadata index
Searcher for metadata index --- Key: MRM-61 URL: http://jira.codehaus.org/browse/MRM-61 Project: Maven Repository Manager Type: New Feature Reporter: Maria Odea Ching Assigned to: Maria Odea Ching -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-44) search by group, artifact and version
[ http://jira.codehaus.org/browse/MRM-44?page=all ] Maria Odea Ching closed MRM-44: --- Resolution: Fixed The patch file attached also covers issues MRM-45, MRM-48 and MRM-52 search by group, artifact and version - Key: MRM-44 URL: http://jira.codehaus.org/browse/MRM-44 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-44-maven-repository-indexer.patch Time Spent: 2 hours, 30 minutes Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-45) search by class or package name
[ http://jira.codehaus.org/browse/MRM-45?page=all ] Maria Odea Ching closed MRM-45: --- Resolution: Fixed The resolution for this issue is included in the patch file attached to issue MRM-44. search by class or package name --- Key: MRM-45 URL: http://jira.codehaus.org/browse/MRM-45 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 3 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-48) search by checksum
[ http://jira.codehaus.org/browse/MRM-48?page=all ] Maria Odea Ching closed MRM-48: --- Resolution: Fixed The resolution for this issue is included in the patch file attached at issue MRM-44. search by checksum -- Key: MRM-48 URL: http://jira.codehaus.org/browse/MRM-48 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Time Spent: 4 hours Remaining: 0 minutes -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MRM-52) integrate with indexing
[ http://jira.codehaus.org/browse/MRM-52?page=all ] Maria Odea Ching closed MRM-52: --- Resolution: Fixed integrate with indexing --- Key: MRM-52 URL: http://jira.codehaus.org/browse/MRM-52 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MRM-44) search by group, artifact and version
[ http://jira.codehaus.org/browse/MRM-44?page=all ] Maria Odea Ching updated MRM-44: Attachment: MRM-44-maven-repository-indexer.patch search by group, artifact and version - Key: MRM-44 URL: http://jira.codehaus.org/browse/MRM-44 Project: Maven Repository Manager Type: Sub-task Components: indexing Reporter: Brett Porter Assignee: Maria Odea Ching Fix For: 1.0-alpha-1 Attachments: MRM-44-maven-repository-indexer.patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-3) The install plugin fails if there are only attached artifacts.
[ http://jira.codehaus.org/browse/MINSTALL-3?page=all ] Maria Odea Ching moved MNG-1616 to MINSTALL-3: -- Version: (was: 2.0) Fix Version: (was: 2.0.3) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-3 (was: MNG-1616) Project: Maven 2.x Install Plugin (was: Maven 2) The install plugin fails if there are only attached artifacts. Key: MINSTALL-3 URL: http://jira.codehaus.org/browse/MINSTALL-3 Project: Maven 2.x Install Plugin Type: Bug Reporter: Julien S Assignee: John Casey Original Estimate: 2 hours Remaining: 2 hours Usually, classifiers are used to produce attached artifacts, together with the main artifact. In some cases, however, it is not possible to produce the different flavors of the artifacts simultaneously (for example, for a version with debug and without debug). Then, in order to have a single artifact _with_ a classifier, one can configure the jar plugin as follow: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration classifiersomeclassifier/classifier /configuration /plugin However, this cause the install plugin (and probably also the deploy plugin) to fail, because it cannot find the main artifact: [INFO] [jar:jar] [INFO] Building jar: /home/julien/cvs/java/libs/attr/target/libattr-3.0-nodebug.jar [INFO] [install:install] [INFO] Installing /home/julien/cvs/java/libs/attr/target/classes to /home/julien/.m2/repository/unicity/libattr/3.0/libattr-3.0.jar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-4) install:install-file makes reactor parse subprojects
[ http://jira.codehaus.org/browse/MINSTALL-4?page=all ] Maria Odea Ching moved MNG-1114 to MINSTALL-4: -- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0 (RC)) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-4 (was: MNG-1114) Project: Maven 2.x Install Plugin (was: Maven 2) install:install-file makes reactor parse subprojects Key: MINSTALL-4 URL: http://jira.codehaus.org/browse/MINSTALL-4 Project: Maven 2.x Install Plugin Type: Bug Reporter: Yann Le Du Assignee: Brett Porter Priority: Trivial When you execute m2 install:install-file -DgroupId=jdbc -DartifactId=jdbc -Dversion=2.0 -Dpackaging=jar -Dfile=/home/maven/repository-manual/jdbc/jdbc/2.0/jdbc-2.0.jar in a parent project, the reactor executes it again in every subproject. Harmless, but unexpected. Maybe somehow related to MNG-432 ? -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-6) Add ability to generate a basic pom when installing a file.
[ http://jira.codehaus.org/browse/MINSTALL-6?page=all ] Maria Odea Ching moved MNG-1279 to MINSTALL-6: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-6 (was: MNG-1279) Project: Maven 2.x Install Plugin (was: Maven 2) Add ability to generate a basic pom when installing a file. --- Key: MINSTALL-6 URL: http://jira.codehaus.org/browse/MINSTALL-6 Project: Maven 2.x Install Plugin Type: New Feature Reporter: Philipp Meier Assignee: Brett Porter Attachments: generatePom.patch, install-file-fix.patch It's desireable to generate a basic pom for a library installed with install:install-file. The attached patch adds the parameter generatePom to the install:install-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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-1) Install plugin installs a jar to repository with default name, even if name is overridden
[ http://jira.codehaus.org/browse/MINSTALL-1?page=all ]
Maria Odea Ching moved MNG-1657 to MINSTALL-1:
--
Version: (was: 2.0)
Component: (was: maven-install-plugin)
Workflow: jira (was: Maven)
Key: MINSTALL-1 (was: MNG-1657)
Project: Maven 2.x Install Plugin (was: Maven 2)
Install plugin installs a jar to repository with default name, even if name
is overridden
-
Key: MINSTALL-1
URL: http://jira.codehaus.org/browse/MINSTALL-1
Project: Maven 2.x Install Plugin
Type: Bug
Environment: winxp
Reporter: ruel loehr
Assignee: Brett Porter
When using the install plugin to install a jar to the repository, the default
name of the jar is used, even if the name is overridden. Also, if you
define your own type via a plugin ('myjar'), when installing, it will be
installed as 'myjar'. This should be overrideable otherwise it is impossible
for a user to override the default type plugins.
[INFO] [jar:jar]
[INFO] Building jar:
c:\projects\maven-jboss-head\jboss-head\common\namespace\ta
rget\testnamespace.doodad.jar.jar
[INFO] [install:install]
[INFO] Installing
c:\projects\maven-jboss-head\jboss-head\common\namespace\targe
t\testnamespace.doodad.jar.jar to C:\Documents and
Settings\ruel\.m2\repository\
org\jboss\server\common\namespace\namespace\5.0-SNAPSHOT\namespace-5.0-SNAPSHOT.
jar
[INFO]
-
This is pretty easy to reproduce all you have to do is give a finalName and
run the install plugin:
project
modelVersion4.0.0/modelVersion
groupIdorg.jboss.server.common.namespace/groupId
artifactIdnamespace/artifactId
packagingjar/packaging
version5.0-SNAPSHOT/version
nameJBoss-Common - namespace/name
parent
groupIdorg.jboss.server.common/groupId
artifactIdproject.common/artifactId
version5.0-SNAPSHOT/version
/parent
build
finalNametestnamespace.doodad.jar/finalName
/build
/project
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-5) non originality pom.xml on install or deploy
[ http://jira.codehaus.org/browse/MINSTALL-5?page=all ]
Maria Odea Ching moved MNG-1714 to MINSTALL-5:
--
Version: (was: 2.0)
Component: (was: maven-install-plugin)
Workflow: jira (was: Maven)
Key: MINSTALL-5 (was: MNG-1714)
Project: Maven 2.x Install Plugin (was: Maven 2)
non originality pom.xml on install or deploy
Key: MINSTALL-5
URL: http://jira.codehaus.org/browse/MINSTALL-5
Project: Maven 2.x Install Plugin
Type: Bug
Environment: windown 2000
Reporter: pinghe
Priority: Critical
Attachments: maven.error.png
for example my-test-plugin.
pom.xml:
project
modelVersion4.0.0/modelVersion
groupIdmy.test/groupId
artifactIdmytest-plugin-parent/artifactId
packagingpom/packaging
version${my.project.version}/version
urlhttp://${my.project.site.ip}/projects/mytest/url
properties
my.project.site.ip10.0.0.1/my.project.site.ip
my.project.version1.0/my.project.version
/properties
/project
-
installed.
mytest-plugin-parent-1.0.pom :
project
modelVersion4.0.0/modelVersion
groupIdmy.test/groupId
artifactIdmytest-plugin-parent/artifactId
packagingpom/packaging
version${my.project.version}/version ---without
replace
urlhttp://${my.project.site.ip}/projects/mytest/url
--- without replace
properties
my.project.site.ip10.0.0.1/my.project.site.ip
my.project.version1.0/my.project.version
/properties
/project
should similarity exported-pom.xml content.
version1.0/version ---replace
urlhttp://10.0.0.1/projects/mytest/url --- replace
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-2) Install-file zeros file if the source file is the target file.
[ http://jira.codehaus.org/browse/MINSTALL-2?page=all ] Maria Odea Ching moved MNG-1322 to MINSTALL-2: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-2 (was: MNG-1322) Project: Maven 2.x Install Plugin (was: Maven 2) Install-file zeros file if the source file is the target file. -- Key: MINSTALL-2 URL: http://jira.codehaus.org/browse/MINSTALL-2 Project: Maven 2.x Install Plugin Type: Bug Environment: linux 2.6.12, sun j2sdk 1.5.0_02-b09 Reporter: Philipp Meier Assignee: John Casey Attachments: MNG-1322-maven-install-plugin.patch Original Estimate: 2 hours Time Spent: 40 minutes Remaining: 0 minutes If the install plugins tries to install a file from the local repository to the same locate it overwrites this one with a zero bytes version. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-8) option on install-file to generate a skeleton pom
[ http://jira.codehaus.org/browse/MINSTALL-8?page=all ] Maria Odea Ching moved MNG-1407 to MINSTALL-8: -- Version: (was: 2.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-8 (was: MNG-1407) Project: Maven 2.x Install Plugin (was: Maven 2) option on install-file to generate a skeleton pom - Key: MINSTALL-8 URL: http://jira.codehaus.org/browse/MINSTALL-8 Project: Maven 2.x Install Plugin Type: Improvement Reporter: Matthew Pocock Assignee: Brett Porter Priority: Minor Sometimes I need to add jars to my local repo using something like: mvn install:install-file -Dfile=.. -DartifactId=.. -DgroupId=... -Dversion=... -Dtype=jar This doesn't generate a pom, which can cause trixinesses. Could we have a -DgeneratePom=true option that writes a skeleton pom in for the artifact? it would default 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MINSTALL-7) Add a parameter to install a custom pom when using install:install-file
[ http://jira.codehaus.org/browse/MINSTALL-7?page=all ] Maria Odea Ching moved MNG-1647 to MINSTALL-7: -- Fix Version: (was: 2.0.1) Component: (was: maven-install-plugin) Workflow: jira (was: Maven) Key: MINSTALL-7 (was: MNG-1647) Project: Maven 2.x Install Plugin (was: Maven 2) Add a parameter to install a custom pom when using install:install-file --- Key: MINSTALL-7 URL: http://jira.codehaus.org/browse/MINSTALL-7 Project: Maven 2.x Install Plugin Type: Improvement Reporter: David Jackman Assignee: Allan Ramirez Priority: Minor Right now, I can install a 3rd party artifact to my repository using install:install-file then, in a separate command, install a custom pom for that artifact using install:install-file again with packaging set to pom and the file parameter pointing to my custom pom file. Since I can do this with two commands successfully, I made this a minor priority issue. It would be nice if the install:install-file goal took an additional parameter referencing my custom pom file and installed it at the same time. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-1) Manifest generation problems caused by valid POM information
[ http://jira.codehaus.org/browse/MJAR-1?page=all ] Maria Odea Ching moved MNG-1558 to MJAR-1: -- Version: (was: 2.0) Fix Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-1 (was: MNG-1558) Project: Maven 2.x Jar Plugin (was: Maven 2) Manifest generation problems caused by valid POM information Key: MJAR-1 URL: http://jira.codehaus.org/browse/MJAR-1 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Bob Allison Assignee: John Casey Attachments: MNG-1558-plexus-archiver.patch It looks like we have some problems with the contents of manifests in jar files. According to Sun's documentation (http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are three basic formatting rules which are not always being enforced: 1) All text must be UTF-8 2) Lines are limited to 72 characters; longer lines must be continued 3) Sections are divided by blank lines Where are these rules being violated? The first rule can be violated by any POM which is in a character set other than UTF-8. The last two rules can be violated by any POM value which spans multiple lines. Both of these are potential problems since a number of POM values go directly into the manifest without sufficient checking. Example: The plugin I have been working on suddenly stopped working. It stopped when I added a two-line description to the POM. I have been able to determine that converting the second line of the description into a proper manifest continuation line fixed the problem. As it turns out, the class loader was ignoring the jar; this created an error where the name of the Mojo class was found but the class could not be loaded. Workarounds for the present: -- Any POM fields which end up in a jar manifest needs to be limited to UTF-8 characters. -- Multi-line values should be constructed so that all lines start with a space character (not strictly required for the first line but it doesn't hurt). -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-3) LICENSE.txt no longer saved in META-INF
[ http://jira.codehaus.org/browse/MJAR-3?page=all ] Maria Odea Ching moved MNG-1615 to MJAR-3: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-3 (was: MNG-1615) Project: Maven 2.x Jar Plugin (was: Maven 2) LICENSE.txt no longer saved in META-INF --- Key: MJAR-3 URL: http://jira.codehaus.org/browse/MJAR-3 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Joerg Schaible Priority: Minor The M1 jar plugin copied the LICENSE.txt file into the MTEA-INF folder of the resulting artifact. The jar plugin for M2 does this no longer. It should be at least configurable. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-8) Maven creates jar for a project without java sources
[ http://jira.codehaus.org/browse/MJAR-8?page=all ] Maria Odea Ching moved MNG-1449 to MJAR-8: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-8 (was: MNG-1449) Project: Maven 2.x Jar Plugin (was: Maven 2) Maven creates jar for a project without java sources Key: MJAR-8 URL: http://jira.codehaus.org/browse/MJAR-8 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Giorgio Gallo Assignee: Brett Porter Priority: Minor Attachments: MNG-1449.zip A jar file is generated even for projects with no java sources (ie: no src/main/java directory) - this creates some problems with the current assembly implementation, since an horrible near-empty jar gets into the assembly. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-12) Missing support for adding sections to the manifest at build time
[ http://jira.codehaus.org/browse/MJAR-12?page=all ] Maria Odea Ching moved MNG-1202 to MJAR-12: --- Version: (was: 2.0 (RC)) Fix Version: (was: 2.0 (RC)) Component: (was: maven-jar-plugin) (was: maven-archiver) Workflow: jira (was: Maven) Key: MJAR-12 (was: MNG-1202) Project: Maven 2.x Jar Plugin (was: Maven 2) Missing support for adding sections to the manifest at build time - Key: MJAR-12 URL: http://jira.codehaus.org/browse/MJAR-12 Project: Maven 2.x Jar Plugin Type: Improvement Environment: Windows XP SP2 Java J2SE 1.4.2_08 Reporter: Mark Russell Assignee: Brett Porter Priority: Minor Attachments: ManifestSectionSupportChanges.zip Currently it is not possible to add additional sections to the manifest by configuring the maven-jar-plugin through the configuration section in the pom.xml. You can only add attributes to the main section using the manifestEntries tag.. Example... It is currently not possible to generate the manifest shown here: Manifest-Version: 1.0 Archiver-Version: Plexus Archiver Created-By: Apache Maven Built-By: RUSM01 Package: org.com.foo.app Build-Jdk: 1.4.2_08 Extension-Name: my-app Specification-Vendor: MyCompany Inc Implementation-Vendor: MyCompany Inc Implementation-Title: my-app Implementation-Version: 1.0-SNAPSHOT Main-Class: org.com.foo.App mode: development url: http://maven.apache.org Name: SampleSectionNumberOne mode: development url: http://maven.apache.org Name: SampleSectionNumberTwo mode: development url: http://maven.apache.org Current workaround: Define the manifest in a seperate file and configure the maven-jar-plugin to use the file for the manifest. Attached to this defect is a zip file containing a potential fix. The zip file contains the changed version of the MavenArchiveConfiguration.java and MavenArchiver.java files, along with a patch file to update the originals. Additionally a new class was needed and is found in the ManifestSection.java file included in the zip. Last, a pom.xml example that shows how the feature would be 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-7) jar plugin recreates jar files all the time
[ http://jira.codehaus.org/browse/MJAR-7?page=all ] Maria Odea Ching moved MNG-1838 to MJAR-7: -- Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-7 (was: MNG-1838) Project: Maven 2.x Jar Plugin (was: Maven 2) jar plugin recreates jar files all the time --- Key: MJAR-7 URL: http://jira.codehaus.org/browse/MJAR-7 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Jochen Wiedmann The jar plugin doesn't seem to check, whether rebuilding a jar file is actually required. For daily work, it would be faster to do what Ant's jar task does: Compare the timestamps of the input files with the timestamp of the target file. While this approach has the obvious advantage of being safe (and thus possibly well choosen as a default), it is not appropriate for large projects, where a single build requires a real lot of jar files being rebuilt, even if only a single source file has been changed. This applies, in particular, because comparable plugins like the war, ear, and assembly plugin are forced to behave in the same manner. Suggestion: - Introduce a new property, for example maven.build.force. The main idea of the property would be, that other plugins (install, war, assembly, ...) would listen to the same property. While they would possible ignore it initially, one could add support later on. - The default property value would be true. - If the property value is set to false, then the jar plugin compares the timestamps of the input files with the timestamp of the output file. If the latter is newer than the input timestamps, then the jar file isn't being rebuilt. I am ready to provide a patch, if my suggestion should find interest. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-10) dealing with licenses
[ http://jira.codehaus.org/browse/MJAR-10?page=all ] Maria Odea Ching moved MNG-1331 to MJAR-10: --- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-10 (was: MNG-1331) Project: Maven 2.x Jar Plugin (was: Maven 2) dealing with licenses - Key: MJAR-10 URL: http://jira.codehaus.org/browse/MJAR-10 Project: Maven 2.x Jar Plugin Type: New Feature Reporter: Jorg Heymans Priority: Minor maven could offer a configurable way to include project licenses in the jar, briefly discussed on IRC today jorgdoes m2 have anything built-in to deal with library licenses ? just wondering ... kenney license tag in the pom is all I think jorgah yep, i knew I saw something about it somewhere, tnx kenney kenney and just distribute poms for non-freely-distributable jars (like the sun ones), stating where you can download/purchase them jorgmmm Typically the licenses listed for the project are that of the project itself, and not of dependencies. jorgok so unless all our dependencies are good maven citizens this won't really work ... jorgno prob, we'll just include them ourselves then kenney do you have to? kenney if people distribute a jar/pom without a license, it's their fault jorgwell we (cocoon) have always done so jorgthat's true though , it's up to them to include them trygvis I think people are a bit slack when it comes to adding that information jorgdefinitely kenney what about the bundle upload system? jorgthat's why i was hoping for maven to be able enforce something trygvis we should probably start to enumerate the various licenses and give them IDs instead kenney bundles have to have a LICENSE file.. where does that go? trygvis not sure, ask carlos kenney yeah or maybe extend the license tag to name the license (ASL-2.0) and the online-url, or alternatively list the license content itself.. or just add a bla-X-LICENSE.txt on ibiblio per project jorgsomething like that yeah, and perhaps offering a configurable way of having the license file included in the jar ? jorgor is that a hairy legal thing maven shouldn't get into ? trygvis kenney: the name there (ASL-2.0) would be the id trygvis jorg: good idea jorgit would certainly advocate , albeit rather enforced, correct usage of libraries -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-9) Support jar signing.
[ http://jira.codehaus.org/browse/MJAR-9?page=all ] Maria Odea Ching moved MNG-1130 to MJAR-9: -- Version: (was: 2.0-beta-3) Fix Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-9 (was: MNG-1130) Project: Maven 2.x Jar Plugin (was: Maven 2) Support jar signing. Key: MJAR-9 URL: http://jira.codehaus.org/browse/MJAR-9 Project: Maven 2.x Jar Plugin Type: New Feature Environment: gentoo linux, jdk 1.4.2_06 Reporter: Corridor Software Developer Assignee: Brett Porter Attachments: MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130-jar-sign.diff, MNG-1130_jar-sign-verify.diff, MNG-1130_jar-sign-verify.diff, MNG-1130_jar-sign-verify.diff, jar-sign-verify.diff, mng-1130.tar.gz The Java webstart framework requires that jars used by a webstart application be signed. Create a new goal on the maven jar plugin called jar:sign. The goal would take a keystore file as input and sign the project artifact prior to installing it to the local repository or deploying it to the repo. The plugin should also allow a specific dependency or dependencies, as well as it's runtime dependencies to be signed. This functionality is required prior to finishing the webstart-maven-plugin. Two example test projects will be attached to the ticket shortly. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-6) dependencies woth scope test are included in Extension-List of the manifest
[ http://jira.codehaus.org/browse/MJAR-6?page=all ] Maria Odea Ching moved MNG-1821 to MJAR-6: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-6 (was: MNG-1821) Project: Maven 2.x Jar Plugin (was: Maven 2) dependencies woth scope test are included in Extension-List of the manifest - Key: MJAR-6 URL: http://jira.codehaus.org/browse/MJAR-6 Project: Maven 2.x Jar Plugin Type: Bug Environment: Any Reporter: Pascal Grange When activating the Extension-List generation for the jar-plugin : build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration manifest addExtensionstrue/addExtensions /manifest ... Event the dependencies that have only a test scope such as junit, for instance, are included in the manifest. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-11) extention parametrization
[ http://jira.codehaus.org/browse/MJAR-11?page=all ] Maria Odea Ching moved MNG-1654 to MJAR-11: --- Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-11 (was: MNG-1654) Project: Maven 2.x Jar Plugin (was: Maven 2) extention parametrization - Key: MJAR-11 URL: http://jira.codehaus.org/browse/MJAR-11 Project: Maven 2.x Jar Plugin Type: Improvement Reporter: Dmitry Tsigelnik Please add parametrization of extention of building file. For example: I want to build ejb3 file or another archive special for concreate Jboss deployer likes .har or .spring -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-5) no Implementation-Vendor-Id in META-INF/MANIFEST.MF
[ http://jira.codehaus.org/browse/MJAR-5?page=all ] Maria Odea Ching moved MNG-1794 to MJAR-5: -- Version: (was: 2.0) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-5 (was: MNG-1794) Project: Maven 2.x Jar Plugin (was: Maven 2) no Implementation-Vendor-Id in META-INF/MANIFEST.MF --- Key: MJAR-5 URL: http://jira.codehaus.org/browse/MJAR-5 Project: Maven 2.x Jar Plugin Type: Bug Environment: Linux 2.6.12-9-386 Kubuntu java version 1.4.2-02 Reporter: Pascal Grange Priority: Blocker mvn package does not generate an entry Implementation-Vendor-Id. This is a blocker when we use the extension mechanisme with tomcat. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-2) Output goes to the console because maven/plexus-archiver are not use as components
[ http://jira.codehaus.org/browse/MJAR-2?page=all ] Maria Odea Ching moved MNG-1071 to MJAR-2: -- Version: (was: 2.0-alpha-3) Fix Version: (was: 2.0-beta-3) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-2 (was: MNG-1071) Project: Maven 2.x Jar Plugin (was: Maven 2) Output goes to the console because maven/plexus-archiver are not use as components -- Key: MJAR-2 URL: http://jira.codehaus.org/browse/MJAR-2 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Jason van Zyl Assignee: Emmanuel Venisse Because the maven/plexus-archivers are instantiated directly they use some code that creates a console logger and will not have a logger handed to it from the logger manager that all the other components use. This creates inconsistent logging from maven-embedder where I'm trying to capture all logging in one place. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-4) Multiline description provides invalid header in the generated jar files
[ http://jira.codehaus.org/browse/MJAR-4?page=all ] Maria Odea Ching moved MNG-1869 to MJAR-4: -- Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-4 (was: MNG-1869) Project: Maven 2.x Jar Plugin (was: Maven 2) Multiline description provides invalid header in the generated jar files - Key: MJAR-4 URL: http://jira.codehaus.org/browse/MJAR-4 Project: Maven 2.x Jar Plugin Type: Bug Reporter: Gilles Scokart When a description text is written on more than 1 line, the produced Manifest files are invalid. Indeed one of the header of this manifiest contains the description text as is. When the jar is loaded, we receive an error saying invalid headers. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-15) Excluding pom.properties and pom.xml from produced artifact
[ http://jira.codehaus.org/browse/MJAR-15?page=all ] Maria Odea Ching moved MNG-1520 to MJAR-15: --- Fix Version: (was: 2.0.1) Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-15 (was: MNG-1520) Project: Maven 2.x Jar Plugin (was: Maven 2) Excluding pom.properties and pom.xml from produced artifact Key: MJAR-15 URL: http://jira.codehaus.org/browse/MJAR-15 Project: Maven 2.x Jar Plugin Type: Wish Reporter: Anuerin Diaz Assignee: Allan Ramirez Original Estimate: 1 hour Time Spent: 30 minutes Remaining: 30 minutes Although the files are supposed to be used in capturing as much build information as necessary, they are considered to be a security risk in some situations. There must be a way to exclude these files even during development packaging. The released Maven plugins do not contain these files so there is a way to remove them. The following configuration do not work when added to the project descriptor: plugin artifactIdmaven-jar-plugin/artifactId configuration excludes**/pom.*/excludes /configuration /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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-13) configure test-jar to include only special classes of the test source
[ http://jira.codehaus.org/browse/MJAR-13?page=all ] Maria Odea Ching moved MNG-1674 to MJAR-13: --- Component: (was: maven-jar-plugin) Workflow: jira (was: Maven) Key: MJAR-13 (was: MNG-1674) Project: Maven 2.x Jar Plugin (was: Maven 2) configure test-jar to include only special classes of the test source - Key: MJAR-13 URL: http://jira.codehaus.org/browse/MJAR-13 Project: Maven 2.x Jar Plugin Type: Improvement Reporter: Joerg Schaible Priority: Minor The test-jar currently contains all test classes, but often you just want to share only some parts of it, e.g. a specialized abstract TestCase or a test toolkit or some mock classes, but not the complete unit test for an asrtifact. The plugin configuration shoulds contain a section with an includes/excludes pattern set. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAR-14) pom.xml information automatically included in META-INF during jar
[ http://jira.codehaus.org/browse/MJAR-14?page=all ]
Maria Odea Ching moved MNG-1543 to MJAR-14:
---
Version: (was: 2.0)
Fix Version: (was: 2.0.3)
Component: (was: maven-jar-plugin)
Workflow: jira (was: Maven)
Key: MJAR-14 (was: MNG-1543)
Project: Maven 2.x Jar Plugin (was: Maven 2)
pom.xml information automatically included in META-INF during jar
--
Key: MJAR-14
URL: http://jira.codehaus.org/browse/MJAR-14
Project: Maven 2.x Jar Plugin
Type: Improvement
Reporter: Jorg Heymans
Assignee: John Casey
Attachments: MNG-1543-maven-archiver.patch
The jar plugin automatically adds a pom.xml in META-INF, which makes sense.
But this pom.xml also contains local paths ie
build
sourceDirectoryd:\src\excalibur-trunk\framework\api\src\java/sourceDirectory
scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory
testSourceDirectoryd:\src\excalibur-trunk\framework\api\src\test/testSourceDirectory
outputDirectoryd:\src\excalibur-trunk\framework\api\target\classes/outputDirectory
testOutputDirectoryd:\src\excalibur-trunk\framework\api\target\test-classes/testOutputDirectory
resources
resource
targetPathMETA-INF/targetPath
directoryd:\src\excalibur-trunk\framework\api\..\../directory
includes
includeLICENSE.txt/include
includeNOTICE.txt/include
/includes
/resource
/resources
testResources
testResource
directoryd:\src\excalibur-trunk\framework\api\src\test\resources/directory
I don't see how this information could be useful to anyone else, and i'ld
rather not have my local paths in distribution jars - call me paranoid :)
Conversation log from IRC :
jorgis there a way to tell maven not to include the pom.xml in
META-INF when creating jars ?
jesse hm, not that I know of
jesse might be a boolean to control it in there somewhere
jorgi looked at the jar plugin config .. didn't seem like it
jorgit's not a real problem, just funny that this is done by default
jesse I don't know, it makes it easier down the road to have
automated things interrogate the jar for dependencies of the things inside
trygvis yeah, you're right there jesse
jorgmmm well yes that makes sense ...
jorgthanks !
trygvis jorg: it's useful for the application itself
trygvis like reading out the version number from pom.properties
jorgtrygvis: yes, but the pom also had my local paths in it for
sourceDirectory and stuff, that's why i found it a bit strange
trygvis makes it easier making versioning-aware application and gives a
thigh integration with your project management tool (aka maven)
trygvis hm
trygvis that should possibly be changed indeed
trygvis File properties should be made relative to ${basedir} again
trygvis when writing out the pom that is
jorgi can understand about the dependencies , but the build
configuration probably shouldn't be in there
jorg
directoryd:\src\excalibur-trunk\framework\api\..\../directory
trygvis jorg: file an issue, it should be relative to ${basedir} if
there at all
trygvis IMO the build parts of a pom could be stripped from the repo
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-1) site-embedded report mode check always returns true
[ http://jira.codehaus.org/browse/MJAVADOC-1?page=all ] Maria Odea Ching moved MNG-1510 to MJAVADOC-1: -- Version: (was: 2.0) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-1 (was: MNG-1510) Project: Maven 2.x Javadoc Plugin (was: Maven 2) site-embedded report mode check always returns true --- Key: MJAVADOC-1 URL: http://jira.codehaus.org/browse/MJAVADOC-1 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Shinobu Kawai Yoshida Assignee: Allan Ramirez Attachments: MNG-1510.patch o.a.m.p.javadoc.JavadocReport#executeReport Line 685: if ( !javadocDirectory.equals( getOutputDirectory() ) ) javadocDirectory is a File and getOutputDirectory() is a String. This will never return 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-3) plugin should honor proxy settings
[ http://jira.codehaus.org/browse/MJAVADOC-3?page=all ] Maria Odea Ching moved MNG-1829 to MJAVADOC-3: -- Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-3 (was: MNG-1829) Project: Maven 2.x Javadoc Plugin (was: Maven 2) plugin should honor proxy settings -- Key: MJAVADOC-3 URL: http://jira.codehaus.org/browse/MJAVADOC-3 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: tested on Linux/Windows Reporter: Dirk Olmes Priority: Minor The maven2 plugin should honor the proxy settings. When specifying the link option, the forked javadoc process always tries to fetch the package-list directly. This fails on corporate networks, where all web access has to go through a proxy. I've tried to specify a proxy by using the additionalparam option but this does not work because all parameters for the javadoc process are written to an options file, which is passed to the forked javadoc process. By the time the javadoc process gets to see the arguments, it is already running so all VM parameters (-J-Dhttp.proxyHost...) cause errors. The most seamless integration would be to pass whatever proxy is configured to the forked javadoc process. Configuration options for specifying the proxy for the javadoc-plugin would be acceptable, too. -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-8) group parameter seems hard to use
[ http://jira.codehaus.org/browse/MJAVADOC-8?page=all ] Maria Odea Ching moved MNG-1154 to MJAVADOC-8: -- Version: (was: 2.0-beta-3) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-8 (was: MNG-1154) Project: Maven 2.x Javadoc Plugin (was: Maven 2) group parameter seems hard to use --- Key: MJAVADOC-8 URL: http://jira.codehaus.org/browse/MJAVADOC-8 Project: Maven 2.x Javadoc Plugin Type: Bug Environment: Windows XP Reporter: Martin Desruisseaux Priority: Minor The group parameter is a comma-separated list. A looks into the source code suggest that the plugin uses StringTokenizer for splitting the String around comas, no matter if the coma were inside quotes or not. Next, the tokens are put between quotes if they contains spaces. This means that the following parameter: group Feature Geometry org.geotools.geometry* /group is translated into the following javadoc options: -group Feature Geometry org.geotools.geometry* when it should has been: -group Feature Geometry org.geotools.geometry* Putting Feature Geometry between quotes in the group parameter doesn't help (it produces an other unexpected result). We really need a space between the title and the packages; it is part of javadoc tools specification, and current maven-javadoc-plugin seems to prevent that. Furthermore, because of the coma-delimited nature of the group argument, we can't put coma in group title. I would like to suggest to replace the current group parameter syntax by the same one than Ant: group title=Feature Geometry packages=org.geotools.geometry*/ -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-5) Sending wrong parameters to -bottom
[ http://jira.codehaus.org/browse/MJAVADOC-5?page=all ]
Maria Odea Ching moved MNG-1029 to MJAVADOC-5:
--
Version: (was: 2.0-beta-2)
Fix Version: (was: 2.0-beta-2)
Component: (was: maven-javadoc-plugin)
Workflow: jira (was: Maven)
Key: MJAVADOC-5 (was: MNG-1029)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
Sending wrong parameters to -bottom
---
Key: MJAVADOC-5
URL: http://jira.codehaus.org/browse/MJAVADOC-5
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Matthew Beermann
Assignee: Brett Porter
Priority: Minor
My POM has inceptionYear2004/inceptionYear, yet the generated Javadoc has
the following footer: Copyright null MyTeamName. All Rights Reserved.
It could have something to do with the stated default for the plugin's
bottom parameter: Copyright ${project.inceptionYear-currentYear}
${project.organization.name}. All Rights Reserved. I could be imagining it,
but doesn't the dash belong outside the braces?
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-7) The project name can't have any spaces
[ http://jira.codehaus.org/browse/MJAVADOC-7?page=all ]
Maria Odea Ching moved MNG-1389 to MJAVADOC-7:
--
Component: (was: maven-javadoc-plugin)
Workflow: jira (was: Maven)
Key: MJAVADOC-7 (was: MNG-1389)
Project: Maven 2.x Javadoc Plugin (was: Maven 2)
The project name can't have any spaces
--
Key: MJAVADOC-7
URL: http://jira.codehaus.org/browse/MJAVADOC-7
Project: Maven 2.x Javadoc Plugin
Type: Bug
Reporter: Alexandre Poitras
If you put space in your project name in your pom.xml file, there is an error
during the javadoc generation.
In my opinion, it looks like the plugin doesn't use string quotes on the
javadoc command line for the doctitle argument, wich default value is
${project.name} ${project.version} API.
--
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
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Moved: (MJAVADOC-10) Javadoc report does not honor site directory when run from site:site
[ http://jira.codehaus.org/browse/MJAVADOC-10?page=all ] Maria Odea Ching moved MNG-873 to MJAVADOC-10: -- Version: (was: 2.0-beta-1) Fix Version: (was: 2.0-beta-1) Component: (was: maven-javadoc-plugin) Workflow: jira (was: Maven) Key: MJAVADOC-10 (was: MNG-873) Project: Maven 2.x Javadoc Plugin (was: Maven 2) Javadoc report does not honor site directory when run from site:site Key: MJAVADOC-10 URL: http://jira.codehaus.org/browse/MJAVADOC-10 Project: Maven 2.x Javadoc Plugin Type: Bug Reporter: Kenney Westerhof Assignee: Kenney Westerhof -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
