[jira] Commented: (TRINIDAD-846) JDev plugin - compiler configuration 11g
[ https://issues.apache.org/jira/browse/TRINIDAD-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549965 ] Aino Andriessen commented on TRINIDAD-846: -- I agree that a reverse filter could be a logical configuration, especially with all the adf xml and jpx files. And it would be great if the ADF BC wizard bug would be fixed. However, the aim of this plugin is to create JDev project files from our maven pom files so that we can develop our application with JDeveloper, e.g. with ADF business components (BC). The developers of this plugin have the choice how the plugin behaves. One of the choices is to use a reverse filter or not. With a reverse filter a problem arises when working with JDeveloper and ADF BC, without it the problem does not arise. So with the reverse filter, we have to make manual changes to the project properties in JDeveloper after using the plugin, without it we don't. Although maybe not the ideal solution, the pragmatic way is to not define the reverse filter in the plugin and follow the IDE's behaviour. JDev plugin - compiler configuration 11g - Key: TRINIDAD-846 URL: https://issues.apache.org/jira/browse/TRINIDAD-846 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.2.5-plugins Reporter: Aino Andriessen Priority: Minor Attachments: project.xml.11.1.1.0.0.patch The compiler configuration in the 11g 'template' project.xml file should not contains a so called reversed filter, because the JDeveloper ADF BC wizards do not take the reverse filter into account. This has been fixed (patched) on the 10.1.3.0.4 project file, but not yet on the 11g version. The same patch cannot be spplied because the jpr structure has been changed. -- 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
[ 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.
[jira] Updated: (TRINIDAD-851) JDev Plugin - configure the release
[ 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] Updated: (TRINIDAD-846) JDev plugin - compiler configuration 11g
[ https://issues.apache.org/jira/browse/TRINIDAD-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aino Andriessen updated TRINIDAD-846: - Status: Patch Available (was: Open) JDev plugin - compiler configuration 11g - Key: TRINIDAD-846 URL: https://issues.apache.org/jira/browse/TRINIDAD-846 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.2.5-plugins Reporter: Aino Andriessen Priority: Minor The compiler configuration in the 11g 'template' project.xml file should not contains a so called reversed filter, because the JDeveloper ADF BC wizards do not take the reverse filter into account. This has been fixed (patched) on the 10.1.3.0.4 project file, but not yet on the 11g version. The same patch cannot be spplied because the jpr structure has been changed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[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
[ 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] Commented: (TRINIDAD-177) JDev plugin - compiler configuration
[ https://issues.apache.org/jira/browse/TRINIDAD-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546616 ] Aino Andriessen commented on TRINIDAD-177: -- Great. Note, this same issue also applies to the 11g project file. I hope to have a patch available soon. The structure of the 11g projectfile has been changed a bit, so it requires a little bit of work and testing. JDev plugin - compiler configuration Key: TRINIDAD-177 URL: https://issues.apache.org/jira/browse/TRINIDAD-177 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.0.1-incubating-plugins-SNAPSHOT Environment: Windows XP, JDeveloper 10.1.3.1 (.0.3984) Reporter: Aino Andriessen Assignee: Matthias Weßendorf Fix For: 1.2.5-plugins Attachments: project.xml.10.1.3.0.4.patch The compiler configuration of the plugin conflicts with the business components wizard. The jdev plugin configures a reverse filter on the 'Copy File Types to Output Directory' and only adds .java on this list. However, when you create a new business component (actually only the first in a project), a bunch of extensions are added to this list that now contains the following entries: .java;.xml;.jpx;.xcfg;.xml;.xml;.xml;.xml;.xml;.xml;.xml When you try to test the model application an exception is raised (I am sorry for the french text) that it cannot find the Model.jpx file: JBO-30003: Le pool d'applications (.10F6E9C218F) n'a pas réussi à extraire (check out) un module d'application en raison de l'exception suivante : oracle.jbo.JboException: JBO-29000: JBO-29000: JBO-25222: Impossible de créer le module dapplication. ... javax.naming.NamingException [Root exception is oracle.jbo.NoXMLFileException: JBO-26001: Fichier XML introuvable pour le conteneur /Model.jpx] This is as expected, because that file is not copied to the classpath (due to the Reverse Filter), but highly unwanted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-846) JDev plugin - compiler configuration 11g
JDev plugin - compiler configuration 11g - Key: TRINIDAD-846 URL: https://issues.apache.org/jira/browse/TRINIDAD-846 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.2.5-plugins Reporter: Aino Andriessen Priority: Minor The compiler configuration in the 11g 'template' project.xml file should not contains a so called reversed filter, because the JDeveloper ADF BC wizards do not take the reverse filter into account. This has been fixed (patched) on the 10.1.3.0.4 project file, but not yet on the 11g version. The same patch cannot be spplied because the jpr structure has been changed. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-843) Jdev plugin - Nullpointer exception
Jdev plugin - Nullpointer exception --- Key: TRINIDAD-843 URL: https://issues.apache.org/jira/browse/TRINIDAD-843 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.2.5-plugins, 1.2.4.1-plugins Environment: Windows Reporter: Aino Andriessen When running the jdev plugin, a nullpointer occurs with the (new) code for handling taglibs. The WEB-INF\lib directory of my projects are empty or are not present at all. Stacktrace : [INFO] [INFO] Building Default ADF Faces application : jdevplugin [INFO]task-segment: [jdev:jdev] [INFO] [INFO] Preparing jdev:jdev [INFO] No goals needed for project - skipping [INFO] [jdev:jdev] [INFO] Generating JDeveloper 10.1.3.0.4 workspace: jdevplugin [INFO] [INFO] Building The generated jdevplugin model project [INFO]task-segment: [jdev:jdev] [INFO] [INFO] Preparing jdev:jdev [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [jdev:jdev] [INFO] Generating JDeveloper 10.1.3.0.4 Project jdevplugin-model [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.replaceLocalTagLibraries(JDeveloperMojo.java:904) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.replaceTagLibraries(JDeveloperMojo.java:1113) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.generateProject(JDeveloperMojo.java:398) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.generateProject(JDeveloperMojo.java:315) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.execute(JDeveloperMojo.java:227) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Nov 28 22:02:12 CET 2007 [INFO] Final Memory: 3M/7M [INFO] D:\tmp\test_projects\jdevplugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Issue Comment Edited: (TRINIDAD-843) Jdev plugin - Nullpointer exception
[ https://issues.apache.org/jira/browse/TRINIDAD-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546417 ] aino_a edited comment on TRINIDAD-843 at 11/28/07 1:42 PM: It seems that the patch of the related issue causes the problems. was (Author: aino_a): It seems that this patch causes the problems. Jdev plugin - Nullpointer exception --- Key: TRINIDAD-843 URL: https://issues.apache.org/jira/browse/TRINIDAD-843 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.2.5-plugins, 1.2.4.1-plugins Environment: Windows Reporter: Aino Andriessen When running the jdev plugin, a nullpointer occurs with the (new) code for handling taglibs. The WEB-INF\lib directory of my projects are empty or are not present at all. Stacktrace : [INFO] [INFO] Building Default ADF Faces application : jdevplugin [INFO]task-segment: [jdev:jdev] [INFO] [INFO] Preparing jdev:jdev [INFO] No goals needed for project - skipping [INFO] [jdev:jdev] [INFO] Generating JDeveloper 10.1.3.0.4 workspace: jdevplugin [INFO] [INFO] Building The generated jdevplugin model project [INFO]task-segment: [jdev:jdev] [INFO] [INFO] Preparing jdev:jdev [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. [INFO] [jdev:jdev] [INFO] Generating JDeveloper 10.1.3.0.4 Project jdevplugin-model [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.replaceLocalTagLibraries(JDeveloperMojo.java:904) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.replaceTagLibraries(JDeveloperMojo.java:1113) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.generateProject(JDeveloperMojo.java:398) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.generateProject(JDeveloperMojo.java:315) at org.apache.myfaces.trinidadbuild.plugin.jdeveloper.JDeveloperMojo.execute(JDeveloperMojo.java:227) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:447) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:333) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:126) at org.apache.maven.cli.MavenCli.main(MavenCli.java:282) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 3 seconds [INFO] Finished at: Wed Nov 28 22:02:12 CET 2007 [INFO] Final Memory: 3M/7M [INFO] D:\tmp\test_projects\jdevplugin -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-177) JDev plugin - compiler configuration
[ https://issues.apache.org/jira/browse/TRINIDAD-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546429 ] Aino Andriessen commented on TRINIDAD-177: -- Patch still needs to be applied. Patch is still valid for version 1.2.4 and higher (1.2.4.1 and 1.2.5-SNAPSHOT) . Tested it today with JDeveloper 10.1.3.3 and the 1.2.4 release. The patch applies correctly with the other (later) releases too but I could not test the result because of issue TRINIDAD-843. Still have to test the version 11 . JDev plugin - compiler configuration Key: TRINIDAD-177 URL: https://issues.apache.org/jira/browse/TRINIDAD-177 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.0.1-incubating-plugins-SNAPSHOT Environment: Windows XP, JDeveloper 10.1.3.1 (.0.3984) Reporter: Aino Andriessen Fix For: 1.0.1-incubating-plugins-SNAPSHOT Attachments: project.xml.10.1.3.0.4.patch The compiler configuration of the plugin conflicts with the business components wizard. The jdev plugin configures a reverse filter on the 'Copy File Types to Output Directory' and only adds .java on this list. However, when you create a new business component (actually only the first in a project), a bunch of extensions are added to this list that now contains the following entries: .java;.xml;.jpx;.xcfg;.xml;.xml;.xml;.xml;.xml;.xml;.xml When you try to test the model application an exception is raised (I am sorry for the french text) that it cannot find the Model.jpx file: JBO-30003: Le pool d'applications (.10F6E9C218F) n'a pas réussi à extraire (check out) un module d'application en raison de l'exception suivante : oracle.jbo.JboException: JBO-29000: JBO-29000: JBO-25222: Impossible de créer le module dapplication. ... javax.naming.NamingException [Root exception is oracle.jbo.NoXMLFileException: JBO-26001: Fichier XML introuvable pour le conteneur /Model.jpx] This is as expected, because that file is not copied to the classpath (due to the Reverse Filter), but highly unwanted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (TRINIDAD-844) JDev plugin - JHeadstart
JDev plugin - JHeadstart Key: TRINIDAD-844 URL: https://issues.apache.org/jira/browse/TRINIDAD-844 Project: MyFaces Trinidad Issue Type: Wish Components: Plugins Reporter: Aino Andriessen It would be great if the jpr file could include the JHeadstart tag that identifies that JHeadstart is enabled on the project, instead of manually adding that tag. It only requires the element : value n=JHEADSTART_ENABLED v=10.1.3.2.51/ This could be identified in the pom file with a property like jheadstart.version (or so). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-177) JDev plugin - compiler configuration
[ https://issues.apache.org/jira/browse/TRINIDAD-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aino Andriessen updated TRINIDAD-177: - Status: Patch Available (was: Open) JDev plugin - compiler configuration Key: TRINIDAD-177 URL: https://issues.apache.org/jira/browse/TRINIDAD-177 Project: MyFaces Trinidad Issue Type: Bug Components: Plugins Affects Versions: 1.0.1-incubating-plugins-SNAPSHOT Environment: Windows XP, JDeveloper 10.1.3.1 (.0.3984) Reporter: Aino Andriessen Fix For: 1.0.1-incubating-plugins-SNAPSHOT Attachments: project.xml.10.1.3.0.4.patch The compiler configuration of the plugin conflicts with the business components wizard. The jdev plugin configures a reverse filter on the 'Copy File Types to Output Directory' and only adds .java on this list. However, when you create a new business component (actually only the first in a project), a bunch of extensions are added to this list that now contains the following entries: .java;.xml;.jpx;.xcfg;.xml;.xml;.xml;.xml;.xml;.xml;.xml When you try to test the model application an exception is raised (I am sorry for the french text) that it cannot find the Model.jpx file: JBO-30003: Le pool d'applications (.10F6E9C218F) n'a pas réussi à extraire (check out) un module d'application en raison de l'exception suivante : oracle.jbo.JboException: JBO-29000: JBO-29000: JBO-25222: Impossible de créer le module dapplication. ... javax.naming.NamingException [Root exception is oracle.jbo.NoXMLFileException: JBO-26001: Fichier XML introuvable pour le conteneur /Model.jpx] This is as expected, because that file is not copied to the classpath (due to the Reverse Filter), but highly unwanted. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
