[jira] Created: (MIDEA-117) Plugin generates invalid entries for test-jar sources
Plugin generates invalid entries for test-jar sources - Key: MIDEA-117 URL: http://jira.codehaus.org/browse/MIDEA-117 Project: Maven 2.x IDEA Plugin Issue Type: Bug Reporter: Andrew Perepelytsya Priority: Critical Given a foo-tests.jar dependency, the plugin generates a foo-tests-sources.jar link for sources (when downloadSources is enabled). However, the fact is maven's source plugin generates the filename as foo-test-sources.jar (test singular). This makes it impossible to link sources to the test-jar dependencies. -- 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: (MIDEA-117) Plugin generates invalid entries for test-jar sources
[ http://jira.codehaus.org/browse/MIDEA-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Perepelytsya updated MIDEA-117: -- Attachment: MIDEA-117-initial.patch.txt I'm attaching a patch that fixes the issue, would appreciate the prompt inclusion in the next release. Plugin generates invalid entries for test-jar sources - Key: MIDEA-117 URL: http://jira.codehaus.org/browse/MIDEA-117 Project: Maven 2.x IDEA Plugin Issue Type: Bug Reporter: Andrew Perepelytsya Priority: Critical Attachments: MIDEA-117-initial.patch.txt Given a foo-tests.jar dependency, the plugin generates a foo-tests-sources.jar link for sources (when downloadSources is enabled). However, the fact is maven's source plugin generates the filename as foo-test-sources.jar (test singular). This makes it impossible to link sources to the test-jar dependencies. -- 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: (MASSEMBLY-285) regression: duplicate files added to the assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129182#action_129182 ] Andrew Perepelytsya commented on MASSEMBLY-285: --- 2.2-beta-2 is badly broken due to this. Does it really take so much time to fix the regression? Pleease? :) regression: duplicate files added to the assembly - Key: MASSEMBLY-285 URL: http://jira.codehaus.org/browse/MASSEMBLY-285 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Reporter: Brett Porter Priority: Blocker Fix For: 2.2-beta-3 I found that it was possible to add a file twice to the assembly through different filesets (a zip file) so that when it extracted it prompted for overwrite. It should error out or collapse the entries (as 2.1 did). -- 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: (MASSEMBLY-285) regression: duplicate files added to the assembly
[ http://jira.codehaus.org/browse/MASSEMBLY-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=129183#action_129183 ] Andrew Perepelytsya commented on MASSEMBLY-285: --- This is reproduced when one tries e.g. to configure permissions on the files in the directory using multiple include/exclude patterns. Each FileSet is instead copied and duplicated in zip. E.g. real config that broke: http://svn.galaxy.muleforge.org/browse/galaxy/trunk/netboot/mule1/distribution/assembly.xml?r=487 regression: duplicate files added to the assembly - Key: MASSEMBLY-285 URL: http://jira.codehaus.org/browse/MASSEMBLY-285 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-1 Reporter: Brett Porter Priority: Blocker Fix For: 2.2-beta-3 I found that it was possible to add a file twice to the assembly through different filesets (a zip file) so that when it extracted it prompted for overwrite. It should error out or collapse the entries (as 2.1 did). -- 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: (MIDEA-96) generated projects do not load in Selena #7020
[
http://jira.codehaus.org/browse/MIDEA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102272
]
Andrew Perepelytsya commented on MIDEA-96:
--
Yes.
generated projects do not load in Selena #7020
--
Key: MIDEA-96
URL: http://jira.codehaus.org/browse/MIDEA-96
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.0
Environment: maven 2.0.4
windows
IntelliJ build #7020
Reporter: zak jacobson
Attachments: MIDEA-96.patch
Idea trows an error:
Error during dispatching of
java.awt.event.MouseEvent[MOUSE_RELEASED,(47,53),button=1,modifiers=Button1,clickCount=1]
on ###overrideRedirect###: Wrong node: [Comment: !-- output
url=file://$C:/P4/TPE/te/tpe/main/Util$/${maven.build.dest}/ --]
java.lang.IllegalArgumentException: Wrong node: [Comment: !-- output
url=file://$project path$/${maven.build.dest}/ --]
at com.intellij.openapi.util.JDOMUtil.internElement(JDOMUtil.java:181)
Manually editing the .iml .ipr files to remove all comments, such as:
!-- Next include each dependency:
orderEntry type=module module-name=${dep.artifactId}/
orderEntry type=module-library
library name=${dep.artifactId}
CLASSES
root url=jar://${lib.path}!//
/CLASSES
JAVADOC/
SOURCES/
/library
/orderEntry
--
is a work around.
--
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: (MIDEA-96) generated projects do not load in Selena #7020
[
http://jira.codehaus.org/browse/MIDEA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102248
]
Andrew Perepelytsya commented on MIDEA-96:
--
Jetbrains have a huge volume of incoming issues, some of them duplicates.
However, my (and others' ) noise caught the right guy's attention at Jetbrains
and it has since been fixed (after b7041 or so)
generated projects do not load in Selena #7020
--
Key: MIDEA-96
URL: http://jira.codehaus.org/browse/MIDEA-96
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.0
Environment: maven 2.0.4
windows
IntelliJ build #7020
Reporter: zak jacobson
Attachments: MIDEA-96.patch
Idea trows an error:
Error during dispatching of
java.awt.event.MouseEvent[MOUSE_RELEASED,(47,53),button=1,modifiers=Button1,clickCount=1]
on ###overrideRedirect###: Wrong node: [Comment: !-- output
url=file://$C:/P4/TPE/te/tpe/main/Util$/${maven.build.dest}/ --]
java.lang.IllegalArgumentException: Wrong node: [Comment: !-- output
url=file://$project path$/${maven.build.dest}/ --]
at com.intellij.openapi.util.JDOMUtil.internElement(JDOMUtil.java:181)
Manually editing the .iml .ipr files to remove all comments, such as:
!-- Next include each dependency:
orderEntry type=module module-name=${dep.artifactId}/
orderEntry type=module-library
library name=${dep.artifactId}
CLASSES
root url=jar://${lib.path}!//
/CLASSES
JAVADOC/
SOURCES/
/library
/orderEntry
--
is a work around.
--
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: (MIDEA-96) generated projects do not load in Selena #7020
[
http://jira.codehaus.org/browse/MIDEA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_100053
]
Andrew Perepelytsya commented on MIDEA-96:
--
Moreover, Jetbrains rejected this as Won't Fix, so plugin has to handle it.
generated projects do not load in Selena #7020
--
Key: MIDEA-96
URL: http://jira.codehaus.org/browse/MIDEA-96
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.0
Environment: maven 2.0.4
windows
IntelliJ build #7020
Reporter: zak jacobson
Idea trows an error:
Error during dispatching of
java.awt.event.MouseEvent[MOUSE_RELEASED,(47,53),button=1,modifiers=Button1,clickCount=1]
on ###overrideRedirect###: Wrong node: [Comment: !-- output
url=file://$C:/P4/TPE/te/tpe/main/Util$/${maven.build.dest}/ --]
java.lang.IllegalArgumentException: Wrong node: [Comment: !-- output
url=file://$project path$/${maven.build.dest}/ --]
at com.intellij.openapi.util.JDOMUtil.internElement(JDOMUtil.java:181)
Manually editing the .iml .ipr files to remove all comments, such as:
!-- Next include each dependency:
orderEntry type=module module-name=${dep.artifactId}/
orderEntry type=module-library
library name=${dep.artifactId}
CLASSES
root url=jar://${lib.path}!//
/CLASSES
JAVADOC/
SOURCES/
/library
/orderEntry
--
is a work around.
--
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: (MIDEA-96) generated projects do not load in Selena #7020
[
http://jira.codehaus.org/browse/MIDEA-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Perepelytsya updated MIDEA-96:
-
Attachment: MIDEA-96.patch
The attached MIDEA-96 patch cleans up offending commented out sections in
module and project templates. Well, the code is in SVN, so those sections could
generally be removed safely anyway. It got me moving on in an 80 module
project.
generated projects do not load in Selena #7020
--
Key: MIDEA-96
URL: http://jira.codehaus.org/browse/MIDEA-96
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.0
Environment: maven 2.0.4
windows
IntelliJ build #7020
Reporter: zak jacobson
Attachments: MIDEA-96.patch
Idea trows an error:
Error during dispatching of
java.awt.event.MouseEvent[MOUSE_RELEASED,(47,53),button=1,modifiers=Button1,clickCount=1]
on ###overrideRedirect###: Wrong node: [Comment: !-- output
url=file://$C:/P4/TPE/te/tpe/main/Util$/${maven.build.dest}/ --]
java.lang.IllegalArgumentException: Wrong node: [Comment: !-- output
url=file://$project path$/${maven.build.dest}/ --]
at com.intellij.openapi.util.JDOMUtil.internElement(JDOMUtil.java:181)
Manually editing the .iml .ipr files to remove all comments, such as:
!-- Next include each dependency:
orderEntry type=module module-name=${dep.artifactId}/
orderEntry type=module-library
library name=${dep.artifactId}
CLASSES
root url=jar://${lib.path}!//
/CLASSES
JAVADOC/
SOURCES/
/library
/orderEntry
--
is a work around.
--
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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91933 ] Andrew Perepelytsya commented on MIDEA-39: -- I don't understand the point of the last comment. That is exactly what this issue is about, and that behavior is a problem. I've rebuild the plugin from trunk, but no, nothing is fixed. In fact, the only difference between having useFullNames on and off is the linkage of sources jar (?!). I'm attaching 2 outputs from idea:module run with the above setting on and off, it always generates links to jars from inside the module. In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository - Key: MIDEA-39 URL: http://jira.codehaus.org/browse/MIDEA-39 Project: Maven 2.x Idea Plugin Issue Type: Improvement Affects Versions: 2.0 Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 Reporter: Vikash Ramanlal Assigned To: Brett Porter Priority: Minor Fix For: 2.1 Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true When I generate my idea files using mvn idea:idea, all works fine. However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository. Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project. -- 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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrew Perepelytsya updated MIDEA-39: - Attachment: mule-module-ognl.iml_false mule-module-ognl.iml_true SVN revision tested: 525253 In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository - Key: MIDEA-39 URL: http://jira.codehaus.org/browse/MIDEA-39 Project: Maven 2.x Idea Plugin Issue Type: Improvement Affects Versions: 2.0 Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 Reporter: Vikash Ramanlal Assigned To: Brett Porter Priority: Minor Fix For: 2.1 Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true When I generate my idea files using mvn idea:idea, all works fine. However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository. Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project. -- 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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91939 ] Andrew Perepelytsya commented on MIDEA-39: -- Thanks for the clarification, Dennis. Then, l saw this linkModules and it was true by default, which haven't generated the desired output. Why do I think it should? E.g. consider a reactor project where your CWD is somewhere down the path in a child. If I modify the root pom to use a different version of e.g. plugin, the project I'm currently in properly resolves all poms upwards to the root (they are all available on the disk), and actually picks up the change. I don't have to run from the root. This leads me to the conclusion that similar behavior should be made available to the IDEA plugin. In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository - Key: MIDEA-39 URL: http://jira.codehaus.org/browse/MIDEA-39 Project: Maven 2.x Idea Plugin Issue Type: Improvement Affects Versions: 2.0 Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 Reporter: Vikash Ramanlal Assigned To: Brett Porter Priority: Minor Fix For: 2.1 Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true When I generate my idea files using mvn idea:idea, all works fine. However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository. Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project. -- 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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91944 ] Andrew Perepelytsya commented on MIDEA-39: -- Almost ;) The above behavior might be a step forward, but for now just being able to resolve the reactor projects and linking to them is all that is needed. In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository - Key: MIDEA-39 URL: http://jira.codehaus.org/browse/MIDEA-39 Project: Maven 2.x Idea Plugin Issue Type: Improvement Affects Versions: 2.0 Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 Reporter: Vikash Ramanlal Assigned To: Brett Porter Priority: Minor Fix For: 2.1 Attachments: module-dependencies.patch, mule-module-ognl.iml_false, mule-module-ognl.iml_true When I generate my idea files using mvn idea:idea, all works fine. However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository. Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project. -- 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: (MNGECLIPSE-77) Add support for WSAD specifics on a J2EE project.
[ http://jira.codehaus.org/browse/MNGECLIPSE-77?page=comments#action_73739 ] Andrew Perepelytsya commented on MNGECLIPSE-77: --- Eugene, I don't understand your comment. We *are* talking about maven-eclipse plugin and nothing else here. Both WSAD and RAD6 plugin extensions reuse much of the original maven-eclipse plugin, so it's only natural to bring it all under one umbrella and refactor/reuse the code. It's trivial to bind those extensions to their own goals, e.g. _mvn eclipse:wsad_ would be a major entry point for WSAD (in fact it is what I did and works well). Add support for WSAD specifics on a J2EE project. - Key: MNGECLIPSE-77 URL: http://jira.codehaus.org/browse/MNGECLIPSE-77 Project: Maven 2.x Extension for Eclipse Issue Type: New Feature Reporter: Joakim Erdfelt Priority: Minor Attachments: sample-projects-wsad6.x.tar.bz2 Need the ability to support the WSAD / J2EE specific configurations. The Eclipse extension needs to either ... # map the WSAD / J2EE project directory structure to a Maven pom. This way allows the user to use the WSAD J2EE wizards. # map a Maven J2EE pom to the WSAD / J2EE project configuration. This way makes Maven the start of all J2EE applications. This could be done by Eclipse extension specifics, or with the use of pre-defined Archetypes that show up on the New Project / Maven Archetype Wizards within Eclipse. -- 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: (MCLOVER-50) Test failure during Site goal should not stop the Clover build
[ http://jira.codehaus.org/browse/MCLOVER-50?page=comments#action_73030 ] Andrew Perepelytsya commented on MCLOVER-50: Vincent, Thanks for taking a look. I think site goal is very different from, e.g. install. Does it make sense to ignore all failures during site generation then? The interesting point Cobertura plugin does work as requested even with test failures, maybe there's some interesting stuff in their code? Anyway, that is the only thing stopping us from using Clover plugin, though I like those polished coverage reports it produces. Test failure during Site goal should not stop the Clover build -- Key: MCLOVER-50 URL: http://jira.codehaus.org/browse/MCLOVER-50 Project: Maven 2.x Clover Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Andrew Perepelytsya Assigned To: Vincent Massol Priority: Critical This problem is similar to whatever surefire-report plugin experienced up until recently. Clover plugin runs tests in its own lifecycle. If there was a test failure, the build should continue and site be generated with failure reports. At the moment the build is stopped with a failure completely, and site *not* generated. -- 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: (MCLOVER-50) Test failure during Site goal should not stop the Clover build
Test failure during Site goal should not stop the Clover build -- Key: MCLOVER-50 URL: http://jira.codehaus.org/browse/MCLOVER-50 Project: Maven 2.x Clover Plugin Issue Type: Bug Affects Versions: 2.2 Reporter: Andrew Perepelytsya Priority: Critical This problem is similar to whatever surefire-report plugin experienced up until recently. Clover plugin runs tests in its own lifecycle. If there was a test failure, the build should continue and site be generated with failure reports. At the moment the build is stopped with a failure completely, and site *not* generated. -- 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: (MNGECLIPSE-77) Add support for WSAD specifics on a J2EE project.
[ http://jira.codehaus.org/browse/MNGECLIPSE-77?page=comments#action_71394 ] Andrew Perepelytsya commented on MNGECLIPSE-77: --- Well, I have the WSAD extensions in the works. You know, it's different from RAD or Eclipse ;) Just a preview of what is already available: * Generates .project, .classpath files from the pom.xml model with WSAD natures and builders * Enables WebSphere AS 5.1 J2EE targeting for projects * Enables EJB Client module preference by default * Adds M2_REPO classpath variable to WSAD workspace (it's different from what Eclipse 3.x plugin does) * Configures JDK compliance to be 1.4 level * Enables multiple output paths for the compiler to accomodate m2 folder layout * Switches the workspace to JDK 1.4 (IBM one), and ensures all projects use it, and not 1.3 (the default one) I will check the MECLIPSE-137 to see if some logic can be reused. Add support for WSAD specifics on a J2EE project. - Key: MNGECLIPSE-77 URL: http://jira.codehaus.org/browse/MNGECLIPSE-77 Project: Maven 2.x Extension for Eclipse Issue Type: New Feature Reporter: Joakim Erdfelt Priority: Minor Attachments: sample-projects-wsad6.x.tar.bz2 Need the ability to support the WSAD / J2EE specific configurations. The Eclipse extension needs to either ... # map the WSAD / J2EE project directory structure to a Maven pom. This way allows the user to use the WSAD J2EE wizards. # map a Maven J2EE pom to the WSAD / J2EE project configuration. This way makes Maven the start of all J2EE applications. This could be done by Eclipse extension specifics, or with the use of pre-defined Archetypes that show up on the New Project / Maven Archetype Wizards within Eclipse. -- 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: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException
(regression)
--
Key: MSUREFIRE-150
URL: http://jira.codehaus.org/browse/MSUREFIRE-150
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Andrew Perepelytsya
Ok, I know how tricky it can be to explain such bug, but I'll try. We've
switched to using 2.3-SNAPSHOT version of the plugin to get the fix for this
error when test reports failed the build in case of test errors without
generating any report. This part works fine now, but it has introduced a
regression.
I'm attaching the test failure reports(it always worked before). To reproduce
the error (tricky part) - I can only think of checking out Mule project SVN
source as of r2315 from http://svn.codehaus.org/mule/ What you need is only a
top-level dir and mule-core.
{panel}
mvn test -Dtest=SerializedUMOMessageTransformersTestCase
{panel}
r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it to
RELEASE, and the problem is again gone.
I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it helps.
--
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: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
[ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]
Andrew Perepelytsya updated MSUREFIRE-150:
--
Attachment: RELEASE-m2-run.txt
TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt
2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException
(regression)
--
Key: MSUREFIRE-150
URL: http://jira.codehaus.org/browse/MSUREFIRE-150
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Andrew Perepelytsya
Attachments:
org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
RELEASE-m2-run.txt, SNAPSHOT-m2-run.txt,
TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
Ok, I know how tricky it can be to explain such bug, but I'll try. We've
switched to using 2.3-SNAPSHOT version of the plugin to get the fix for this
error when test reports failed the build in case of test errors without
generating any report. This part works fine now, but it has introduced a
regression.
I'm attaching the test failure reports(it always worked before). To reproduce
the error (tricky part) - I can only think of checking out Mule project SVN
source as of r2315 from http://svn.codehaus.org/mule/ What you need is only a
top-level dir and mule-core.
{panel}
mvn test -Dtest=SerializedUMOMessageTransformersTestCase
{panel}
r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it
to RELEASE, and the problem is again gone.
I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it
helps.
--
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: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
[ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]
Andrew Perepelytsya updated MSUREFIRE-150:
--
Attachment: SNAPSHOT-m2-run.txt
2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException
(regression)
--
Key: MSUREFIRE-150
URL: http://jira.codehaus.org/browse/MSUREFIRE-150
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Andrew Perepelytsya
Attachments:
org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
RELEASE-m2-run.txt, SNAPSHOT-m2-run.txt,
TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
Ok, I know how tricky it can be to explain such bug, but I'll try. We've
switched to using 2.3-SNAPSHOT version of the plugin to get the fix for this
error when test reports failed the build in case of test errors without
generating any report. This part works fine now, but it has introduced a
regression.
I'm attaching the test failure reports(it always worked before). To reproduce
the error (tricky part) - I can only think of checking out Mule project SVN
source as of r2315 from http://svn.codehaus.org/mule/ What you need is only a
top-level dir and mule-core.
{panel}
mvn test -Dtest=SerializedUMOMessageTransformersTestCase
{panel}
r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it
to RELEASE, and the problem is again gone.
I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it
helps.
--
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: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
[ http://jira.codehaus.org/browse/MSUREFIRE-150?page=comments#action_70562
]
Andrew Perepelytsya commented on MSUREFIRE-150:
---
For your convenience: source code for the test case
http://svn.mule.codehaus.org/browse/mule/trunk/mule/mule/src/test/java/org/mule/test/transformers/SerializedUMOMessageTransformersTestCase.java?r=2176
2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException
(regression)
--
Key: MSUREFIRE-150
URL: http://jira.codehaus.org/browse/MSUREFIRE-150
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Andrew Perepelytsya
Attachments:
org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
RELEASE-m2-run.txt, SNAPSHOT-m2-run.txt,
TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
Ok, I know how tricky it can be to explain such bug, but I'll try. We've
switched to using 2.3-SNAPSHOT version of the plugin to get the fix for this
error when test reports failed the build in case of test errors without
generating any report. This part works fine now, but it has introduced a
regression.
I'm attaching the test failure reports(it always worked before). To reproduce
the error (tricky part) - I can only think of checking out Mule project SVN
source as of r2315 from http://svn.codehaus.org/mule/ What you need is only a
top-level dir and mule-core.
{panel}
mvn test -Dtest=SerializedUMOMessageTransformersTestCase
{panel}
r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it
to RELEASE, and the problem is again gone.
I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it
helps.
--
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: (MSUREFIRE-150) 2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException (regression)
[ http://jira.codehaus.org/browse/MSUREFIRE-150?page=all ]
Andrew Perepelytsya updated MSUREFIRE-150:
--
Attachment:
FAILED_TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
FAILED_org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt
2.3-SNAPSHOT fails to deserialize an object due to ClassNotFoundException
(regression)
--
Key: MSUREFIRE-150
URL: http://jira.codehaus.org/browse/MSUREFIRE-150
Project: Maven 2.x Surefire Plugin
Issue Type: Bug
Affects Versions: 2.3
Reporter: Andrew Perepelytsya
Attachments:
FAILED_org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
FAILED_TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml,
org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.txt,
RELEASE-m2-run.txt, SNAPSHOT-m2-run.txt,
TEST-org.mule.test.transformers.SerializedUMOMessageTransformersTestCase.xml
Ok, I know how tricky it can be to explain such bug, but I'll try. We've
switched to using 2.3-SNAPSHOT version of the plugin to get the fix for this
error when test reports failed the build in case of test errors without
generating any report. This part works fine now, but it has introduced a
regression.
I'm attaching the test failure reports(it always worked before). To reproduce
the error (tricky part) - I can only think of checking out Mule project SVN
source as of r2315 from http://svn.codehaus.org/mule/ What you need is only a
top-level dir and mule-core.
{panel}
mvn test -Dtest=SerializedUMOMessageTransformersTestCase
{panel}
r2315 has 2.3-SNAPSHOT plugin version declared in a top-level pom. Change it
to RELEASE, and the problem is again gone.
I'm also attaching m2 debug output for SNAPSHOT and RELEASE runs, hope it
helps.
--
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-54) Fixed range versions in dependencies corrupt the module file
Fixed range versions in dependencies corrupt the module file
Key: MIDEA-54
URL: http://jira.codehaus.org/browse/MIDEA-54
Project: Maven 2.x Idea Plugin
Type: Bug
Environment: maven 2.0.4, plugin snapshot built from svn
Reporter: Andrew Perepelytsya
I have the following config snippet declared in pom.xml:
{code}
dependency
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
!--
Explicitly fixing on a dependency version (those square
brackets)
does not seem to work completely as expected at the
moment.
As a workaround, dependency excludes are sprinkled
throughout the project.
Keep an eye on:
http://jira.codehaus.org/browse/MNG-1577
--
version[2.8.0]/version
/dependency
{code}
Note those *square brackets*, this works ok with Maven letting it sort of fix
the 2.8.0 version. Now it seemed to be fine when I initially generated
idea:idea project (dependency was at 2.6.2 version then). Recently it has been
upgraded, and I went back to re-generate the core module via idea:module. The
error I got:
{panel}
[WARNING] An error occurred during dependency resolution of the following
artifact:
org.codehaus.mule:mule-core2.0-SNAPSHOT
Caused by: Missing:
--
1) xerces:xercesImpl:jar:[2.8.0]
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=xerces -DartifactId=xercesImpl \
-Dversion=[2.8.0] -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mule:mule-core:jar:2.0-SNAPSHOT
2) xerces:xercesImpl:jar:[2.8.0]
--
1 required artifact is missing.
{panel}
The generated iml file had *all libraries removed*.
--
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: (MIDEA-54) Fixed range versions in dependencies corrupt the module file
[ http://jira.codehaus.org/browse/MIDEA-54?page=comments#action_65235 ]
Andrew Perepelytsya commented on MIDEA-54:
--
If I temporarily modify pom to reference the version without [] it is ok again,
but I can't leave it like this in the project.
Fixed range versions in dependencies corrupt the module file
Key: MIDEA-54
URL: http://jira.codehaus.org/browse/MIDEA-54
Project: Maven 2.x Idea Plugin
Type: Bug
Environment: maven 2.0.4, plugin snapshot built from svn
Reporter: Andrew Perepelytsya
I have the following config snippet declared in pom.xml:
{code}
dependency
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
!--
Explicitly fixing on a dependency version (those
square brackets)
does not seem to work completely as expected at the
moment.
As a workaround, dependency excludes are sprinkled
throughout the project.
Keep an eye on:
http://jira.codehaus.org/browse/MNG-1577
--
version[2.8.0]/version
/dependency
{code}
Note those *square brackets*, this works ok with Maven letting it sort of fix
the 2.8.0 version. Now it seemed to be fine when I initially generated
idea:idea project (dependency was at 2.6.2 version then). Recently it has
been upgraded, and I went back to re-generate the core module via
idea:module. The error I got:
{panel}
[WARNING] An error occurred during dependency resolution of the following
artifact:
org.codehaus.mule:mule-core2.0-SNAPSHOT
Caused by: Missing:
--
1) xerces:xercesImpl:jar:[2.8.0]
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=xerces -DartifactId=xercesImpl \
-Dversion=[2.8.0] -Dpackaging=jar -Dfile=/path/to/file
Path to dependency:
1) org.codehaus.mule:mule-core:jar:2.0-SNAPSHOT
2) xerces:xercesImpl:jar:[2.8.0]
--
1 required artifact is missing.
{panel}
The generated iml file had *all libraries removed*.
--
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: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository
[ http://jira.codehaus.org/browse/MIDEA-39?page=comments#action_62069 ] Andrew Perepelytsya commented on MIDEA-39: -- I don't think that's a 100% solution. When I have 30 something modules in the project I can generate idea files as you said, once. Then, when 1 module is added, I really want to have an option whether to generate it with the libs or with project dependencies. I guess poms contain all the information requried to have this kind of functinality. To make things worse, some latest IDEA builds have HUGE problems if you have both library jars and project dependencies (sources), resulting in debug breakpoints being skipped altogether (read, impossible to debug anything). In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository - Key: MIDEA-39 URL: http://jira.codehaus.org/browse/MIDEA-39 Project: Maven 2.x Idea Plugin Type: Improvement Versions: 2.0 Environment: Windows XP, IntelliJ 5.1, JDK 1.5.0_06, Maven 2.0.2 Reporter: Vikash Ramanlal Assignee: Brett Porter Priority: Minor When I generate my idea files using mvn idea:idea, all works fine. However if I have module a and module b (both jar packaging) and b depends on a, then I expected the idea plugin to generate the project files such that for module b, a is a dependent module. However what I get is a library entry for a that points to a jar in the local repository. Maven 1.0.2 idea plugin did not work this way. I created the module dependencies in correctly in the idea project. -- 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
