You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Alexandre Poitras (JIRA)" <ji...@codehaus.org> on 2005/11/01 23:56:45 UTC
[jira] Created: (MPJAVADOC-63) The project name can't have any spaces
The project name can't have any spaces
--------------------------------------
Key: MPJAVADOC-63
URL: http://jira.codehaus.org/browse/MPJAVADOC-63
Project: maven-javadoc-plugin
Type: Bug
Versions: 1.7
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
RE: JIRA
Posted by Arnaud HERITIER <ah...@gmail.com>.
>
> Hi,
Hi,
>
> Two questions about JIRA:
>
> - I notice an increasing number of people opening issues
> under m1 plugins that are really m2 issues. Is there a way to
> make it clearer that, eg MPJAVADOC, is for javadoc _m1_
> plugin only? Btw, there is no 'How do I report a bug?'
> section in the FAQ of the m2 site, like there is in m1.
Jason, do you have the time to document it ?
Do you want we submit a patch ?
>
> - It also happens (not that often though) that users file
> duplicate issues or ask on the list about already fixed
> issues, because it's closed on JIRA but not yet released.
> What would be the easiest, quickest, safest way for a user to
> find out which issues have been fixed in the current
> development version? Check the roadmap on JIRA? The changes
> report (requires we republish the site for every fix)? The
> latest SNAPSHOT (requires we publish a SNAPSHOT for every fix)?
I think that it is not a good think to update the documentation about plugins each time we publish a snapshot because it will
confuse users.
Even if we did it recently I prefer we keep online the documentation for the last release.
But we can (what i often do) publish the documentation on the staging site.
Maybe it could be a good idea to have a real site as a staging site (http://staging.maven.apache.org ??) and not brett's account.
Concerning the changes I prefer that users take a look at the roadmap.
Personnaly when I have a bug, I search on Jira to see if there's a bug report and if I found one closed I try to get the release or
the snapshot which fix it.
Perhaps it's not well documented for beginners. But it's not maven specific. It's how to work with external projects (from
opensource or editors).
Arnaud
>
> Any thoughts?
>
> Cheers,
> Lukas
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For
> additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
JIRA
Posted by Lukas Theussl <lt...@apache.org>.
Hi,
Two questions about JIRA:
- I notice an increasing number of people opening issues under m1
plugins that are really m2 issues. Is there a way to make it clearer
that, eg MPJAVADOC, is for javadoc _m1_ plugin only? Btw, there is no
'How do I report a bug?' section in the FAQ of the m2 site, like there
is in m1.
- It also happens (not that often though) that users file duplicate
issues or ask on the list about already fixed issues, because it's
closed on JIRA but not yet released. What would be the easiest,
quickest, safest way for a user to find out which issues have been fixed
in the current development version? Check the roadmap on JIRA? The
changes report (requires we republish the site for every fix)? The
latest SNAPSHOT (requires we publish a SNAPSHOT for every fix)?
Any thoughts?
Cheers,
Lukas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-1389) The project name can't have any spaces
Posted by "Alexandre Poitras (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1389?page=comments#action_49917 ]
Alexandre Poitras commented on MNG-1389:
----------------------------------------
Sorry, the problem is not with spaces but with having quotes.
> The project name can't have any spaces
> --------------------------------------
>
> Key: MNG-1389
> URL: http://jira.codehaus.org/browse/MNG-1389
> Project: Maven 2
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-1389) The project name can't have any spaces
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-1389?page=all ]
Brett Porter updated MNG-1389:
------------------------------
Description:
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".
was:
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".
Component: maven-javadoc-plugin
Environment:
> The project name can't have any spaces
> --------------------------------------
>
> Key: MNG-1389
> URL: http://jira.codehaus.org/browse/MNG-1389
> Project: Maven 2
> Type: Bug
> Components: maven-javadoc-plugin
> 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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MJAVADOC-7) The project name can't have quotes
Posted by "Mike Perham (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-7?page=all ]
Mike Perham updated MJAVADOC-7:
-------------------------------
Priority: Trivial (was: Major)
Description: If you put a single quote in your project name in your pom.xml file, there is an error during the javadoc generation. (was: 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".)
Summary: The project name can't have quotes (was: The project name can't have any spaces)
> The project name can't have quotes
> ----------------------------------
>
> Key: MJAVADOC-7
> URL: http://jira.codehaus.org/browse/MJAVADOC-7
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Reporter: Alexandre Poitras
> Priority: Trivial
>
>
> If you put a single quote in your project name in your pom.xml file, there is an error during the javadoc generation.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MJAVADOC-7) The project name can't have quotes
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MJAVADOC-7?page=all ]
Brett Porter closed MJAVADOC-7:
-------------------------------
Assign To: Brett Porter
Resolution: Duplicate
> The project name can't have quotes
> ----------------------------------
>
> Key: MJAVADOC-7
> URL: http://jira.codehaus.org/browse/MJAVADOC-7
> Project: Maven 2.x Javadoc Plugin
> Type: Bug
> Reporter: Alexandre Poitras
> Assignee: Brett Porter
> Priority: Trivial
>
>
> If you put a single quote in your project name in your pom.xml file, there is an error during the javadoc generation.
--
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: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org