You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Aino Andriessen (JIRA)" <de...@myfaces.apache.org> on 2007/12/05 22:04:43 UTC
[jira] Created: (TRINIDAD-851) JDev Plugin - configure the release
JDev Plugin - configure the release
-----------------------------------
Key: TRINIDAD-851
URL: https://issues.apache.org/jira/browse/TRINIDAD-851
Project: MyFaces Trinidad
Issue Type: Improvement
Components: Plugins
Affects Versions: 1.2.6-plugins
Reporter: Aino Andriessen
Priority: Minor
Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-851) JDev Plugin - configure the
release
Posted by "Aino Andriessen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548865 ]
Aino Andriessen commented on TRINIDAD-851:
------------------------------------------
I'm obviously doing something wrong because I cannot reproduce your suggestion. It keeps creating 10.3.x project files.
> JDev Plugin - configure the release
> -----------------------------------
>
> Key: TRINIDAD-851
> URL: https://issues.apache.org/jira/browse/TRINIDAD-851
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 1.2.6-plugins
> Reporter: Aino Andriessen
> Priority: Minor
> Attachments: JDeveloperMojo.patch
>
>
> Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-851) JDev Plugin - configure the release
Posted by "Aino Andriessen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aino Andriessen updated TRINIDAD-851:
-------------------------------------
Status: Patch Available (was: Open)
> JDev Plugin - configure the release
> -----------------------------------
>
> Key: TRINIDAD-851
> URL: https://issues.apache.org/jira/browse/TRINIDAD-851
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 1.2.6-plugins
> Reporter: Aino Andriessen
> Priority: Minor
> Attachments: JDeveloperMojo.patch
>
>
> Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-851) JDev Plugin - configure the
release
Posted by "Gary Kind (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548885 ]
Gary Kind commented on TRINIDAD-851:
------------------------------------
I put ours at the top of the maven project's parent pom file, before the <build> section. That way the property is available for all maven projects under the parent. I can't tell you much more than that. It works fine for us. You may have to debug into your JDeveloperMojo.java to see why it isn't working for you. I did that by creating a plugin.jws and plugin.jpr for the maven-jdev-plugin. I set remote debugging to true in the Project Properties -> Run/Debug/Settings -> default. Set the attachment port at 4000.
Then on the command line of a terminal or cmd.exe window:
> set MAVEN_OPTS=-Xdebug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=y,address=4000
> mvn jdev:jdev
This will wait until JDev attaches to it.
Go back into jdev and debug your project. It will attach to the maven project and away you go.
> JDev Plugin - configure the release
> -----------------------------------
>
> Key: TRINIDAD-851
> URL: https://issues.apache.org/jira/browse/TRINIDAD-851
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 1.2.6-plugins
> Reporter: Aino Andriessen
> Priority: Minor
> Attachments: JDeveloperMojo.patch
>
>
> Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-851) JDev Plugin - configure the
release
Posted by "Gary Kind (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549460 ]
Gary Kind commented on TRINIDAD-851:
------------------------------------
Actually Aino, you must using and looking at the old version of JDeveloperMojo.java. The current version that was just put into 1.2.5 has this code:
/**
* @parameter expression="${jdev.release}" default-value="10.1.3.0.4"
*/
private String release;
The patch you added in this issue is:
/**
* @parameter expression="10.1.3.0.4"
* @required
- * @readonly
*/
private String release;
indicating you are looking at the old version of the JDev Plugin. That is also why the jdev.release property is not working for you. You should probably close this issue since the current plugin already does what you want.
> JDev Plugin - configure the release
> -----------------------------------
>
> Key: TRINIDAD-851
> URL: https://issues.apache.org/jira/browse/TRINIDAD-851
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 1.2.6-plugins
> Reporter: Aino Andriessen
> Priority: Minor
> Attachments: JDeveloperMojo.patch
>
>
> Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-851) JDev Plugin - configure the
release
Posted by "Gary Kind (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548825 ]
Gary Kind commented on TRINIDAD-851:
------------------------------------
The plugin's release can already be set by using the jdev.release property. In a pom file it would look like:
<properties>
<jdev.release>11.1.1.0.0</jdev.release>
</properties>
> JDev Plugin - configure the release
> -----------------------------------
>
> Key: TRINIDAD-851
> URL: https://issues.apache.org/jira/browse/TRINIDAD-851
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 1.2.6-plugins
> Reporter: Aino Andriessen
> Priority: Minor
> Attachments: JDeveloperMojo.patch
>
>
> Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-851) JDev Plugin - configure the
release
Posted by "Aino Andriessen (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549969 ]
Aino Andriessen commented on TRINIDAD-851:
------------------------------------------
Sorry, I got a bit confused, because I was working with the trunk (that still lacks this improvement) and not the 1.2.5 branch.
> JDev Plugin - configure the release
> -----------------------------------
>
> Key: TRINIDAD-851
> URL: https://issues.apache.org/jira/browse/TRINIDAD-851
> Project: MyFaces Trinidad
> Issue Type: Improvement
> Components: Plugins
> Affects Versions: 1.2.6-plugins
> Reporter: Aino Andriessen
> Priority: Minor
> Attachments: JDeveloperMojo.patch
>
>
> Be able to configure which JDeveloper version the project files are generated for. Especially meaningful with the upcoming 11g release.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.