[jira] Commented: (MRESOURCES-104) while filtering resources the token replacement stops at the character @
[
http://jira.codehaus.org/browse/MRESOURCES-104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=264262#action_264262
]
gotama commented on MRESOURCES-104:
---
This is still broken in Maven 3.0.3 and maven-resources-plugin 2.5.
The following is not resource filtered:
a href=mailto:em...@address.com;img src=${content.url}/images/my.gif//a
Additionally, using the following work around breaks the pom.xml schema in
violation of the required element outputDirectory:
configuration
!--outputDirectory${project.build.outputDirectory}/outputDirectory--
useDefaultDelimitersfalse/useDefaultDelimiters
delimiters
delimiter${*}/delimiter
/delimiters
/configuration
and, for some reason, uncommenting the above outputDirectory config to forcing
defining the value to its default, breaks my hibernate unit tests for some
reason due to malconfiguring the datasource.
while filtering resources the token replacement stops at the character @
-
Key: MRESOURCES-104
URL: http://jira.codehaus.org/browse/MRESOURCES-104
Project: Maven 2.x Resources Plugin
Issue Type: Bug
Affects Versions: 2.4
Environment: Windows XP, Java 1.6.0_16
Reporter: Thomas Fahrmeyer
Assignee: Olivier Lamy
Priority: Critical
Fix For: 2.5
Attachments: m3-resource-filtering.zip, MRESOURCES-104.zip
Create a simple file hello.txt under src/main/resources with following
content:
This property ${testProperty} was replaced
but the one behind a @ will not be processed, as you
see: ${testProperty}. You shouldn't see a property reference.
define a build section in your pom.xml like this
build
resources
resource
directorysrc/main/resources/directory
filteringtrue/filtering
includes
include**/*.txt/include
/includes
/resource
resource
directorysrc/main/resources/directory
filteringfalse/filtering
excludes
exclude**/*.txt/exclude
/excludes
/resource
/resources
Run the command:
mvn process-resources -DtestProperty=IwasReplaced
this produces the output
This property IwasReplaced was replaced
but the one behind a @ will not be processed, as you
see: ${testProperty}. You shouldn't see a property reference.
As you see, the second property reference was not resolved. The replacement
just stops after the @ character.
--
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: (MWAR-168) Dependency Has Changed Incorrectly Reported
Dependency Has Changed Incorrectly Reported
-
Key: MWAR-168
URL: http://jira.codehaus.org/browse/MWAR-168
Project: Maven 2.x War Plugin
Issue Type: Bug
Affects Versions: 2.1-alpha-2
Reporter: gotama
In maven-war-plugin 2.1-alpha-2, execute the following on a war project:
mvn clean;
mvn install;
mvn install;
The 3rd command incorrectly lists messages for each dependency as follows:
[INFO] Dependency[Dependency {groupId=com.mycompany, artifactId=myartifact,
version=8.6.1, type=jar}]
has changed (was Dependency {groupId=com.mycompany, artifactId=myartifact,
version=8.6.1, type=jar}).
The first time that mvn install is run, dependencies are added to:
target\myapp-war-1.1-SNAPSHOT\WEB-INF\lib
The second invocation of mvn install appears to fail in comparing the existing
jars in the above path with what is in the repository. The message states the
dependencies have changed when in fact they have not.
This problem does not exist in maven-war-plugin 2.0.2.
--
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=144960#action_144960
]
gotama commented on MASSEMBLY-285:
--
I found this bug while trying to merge 2 fileset directories expecting that
the 2nd would overwrite the first set of files where they overlap (in using one
fileset as default files and the 2nd fileset as overrides).
The result was as described in the bug - 2 identical files added to the
resulting zip file. Upon extraction of the zip, I was prompted for an option to
override one of the files. I also verified that the case on both files was
lower case, so its NOT an issue with the same filename with different case; ie
creating the archive on unix and extracting on Windows.
This bug has been open for a long time. It would be appreciated if this was
fixed ASAP. Its a huge blocker. Thanks!
example assembly.xml file:
assembly xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd;
idbin/id
formats
formatzip/format
/formats
fileSets
fileSet
!--must use absolute reference with ${pom.basedir} to achieve
filtering --
directory${pom.basedir}/src/main/config/defaults//directory
outputDirectory${pom.basedir}/target/work//outputDirectory
filteredtrue/filtered
/fileSet
fileSet
!-- must use absolute reference with ${pom.basedir} to achieve
filtering --
directory${pom.basedir}/src/main/config/overrides//directory
outputDirectory${pom.basedir}/target/work//outputDirectory
filteredtrue/filtered
/fileSet
/fileSets
/assembly
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=144961#action_144961
]
gotama commented on MASSEMBLY-285:
--
Until this is fixed, here is an example work around, if you are interested (the
modules parent is a default jboss-assembly module - the child module inherits
the src and config of the default jboss-assembly):
pom.xml:
plugins
!-- generate resources. merge default and current configurations.
--
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasegenerate-resources/phase
configuration
tasks
copy
todir=${project.build.directory}/generated-resources/
preservelastmodified=true
verbose=true overwrite=true
fileset
dir=${basedir}/../jboss-assembly/src/main/config//
/copy
copy
todir=${project.build.directory}/generated-resources/
preservelastmodified=true
verbose=true overwrite=true
fileset dir=${basedir}/src/main/config//
/copy
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
-- maven assembly plugin --
/plugins
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] Created: (MASSEMBLY-346) DependencySets Includes/Excludes Do Not Work Correctly And Type Is Ignored
DependencySets Includes/Excludes Do Not Work Correctly And Type Is Ignored -- Key: MASSEMBLY-346 URL: http://jira.codehaus.org/browse/MASSEMBLY-346 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Environment: Win2003/Cygwin Maven 2.0.8 Reporter: gotama There are a lot of things wrong with includes/excludes and types in DependencySets. Basically, it needs to be completely regression tested as it completely does not work right in many ways. group:artifact:type In describing type, its ignored. When I put zip for type, I can get ear files. When I exclude all com.* artifacts then include my own com.mydotcom.* - I actually get double the ears in my resulting zip artifact. Example below: dependencySets dependencySet outputDirectory/opt/jboss/server/default/deploy//outputDirectory excludes excludecom:*/exclude /excludes /dependencySet dependencySet outputDirectory/opt/jboss/server/default/deploy//outputDirectory includes includecom.mydotcom:*:ear/include /includes /dependencySet /dependencySets In general, there seems to be issue with the wild card. Putting com.mydotcom:*:zip - once the * is hit, everything after it is ignored. However, for include putting com:*:zip does work correctly - oddly enough. It correctly does NOT give me ear files. When I put com:*:ear I correctly get ears. When I put com.mydotcom:*:zip, then I incorrectly get all ears. Lots of inconsistencies here and odd behavior. Here is a good document on includes/excludes. Unfortunately, this does not work right. I'd suggest excludes/includes be completely re-looked at. Thanks!!! http://www.sonatype.com/book/reference/assemblies.html#d0e13207 -- 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-327) Using filtered within dependencySet unpackOptions
[
http://jira.codehaus.org/browse/MASSEMBLY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=144766#action_144766
]
gotama commented on MASSEMBLY-327:
--
In analyzing the Maven Assembly Plugin code base, from what I can see, the
filtered tag (child of unpackoptions) is not supported.
Please look at AddDependencySetsTask:170:
UnpackOptions opts = dependencySet.getUnpackOptions();
if ( dependencySet.isUnpack() ( opts != null ) )
{
task.setIncludes( opts.getIncludes() );
task.setExcludes( opts.getExcludes() );
}
It does not appear that Maven Assembly Plugin actually supports the filtered
tag given this piece of code which ignores the option.
Further, the UnpackOptions.java isFiltered() method is not referenced in the
Maven Assembly Plugin code base.
The documentation shows that DependencySet supports the UnpackOptions,
which contains the filtered option.
If DependencySet supports UnpackOptions, it should support all three
options; includes, excludes AND filtered - not just two of them.
This is partially implemented support for UnpackOptions. When could we see this
completed? Would be appreciated. Thanks.
Using filtered within dependencySet unpackOptions
-
Key: MASSEMBLY-327
URL: http://jira.codehaus.org/browse/MASSEMBLY-327
Project: Maven 2.x Assembly Plugin
Issue Type: Bug
Affects Versions: 2.2-beta-2
Reporter: Andy Yeung
The files within the unpacked jar did not apply the filters defined.
pom configuration includes
configuration
filters
filtersrc/assemble/filter.properties/filter
/filters
/configuration
which contains
storage.id=abcde
assembly.xml defines dependency set
dependencySet
outputDirectory/snp-agent1/outputDirectory
unpacktrue/unpack
unpackOptions
filteredtrue/filtered
/unpackOptions
scoperuntime/scope
includes
include
XXX.agent:agent-ear-config
/include
/includes
/dependencySet
However, the files within are not filtered.
--
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-327) Using filtered within dependencySet unpackOptions
[ http://jira.codehaus.org/browse/MASSEMBLY-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=144746#action_144746 ] gotama commented on MASSEMBLY-327: -- Any progress on this bug? I have the same problem with dependencysets not being filtered. Thanks. Using filtered within dependencySet unpackOptions - Key: MASSEMBLY-327 URL: http://jira.codehaus.org/browse/MASSEMBLY-327 Project: Maven 2.x Assembly Plugin Issue Type: Bug Affects Versions: 2.2-beta-2 Reporter: Andy Yeung The files within the unpacked jar did not apply the filters defined. pom configuration includes configuration filters filtersrc/assemble/filter.properties/filter /filters /configuration which contains storage.id=abcde assembly.xml defines dependency set dependencySet outputDirectory/snp-agent1/outputDirectory unpacktrue/unpack unpackOptions filteredtrue/filtered /unpackOptions scoperuntime/scope includes include XXX.agent:agent-ear-config /include /includes /dependencySet However, the files within are not filtered. -- 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-102) Module filepath is generated incorrectly for sibling parent
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133423#action_133423
]
gotama commented on MIDEA-102:
--
Dennis,
Have you made any headway on this? I'm sure a lot of people would appreciate
this fix and a working 2.2 IDEA Maven2 plugin.
How can we help?
When you say the tests fail, are those checked in 2.2 junit tests? We should be
able to do something like create a test project and a junit test, check them
in, and then test it in all environments (XP/Cygwin, XP, Linux, OSX) until it
passes. Is this already checked in? If it is, then contributors could try to
fix it and we'd all agree on exactly what has to pass. Can we try to outline
this?
Thanks,
Blaine
Module filepath is generated incorrectly for sibling parent
---
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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-102) Module filepath is generated incorrectly for sibling parent
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=131030#action_131030
]
gotama commented on MIDEA-102:
--
What is the status of this issue?
I'm willing to forgo the whole implementation style argument for simply getting
A fixed version of 2.2 out the door.
The current SNAPSHOT works, so I vote for releasing it, then later on
revisiting the 3 different ways the paths can be corrected. The important thing
is that it is fixed.
In the mean time, there are people out there trying to use Maven for the first
time, and they will not be impressed when 'mvn idea:idea' does not work. This
is one of the cool selling points of Maven to a team of developers and its been
busted for a year.
Release 2.2...
Thanks.
Module filepath is generated incorrectly for sibling parent
---
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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-102) Module filepath is generated incorrectly for sibling parent
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128078
]
gotama commented on MIDEA-102:
--
Dennis, the patch you applied is highly unnecessarily complex. Take a look at
the patch that Roman lists above. This is the one that should be applied. Its 3
times smaller and easy to follow. If Roman's patch does not work, please
explain why your patch works better.
However, Daniel, I have tested both Roman's patch and Dennis' patch, and they
both work. I did not pull the snapshot though, I complied the patches myself.
You may want to delete the
.m2\repository\org\apache\maven\plugins\maven-idea-plugin directory to ensure
you are in fact using the 2.2-SNAPSHOT. If it still does not work, please
elaborate using the test pom's below.
Example:
module filepath=$PROJECT_DIR$/parent.iml/
module filepath=$PROJECT_DIR$/../child/child.iml/
Is the result of running mvn idea:idea on:
c:\foo\parent\pom.xml
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdcom.test/groupId
artifactIdparent/artifactId
namestubhub.com/name
packagingpom/packaging
version3.0.6/version
descriptionParent POM/description
inceptionYear2008/inceptionYear
modules
module../child/module
/modules
/project
c:\foo\child\pom.xml
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdcom.test/groupId
artifactIdparent/artifactId
version3.0.6/version
/parent
artifactIdchild/artifactId
nametest/name
packagingpom/packaging
version3.0.6/version
descriptionchild of test/description
inceptionYear2008/inceptionYear
/project
So, again, lets throw Roman's patch in 2.2 and release this puppy. Nothing else
is open for 2.2.
Thanks.
Module filepath is generated incorrectly for sibling parent
---
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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-102) Module filepath is generated incorrectly for sibling parent
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_128079
]
gotama commented on MIDEA-102:
--
Also, this issue should not be closed until its agreed its fixed. Please reopen.
Module filepath is generated incorrectly for sibling parent
---
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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: (MANTRUN-51) Can't find plugin dependency in multiproject
[
http://jira.codehaus.org/browse/MANTRUN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126760
]
gotama commented on MANTRUN-51:
---
Steinar - THANK YOU for the workaround! OMG I was going nuts for 2 days trying
to figure this out. I figured it was a bug. I was simply trying to use Ant to
scp some files and discovered the same - that on the module itself, it works
but when exec from a parent POM on a multi-module project, the 'scp' fails. I
added:
dependencies
dependency
groupIdant/groupId
artifactIdant-optional/artifactId
version1.5.3-1/version
/dependency
dependency
groupIdant/groupId
artifactIdant-jsch/artifactId
version1.6.5/version
/dependency
/dependencies
to the ant plugin for the first executing module in the multi-module project
and when the last module was exec'd w/ the 'scp' command, all worked ok.
OK, so this bug is 2 years old and still causing pain. Whats the status on
getting this fixed? Any interest? Thanks.
Can't find plugin dependency in multiproject
Key: MANTRUN-51
URL: http://jira.codehaus.org/browse/MANTRUN-51
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.0, 1.1
Environment: maven 2.0.4, antrun 1.0 1.1, jdk 1.5.0_06, windows xp
Reporter: Fredrik Vraalsen
I'm using antrun in my project to create an IzPack installation. The plugin
configuration is below.
When maven is run from the top-level project, the ant taskdef fails because
it cannot find the IzPackTask class. However, when I run maven from the
subproject itself, it works fine. Not sure if this is related to
http://jira.codehaus.org/browse/MANTRUN-49. The error message from maven is
at the bottom.
{noformat}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
phasepackage/phase
configuration
tasks
taskdef name=izpack
classname=com.izforge.izpack.ant.IzPackTask/
izpack
input=${project.build.directory}/classes/izPack.xml
output=${project.build.directory}/CorasTool-${coras.version}-installer.jar
basedir=${project.build.directory}/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdizpack/groupId
artifactIdstandalone-compiler/artifactId
version3.8.0/version
/dependency
/dependencies
/plugin
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error executing ant tasks
Embedded error: taskdef class com.izforge.izpack.ant.IzPackTask cannot be
found
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error executing ant
tasks
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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:585)
[jira] Commented: (MANTRUN-66) Can't execute ant ftp under Java6
[ http://jira.codehaus.org/browse/MANTRUN-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126784 ] gotama commented on MANTRUN-66: --- FTP is an optional ant task. Sounds like you need to define the optional ant tasks dependencies under plugin. This is likely NAB. Can't execute ant ftp under Java6 - Key: MANTRUN-66 URL: http://jira.codehaus.org/browse/MANTRUN-66 Project: Maven 2.x Antrun Plugin Issue Type: Bug Affects Versions: 1.1 Environment: Windows XP, Java 1.6 Reporter: Massimiliano Amato I have a simple and build.xml file that perform an FTP, that is called by antrun, if i execute it using Java5 it works like a charm, if i execute using Java6 it doesn't work and says i can't find a needed library Problem is that if i use Java6 and i call the ant file directly works so it must be some kind of antrun issue with java6 i think, i have also another antrun task defined in my project and that works, so probably issue is only with tasks (like ftp) that needs library -- 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-102) CLONE -still broken - Module filepath is generated incorrectly
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126511
]
gotama commented on MIDEA-102:
--
http://cygwin.com/setup.exe
... just click through 'next' on everything and get the basic install. quick
easy setup... beats the windows prompt for those on the corporate XP system! :)
CLONE -still broken - Module filepath is generated incorrectly
--
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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-102) CLONE -still broken - Module filepath is generated incorrectly
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126280
]
gotama commented on MIDEA-102:
--
Actually, I just tested Roman's code above - adding it to the latest
2.2-SNAPSHOT and the paths are correct for an idea project with the parent and
modules at the same level. The modules paths are correctly relative using ../.
Someone should throw that code in there, close this out and release 2.2. WFM.
CLONE -still broken - Module filepath is generated incorrectly
--
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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-102) CLONE -still broken - Module filepath is generated incorrectly
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126381
]
gotama commented on MIDEA-102:
--
I would add it - but I'm new to this project so I don't know how to get
permissions to check in code and what the official release process is. How do
you become a committer?
Also, someone should check out the ClassWorlds dependency for the tests. The
tests fail because they are missing the ClassWorlds dependency.
dependency
groupIdclassworlds/groupId
artifactIdclassworlds/artifactId
version1.1/version
scopetest/scope
/dependency
CLONE -still broken - Module filepath is generated incorrectly
--
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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: (MANTRUN-53) add ant optional task support
[
http://jira.codehaus.org/browse/MANTRUN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126098
]
gotama commented on MANTRUN-53:
---
This Maven config uses the optional ant tasks scp and sshexec to remotely stop
JBoss, copy an EAR file to a remote server, and remotely start JBoss.
plugins
plugin
artifactIdmaven-antrun-plugin/artifactId
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-jsch/artifactId
version1.7.0/version
/dependency
dependency
groupIdcom.jcraft/groupId
artifactIdjsch/artifactId
version0.1.31/version
/dependency
/dependencies
executions
execution
phasecompile/phase
configuration
tasks
property environment=env/
sshexec host=hostname
username=username
keyfile=${env.USERPROFILE}/.ssh/id_rsa
command=service jboss stop
/
scp file=c:/deploy/myApp.ear
todir=[EMAIL
PROTECTED]:/opt/jboss/server/default/deploy
keyfile=${env.USERPROFILE}/.ssh/id_rsa
passphrase=
verbose=true
/
sshexec host=hostname
username=username
keyfile=${env.USERPROFILE}/.ssh/id_rsa
command=service jboss start
/
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
/plugin
add ant optional task support
-
Key: MANTRUN-53
URL: http://jira.codehaus.org/browse/MANTRUN-53
Project: Maven 2.x Antrun Plugin
Issue Type: Improvement
Affects Versions: 1.2
Environment: windows 2000,java 1.4.2
Reporter: bingwuli
Assignee: Carlos Sanchez
I use maven-antrun-plugin for my project recently. Althought this plugin give
me some convenience, I find it doesn't support ant optional task. In my
project ,I need to use native2ascii to convert my messages. When I put such
ant segment tasksnative2ascii encoding=GBK src=src/main/conf/message
dest=${project.build.outputDirectory} includes=**/*.txt ext =
.properties//tasks into plugin's configuration, it doesn't work.
After I carefully study plugin's docment ,I find the plugin doesn't depend on
ant optional jar .After I add ant-optional jar into dependency path ,and
rewrite ant segent as such ,it does work for me.
tasktaskdef name=native2ascii
classname=org.apache.tools.ant.taskdefs.optional.Native2Ascii classpathref
= maven.compile.classpath /native2ascii encoding=GBK
src=src/main/conf/messagedest=${project.build.outputDirectory}
includes=**/*.txt ext = .properties//task
I think it good idea that this plugin will support ant optional task.
--
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-102) CLONE -still broken - Module filepath is generated incorrectly
[
http://jira.codehaus.org/browse/MIDEA-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126270
]
gotama commented on MIDEA-102:
--
I am running XP, Maven 2.0.8, Maven IDEA plugin 2.1 and Cygwin. When I issue
'mvn idea:idea' on the XP command line my IDEA project file is fine. When I
issue the same command in Cygwin, the paths are incorrect.
Using the 2.2-SNAPSHOT it works fine, except for the above noted conditions
where the parent and module dirs are at the same level. This is a different bug.
This issue is working on over 8 months without a release, yet there is a fix
for one of the show stopping bugs which prevents you from using the plugin. 2.2
should be released as is now and a new fresh jira issue should be created to
address the bug about the paths being incorrect for when the parents and
modules are at the same level. This plugin is broken without releasing 2.2.
CLONE -still broken - Module filepath is generated incorrectly
--
Key: MIDEA-102
URL: http://jira.codehaus.org/browse/MIDEA-102
Project: Maven 2.x IDEA Plugin
Issue Type: Bug
Affects Versions: 2.1
Environment: $ mvn -v
Maven version: 2.0.7
Java version: 1.5.0_11
OS name: windows xp version: 5.1 arch: x86
cygwin
Reporter: Joern Huxhorn
Assignee: Dennis Lundberg
Fix For: 2.2
Attachments: maven-idea-plugin-MIDEA-102.patch
I have a multi-module mvn project.
When I do an mvn idea:clean idea:idea, the following ProjectModuleManager
snippet in the top level .ipr is generated:
component name=ProjectModuleManager
modules
!-- module filepath=$$PROJECT_DIR$$/${pom.artifactId}.iml/ --
module filepath=$PROJECT_DIR$/gateway.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/domain/gateway-domain.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/instruction-store/gateway-instruction-store.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/parser/gateway-parser.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/psrgeneration/gateway-psr-generation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/output/gateway-output.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/destination-resolver/gateway-destination-resolver.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/choreography/gateway-choreography.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/presentation/gateway-presentation.iml/
module
filepath=$PROJECT_DIR$/C:/dev/voca/gateway/assembly/gateway-assembly.iml/
/modules
/component
The $PROJECT_DIR in this case is C:/dev/voca/gateway/.
But this path is being appended in a hard-coded fashion after the
$PROJECT_DIR entry.
The symptom in Intellij is the following error message:
Cannot load module: File
C:\dev\voca\gateway\C:\dev\voca\gateway\domain\gateway-domain.iml does not
exist
Would you like to remove the module from the project?
The workaround is to delete the extra appended file path from each module
entry in the above mentioned snippet.
--
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
