[jira] (MCHANGES-311) Provide an allura-report goal (sourceforge.net)
[ https://jira.codehaus.org/browse/MCHANGES-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=354401#comment-354401 ] Richard van Nieuwenhoven commented on MCHANGES-311: --- Just a little help, i do not have the time to really integrate the allura stuff in the changes plugin (just to many projects). But i have written a very small module that is already implemented in the changes plugin style. Somebody here that knows the changes plugin a little more could use is as a base and integrate it in "no time". Now it just generates the changes.xml from the sourceforge/allura ticket system using stuff from the insides of the changes plugin. http://sourceforge.net/p/indiforjava/code/ci/master/tree/tools/changes/ hope it helps, and somebody includes the stuff in the "right" way. > Provide an allura-report goal (sourceforge.net) > --- > > Key: MCHANGES-311 > URL: https://jira.codehaus.org/browse/MCHANGES-311 > Project: Maven Changes Plugin > Issue Type: Wish > Components: other issue-trackers >Reporter: Florian Brunner > > Provide an allura-report goal. > This would allow to generate issues reports for projects hosted at > sourceforge (and other platforms running Allura). > http://sourceforge.net/p/allura/wiki/Allura%20Wiki/ > Allura is in the Apache Incubator: > http://incubator.apache.org/projects/allura.html -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] Commented: (MECLIPSE-415) settings stored in wrong project directory
[
http://jira.codehaus.org/browse/MECLIPSE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=158463#action_158463
]
Richard van Nieuwenhoven commented on MECLIPSE-415:
---
This request was on a far to short notice, and at the moment i do not have the
time to check if the trunk still has this behavior.
Please make sure in your test to use a multi module hierarchical project, they
are the ones with the most problems ;-)
And also please look into my note for Arnaud to remove unreachable codes, the
plugin is complicated as it is.
> settings stored in wrong project directory
> ---
>
> Key: MECLIPSE-415
> URL: http://jira.codehaus.org/browse/MECLIPSE-415
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath), Core : Workspace settings
>Affects Versions: 2.5, 2.5.1
> Environment: all
>Reporter: Richard van Nieuwenhoven
>Assignee: Barrie Treloar
> Fix For: 2.6
>
> Attachments: executedProject.patch, pom.xml
>
>
> When i store my projects in a directory which isn't my eclipse workspace.
> If I define the workspace attribute to be able to read its settings,
> when I call eclipse:eclipse, my projects settings are written in the
> workspace and not in each project's directory.
> this problem seems to be connected to the wrongly used executedProject
> parameter and maven 2.0.9..
> the wrong directory problem can be solved by giving the eclipseProjectDir a
> default value ${basedir} .
> Arnaud: i think you can safely remove much of the code in
> EclipsePlugin.validate method where the eclipseProjectDir does not exist or
> !eclipseProjectDir.equals( project.getBasedir() ) these cases will almoust
> never work anymore (only for very very simple eclipse projects), and it is
> certainly discouraged.
> in the attached patch i have included the removal of the executedProject
> parameter but not the code mentioned above, the strange thing i did not have
> the time to solve is that "testProject11" now fails (it survived the default
> value but not the removal of the executedProject parameter)
--
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
[jira] Commented: (MECLIPSE-416) Build failures (EclipsePluginTest failures and errors)
[ http://jira.codehaus.org/browse/MECLIPSE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129666#action_129666 ] Richard van Nieuwenhoven commented on MECLIPSE-416: --- the requireMavenVersion also applies to the runtime, but 2.0.8 is just required for the testing during the build. As far as i know not for the runtime. We use the plugin in a lot of projects that are locked to maven 2.0.7. So please limit it only for the build time. > Build failures (EclipsePluginTest failures and errors) > -- > > Key: MECLIPSE-416 > URL: http://jira.codehaus.org/browse/MECLIPSE-416 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: $ uname -a > Linux expresso2 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 > GNU/Linux > $ java -version > java version "1.5.0_11" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode) >Reporter: Jerome Lacoste >Assignee: Arnaud Heritier > Fix For: 2.5.2 > > Attachments: MECLIPSE-416.diff, > org.apache.maven.plugin.eclipse.EclipsePluginTest.txt > > > Trunk build fails (r642941). > Results : > Failed tests: > testProject33(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests in error: > testProject16(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject17(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testMECLIPSE_56_encoding(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests run: 91, Failures: 1, Errors: 3, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > $ svn info > Path: . > URL: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 642941 > Node Kind: directory > Schedule: normal > Last Changed Author: aheritier > Last Changed Rev: 642029 > Last Changed Date: 2008-03-28 00:43:44 +0100 (Fri, 28 Mar 2008) > This probably encompass various failures. -- 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
[jira] Commented: (MECLIPSE-416) Build failures (EclipsePluginTest failures and errors)
[ http://jira.codehaus.org/browse/MECLIPSE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129213#action_129213 ] Richard van Nieuwenhoven commented on MECLIPSE-416: --- maven 2.0.8 is a requirement for building the eclipse plugin. > Build failures (EclipsePluginTest failures and errors) > -- > > Key: MECLIPSE-416 > URL: http://jira.codehaus.org/browse/MECLIPSE-416 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Environment: $ uname -a > Linux expresso2 2.6.24-12-generic #1 SMP Wed Mar 12 23:01:54 UTC 2008 i686 > GNU/Linux > $ java -version > java version "1.5.0_11" > Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_11-b03) > Java HotSpot(TM) Server VM (build 1.5.0_11-b03, mixed mode) >Reporter: Jerome Lacoste > Attachments: MECLIPSE-416.diff, > org.apache.maven.plugin.eclipse.EclipsePluginTest.txt > > > Trunk build fails (r642941). > Results : > Failed tests: > testProject33(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests in error: > testProject16(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testProject17(org.apache.maven.plugin.eclipse.EclipsePluginTest) > testMECLIPSE_56_encoding(org.apache.maven.plugin.eclipse.EclipsePluginTest) > Tests run: 91, Failures: 1, Errors: 3, Skipped: 0 > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] There are test failures. > $ svn info > Path: . > URL: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-eclipse-plugin > Repository Root: http://svn.apache.org/repos/asf > Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 > Revision: 642941 > Node Kind: directory > Schedule: normal > Last Changed Author: aheritier > Last Changed Rev: 642029 > Last Changed Date: 2008-03-28 00:43:44 +0100 (Fri, 28 Mar 2008) > This probably encompass various failures. -- 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
[jira] Created: (MECLIPSE-415) settings stored in wrong project directory
settings stored in wrong project directory
---
Key: MECLIPSE-415
URL: http://jira.codehaus.org/browse/MECLIPSE-415
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path, Core :
Workspace settings
Affects Versions: 2.5, 2.5.1
Environment: all
Reporter: Richard van Nieuwenhoven
Attachments: executedProject.patch
When i store my projects in a directory which isn't my eclipse workspace.
If I define the workspace attribute to be able to read its settings,
when I call eclipse:eclipse, my projects settings are written in the
workspace and not in each project's directory.
this problem seems to be connected to the wrongly used executedProject
parameter and maven 2.0.9..
the wrong directory problem can be solved by giving the eclipseProjectDir a
default value ${basedir} .
Arnaud: i think you can safely remove much of the code in
EclipsePlugin.validate method where the eclipseProjectDir does not exist or
!eclipseProjectDir.equals( project.getBasedir() ) these cases will almoust
never work anymore (only for very very simple eclipse projects), and it is
certainly discouraged.
in the attached patch i have included the removal of the executedProject
parameter but not the code mentioned above, the strange thing i did not have
the time to solve is that "testProject11" now fails (it survived the default
value but not the removal of the executedProject parameter)
--
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
[jira] Commented: (MECLIPSE-413) EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName
[ http://jira.codehaus.org/browse/MECLIPSE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128935#action_128935 ] Richard van Nieuwenhoven commented on MECLIPSE-413: --- true, but the necessary pde option destroys my manifest. An alternative would be to deactivate it, but that would be a big change for a 2.5.1 release. > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > - > > Key: MECLIPSE-413 > URL: http://jira.codehaus.org/browse/MECLIPSE-413 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: OSGi, Manifest >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: osgi.patch > > > EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName > the EclipseOSGiManifestWriter should also honor the project name template! > this is a very small patch. -- 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
[jira] Created: (MECLIPSE-413) EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName
EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName - Key: MECLIPSE-413 URL: http://jira.codehaus.org/browse/MECLIPSE-413 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: OSGi, Manifest Affects Versions: 2.5 Reporter: Richard van Nieuwenhoven Attachments: osgi.patch EclipseOSGiManifestWriter uses the artifact id and not the EclipseProjectName the EclipseOSGiManifestWriter should also honor the project name template! this is a very small patch. -- 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
[jira] Commented: (MECLIPSE-411) manifest property usage is only for ogsi maifests
[ http://jira.codehaus.org/browse/MECLIPSE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=128843#action_128843 ] Richard van Nieuwenhoven commented on MECLIPSE-411: --- just tested and it works, thanks! now to the vote. > manifest property usage is only for ogsi maifests > - > > Key: MECLIPSE-411 > URL: http://jira.codehaus.org/browse/MECLIPSE-411 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: OSGi, Manifest, WTP support >Affects Versions: 2.5 > Environment: any >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5.1 > > Attachments: manifest.patch > > > the manifest property of the eclipse plugin is only for the osgi writer and > not for the wtp manifest, because the wtp manifest is a special case that > will not be included in the maven build just in the eclipse classpath. The > problem is that the property has a default value and by that deacivates the > WTP classpath! > included a patch for the 2.5 release, including some renaming so it won't > happen again. > please release a 2.5.1 version with this patch! -- 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
[jira] Created: (MECLIPSE-411) maifest property usage is only for ogsi maifests
maifest property usage is only for ogsi maifests Key: MECLIPSE-411 URL: http://jira.codehaus.org/browse/MECLIPSE-411 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: OSGi, Manifest, WTP support Affects Versions: 2.5 Environment: any Reporter: Richard van Nieuwenhoven Attachments: manifest.patch the manifest property of the eclipse plugin is only for the osgi writer and not for the wtp manifest, because the wtp manifest is a special case that will not be included in the maven build just in the eclipse classpath. The problem is that the property has a default value and by that deacivates the WTP classpath! included a patch for the 2.5 release, including some renaming so it won't happen again. please release a 2.5.1 version with this patch! -- 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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126688 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- Only linking the SNAPSHOT's, can be done, the problem is the list of options are getting more and more complex and interweaving. So i think it is best to make no new option but let the user decide with the eclipse means available (what's in the workspace will be linked). I think the best solution is to import or delete (just from the workspace) the projects as needed and then let the eclipse plugin connect them. > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Core : Dependencies resolution and build path >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, > MECLIPSE-344.patch, MECLIPSE-344.tgz, workspace-new-files.tgz, > workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117608 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- it contains the binary files for the patch! "svn diff" can not handle binary files. > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Dependencies resolution and build path >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz, > MECLIPSE-344.patch, MECLIPSE-344.tgz, workspace-new-files.tgz, > workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Updated: (MECLIPSE-344) connecting existing workspace artifact-projects
[
http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard van Nieuwenhoven updated MECLIPSE-344:
--
Attachment: MECLIPSE-344+rad7.tgz
MECLIPSE-344+rad7.patch
Updated the patch for the current snapshot and included the standard JRE
resolution of eclipse.
The workspace scanning is now re factored to reader and data class.
Now also included is the RAD-7 support (that needs the workspace reading) with
tests.
- MECLIPSE-344+rad7.patch contains the patch and all new text files
- MECLIPSE-344+rad7.tgz contains the new binary files
to use the RAD-7 support the option
- workspaceToConnect must point to the current workspace directory (use
${workspace_loc} in eclipse launches)
- wtpdefaultserver contains the exact name or a substring of the defined wtp
server to use
> connecting existing workspace artifact-projects
> ---
>
> Key: MECLIPSE-344
> URL: http://jira.codehaus.org/browse/MECLIPSE-344
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Dependencies resolution and build path
>Reporter: Richard van Nieuwenhoven
>Assignee: Arnaud Heritier
> Attachments: MECLIPSE-344+rad7.patch, MECLIPSE-344+rad7.tgz,
> MECLIPSE-344.patch, MECLIPSE-344.tgz, workspace-new-files.tgz,
> workspace.patch, workspace_with_limit.patch
>
>
> This patch enables you to specify your workspace, and all dependent artefacts
> that are available in your eclipse-workspace will be attached as project
> references even if they are not in the reactor.
> the property can be set with -DworkspaceToConnect=.
> I did not have the time to create Test cases but, i maybe someone can help
> with that!
> The patch is based on the MECLIPSE-333 branch.
> as usual the new files are in the extra tgz.
--
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
[jira] Commented: (MECLIPSE-361) eclipse plugin and WTP generating warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117392 ] Richard van Nieuwenhoven commented on MECLIPSE-361: --- @Rob Yes, i mean references to third-party library dependencies (in the local repository). The resolved dependencies of the WAR / EAR are the one's used for the WTP deployment. @Yann Albou Yes, it is only a warning and till the next WTP / Eclipse version we must ignore it. > eclipse plugin and WTP generating warnings in Europa > - > > Key: MECLIPSE-361 > URL: http://jira.codehaus.org/browse/MECLIPSE-361 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5 > Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the > last maven-eclipse-plugin 2.5-SNAPSHOT >Reporter: Yann Albou >Priority: Minor > Attachments: wtpTest.zip > > > The issue is regarding warnings in Europa and WTP: > "Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be > exported or published. Runtime ClassNotFoundExceptions may result." > 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.5-SNAPSHOT => I get the same behaviour in EUROPA (WARNINGS) > 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.4 => I get the same behaviour in EUROPA (WARNINGS) > 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse > 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or > 2.5-SNAPSHOT => Everything is perfect, no more warnings > I create a simple test in order to reproduce the issue. > This test is a multi module application composed of 1 Ejb module and 1 Ear > module. > So at the top level Just run "mvn install eclipse:eclipse" > And then in an europa workspace import the projetcs and you should see the > warnings on the EJB module. > It will behave the same way if it exists other modules. > I notice that, in the case you update parameters on the eclipse plugin you > will need to remove projects from workspace and import them again. > otherwise some old parameter will stay in the eclipse cache... > let me know if you need other tests > Yann. -- 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
[jira] Issue Comment Edited: (MECLIPSE-341) Support RAD7
[ http://jira.codehaus.org/browse/MECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117384 ] ritchie edited comment on MECLIPSE-341 at 12/20/07 7:53 AM: - Very good RAD-7 is almost compatible to WTP 1.5 just 2 small differences. - in the application xml the location must be different - the target WebSphere server must be known (this can be done by extending MECLIPSE-344) I am still testing but later today i will update MECLIPSE-344 with a patch that will include rad-7 support. was (Author: ritchie): Very good RAD-7 is almost compatible to WTP 1.5 just 2 small differences. - in the application xml the location must be different - the target WEBSHERE server must be known (this can be done by extending MECLIPSE-344) I am still testing but later today i will update MECLIPSE-344 with a patch that will include rad-7 support. > Support RAD7 > > > Key: MECLIPSE-341 > URL: http://jira.codehaus.org/browse/MECLIPSE-341 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: RAD support >Affects Versions: 2.4 > Environment: RAD7 >Reporter: David J. M. Karlsen > > The current rad goal only supports RAD6. > If I run this goal and try to import the projects into RAD, the capabilities > are not recognized, thus it's not possible to "debug on server" and so on. -- 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
[jira] Issue Comment Edited: (MECLIPSE-341) Support RAD7
[ http://jira.codehaus.org/browse/MECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117384 ] ritchie edited comment on MECLIPSE-341 at 12/20/07 7:52 AM: - Very good RAD-7 is almost compatible to WTP 1.5 just 2 small differences. - in the application xml the location must be different - the target WEBSHERE server must be known (this can be done by extending MECLIPSE-344) I am still testing but later today i will update MECLIPSE-344 with a patch that will include rad-7 support. was (Author: ritchie): Very good RAD-7 is almost compatible to WTP 1.5 just 2 small differences. - in the application xml the location must be differnt - the target WEBSHERE server must be known (this can be done by extending MECLIPSE-344) I am still testing but later today i will update MECLIPSE-344 with a patch that will include rad-7 support. > Support RAD7 > > > Key: MECLIPSE-341 > URL: http://jira.codehaus.org/browse/MECLIPSE-341 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: RAD support >Affects Versions: 2.4 > Environment: RAD7 >Reporter: David J. M. Karlsen > > The current rad goal only supports RAD6. > If I run this goal and try to import the projects into RAD, the capabilities > are not recognized, thus it's not possible to "debug on server" and so on. -- 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
[jira] Commented: (MECLIPSE-341) Support RAD7
[ http://jira.codehaus.org/browse/MECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117384 ] Richard van Nieuwenhoven commented on MECLIPSE-341: --- Very good RAD-7 is almost compatible to WTP 1.5 just 2 small differences. - in the application xml the location must be differnt - the target WEBSHERE server must be known (this can be done by extending MECLIPSE-344) I am still testing but later today i will update MECLIPSE-344 with a patch that will include rad-7 support. > Support RAD7 > > > Key: MECLIPSE-341 > URL: http://jira.codehaus.org/browse/MECLIPSE-341 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: RAD support >Affects Versions: 2.4 > Environment: RAD7 >Reporter: David J. M. Karlsen > > The current rad goal only supports RAD6. > If I run this goal and try to import the projects into RAD, the capabilities > are not recognized, thus it's not possible to "debug on server" and so on. -- 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
[jira] Commented: (MECLIPSE-361) eclipse plugin and WTP generating warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117192 ] Richard van Nieuwenhoven commented on MECLIPSE-361: --- Ok, just checked for a possibility to remove this unwanted warning, and found that it is a known bug in eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=190783 So we can generate the nondependency attribute for the next release of eclipse/wtp. > eclipse plugin and WTP generating warnings in Europa > - > > Key: MECLIPSE-361 > URL: http://jira.codehaus.org/browse/MECLIPSE-361 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5 > Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the > last maven-eclipse-plugin 2.5-SNAPSHOT >Reporter: Yann Albou >Priority: Minor > Attachments: wtpTest.zip > > > The issue is regarding warnings in Europa and WTP: > "Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be > exported or published. Runtime ClassNotFoundExceptions may result." > 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.5-SNAPSHOT => I get the same behaviour in EUROPA (WARNINGS) > 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.4 => I get the same behaviour in EUROPA (WARNINGS) > 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse > 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or > 2.5-SNAPSHOT => Everything is perfect, no more warnings > I create a simple test in order to reproduce the issue. > This test is a multi module application composed of 1 Ejb module and 1 Ear > module. > So at the top level Just run "mvn install eclipse:eclipse" > And then in an europa workspace import the projetcs and you should see the > warnings on the EJB module. > It will behave the same way if it exists other modules. > I notice that, in the case you update parameters on the eclipse plugin you > will need to remove projects from workspace and import them again. > otherwise some old parameter will stay in the eclipse cache... > let me know if you need other tests > Yann. -- 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
[jira] Commented: (MECLIPSE-341) Support RAD7
[ http://jira.codehaus.org/browse/MECLIPSE-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117181 ] Richard van Nieuwenhoven commented on MECLIPSE-341: --- Just got the permission to work on this task. It seems the WTP 1.5 support will go as far as WAR projects but breaks on EAR projects. > Support RAD7 > > > Key: MECLIPSE-341 > URL: http://jira.codehaus.org/browse/MECLIPSE-341 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: RAD support >Affects Versions: 2.4 > Environment: RAD7 >Reporter: David J. M. Karlsen > > The current rad goal only supports RAD6. > If I run this goal and try to import the projects into RAD, the capabilities > are not recognized, thus it's not possible to "debug on server" and so on. -- 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
[jira] Commented: (MECLIPSE-361) eclipse plugin and WTP generating warnings in Europa
[ http://jira.codehaus.org/browse/MECLIPSE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117179 ] Richard van Nieuwenhoven commented on MECLIPSE-361: --- The problem is that this warning is correct and the behavior is intended. The eclipse plugin works on a per project basis, So it will not export the dependencies, every projects gets the correct dependencies from the dependency resolution. So our issue here is how to tell eclipse that it's OK, and we know and we want it that way. > eclipse plugin and WTP generating warnings in Europa > - > > Key: MECLIPSE-361 > URL: http://jira.codehaus.org/browse/MECLIPSE-361 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: WTP support >Affects Versions: 2.5 > Environment: Eclipse 3.3.1.1 and WTP 2.0.1 Using Maven 2.0.7 and the > last maven-eclipse-plugin 2.5-SNAPSHOT >Reporter: Yann Albou >Priority: Minor > Attachments: wtpTest.zip > > > The issue is regarding warnings in Europa and WTP: > "Classpath entry M2_REPO/log4j/log4j/1.2.13/log4j-1.2.13.jar will not be > exported or published. Runtime ClassNotFoundExceptions may result." > 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.5-SNAPSHOT => I get the same behaviour in EUROPA (WARNINGS) > 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin > version 2.4 => I get the same behaviour in EUROPA (WARNINGS) > 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse > 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or > 2.5-SNAPSHOT => Everything is perfect, no more warnings > I create a simple test in order to reproduce the issue. > This test is a multi module application composed of 1 Ejb module and 1 Ear > module. > So at the top level Just run "mvn install eclipse:eclipse" > And then in an europa workspace import the projetcs and you should see the > warnings on the EJB module. > It will behave the same way if it exists other modules. > I notice that, in the case you update parameters on the eclipse plugin you > will need to remove projects from workspace and import them again. > otherwise some old parameter will stay in the eclipse cache... > let me know if you need other tests > Yann. -- 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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116352 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- this part of file format did not change since 2.0 and that's a long time. It is also protected by a magic code so no version incompatibility possible. And we will now use a dependency to the original eclipse (binaries) to read them, so i think we are on the save side here ;-) > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Dependencies resolution and build path >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Attachments: MECLIPSE-344.patch, MECLIPSE-344.tgz, > workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116350 ] Richard van Nieuwenhoven commented on MECLIPSE-333: --- please specify the parameters do you give eclipse:eclipse? i use 3.3.1 and have no such problems and my parameters are: -Declipse.wtpmanifest=true -Declipse.wtpapplicationxml=true -Dwtpversion=2.0 did you forget the wtpversion parameter? > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: Multi-projects, WTP support >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: Eclipse-3.3.0-about.png, > Eclipse-3.3.0-project-upgrade.png, maven-eclipse-plugin_only_new.tar.gz, > maven-eclipse-plugin_only_new_2.tar.tgz, > wtp-2.0-and-more-2.5-SNAPSHOT-2.patch, wtp-2.0-and-more-2.5-SNAPSHOT-3.patch, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[
http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115894
]
Richard van Nieuwenhoven commented on MECLIPSE-344:
---
a small fix for my patch that will give the class path container lookup partly
back to eclipse.
-ReadWorkspaceLocations---
//add constant
private static final String CLASSPATHENTRY_STANDARD =
CLASSPATHENTRY_DEFAULT+"/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/";
-ReadWorkspaceLocations---
//change the method to add defaults known by eclipse
public static HashMap readAvailableJREs( String workspaceLocation, Log logger )
{
HashMap jreMap = new HashMap();
jreMap.put( "1.2", CLASSPATHENTRY_STANDARD+"J2SE-1.2" );
jreMap.put( "1.3", CLASSPATHENTRY_STANDARD+"J2SE-1.3" );
jreMap.put( "1.4", CLASSPATHENTRY_STANDARD+"J2SE-1.4" );
jreMap.put( "1.5", CLASSPATHENTRY_STANDARD+"J2SE-1.5" );
jreMap.put( "5", jreMap.get("1.5") );
jreMap.put( "1.6", CLASSPATHENTRY_STANDARD+"JavaSE-1.6" );
jreMap.put( "6", jreMap.get("1.6") );
-EclipsePluginTest---
// changed test result in testProject38and39()
doTestProject38and39( "project-38", workspace15, "J2SE-1.3" ,null);
-
> connecting existing workspace artifact-projects
> ---
>
> Key: MECLIPSE-344
> URL: http://jira.codehaus.org/browse/MECLIPSE-344
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Dependencies resolution and build path
>Reporter: Richard van Nieuwenhoven
>Assignee: Arnaud Heritier
> Attachments: MECLIPSE-344.patch, MECLIPSE-344.tgz,
> workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch
>
>
> This patch enables you to specify your workspace, and all dependent artefacts
> that are available in your eclipse-workspace will be attached as project
> references even if they are not in the reactor.
> the property can be set with -DworkspaceToConnect=.
> I did not have the time to create Test cases but, i maybe someone can help
> with that!
> The patch is based on the MECLIPSE-333 branch.
> as usual the new files are in the extra tgz.
--
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
[jira] Commented: (MECLIPSE-334) Add a rule that determined artifacts will be always recognized as reactor projects
[ http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115479 ] Richard van Nieuwenhoven commented on MECLIPSE-334: --- This is exactly the one of the usecases that MECLIPSE-344 covers, I have discussed this with Martin and now he is also convinced that 344 covers his needs. But he is at a conference so he can't respond till Monday. > Add a rule that determined artifacts will be always recognized as reactor > projects > -- > > Key: MECLIPSE-334 > URL: http://jira.codehaus.org/browse/MECLIPSE-334 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Affects Versions: 2.4 >Reporter: Martin Zeltner > Attachments: patch_maven-eclipse-plugin-r587020.patch > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > I've implemented a feature that determined artifacts will be always > recognized as reactor projects, doesn't matter where the "mvn > eclipse:eclipse" is executed. The idea is to set a list of groupId prefixes. > Example: > [code] > > org.apache.maven.plugins > maven-eclipse-plugin > > > ch.elca., > org.sp, > net.sf > > > > [/code] > All artifacts where the groupId starts with "ch.elca.", "org.sp" or "net.sf" > will be handled as reactor projects. > Cheers, > Martin -- 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
[jira] Commented: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.
[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115255 ] Richard van Nieuwenhoven commented on MECLIPSE-172: --- great, thanks (saves searching) i will honor that in the MECLIPSE-344 patch. just when the executable was specified (vendor specific server jre) i will use the specific else the standard (depending on the compiler version). > Don't add Default ClasspathContainer if a alternate JRE or a "Execution > Environment" is configured as ClasspathContainer. > - > > Key: MECLIPSE-172 > URL: http://jira.codehaus.org/browse/MECLIPSE-172 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.2, 2.3 > Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP >Reporter: Markus Grieder >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: EclipsePlugin.java.patch, > MECLIPSE-172-fix-and-test.patch, org.eclipse.jdt.launching.prefs, patch.txt > > > If have a Eclipse Workspace with Projects where some use Java 1.5 (Default > JRE) and some Java 1.3 > For 1.3-Projects i have configured the following ClasspathContainer: > > org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre > > This generates in ".classpath": > > path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre"/> > Which is wrong, because the Default JRE is Java 1.5, but the Project should > only see Java 1.3-Libraries and not both. > -> The Default ClasspathContainer should only be added if no JRE_CONTAINER > (alternate JRE or a Execution Environment (>=Eclipse 3.2)) was specified. The > attached Patch replace the "contains"-match with a "starts-with"-match, which > only adds the Default ClasspathContainer if no classpathContainer is > configured which starts with the "JRE_CONTAINER"-Path. -- 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
[jira] Commented: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.
[
http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115180
]
Richard van Nieuwenhoven commented on MECLIPSE-172:
---
A lot of troubles i faced, trying to convince eclipse developers to use maven
have to do with the missing workspace...
But you are right that we should not over stretch it, i didn't know of the
"OSGi Execution Environment enumeration" can you point me to a bit of
documentation on how eclipse handles that (or the source if no documentation is
available).
In a shared eclipse launch adding a workspace is simple
"-Declipse.workspaceToConnect=${workspace_loc}" works for all, on the command
line you are right but there i never need eclipse:eclipse.
> Don't add Default ClasspathContainer if a alternate JRE or a "Execution
> Environment" is configured as ClasspathContainer.
> -
>
> Key: MECLIPSE-172
> URL: http://jira.codehaus.org/browse/MECLIPSE-172
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
>Affects Versions: 2.2, 2.3
> Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP
>Reporter: Markus Grieder
>Assignee: Arnaud Heritier
> Fix For: 2.5
>
> Attachments: EclipsePlugin.java.patch,
> MECLIPSE-172-fix-and-test.patch, org.eclipse.jdt.launching.prefs, patch.txt
>
>
> If have a Eclipse Workspace with Projects where some use Java 1.5 (Default
> JRE) and some Java 1.3
> For 1.3-Projects i have configured the following ClasspathContainer:
>
> org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre
>
> This generates in ".classpath":
>
> path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre"/>
> Which is wrong, because the Default JRE is Java 1.5, but the Project should
> only see Java 1.3-Libraries and not both.
> -> The Default ClasspathContainer should only be added if no JRE_CONTAINER
> (alternate JRE or a Execution Environment (>=Eclipse 3.2)) was specified. The
> attached Patch replace the "contains"-match with a "starts-with"-match, which
> only adds the Default ClasspathContainer if no classpathContainer is
> configured which starts with the "JRE_CONTAINER"-Path.
--
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
[jira] Commented: (MECLIPSE-334) Add a rule that determined artifacts will be always recognized as reactor projects
[ http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115175 ] Richard van Nieuwenhoven commented on MECLIPSE-334: --- dangerous means for me things you can configure that can lead to "bad" style. But lets concentrate on your usecase. Can you explain the situation for which you need this! Because you are willing to write the configuration in your pom, and a pom should not (in my opinion) expect other artefact's to be available in source (exception are all submodules). So please explain what are you trying to accomplish, and how this configuration helps. > Add a rule that determined artifacts will be always recognized as reactor > projects > -- > > Key: MECLIPSE-334 > URL: http://jira.codehaus.org/browse/MECLIPSE-334 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Affects Versions: 2.4 >Reporter: Martin Zeltner > Attachments: patch_maven-eclipse-plugin-r587020.patch > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > I've implemented a feature that determined artifacts will be always > recognized as reactor projects, doesn't matter where the "mvn > eclipse:eclipse" is executed. The idea is to set a list of groupId prefixes. > Example: > [code] > > org.apache.maven.plugins > maven-eclipse-plugin > > > ch.elca., > org.sp, > net.sf > > > > [/code] > All artifacts where the groupId starts with "ch.elca.", "org.sp" or "net.sf" > will be handled as reactor projects. > Cheers, > Martin -- 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
[jira] Commented: (MECLIPSE-354) application.xml is not the correct and not the same in the EAR package
[
http://jira.codehaus.org/browse/MECLIPSE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115168
]
Richard van Nieuwenhoven commented on MECLIPSE-354:
---
I would like that, but that would mean synchronizing ~10 different projects and
growing. And synchronizing 2 is already difficult.
And even then, there are still a lot out there that do the stuff differently
After writing, and reverse engineering a few of what the maven-xxx-plugin does
and how wtp does it differently,
I noticed that some things are very difficult to do in the resources phase and
a peace of cake in a later (package) phase.
Good examples are the application.xml generation and the MANIFEST.MF
generation.
In case of the MANIFEST.MF i tried using the common lib available but for that
we need the dependency resolution of maven finished and when i tried to
activate that,
the eclipse plugin dependency resolution fails.
When we split the eclipse plugin in two phases a lot of the intelligence of the
eclipse plugin can be deleted. Because in many (now) special cases , it is
"just" a case of
- creating an eclipse source directory (not used by Maven)
- extract all the source and resources in the packaged jar in that directory
excluding all already available (=all generated stuff)
- e.v. adapting the files to eclipse needs
But i know this would be a major change of concept. still WDYT
> application.xml is not the correct and not the same in the EAR package
> ---
>
> Key: MECLIPSE-354
> URL: http://jira.codehaus.org/browse/MECLIPSE-354
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: RAD support
>Affects Versions: 2.4
> Environment: Windows XP; JDK1.4; RAD6
>Reporter: Olivier Chaumont
>
> When I execute mvn eclipse:rad command on an EAR maven project, the eclipse
> plugin generate the file META-INF/application.xml.
> To generate the content of this file the eclipse plugin read the config of
> the "maven-ear-plugin" in the pom.xml.
> Below the config of the "maven-ear-plugin":
>
> org.apache.maven.plugins
> maven-ear-plugin
>
> Â Â ${project.name}
> Â Â lib
>
> Â Â true
> Â Â ${basedir}/target
> Â Â
>
> Â
> Â Â Â com.bnpparibas.assurance.ic
> Â Â Â mypres
>
> Â Â Â mypres1
> Â Â Â mypres-1.0.war
> Â
>
> Â
> Â Â Â com.bnpparibas.assurance.ic
> Â Â Â mypres
>
> Â Â Â mypres2
> Â Â Â mypres-1.0.war
> Â
>
> Â
> Â Â Â com.bnpparibas.assurance.ic
> Â Â Â Ref_SERV_EJB
> Â Â Â myEJB.jar
> Â
> Â
> Â ${project.name}-${project.version}
> ;
>
> The generated application.xml file with mvn eclipse:rad :
>
> http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
> xmlns="http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; id="Application_ID"
> version="1.4">
>
> myEAR2
>
> Ref_SERV_EJB.jar
>
>
>
> mypres.war
> mypres1
>
>
>
> The generated application.xml file with mvn install:
>
>"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
> "http://java.sun.com/dtd/application_1_3.dtd";>
>
> myEAR2
>
>
> mypres-1.0.war
> mypres1
>
>
>
>
> mypres-1.0.war
> mypres2
>
>
>
> myEJB.jar
>
>
> The problem is that the application.xml generated by eclipse plugin and the
> one generated by ear plugin is not the same, and I think ear plugin is good
> one:
> 1- There is one web module in the application.xml file and not two like in
> the pom.xml file.
> 2- The name of the web-uri and the ejb module is not the value of the
> bundleFileName, bit the value of the artifactId.
> 3- The doctype is not the same (it is possible to configure it?)
> Also, I think it would be better that maven-eclipse-plugin doesn't generate
> the application.xml file because maven-ear-plugin do the same thing. Perhaps
> it is possible that maven-eclipse-plugin call maven-ear-plugin code to
> generate it, and so we are sure that the files will be the same.
> Thanks a lot.
> Olivier
--
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/jir
[jira] Commented: (MECLIPSE-334) Add a rule that determined artifacts will be always recognized as reactor projects
[ http://jira.codehaus.org/browse/MECLIPSE-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115166 ] Richard van Nieuwenhoven commented on MECLIPSE-334: --- yes, i think it is too dangerous and would create a lot "why doesn't it work" questions. The wish to include whole bunches of projects with same groupId's sounds like the need for modularization. Can you elaborate a little more why you need this? > Add a rule that determined artifacts will be always recognized as reactor > projects > -- > > Key: MECLIPSE-334 > URL: http://jira.codehaus.org/browse/MECLIPSE-334 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Affects Versions: 2.4 >Reporter: Martin Zeltner > Attachments: patch_maven-eclipse-plugin-r587020.patch > > Original Estimate: 10 minutes > Remaining Estimate: 10 minutes > > I've implemented a feature that determined artifacts will be always > recognized as reactor projects, doesn't matter where the "mvn > eclipse:eclipse" is executed. The idea is to set a list of groupId prefixes. > Example: > [code] > > org.apache.maven.plugins > maven-eclipse-plugin > > > ch.elca., > org.sp, > net.sf > > > > [/code] > All artifacts where the groupId starts with "ch.elca.", "org.sp" or "net.sf" > will be handled as reactor projects. > Cheers, > Martin -- 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
[jira] Commented: (MECLIPSE-312) WebContent folder linked to webapp folder is not generated
[
http://jira.codehaus.org/browse/MECLIPSE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115010
]
Richard van Nieuwenhoven commented on MECLIPSE-312:
---
The "/WebContent " is not fixed anymore in WTP (in very early versions it was!).
Best practice is to use the maven default (defined by the maven-war-plugin)
which is ${basedir}/src/main/webapp
The eclipse plugin will get the setting from the maven-war-plugin and configure
it for eclipse wtp, so no need for the webcontent link!
If you really!! want another web content directory you will have to configure
the maven-war-plugin!
> WebContent folder linked to webapp folder is not generated
> --
>
> Key: MECLIPSE-312
> URL: http://jira.codehaus.org/browse/MECLIPSE-312
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
> Environment: Maven 2, Linux & Windows
>Reporter: Cyril JOUI
> Attachments: EclipseProjectWriter.java, EclipseWtpComponentWriter.java
>
>
> When I generate a eclipse project with wtpsupport, maven plugin doesn't
> create a WebContent folder in web project.
> Configuration part in eclipse is:
> in org.eclipse.wst.common.component:
>
> and /WebContent is refered by:
>
> WebContent
> 2
>
> //rpf/dev/modules/rpf-gateway/src/main/webapp
>
> in .project file
> I made modification on EclipseProjectWriter:
> // if war project (add WebContent => webapp)
> if ("war".equals(config.getProject().getPackaging())) {
> addLink (writer, "WebContent",
> config.getProject().getBasedir() +
> "/src/main/webapp", LINK_TYPE_DIRECTORY);
> }
> And
> writer.startElement( ELT_WB_RESOURCE );
> writer.addAttribute( ATTR_DEPLOY_PATH, "/" ); //$NON-NLS-1$
> writer.addAttribute( ATTR_SOURCE_PATH, "/WebContent");
> /*
> writer.addAttribute( ATTR_SOURCE_PATH, IdeUtils
> .toRelativeAndFixSeparator(
> config.getEclipseProjectDirectory(), warSourceDirectory, false ) );
> */
> writer.endElement();
> in EclipseWtpComponentWriter
--
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
[jira] Commented: (MECLIPSE-354) application.xml is not the correct and not the same in the EAR package
[
http://jira.codehaus.org/browse/MECLIPSE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114894
]
Richard van Nieuwenhoven commented on MECLIPSE-354:
---
This type of problem needs some discussion!
- The real problem is that "some" maven plugin generates a file (from
MANIFEST.MF over ejb-jar.xml to application.xml) in a very late life cycle
phase (package).
- eclipse (wtp or rad or other) needs to have the same file in a very early
life cycle phase (resources) and it must be modified to the tool.
normally some id's or references are included to connect the file to some
other configuration file
- eclipse (wtp or rad or other) needs the file in a different (sometimes even
fixed) position
To do this we need a change of concept!
- the life cycle phase the eclipse plugin runs must be changed to package
But this means that a project must be packageable to attach it to eclipse.
In the hole i think we need to split the plugin
- one in the resources phase to get not packageable projects in eclipse
- one that realy integerates itself in the packageing phase and can use the
generated files of the other plugins.
> application.xml is not the correct and not the same in the EAR package
> ---
>
> Key: MECLIPSE-354
> URL: http://jira.codehaus.org/browse/MECLIPSE-354
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: RAD support
>Affects Versions: 2.4
> Environment: Windows XP; JDK1.4; RAD6
>Reporter: Olivier Chaumont
>
> When I execute mvn eclipse:rad command on an EAR maven project, the eclipse
> plugin generate the file META-INF/application.xml.
> To generate the content of this file the eclipse plugin read the config of
> the "maven-ear-plugin" in the pom.xml.
> Below the config of the "maven-ear-plugin":
>
> org.apache.maven.plugins
> maven-ear-plugin
>
> Â Â ${project.name}
> Â Â lib
>
> Â Â true
> Â Â ${basedir}/target
> Â Â
>
> Â
> Â Â Â com.bnpparibas.assurance.ic
> Â Â Â mypres
>
> Â Â Â mypres1
> Â Â Â mypres-1.0.war
> Â
>
> Â
> Â Â Â com.bnpparibas.assurance.ic
> Â Â Â mypres
>
> Â Â Â mypres2
> Â Â Â mypres-1.0.war
> Â
>
> Â
> Â Â Â com.bnpparibas.assurance.ic
> Â Â Â Ref_SERV_EJB
> Â Â Â myEJB.jar
> Â
> Â
> Â ${project.name}-${project.version}
> ;
>
> The generated application.xml file with mvn eclipse:rad :
>
> http://java.sun.com/xml/ns/j2ee
> http://java.sun.com/xml/ns/j2ee/application_1_4.xsd";
> xmlns="http://java.sun.com/xml/ns/j2ee";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; id="Application_ID"
> version="1.4">
>
> myEAR2
>
> Ref_SERV_EJB.jar
>
>
>
> mypres.war
> mypres1
>
>
>
> The generated application.xml file with mvn install:
>
>"-//Sun Microsystems, Inc.//DTD J2EE Application 1.3//EN"
> "http://java.sun.com/dtd/application_1_3.dtd";>
>
> myEAR2
>
>
> mypres-1.0.war
> mypres1
>
>
>
>
> mypres-1.0.war
> mypres2
>
>
>
> myEJB.jar
>
>
> The problem is that the application.xml generated by eclipse plugin and the
> one generated by ear plugin is not the same, and I think ear plugin is good
> one:
> 1- There is one web module in the application.xml file and not two like in
> the pom.xml file.
> 2- The name of the web-uri and the ejb module is not the value of the
> bundleFileName, bit the value of the artifactId.
> 3- The doctype is not the same (it is possible to configure it?)
> Also, I think it would be better that maven-eclipse-plugin doesn't generate
> the application.xml file because maven-ear-plugin do the same thing. Perhaps
> it is possible that maven-eclipse-plugin call maven-ear-plugin code to
> generate it, and so we are sure that the files will be the same.
> Thanks a lot.
> Olivier
--
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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114677 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- these two include the complete patch on the today trunk R597676 - MECLIPSE-344.patch - MECLIPSE-344.tgz the others are old and included. > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: dependency resolution >Reporter: Richard van Nieuwenhoven > Attachments: MECLIPSE-344.patch, MECLIPSE-344.tgz, > workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Updated: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-344: -- Attachment: MECLIPSE-344.tgz MECLIPSE-344.patch updated the patch to include test cases for the workspace code! included is now: - connect to artefact's available in the workspace as projects - use the correct default class path container depending on the compiler - exclude artefact's from using project references (by removing them from the workspace) I did not have the time to refactor the workspace reader stuff... Creating tests took a lot of time.. But i think we should split the workspace configuration class in a class not eclipse specific and an eclipse specific subclass. > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: dependency resolution >Reporter: Richard van Nieuwenhoven > Attachments: MECLIPSE-344.patch, MECLIPSE-344.tgz, > workspace-new-files.tgz, workspace.patch, workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114636 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- a good question! the problem is that the eclipse.workspace variable is used for something different. And i didn't want to break the old behavior! Could you check if it it is still needed? maybe even deprecate it? > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: dependency resolution >Reporter: Richard van Nieuwenhoven > Attachments: workspace-new-files.tgz, workspace.patch, > workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Commented: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.
[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114539 ] Richard van Nieuwenhoven commented on MECLIPSE-172: --- yes thats true, but with MECLIPSE-344 and the workspace location know it not that difficult, just wrote a good working version based on MECLIPSE-344! The only problem is ... test cases because eclipse writes absolute paths in its configuration files, and some of the files are binary. That makes writing a MOCK workspace directory for testing rather difficult. but possible. IMPORTANT: Could you people here send me your ".metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.launching.prefs" files and the maven-compiler-plugin configuration from your pom,xml that way i can write a representative test case. Arnaud: Could you move the WorkspaceConfiguration bean class from the writer.workspace package to the plugin ide package (i do not know how to do that in a patch). This way i can reuse it for a workspace reader! > Don't add Default ClasspathContainer if a alternate JRE or a "Execution > Environment" is configured as ClasspathContainer. > - > > Key: MECLIPSE-172 > URL: http://jira.codehaus.org/browse/MECLIPSE-172 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.2, 2.3 > Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP >Reporter: Markus Grieder >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: EclipsePlugin.java.patch, > MECLIPSE-172-fix-and-test.patch, patch.txt > > > If have a Eclipse Workspace with Projects where some use Java 1.5 (Default > JRE) and some Java 1.3 > For 1.3-Projects i have configured the following ClasspathContainer: > > org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre > > This generates in ".classpath": > > path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre"/> > Which is wrong, because the Default JRE is Java 1.5, but the Project should > only see Java 1.3-Libraries and not both. > -> The Default ClasspathContainer should only be added if no JRE_CONTAINER > (alternate JRE or a Execution Environment (>=Eclipse 3.2)) was specified. The > attached Patch replace the "contains"-match with a "starts-with"-match, which > only adds the Default ClasspathContainer if no classpathContainer is > configured which starts with the "JRE_CONTAINER"-Path. -- 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
[jira] Commented: (MECLIPSE-172) Don't add Default ClasspathContainer if a alternate JRE or a "Execution Environment" is configured as ClasspathContainer.
[ http://jira.codehaus.org/browse/MECLIPSE-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114452 ] Richard van Nieuwenhoven commented on MECLIPSE-172: --- To really fix this bug, should the eclipse plugin not read the workspace file: .metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.jdt.launching.prefs and select from there the JRE to use, depending on the configured executable in the maven-compiler-plugin? > Don't add Default ClasspathContainer if a alternate JRE or a "Execution > Environment" is configured as ClasspathContainer. > - > > Key: MECLIPSE-172 > URL: http://jira.codehaus.org/browse/MECLIPSE-172 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug >Affects Versions: 2.2, 2.3 > Environment: Maven 2.0.4, Eclipse 3.2.1, Windows XP >Reporter: Markus Grieder > Attachments: EclipsePlugin.java.patch, > MECLIPSE-172-fix-and-test.patch, patch.txt > > > If have a Eclipse Workspace with Projects where some use Java 1.5 (Default > JRE) and some Java 1.3 > For 1.3-Projects i have configured the following ClasspathContainer: > > org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre > > This generates in ".classpath": > > path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/server_jre"/> > Which is wrong, because the Default JRE is Java 1.5, but the Project should > only see Java 1.3-Libraries and not both. > -> The Default ClasspathContainer should only be added if no JRE_CONTAINER > (alternate JRE or a Execution Environment (>=Eclipse 3.2)) was specified. The > attached Patch replace the "contains"-match with a "starts-with"-match, which > only adds the Default ClasspathContainer if no classpathContainer is > configured which starts with the "JRE_CONTAINER"-Path. -- 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
[jira] Updated: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-344: -- Attachment: workspace_with_limit.patch There are a few jira's about exluding some projects from using project references. Now this is rather easy done if the workspace is known. I extended the patch to include the option: -Declipse.limitProjectReferencesToWorkspace=true This option will force projects that are not in the workspace but in the reactor to be used as jars. this patch includes the original patch! > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: dependency resolution >Reporter: Richard van Nieuwenhoven > Attachments: workspace-new-files.tgz, workspace.patch, > workspace_with_limit.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Commented: (MECLIPSE-158) Add the ability to selectively treat a referenced project as a local repository file
[
http://jira.codehaus.org/browse/MECLIPSE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114235
]
Richard van Nieuwenhoven commented on MECLIPSE-158:
---
see: http://maven.apache.org/guides/introduction/introduction-to-profiles.html
for a good explanation how to make and activate profiles.
the module with with XML beans moves to the modules section in your profile,
but i must note that i do not like the notion that the ide control's my pom
structure
As soon as MECLIPSE-344 in integrated, it is possible to add an option that
only projects already available in the workspace are directly referenced, that
would solve the problem.
> Add the ability to selectively treat a referenced project as a local
> repository file
>
>
> Key: MECLIPSE-158
> URL: http://jira.codehaus.org/browse/MECLIPSE-158
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: multiproject
>Affects Versions: 2.2
>Reporter: Tim O'Brien
>
> The issue is that I have a large project with many interdependent submodules.
> One of the submodules uses XML Beans to generate a set of objects from an
> XML Schema. This works perfectly, but Eclipse has a problem with the class
> names used in XMLBeans, and I have to close that particular project for
> Eclipse not to complain. But, if I close that project, all of the projects
> that depend on it directly (through a referenced project), then complain that
> they are missing a referenced project.
> The solution is to relate the project via the local repository (M2_REPO/...)
> not via a project reference, but in EclipseClasspathWriter, all projects
> available via the reactor are treated as referenced projects:
> if ( dep.isReferencedProject() && !config.isPde() )
> {
> path = "/" + dep.getArtifactId(); //$NON-NLS-1$
> kind = ATTR_SRC;
> }
> One solution would be to not use project references, but the problem only
> happens with specific projects, and I want to be able to selectively mark
> dependencies as not being referenced.
> Something as simple as, this:
>
>
> blah
> blah
>
>
> Where the dependency identified by that groupId and artifactId would be
> treated not as a direct project reference but as a link to the local
> repository.
> Does that make any sense?
--
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
[jira] Issue Comment Edited: (MECLIPSE-32) Allow for forcing the creation of direct project references for dependencies
[ http://jira.codehaus.org/browse/MECLIPSE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114032 ] Richard van Nieuwenhoven edited comment on MECLIPSE-32 at 11/16/07 5:37 AM: MECLIPSE-344 is an other solution to connect workspace projects was: an other solution to connect workspace projects > Allow for forcing the creation of direct project references for dependencies > > > Key: MECLIPSE-32 > URL: http://jira.codehaus.org/browse/MECLIPSE-32 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject >Affects Versions: 2.0 >Reporter: Barry Kaplan > > For some thirdparty dependencies, it is common (for me at least) that an > eclipse project for that dependency does/will exist in the workspace. It > would be nice if dependencies in eclipse projects can be forced to use a > direct project reference. eg: > > backport-util-concurrent > backport-util-concurrent > 2.0_01_pd > runtime > > > > > Where can be: > - 'project' -- always create a project reference > - 'jar' -- always create a jar reference as in MNG-955 > - 'auto' -- the behavior prior to MNG-955 -- 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
[jira] Commented: (MECLIPSE-344) connecting existing workspace artifact-projects
[ http://jira.codehaus.org/browse/MECLIPSE-344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113804 ] Richard van Nieuwenhoven commented on MECLIPSE-344: --- typo the property is -Declipse.workspaceToConnect=... > connecting existing workspace artifact-projects > --- > > Key: MECLIPSE-344 > URL: http://jira.codehaus.org/browse/MECLIPSE-344 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: dependency resolution >Reporter: Richard van Nieuwenhoven > Attachments: workspace-new-files.tgz, workspace.patch > > > This patch enables you to specify your workspace, and all dependent artefacts > that are available in your eclipse-workspace will be attached as project > references even if they are not in the reactor. > the property can be set with -DworkspaceToConnect=. > I did not have the time to create Test cases but, i maybe someone can help > with that! > The patch is based on the MECLIPSE-333 branch. > as usual the new files are in the extra tgz. -- 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
[jira] Created: (MECLIPSE-344) connecting existing workspace artifact-projects
connecting existing workspace artifact-projects --- Key: MECLIPSE-344 URL: http://jira.codehaus.org/browse/MECLIPSE-344 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Components: dependency resolution Reporter: Richard van Nieuwenhoven Attachments: workspace-new-files.tgz, workspace.patch This patch enables you to specify your workspace, and all dependent artefacts that are available in your eclipse-workspace will be attached as project references even if they are not in the reactor. the property can be set with -DworkspaceToConnect=. I did not have the time to create Test cases but, i maybe someone can help with that! The patch is based on the MECLIPSE-333 branch. as usual the new files are in the extra tgz. -- 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
[jira] Commented: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112891 ] Richard van Nieuwenhoven commented on MECLIPSE-213: --- The NPE is fixed (with tests) in the patch for MECLIPSE-333. I am looking into a way to detect current projects / artifacts in the workspace, but for now use the multi module builds for them. If they are not an option for your case, use a "build" pom that references all projects in your workspace (this way they will be linked together) . > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven >Assignee: Brian Fox > Fix For: 2.5 > > Attachments: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch, > maven-eclipse-plugin-2.3-PATCH-2007-03-08.tgz, > maven-eclipse-plugin-R494407.patch, maven-eclipse-plugin.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112625 ] Richard van Nieuwenhoven commented on MECLIPSE-333: --- Another question? should we report an error if the "archiveClasses" setting in the war configuration or war overriding was activated? because wtp-2/maven-eclipse-plugin can not handle them "yet". > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-eclipse-plugin_only_new.tar.gz, > maven-eclipse-plugin_only_new_2.tar.tgz, > wtp-2.0-and-more-2.5-SNAPSHOT-2.patch, wtp-2.0-and-more-2.5-SNAPSHOT-3.patch, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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
[jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112624 ] Richard van Nieuwenhoven commented on MECLIPSE-333: --- They should be applyable with "patch -p0". I used diff -u to create them. The code style must have been wrong before, because i used the eclipse formatter with the "Maven code style" settings. So after you apply the patches you could apply the Formatter / Clean-Up and the Organize imports to the hole project! When you do not succeed with patches 2/3 commit the wtp-2 branch with patch-1 and i will generate a "svn diff" patch for them. > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.4 >Reporter: Richard van Nieuwenhoven >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-eclipse-plugin_only_new.tar.gz, > maven-eclipse-plugin_only_new_2.tar.tgz, > wtp-2.0-and-more-2.5-SNAPSHOT-2.patch, wtp-2.0-and-more-2.5-SNAPSHOT-3.patch, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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
[jira] Updated: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-333: -- Attachment: wtp-2.0-and-more-2.5-SNAPSHOT-3.patch maven-eclipse-plugin_only_new_2.tar.tgz wtp-2.0-and-more-2.5-SNAPSHOT-2.patch here are the next incremental patches, with some fixes / improvements and tests > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven >Assignee: Brian Fox > Attachments: maven-eclipse-plugin_only_new.tar.gz, > maven-eclipse-plugin_only_new_2.tar.tgz, > wtp-2.0-and-more-2.5-SNAPSHOT-2.patch, wtp-2.0-and-more-2.5-SNAPSHOT-3.patch, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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
[jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_111548 ] Richard van Nieuwenhoven commented on MECLIPSE-333: --- as far as i know one should not make a dependency between war's. Does the war plugin handle such things at all? When i need such a requirement i use a system like tobago uses. a jar resource that will be extracted in the dependent war resource . As far as i know WTP has no other way to split the WebContent into to directories or even in two modules/projects. The classes of a dependent jar will never be exploded in the WEB-INF/classes directory. WTP will package your dependent jar into WEB-INF/lib, as it should! and as maven does! WTP will also do the hot deployment of your changed classes during debugging so no need of copying classes. When it can't update them just do a republish. regards, Ritchie > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven >Assignee: Brian Fox > Attachments: maven-eclipse-plugin_only_new.tar.gz, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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
[jira] Commented: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
[ http://jira.codehaus.org/browse/MECLIPSE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110621 ] Richard van Nieuwenhoven commented on MECLIPSE-333: --- you will have to checkout the sources and apply the patch to it (and add the additional files from the tar) > WTP-2.0 support with howto apt, refactoring and contextroot handling > - > > Key: MECLIPSE-333 > URL: http://jira.codehaus.org/browse/MECLIPSE-333 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.5 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin_only_new.tar.gz, > wtp-2.0-and-more-2.5-SNAPSHOT.patch > > > This patch contains: > - WTP.2.0 support for ear and war's (includes MECLIPSE-264) > - context root handling very much improved > (war takes configuration from the ear, if available) > - refactoring (constant usage, foreign plug-in access centralized) > - a detailed description how we use maven-2 with WTP in multi module projects > - testing code included > the patch is attached, together with a tar with all the new files. -- 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
[jira] Closed: (MECLIPSE-163) eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
[ http://jira.codehaus.org/browse/MECLIPSE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven closed MECLIPSE-163. - Resolution: Fixed resolved with MECLIPSE-213 > eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes > -- > > Key: MECLIPSE-163 > URL: http://jira.codehaus.org/browse/MECLIPSE-163 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 >Reporter: Richard van Nieuwenhoven > Fix For: 2.5 > > Attachments: maven-eclipse-plugin-R448503.patch > > > we needed eclipse:eclipse to function with wtp 1.5 but we had some problems > with the 2.3 SNAPSHOT version. > 1) create a seperate eardefinition for eclipse > this makes it possible to include the reactor modules as projects (not > as versioned packages) > 2) enable ejb3 projects ejb3 > 3) module types in the components file corrected (war ejb modules included > now with module-reference) > 4) created a manifest-writer to write a eclipse/wtp compatible manifest for > module dependencies > this sould probably be done in a generated resources directory, but for > now i put it in src/main/resources > i will include the patch file as an attachment. Any one interested can > include the sources in the SNAPSHOT. > i use the patch for jboss and it works good, ejb(3) and web deployment is now > functional from scratch. -- 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
[jira] Commented: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110487 ] Richard van Nieuwenhoven commented on MECLIPSE-264: --- the test will work when you add the (partly binary) data from the tar. > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.4 >Reporter: Geir Pettersen >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-264.patch, MECLIPSE-264-NEW.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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
[jira] Commented: (MECLIPSE-264) Support for WTP2.0
[ http://jira.codehaus.org/browse/MECLIPSE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110451 ] Richard van Nieuwenhoven commented on MECLIPSE-264: --- new patch with tests, documentation, other bug-fixes and some extra functionality like context root detection is available here -> MECLIPSE-333 > Support for WTP2.0 > -- > > Key: MECLIPSE-264 > URL: http://jira.codehaus.org/browse/MECLIPSE-264 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.4 >Reporter: Geir Pettersen >Assignee: Arnaud Heritier > Fix For: 2.5 > > Attachments: maven-264.patch, MECLIPSE-264-NEW.patch > > > As far as I can see this plugin only supports WTP version 1.0 and 1.5. while > WTP 2.0 is already released in milestone 6 -- 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
[jira] Created: (MECLIPSE-333) WTP-2.0 support with howto apt, refactoring and contextroot handling
WTP-2.0 support with howto apt, refactoring and contextroot handling - Key: MECLIPSE-333 URL: http://jira.codehaus.org/browse/MECLIPSE-333 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: multiproject, WTP support Affects Versions: 2.5 Reporter: Richard van Nieuwenhoven Attachments: maven-eclipse-plugin_only_new.tar.gz, wtp-2.0-and-more-2.5-SNAPSHOT.patch This patch contains: - WTP.2.0 support for ear and war's (includes MECLIPSE-264) - context root handling very much improved (war takes configuration from the ear, if available) - refactoring (constant usage, foreign plug-in access centralized) - a detailed description how we use maven-2 with WTP in multi module projects - testing code included the patch is attached, together with a tar with all the new files. -- 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
[jira] Issue Comment Edited: (MECLIPSE-242) RAD goal: missing lib-modules in .websettings
[ http://jira.codehaus.org/browse/MECLIPSE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108522 ] Richard van Nieuwenhoven edited comment on MECLIPSE-242 at 9/28/07 7:39 AM: That is strange! can it be that you forgot the M2_HOME variable before starting the build? i made the following steps: - delete local reposetory - delete the project localy - svn checkout http://svn.apache.org/repos/asf/maven/plugins/branches/MECLIPSE-242 - export M2_HOME=/tmp/maven-2.0.7 - export MAVEN_HOME=/tmp/maven-2.0.7 - cd MECLIPSE-242 - mvn install and the result was --- Results : Tests run: 67, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 8 minutes 6 seconds [INFO] Finished at: Fri Sep 28 14:02:30 CEST 2007 [INFO] Final Memory: 10M/24M [INFO] --- was: That is strange! can it be that you forgot the M2_HOME variable before starting the build? i did: - delele local reposetory - delete the project localy - svn checkout http://svn.apache.org/repos/asf/maven/plugins/branches/MECLIPSE-242 - export M2_HOME=/tmp/maven-2.0.7 - export MAVEN_HOME=/tmp/maven-2.0.7 - cd MECLIPSE-242 - mvn install and the result was --- Results : Tests run: 67, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 8 minutes 6 seconds [INFO] Finished at: Fri Sep 28 14:02:30 CEST 2007 [INFO] Final Memory: 10M/24M [INFO] --- > RAD goal: missing lib-modules in .websettings > - > > Key: MECLIPSE-242 > URL: http://jira.codehaus.org/browse/MECLIPSE-242 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support >Affects Versions: 2.3, 2.4 > Environment: IBM Rational Application Developer 6.0.x >Reporter: Klaus Brunner > Attachments: addedTestFiles.patch, addedTestFiles.tgz, > MECLIPSE-242-for-2.5-SNAPSHOT.patch, RadWebSettingsWriter.java > > > The eclipse:rad goal does not currently write the lib-modules element of the > .websettings file. When developing with RAD and WAS, this results in > dependent projects' code not being packaged and deployed as part of the WAR > by the RAD build and deploy process. This applies to project dependencies > only. > Adapted version of RadWebSettingsWriter.java is attached. -- 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
[jira] Commented: (MECLIPSE-242) RAD goal: missing lib-modules in .websettings
[ http://jira.codehaus.org/browse/MECLIPSE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_108522 ] Richard van Nieuwenhoven commented on MECLIPSE-242: --- That is strange! can it be that you forgot the M2_HOME variable before starting the build? i did: - delele local reposetory - delete the project localy - svn checkout http://svn.apache.org/repos/asf/maven/plugins/branches/MECLIPSE-242 - export M2_HOME=/tmp/maven-2.0.7 - export MAVEN_HOME=/tmp/maven-2.0.7 - cd MECLIPSE-242 - mvn install and the result was --- Results : Tests run: 67, Failures: 0, Errors: 0, Skipped: 0 [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 8 minutes 6 seconds [INFO] Finished at: Fri Sep 28 14:02:30 CEST 2007 [INFO] Final Memory: 10M/24M [INFO] --- > RAD goal: missing lib-modules in .websettings > - > > Key: MECLIPSE-242 > URL: http://jira.codehaus.org/browse/MECLIPSE-242 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support >Affects Versions: 2.3, 2.4 > Environment: IBM Rational Application Developer 6.0.x >Reporter: Klaus Brunner > Attachments: addedTestFiles.patch, addedTestFiles.tgz, > MECLIPSE-242-for-2.5-SNAPSHOT.patch, RadWebSettingsWriter.java > > > The eclipse:rad goal does not currently write the lib-modules element of the > .websettings file. When developing with RAD and WAS, this results in > dependent projects' code not being packaged and deployed as part of the WAR > by the RAD build and deploy process. This applies to project dependencies > only. > Adapted version of RadWebSettingsWriter.java is attached. -- 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
[jira] Updated: (MECLIPSE-242) RAD goal: missing lib-modules in .websettings
[ http://jira.codehaus.org/browse/MECLIPSE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-242: -- Attachment: addedTestFiles.tgz addedTestFiles.patch The old svn problem ... i forgot to include the added files (pom and empty resource file of the test project) just retested it, all test ok now. the added files as patch and as tgz on the branch. > RAD goal: missing lib-modules in .websettings > - > > Key: MECLIPSE-242 > URL: http://jira.codehaus.org/browse/MECLIPSE-242 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support >Affects Versions: 2.3, 2.4 > Environment: IBM Rational Application Developer 6.0.x >Reporter: Klaus Brunner > Attachments: addedTestFiles.patch, addedTestFiles.tgz, > MECLIPSE-242-for-2.5-SNAPSHOT.patch, RadWebSettingsWriter.java > > > The eclipse:rad goal does not currently write the lib-modules element of the > .websettings file. When developing with RAD and WAS, this results in > dependent projects' code not being packaged and deployed as part of the WAR > by the RAD build and deploy process. This applies to project dependencies > only. > Adapted version of RadWebSettingsWriter.java is attached. -- 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
[jira] Updated: (MECLIPSE-242) RAD goal: missing lib-modules in .websettings
[ http://jira.codehaus.org/browse/MECLIPSE-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-242: -- Attachment: MECLIPSE-242-for-2.5-SNAPSHOT.patch This patch for the 2.5-SNAPSHOT trunk includes the necessary changes! The patch also includes a test for the fix. > RAD goal: missing lib-modules in .websettings > - > > Key: MECLIPSE-242 > URL: http://jira.codehaus.org/browse/MECLIPSE-242 > Project: Maven 2.x Eclipse Plugin > Issue Type: Bug > Components: RAD support >Affects Versions: 2.3, 2.4 > Environment: IBM Rational Application Developer 6.0.x >Reporter: Klaus Brunner > Attachments: MECLIPSE-242-for-2.5-SNAPSHOT.patch, > RadWebSettingsWriter.java > > > The eclipse:rad goal does not currently write the lib-modules element of the > .websettings file. When developing with RAD and WAS, this results in > dependent projects' code not being packaged and deployed as part of the WAR > by the RAD build and deploy process. This applies to project dependencies > only. > Adapted version of RadWebSettingsWriter.java is attached. -- 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
[jira] Commented: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106268 ] Richard van Nieuwenhoven commented on MECLIPSE-213: --- Just tested it on 3 different projects, looks very good! all worked! Do you need more tests before releasing the changes to the 2.5-SNAPSHOT ? Or should i wait for your 2.5-SNAPSHOT update? > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven >Assignee: Brian Fox > Attachments: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch, > maven-eclipse-plugin-2.3-PATCH-2007-03-08.tgz, > maven-eclipse-plugin-R494407.patch, maven-eclipse-plugin.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Updated: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-213: -- Attachment: maven-eclipse-plugin.patch re patched for version 2.5-SNAPSHOT now including an initial test case (i will write more detailed asserts in the next 2 weeks). But because these were a lot of changes, i do not want to do them again on a changed trunk.. my changes in short * an IdeDependency now knows the name of the eclipse project if it is in the reactor. * an IdeDependency now has an equals that supports multiple system dependencies to the same file * an IdeDependency now knows if a system dependency is outside or inside the reactor some work has to be done here how to detect it correctly * duplicate dependencies (to the same file) are not included in the classpath * an eclipse application.xml can be generated in a target/eclipseEar directory this resolves the problem of wtp including far to mutch in the ear * eclipse manifests are written so that they do not interfere with the maven manifest's in a extra resource directory not known by maven, i commented out the code that uses that standard pexus stuff to generate a manifest because that requires a dependency resolution that failes in a lot of tests.. * changed multible places where the getArtifactId() is used instead of getEclipseProjectName() * the ComponentWriter now uses the deployPath for the ear plugin definition * the ComponentWriter will not include jars outside the reactor in the component (this is specially for dependencies on jars of an application server) Please report me if the patch has any problems that prohibiting an apply. So that i correct it immediately. Does anyone has tips for the manifest generation problems? Ritchie > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch, > maven-eclipse-plugin-2.3-PATCH-2007-03-08.tgz, > maven-eclipse-plugin-R494407.patch, maven-eclipse-plugin.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Updated: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-213: -- Attachment: maven-eclipse-plugin-2.3-PATCH-2007-03-08.tgz This is the pre build version of the patch for anyone who wants to try it. > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch, > maven-eclipse-plugin-2.3-PATCH-2007-03-08.tgz, > maven-eclipse-plugin-R494407.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Updated: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard van Nieuwenhoven updated MECLIPSE-213: -- Attachment: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch this is the patch that i use to * create eclipse- only manifests * to define the eclipse lib directory equal to the maven ear lib directory * to generate the project names as artifact names (including version) * to generate a WTP able application.xml to activate the extentions add: * -Declipse.wtpmanifest=true * -Declipse.wtpapplicationxml=true * -Declipse.addVersionToProjectName=true > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin-2.3-CFC-2007-03-08.patch, > maven-eclipse-plugin-R494407.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Commented: (MECLIPSE-163) eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
[ http://jira.codehaus.org/browse/MECLIPSE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90115 ] Richard van Nieuwenhoven commented on MECLIPSE-163: --- not realy, but i have made a new one based on the released eclipse 2.3 version see MECLIPSE-213 > eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes > -- > > Key: MECLIPSE-163 > URL: http://jira.codehaus.org/browse/MECLIPSE-163 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: multiproject, WTP support >Affects Versions: 2.3 >Reporter: Richard van Nieuwenhoven > Fix For: 2.4 > > Attachments: maven-eclipse-plugin-R448503.patch > > > we needed eclipse:eclipse to function with wtp 1.5 but we had some problems > with the 2.3 SNAPSHOT version. > 1) create a seperate eardefinition for eclipse > this makes it possible to include the reactor modules as projects (not > as versioned packages) > 2) enable ejb3 projects ejb3 > 3) module types in the components file corrected (war ejb modules included > now with module-reference) > 4) created a manifest-writer to write a eclipse/wtp compatible manifest for > module dependencies > this sould probably be done in a generated resources directory, but for > now i put it in src/main/resources > i will include the patch file as an attachment. Any one interested can > include the sources in the SNAPSHOT. > i use the patch for jboss and it works good, ejb(3) and web deployment is now > functional from scratch. -- 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
[jira] Commented: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90114 ] Richard van Nieuwenhoven commented on MECLIPSE-213: --- Currently i use the mavenarchiver to generate a manifest. The problem is that wtp needs a manifest (with classpath) for multiy module projects. (And we do not want it to intrefere with the one generated by the jar plugin). The mavenarchiver can only be used if the jar names include the version, that is not the normal behavior of the maven-eclipse-plugin, i now made a extra option to change the project name to the "maven compatible" name with version. i can post this patch but it is based on the realeased 2.3 version. At the moment i do not have the time to diliver a patch based on the current SNAPSHOT. when you want it please report it here, because than i will make some checks first. > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin-R494407.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Commented: (MJAVADOC-97) enable internal/external dependency references as links
[ http://jira.codehaus.org/browse/MJAVADOC-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_90113 ] Richard van Nieuwenhoven commented on MJAVADOC-97: -- i know it is not the best solution but i needed a solution fast, any volunteers on beatifying this "nessesary" feature. maybe somewone can comine the effort with the xref generation, to solve the same problem for both projects > enable internal/external dependency references as links > > > Key: MJAVADOC-97 > URL: http://jira.codehaus.org/browse/MJAVADOC-97 > Project: Maven 2.x Javadoc Plugin > Issue Type: New Feature >Affects Versions: 2.1 >Reporter: Richard van Nieuwenhoven >Priority: Minor > Attachments: maven-javadoc-plugin-2.1.patch > > > This patch enables the java doc plugin to autmaticaly connect the dependent > javadoc pages as links. > There is no more need to add links in your pom's for internal and external > maven projects. > The plugin resolves the dependencies and adds the defined project url's > extended with "/apidocs" to the links in the plugin. > TODO: a warning occures when the project has no javadocs (or no maven > generated javadoc on its homepage) .. -- 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
[jira] Commented: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=comments#action_85355 ] Richard van Nieuwenhoven commented on MECLIPSE-137: --- as far as i can see thes plugin is integrated in maven-eclipse-plugin-2.3 so use that one > Developed RAD-6 Plugin Extention > > > Key: MECLIPSE-137 > URL: http://jira.codehaus.org/browse/MECLIPSE-137 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Richard van Nieuwenhoven > Assigned To: John Casey > Attachments: maven-rad-plugin-WebContent.zip, > maven-rad-plugin.tar.gz, maven-rad-plugin.zip, > MECLIPSE-137-maven-eclipse-plugin.patch, MECLIPSE-137-maven-rad-plugin.zip > > > I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) > extention to the eclipse plugin. > It supports J2EE projects with the websphere development envorment, supported > are > - EJB projects > - Web projects > - EAR- projects > all these projects are recognized by rad-6 as what they. The websphere > development enviorment including hot-deployment features funktions out of the > box. > i wrote writers for: > - the ".j2ee" files > - the "application.xml" and the "modulemaps" file > - copying the extrenal libs in the ear project root > - adapting the MANIFEST.MF of the projects (nessesary for the websphere > development enviorment) > - the ".websettings" file > - the ".websiteconfig" file > - the ".project" (only alternative project natures/builders) > do you want to include it the the eclipse plugin or sould it be an extra > plugin? i should not be complicated to include it because i did the real work > in writer-classes. > should i add a tgz with the sources? or how do you want the sources? -- 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
[jira] Commented: (MECLIPSE-213) more jee support for wtp
[ http://jira.codehaus.org/browse/MECLIPSE-213?page=comments#action_84845 ] Richard van Nieuwenhoven commented on MECLIPSE-213: --- the idea to rename the project to the name with version name attached to it is realy very good. this solves a lot of troubles i have with the combination of maven with eclipse. when somebody needs it, i can sent an other patch to this pach that includes that setting! This makes project references a lot more simple to handle. - the manifest for eclipse could be done by the plexus-archiver now (open) this makes the generated artifacts of wtp more equal to the maven generated artifacts - the application.xml for eclipse could also be generated by the ear plugin (open) only the eclipse spesific ids must be added - it is now easy to have textual references to jar names in code, no more need for differences between eclipse-wtp and maven generated jar names. i must say that i vote for including the version into the name by default! > more jee support for wtp > > > Key: MECLIPSE-213 > URL: http://jira.codehaus.org/browse/MECLIPSE-213 > Project: Maven 2.x Eclipse Plugin > Issue Type: Improvement > Components: WTP support >Affects Versions: 2.3 > Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 >Reporter: Richard van Nieuwenhoven > Attachments: maven-eclipse-plugin-R494407.patch > > > I tried the new release 2.3 of the eclipse plugin and noteted that not alle > of my paches where included. > I re-pached the 2.3 version again this time i made my changes configurable so > they can be turned on and off. > my changes: > - prohibit dupicate entries in the classpath > provided system paths in combination with log4j/commons-logging/xerces > can easely create such problems > - system paths are only included in ears and war when they are inside the > project >bether behavior would be to exclude all system paths because the war and > ear plugin also ignore these > - an application.xml specialy for eclipse-wtp >this makes wtp ears function correctly it includes the eclipse project > modules instead of the maven generated jars > - manifest generation for wtp >wtp needs manifest files, but not the ones maven creates because they have > version names for all modules etc >this generates a wtp manifest that will be in a ons eclipse source > directory that is ignored my maven itself > use the parameters -Declipse.wtpmanifest=true > -Declipse.wtpapplicationxml=true to acivate the patch. > The manifest generator could be combined with the RadManifestWriter in the > future, they are almost the same. > regards, > Ritchie -- 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
[jira] Created: (MECLIPSE-213) more jee support for wtp
more jee support for wtp Key: MECLIPSE-213 URL: http://jira.codehaus.org/browse/MECLIPSE-213 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: WTP support Affects Versions: 2.3 Environment: linux suse 10.0 eclipse 3.2.1 and wtp 1.5.1 java 1.5.0_8 Reporter: Richard van Nieuwenhoven Attachments: maven-eclipse-plugin-R494407.patch I tried the new release 2.3 of the eclipse plugin and noteted that not alle of my paches where included. I re-pached the 2.3 version again this time i made my changes configurable so they can be turned on and off. my changes: - prohibit dupicate entries in the classpath provided system paths in combination with log4j/commons-logging/xerces can easely create such problems - system paths are only included in ears and war when they are inside the project bether behavior would be to exclude all system paths because the war and ear plugin also ignore these - an application.xml specialy for eclipse-wtp this makes wtp ears function correctly it includes the eclipse project modules instead of the maven generated jars - manifest generation for wtp wtp needs manifest files, but not the ones maven creates because they have version names for all modules etc this generates a wtp manifest that will be in a ons eclipse source directory that is ignored my maven itself use the parameters -Declipse.wtpmanifest=true -Declipse.wtpapplicationxml=true to acivate the patch. The manifest generator could be combined with the RadManifestWriter in the future, they are almost the same. regards, Ritchie -- 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
[jira] Commented: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=comments#action_80409 ] Richard van Nieuwenhoven commented on MECLIPSE-137: --- to Girish Khemani: Yes probably because RAD-6 is based on eclipse 3.0 and RAD-7 will be based on eclipse 3.2 It is just the question how mutch of IBM's special stull they left over I also posted some fixes for the eclipse-plugin for eclipse 3.2 they were partly extracted from this RAD-6 plugin. to John Casey: the testing was copied from the original (old) eclipse-plugin and adaped to fit the RAD-6 needs, the structure of the test was rather bad but i did not have the time to resolve this testing problems. from what i read on the mailing lists the maven-plugin test enviorment has improved a lot. so it is probably the best to create new test cases. > Developed RAD-6 Plugin Extention > > > Key: MECLIPSE-137 > URL: http://jira.codehaus.org/browse/MECLIPSE-137 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Richard van Nieuwenhoven > Assigned To: John Casey > Attachments: maven-rad-plugin-WebContent.zip, > maven-rad-plugin.tar.gz, maven-rad-plugin.zip > > > I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) > extention to the eclipse plugin. > It supports J2EE projects with the websphere development envorment, supported > are > - EJB projects > - Web projects > - EAR- projects > all these projects are recognized by rad-6 as what they. The websphere > development enviorment including hot-deployment features funktions out of the > box. > i wrote writers for: > - the ".j2ee" files > - the "application.xml" and the "modulemaps" file > - copying the extrenal libs in the ear project root > - adapting the MANIFEST.MF of the projects (nessesary for the websphere > development enviorment) > - the ".websettings" file > - the ".websiteconfig" file > - the ".project" (only alternative project natures/builders) > do you want to include it the the eclipse plugin or sould it be an extra > plugin? i should not be complicated to include it because i did the real work > in writer-classes. > should i add a tgz with the sources? or how do you want the sources? -- 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
[jira] Created: (MJAVADOC-97) enable internal/external dependency references as links
enable internal/external dependency references as links Key: MJAVADOC-97 URL: http://jira.codehaus.org/browse/MJAVADOC-97 Project: Maven 2.x Javadoc Plugin Issue Type: New Feature Affects Versions: 2.1 Reporter: Richard van Nieuwenhoven Priority: Minor Attachments: maven-javadoc-plugin-2.1.patch This patch enables the java doc plugin to autmaticaly connect the dependent javadoc pages as links. There is no more need to add links in your pom's for internal and external maven projects. The plugin resolves the dependencies and adds the defined project url's extended with "/apidocs" to the links in the plugin. TODO: a warning occures when the project has no javadocs (or no maven generated javadoc on its homepage) .. -- 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
[jira] Commented: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=comments#action_78408 ] Richard van Nieuwenhoven commented on MECLIPSE-137: --- Thats getting difficult... and i do not have the time to do this right now.. (it was based on an 4 months old version of eclipse:eclipse ).. But almost all differences are all in additional workers. (by intended design of the eclipse plugin) . Some of these workers i copied for my wtp 1.5 patch that i posted a while ago, i had the some same problems there as i had in RAD6. When you realy need a rework as a patch, i can send you the contact in the company for whom i made the plugin (UNIQA). maybe they have some resources free for rework (when it realy gets integerated in the official version of eclipse:eclipse). . > Developed RAD-6 Plugin Extention > > > Key: MECLIPSE-137 > URL: http://jira.codehaus.org/browse/MECLIPSE-137 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Richard van Nieuwenhoven > Attachments: maven-rad-plugin-WebContent.zip, > maven-rad-plugin.tar.gz, maven-rad-plugin.zip > > > I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) > extention to the eclipse plugin. > It supports J2EE projects with the websphere development envorment, supported > are > - EJB projects > - Web projects > - EAR- projects > all these projects are recognized by rad-6 as what they. The websphere > development enviorment including hot-deployment features funktions out of the > box. > i wrote writers for: > - the ".j2ee" files > - the "application.xml" and the "modulemaps" file > - copying the extrenal libs in the ear project root > - adapting the MANIFEST.MF of the projects (nessesary for the websphere > development enviorment) > - the ".websettings" file > - the ".websiteconfig" file > - the ".project" (only alternative project natures/builders) > do you want to include it the the eclipse plugin or sould it be an extra > plugin? i should not be complicated to include it because i did the real work > in writer-classes. > should i add a tgz with the sources? or how do you want the sources? -- 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
[jira] Commented: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=comments#action_77541 ] Richard van Nieuwenhoven commented on MECLIPSE-137: --- Hi, you did it the wrong way around, at least as i do it. this plugin is designed to work the maven way and adapting the project in such a way that it also works in RAD-6. So there should NOT be a "WebContent" directory there should be "src/main/webapp" as a webcontent. all dependent libraries are copied into src/main/webapp/WEB-INF/lib . this directory should be ignored in scm. regards, Ritchie > Developed RAD-6 Plugin Extention > > > Key: MECLIPSE-137 > URL: http://jira.codehaus.org/browse/MECLIPSE-137 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Richard van Nieuwenhoven > Attachments: maven-rad-plugin.tar.gz, maven-rad-plugin.zip > > > I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) > extention to the eclipse plugin. > It supports J2EE projects with the websphere development envorment, supported > are > - EJB projects > - Web projects > - EAR- projects > all these projects are recognized by rad-6 as what they. The websphere > development enviorment including hot-deployment features funktions out of the > box. > i wrote writers for: > - the ".j2ee" files > - the "application.xml" and the "modulemaps" file > - copying the extrenal libs in the ear project root > - adapting the MANIFEST.MF of the projects (nessesary for the websphere > development enviorment) > - the ".websettings" file > - the ".websiteconfig" file > - the ".project" (only alternative project natures/builders) > do you want to include it the the eclipse plugin or sould it be an extra > plugin? i should not be complicated to include it because i did the real work > in writer-classes. > should i add a tgz with the sources? or how do you want the sources? -- 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
[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Richard van Nieuwenhoven updated MECLIPSE-137: -- Attachment: maven-rad-plugin.zip I have not much time to spend for support on this plugin, i made/appened it for a customer (UNIQA Austria). But still any extentions are welcome, and as long as there is no own project and it is not integerated in the eclipse plugin we should post them here. i have not the time to make and support a seperate project. Because the project (i worked on) ended successfuly, i do not work on this plugin anymore (for now). Please feel free to contact me, i will give you an email kontact of the responsible person in UNIQA Austria. They are happy to meet and work together with others also using Maven-2, RAD6 and websphere. They also ported or working on porting a lot of the was-5/6 admin ant tasks to maven-2 goals for websphere-6 integration tests. in this updated version i deleted the localreposetorys (sorry for that) so it should build anywhere now. > Developed RAD-6 Plugin Extention > > > Key: MECLIPSE-137 > URL: http://jira.codehaus.org/browse/MECLIPSE-137 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Richard van Nieuwenhoven > Attachments: maven-rad-plugin.tar.gz, maven-rad-plugin.zip > > > I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) > extention to the eclipse plugin. > It supports J2EE projects with the websphere development envorment, supported > are > - EJB projects > - Web projects > - EAR- projects > all these projects are recognized by rad-6 as what they. The websphere > development enviorment including hot-deployment features funktions out of the > box. > i wrote writers for: > - the ".j2ee" files > - the "application.xml" and the "modulemaps" file > - copying the extrenal libs in the ear project root > - adapting the MANIFEST.MF of the projects (nessesary for the websphere > development enviorment) > - the ".websettings" file > - the ".websiteconfig" file > - the ".project" (only alternative project natures/builders) > do you want to include it the the eclipse plugin or sould it be an extra > plugin? i should not be complicated to include it because i did the real work > in writer-classes. > should i add a tgz with the sources? or how do you want the sources? -- 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
[jira] Created: (MECLIPSE-163) eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes -- Key: MECLIPSE-163 URL: http://jira.codehaus.org/browse/MECLIPSE-163 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: multiproject, WTP support Affects Versions: 2.3 Reporter: Richard van Nieuwenhoven Attachments: maven-eclipse-plugin-R448503.patch we needed eclipse:eclipse to function with wtp 1.5 but we had some problems with the 2.3 SNAPSHOT version. 1) create a seperate eardefinition for eclipse this makes it possible to include the reactor modules as projects (not as versioned packages) 2) enable ejb3 projects ejb3 3) module types in the components file corrected (war ejb modules included now with module-reference) 4) created a manifest-writer to write a eclipse/wtp compatible manifest for module dependencies this sould probably be done in a generated resources directory, but for now i put it in src/main/resources i will include the patch file as an attachment. Any one interested can include the sources in the SNAPSHOT. i use the patch for jboss and it works good, ejb(3) and web deployment is now functional from scratch. -- 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
[jira] Updated: (MECLIPSE-137) Developed RAD-6 Plugin Extention
[ http://jira.codehaus.org/browse/MECLIPSE-137?page=all ] Richard van Nieuwenhoven updated MECLIPSE-137: -- Attachment: maven-rad-plugin.tar.gz sorry that it took so long but i was not at work... this is the tarball with the plugin. some hints for RAD6 users - do not use java classes in a war project, put all java classes in dependent projects - best thing to do is to make all jars in the war project provided and put them in the ear dependencys - there will be a classpath directory included in ejb projects here you can put your generated ejb classes for nor i use the websphere-ant jobs in the project-pom to generate them. (in the package phase overwiting the jar and the client-jar and copieing the classes to the classes-folder included by this plugin, the ant-job does not generate the java files...) - the META-INF of the ejb project MUST!!! be a toplevel folder so include this top-level-folder in your resources list of the pom (the java files can stay in src/main/java - don't forget to fill the ".cvsignore" files especialy the jar's and wars in the ear-project's and the war-project's regards, Ritchie > Developed RAD-6 Plugin Extention > > > Key: MECLIPSE-137 > URL: http://jira.codehaus.org/browse/MECLIPSE-137 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature >Reporter: Richard van Nieuwenhoven > Attachments: maven-rad-plugin.tar.gz > > > I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) > extention to the eclipse plugin. > It supports J2EE projects with the websphere development envorment, supported > are > - EJB projects > - Web projects > - EAR- projects > all these projects are recognized by rad-6 as what they. The websphere > development enviorment including hot-deployment features funktions out of the > box. > i wrote writers for: > - the ".j2ee" files > - the "application.xml" and the "modulemaps" file > - copying the extrenal libs in the ear project root > - adapting the MANIFEST.MF of the projects (nessesary for the websphere > development enviorment) > - the ".websettings" file > - the ".websiteconfig" file > - the ".project" (only alternative project natures/builders) > do you want to include it the the eclipse plugin or sould it be an extra > plugin? i should not be complicated to include it because i did the real work > in writer-classes. > should i add a tgz with the sources? or how do you want the sources? -- 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
[jira] Created: (MECLIPSE-137) Developed RAD-6 Plugin Extention
Developed RAD-6 Plugin Extention Key: MECLIPSE-137 URL: http://jira.codehaus.org/browse/MECLIPSE-137 Project: Maven 2.x Eclipse Plugin Issue Type: New Feature Reporter: Richard van Nieuwenhoven I just finisched developing a RAD-6 (IBM Rational Application Developer 6.0) extention to the eclipse plugin. It supports J2EE projects with the websphere development envorment, supported are - EJB projects - Web projects - EAR- projects all these projects are recognized by rad-6 as what they. The websphere development enviorment including hot-deployment features funktions out of the box. i wrote writers for: - the ".j2ee" files - the "application.xml" and the "modulemaps" file - copying the extrenal libs in the ear project root - adapting the MANIFEST.MF of the projects (nessesary for the websphere development enviorment) - the ".websettings" file - the ".websiteconfig" file - the ".project" (only alternative project natures/builders) do you want to include it the the eclipse plugin or sould it be an extra plugin? i should not be complicated to include it because i did the real work in writer-classes. should i add a tgz with the sources? or how do you want the sources? -- 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
