[jira] Created: (MECLIPSE-663) Overriding Packaging does not work correctly for WTP-Project
Overriding Packaging does not work correctly for WTP-Project
Key: MECLIPSE-663
URL: http://jira.codehaus.org/browse/MECLIPSE-663
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: WTP support
Affects Versions: 2.8
Environment: All
Reporter: Benjamin Gniza
I found out that overriding the packaging - type (MECLIPSE-331) does not work
correct if you want to have a wtp project:
{code:xml}
4.0.0
com.mycompany.app
my-webapp2
jar
org.apache.maven.plugins
maven-eclipse-plugin
war
${jdk.version}
${jdk.version}
1.5
{code}
This configuration leads to a Nullpointer Exception:
{noformat}
java.lang.NullPointerException
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXml(PrettyPrintXMLWriter.java:151)
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.escapeXmlAttribute(PrettyPrintXMLWriter.java:166)
at
org.codehaus.plexus.util.xml.PrettyPrintXMLWriter.addAttribute(PrettyPrintXMLWriter.java:190)
at
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponent15Writer.writeContextRoot(EclipseWtpComponent15Writer.java:68)
at
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter.writeModuleTypeComponent(EclipseWtpComponentWriter.java:149)
at
org.apache.maven.plugin.eclipse.writers.wtp.EclipseWtpComponentWriter.write(EclipseWtpComponentWriter.java:106)
at
org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:1110)
at
org.apache.maven.plugin.ide.AbstractIdeSupportMojo.execute(AbstractIdeSupportMojo.java:511)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:41)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:592)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
{noformat}
The cause for that NullpointerException is that _config.getContextName()_ in
*EclipseWtpComponent15Writer.java:68* is null.
I found out that you are referring to *project.getPackaging()* or
*config.getProject().getPackaging()* instead of *config.getPackaging()* in many
places:
* EclipseManifestWriter
* EclipsePlugin (in this class the method
_collectWarContextRootsFromReactorEarConfiguration_ should set the missing
context name, but the method refers to *project.getPackaging()* which is still
*jar*
** here a _reactorProject.getPackaging()_ can also be fond, I don't know if
this is correct.
* RadManifestWriter
* MyEclipseMetadataWriter
* MyEclipseStrutsDataWriter
* EclipseWtpApplicationXMLWriter
* MyEclipsePlugin
* AbstractWtpResourceWriter
After replacing all references to project.getPackaging() to
config.getPackaging() the NullpointerException has gone and the plugin works as
expected.
I did only test the combination of project-packaging=jar and
eclipse-packaging=war for Eclipse. I did not test MyEclipse, RAD 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-661) Build Path getting corrupted after maven clean install
[ http://jira.codehaus.org/browse/MECLIPSE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227113#action_227113 ] Benjamin Gniza commented on MECLIPSE-661: - *Note: I am not involved in this plugin, I am also only a user.* AFAIK this problem doesn't have to do anything with the position of the JRE. The problem is that Eclipse doesn't like you to touch the generated classes outside of the IDE. Usually it helps to just clean the project to get Eclipse running again. From the Menu select "Project"->"Clean", select your project and press "Ok". Changing the position of the JRE causes a recompile to, but the position of the JRE is not the cause for this problem.. > Build Path getting corrupted after maven clean install > -- > > Key: MECLIPSE-661 > URL: http://jira.codehaus.org/browse/MECLIPSE-661 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Core : Dependencies resolution and build path > (.classpath) > Environment: Production >Reporter: prateek >Priority: Critical > > After doing the maven clean install on the project, > In the Eclipse Build Path for the project, the JRE System Library is pushed > down to the Bottom and due to which we are getting compile time errors. After > manually pushing the JRE to in the Build Path / Order and Export Tab. > The compile issues are getting resolved. > I have done lot of research to look for a way to make sure the JRE Library > Stays on Top, > But i vain. Can somebody help me out -- 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-661) Build Path getting corrupted after maven clean install
[ http://jira.codehaus.org/browse/MECLIPSE-661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227113#action_227113 ] Benjamin Gniza edited comment on MECLIPSE-661 at 7/3/10 6:50 AM: - *Note: I am not involved in this plugin, I am also only a user.* AFAIK this problem doesn't have to do anything with the position of the JRE. The problem is that Eclipse doesn't like you to touch the generated classes outside of the IDE. Usually it helps to just clean the project to get Eclipse running again. From the Menu select "Project"->"Clean", select your project and press "Ok". Changing the position of the JRE causes a recompile too, but the position of the JRE is not the cause for this problem.. was (Author: benjamin.gniza): *Note: I am not involved in this plugin, I am also only a user.* AFAIK this problem doesn't have to do anything with the position of the JRE. The problem is that Eclipse doesn't like you to touch the generated classes outside of the IDE. Usually it helps to just clean the project to get Eclipse running again. From the Menu select "Project"->"Clean", select your project and press "Ok". Changing the position of the JRE causes a recompile to, but the position of the JRE is not the cause for this problem.. > Build Path getting corrupted after maven clean install > -- > > Key: MECLIPSE-661 > URL: http://jira.codehaus.org/browse/MECLIPSE-661 > Project: Maven 2.x Eclipse Plugin > Issue Type: New Feature > Components: Core : Dependencies resolution and build path > (.classpath) > Environment: Production >Reporter: prateek >Priority: Critical > > After doing the maven clean install on the project, > In the Eclipse Build Path for the project, the JRE System Library is pushed > down to the Bottom and due to which we are getting compile time errors. After > manually pushing the JRE to in the Build Path / Order and Export Tab. > The compile issues are getting resolved. > I have done lot of research to look for a way to make sure the JRE Library > Stays on Top, > But i vain. Can somebody help me out -- 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: (MPIR-171) support "TimeZones" as a timezone
[
http://jira.codehaus.org/browse/MPIR-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPIR-171:
---
Description:
The POM XSD defiens the TimeZone as an xs:string (although the descriptions
says an integer between -11 and 12)
If the desctription is enforced you can not be in a timezone that is not a
multiple of 1 hour away from UTC (e.g. certain parts of india)
So the description is wrong and it's just a String.
So why not support a full formatted timezone such as Europe/London, then the
mpir can use funky javascript to show your actual time including any daylight
saving offset. (as opposed to a fixed offset from GMT ignoring DST changes)
e.g. support
{code:xml}
bob
Bob Hacker
b...@example.com
Europe/London
developer
{code}
Currently the site shows NaN for the Current time.
was:
The POM XSD defiens the TimeZone as an xs:string (although the descriptions
says an integer between -11 and 12)
If the desctription is enforced you can not be in a timezone that is not a
multiple of 1 hour away from UTC (e.g. certain parts of india)
So the description is wrong and it's just a String.
So why not support a full formatted timezone such as Europe/London, then the
mpir can use funky javascript to show your actual time including any daylight
saving offset. (as opposed to a fixed offset from GMT ignoring DST changes)
e.g. support
bob
Bob Hacker
b...@example.com
Europe/London
developer
Currently the site shows NaN for the Current time.
> support "TimeZones" as a timezone
> -
>
> Key: MPIR-171
> URL: http://jira.codehaus.org/browse/MPIR-171
> Project: Maven 2.x Project Info Reports Plugin
> Issue Type: Improvement
>Affects Versions: 2.1.2
>Reporter: James Nord
>Priority: Trivial
>
> The POM XSD defiens the TimeZone as an xs:string (although the descriptions
> says an integer between -11 and 12)
> If the desctription is enforced you can not be in a timezone that is not a
> multiple of 1 hour away from UTC (e.g. certain parts of india)
> So the description is wrong and it's just a String.
> So why not support a full formatted timezone such as Europe/London, then the
> mpir can use funky javascript to show your actual time including any daylight
> saving offset. (as opposed to a fixed offset from GMT ignoring DST changes)
> e.g. support
> {code:xml}
>
> bob
> Bob Hacker
> b...@example.com
> Europe/London
>
> developer
>
>
> {code}
> Currently the site shows NaN for the Current time.
--
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: (MENFORCER-98) requirePluginVersions rule is not compatible with maven 3.0-beta-1
[ http://jira.codehaus.org/browse/MENFORCER-98?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=227118#action_227118 ] jieryn commented on MENFORCER-98: - Even though M3 already does a lot of the work this rule provides, this rule is far more flexible.. it would be nice if it was continued to be supported in M3. > requirePluginVersions rule is not compatible with maven 3.0-beta-1 > -- > > Key: MENFORCER-98 > URL: http://jira.codehaus.org/browse/MENFORCER-98 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-beta-1 > Environment: Windows XP > Sun JDK 1.6.0_18 > Maven 3.0-beta-1 >Reporter: Anders Hammar > > When using the requirePluginVersions rule, I get a message saying "This rule > is not compatible with the current version of Maven. The rule is not able to > perform any checks." -- 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: (MIDEA-126) Add Android Support (when packaging type is apk)
Add Android Support (when packaging type is apk) Key: MIDEA-126 URL: http://jira.codehaus.org/browse/MIDEA-126 Project: Maven 2.x IDEA Plugin Issue Type: Improvement Affects Versions: 2.2 Reporter: Mathieu Carbou Attachments: add-android-support.patch Hi, When developping with applications for Android platform, we have the ability to also use Maven thanks to this plugin your moght know: http://code.google.com/p/maven-android-plugin/ http://www.sonatype.com/books/mvnref-book/reference/android-dev-sect-using.html The artifact packaging must be set to 'apk'. IntelliJ IDEA has a special module type for this: the module type must be set to ANDROID_MODULE. Attached is a patched that was build upon the trunk code of 3rd July 2010 that add support for Android. When we issue a mvn idea:idea, the correct IntelliJ module type is created with the plateform we want: maven-idea-plugin 2.3-20100703-SNAPSHOT true false Android 2.2 Platform -- 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: (MRESOURCES-127) favico.ico file was corrupted after copying
favico.ico file was corrupted after copying --- Key: MRESOURCES-127 URL: http://jira.codehaus.org/browse/MRESOURCES-127 Project: Maven 2.x Resources Plugin Issue Type: Bug Affects Versions: 2.4.3 Environment: Windows XP, JRE 1.6.0_20, Maven 2.2.1 Reporter: jose cueto Priority: Minor Attachments: issues.zip Steps: 1. added the resources plugin in my pom file (see attached file) 2. the resources plugin is associated in the "mvn clean" phase 3. after cleaning all files from the src directory where copied but favico.ico is corrupted attachement: - xml for maven resource plugin - favico.ico corrupted - favico.ico original -- 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
