[
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.
