You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gary Kind (JIRA)" <de...@myfaces.apache.org> on 2008/01/11 19:09:34 UTC
[jira] Created: (TRINIDAD-893) Added 3 new parameters to the
maven-jdev-plugin.
Added 3 new parameters to the maven-jdev-plugin.
------------------------------------------------
Key: TRINIDAD-893
URL: https://issues.apache.org/jira/browse/TRINIDAD-893
Project: MyFaces Trinidad
Issue Type: Improvement
Reporter: Gary Kind
Attachments: maven-jdev-plugin2.patch
1. Added 3 new parameters the jdev:jdev goal:
* compiler: so that the default compiler (which is Ojc) can be changed to Javac
* makeProject: so that the "Make Project" checkbox can be checked and a project will compile before run. The default is "false".
* runTarget: set the default run target so it does not have to be manually. This is particularly useful for adf-richclient-test
2. Changed it so that libraries specified in a pom file will be added to the default libraries, JSP Runtime & JSF 1.2. In the current version, if you wanted to add libraries in your pom file, you would have to also include these default libraries in your list. I did not like this, so I changed it.
3. As part of my project to fully document our plugins, I went through all of the parameters and documented them so that meaningful plugin documentation is generated for the maven-jdev-plugin. I ran 'mvn site:site' on trinidad-maven/trunk so see what kind of documentation would get generated. The maven-jdev-plugin now looks great and one can actually get some useful information out of it. I also went on the internet and was able to find the current documentation at . This documentation gets generated regularly, so as soon as my new code gets rolled into open-source (Matthias), the documentation for the maven-jdev-plugin will get updated and be meaningful.
4. Removed method replaceDemoConfiguration() which is a hack. It currently does nothing that is not already done and should have been removed in the last version of the maven-jdev-plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (TRINIDAD-893) Added 3 new parameters to the
maven-jdev-plugin.
Posted by "Matthias Weßendorf (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-893?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Weßendorf resolved TRINIDAD-893.
-----------------------------------------
Resolution: Fixed
Fix Version/s: 1.2.6-plugins
> Added 3 new parameters to the maven-jdev-plugin.
> ------------------------------------------------
>
> Key: TRINIDAD-893
> URL: https://issues.apache.org/jira/browse/TRINIDAD-893
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Reporter: Gary Kind
> Fix For: 1.2.6-plugins
>
> Attachments: maven-jdev-plugin-2_1.patch
>
>
> 1. Added 3 new parameters the jdev:jdev goal:
> * compiler: so that the default compiler (which is Ojc) can be changed to Javac
> * makeProject: so that the "Make Project" checkbox can be checked and a project will compile before run. The default is "false".
> * runTarget: set the default run target so it does not have to be manually. This is particularly useful for adf-richclient-test
> 2. Changed it so that libraries specified in a pom file will be added to the default libraries, JSP Runtime & JSF 1.2. In the current version, if you wanted to add libraries in your pom file, you would have to also include these default libraries in your list. I did not like this, so I changed it.
> 3. As part of my project to fully document our plugins, I went through all of the parameters and documented them so that meaningful plugin documentation is generated for the maven-jdev-plugin. I ran 'mvn site:site' on trinidad-maven/trunk so see what kind of documentation would get generated. The maven-jdev-plugin now looks great and one can actually get some useful information out of it. I also went on the internet and was able to find the current documentation at . This documentation gets generated regularly, so as soon as my new code gets rolled into open-source (Matthias), the documentation for the maven-jdev-plugin will get updated and be meaningful.
> 4. Removed method replaceDemoConfiguration() which is a hack. It currently does nothing that is not already done and should have been removed in the last version of the maven-jdev-plugin.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.