[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-tabpanelfocusedCommentId=133654#action_133654
]
bastian kaempfe commented on MANTRUN-51:
My guess is that the problem is caused ANT.
ANT simply can set properties only ONE TIME. if you try to set a named property
severeal times, you succeed only the first time.
every next try does not overwrite the first value, thus when using the
property, you will always get the first value.
the maven-antrun-plugins tries to set several properties, for example:
maven.plugin.classpath.
so the first project wins. every property this antrun-plugin sets will be
available in every other projet, running after this one.
and no other project can overwrite properties, the first project has set.
maybe the solution could be to start the ant-task in an own java-process, like
the fork of the maven-compiler-plugin.
another way could be to define a prefix or suffix for every property that
will be set by maven within a maven-antrun-plugin-block.
could be: prefix=srcgen - maven property : maven.plugin.classpath.srcgen
instead of only maven.plugin.classpath
or one could use the maven-antrun-plugin-id, if one is provided.
so if my execution-id is backend-wsdl2java the maven-set properties could be
maven.plugin.classpath.backend-wsdl2java
i hope, this helps in understanding and solving...
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)
[jira] Commented: (MANTRUN-52) plugin dependencies seem to get lost when using the plugin multiple times
[
http://jira.codehaus.org/browse/MANTRUN-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133657#action_133657
]
bastian kaempfe commented on MANTRUN-52:
i thing, this might basically be ste same problem as described in MANTRUN-51
http://jira.codehaus.org/browse/MANTRUN-51
plugin dependencies seem to get lost when using the plugin multiple times
-
Key: MANTRUN-52
URL: http://jira.codehaus.org/browse/MANTRUN-52
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.1
Reporter: Jorg Heymans
Priority: Critical
say in the same pom you have
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
configuration
tasks
replace dir=${project.build.outputDirectory}
replaceFilterFile=${basedir}/src/main/properties/replaceSchemaNames.properties
/
/tasks
/configuration
/build
and
profiles
profile
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idDatabase recreation/id
configuration
tasks
sql /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdoracle/groupId
artifactIdoracle-jdbc/artifactId
version1.4_g/version
/dependency
/dependencies
/plugin
/plugins
/build
/profile
then the antrun configured in the profile will fail saying that it can't find
the oracle driver. If i move the oracle dependency to the plugin configured
in build then it works.
--
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: (MANTRUN-52) plugin dependencies seem to get lost when using the plugin multiple times
[
http://jira.codehaus.org/browse/MANTRUN-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133657#action_133657
]
seafoxx edited comment on MANTRUN-52 at 5/6/08 5:11 AM:
i thing, this might basically be ste same problem as described in MANTRUN-51
http://jira.codehaus.org/browse/MANTRUN-51
- When using more than one antrun-blocks, the first one sets all properties
which cannot be overwritten by the other antrun-blocks called afterwards
was (Author: seafoxx):
i thing, this might basically be ste same problem as described in MANTRUN-51
http://jira.codehaus.org/browse/MANTRUN-51
plugin dependencies seem to get lost when using the plugin multiple times
-
Key: MANTRUN-52
URL: http://jira.codehaus.org/browse/MANTRUN-52
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.1
Reporter: Jorg Heymans
Priority: Critical
say in the same pom you have
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
configuration
tasks
replace dir=${project.build.outputDirectory}
replaceFilterFile=${basedir}/src/main/properties/replaceSchemaNames.properties
/
/tasks
/configuration
/build
and
profiles
profile
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idDatabase recreation/id
configuration
tasks
sql /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdoracle/groupId
artifactIdoracle-jdbc/artifactId
version1.4_g/version
/dependency
/dependencies
/plugin
/plugins
/build
/profile
then the antrun configured in the profile will fail saying that it can't find
the oracle driver. If i move the oracle dependency to the plugin configured
in build then it works.
--
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: (MANTRUN-52) plugin dependencies seem to get lost when using the plugin multiple times
[
http://jira.codehaus.org/browse/MANTRUN-52?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133657#action_133657
]
seafoxx edited comment on MANTRUN-52 at 5/6/08 5:11 AM:
i thing, this might basically be ste same problem as described in MANTRUN-51
- When using more than one antrun-blocks, the first one sets all properties
which cannot be overwritten by the other antrun-blocks called afterwards
was (Author: seafoxx):
i thing, this might basically be ste same problem as described in MANTRUN-51
http://jira.codehaus.org/browse/MANTRUN-51
- When using more than one antrun-blocks, the first one sets all properties
which cannot be overwritten by the other antrun-blocks called afterwards
plugin dependencies seem to get lost when using the plugin multiple times
-
Key: MANTRUN-52
URL: http://jira.codehaus.org/browse/MANTRUN-52
Project: Maven 2.x Antrun Plugin
Issue Type: Bug
Affects Versions: 1.1
Reporter: Jorg Heymans
Priority: Critical
say in the same pom you have
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
configuration
tasks
replace dir=${project.build.outputDirectory}
replaceFilterFile=${basedir}/src/main/properties/replaceSchemaNames.properties
/
/tasks
/configuration
/build
and
profiles
profile
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idDatabase recreation/id
configuration
tasks
sql /
/tasks
/configuration
goals
goalrun/goal
/goals
/execution
/executions
dependencies
dependency
groupIdoracle/groupId
artifactIdoracle-jdbc/artifactId
version1.4_g/version
/dependency
/dependencies
/plugin
/plugins
/build
/profile
then the antrun configured in the profile will fail saying that it can't find
the oracle driver. If i move the oracle dependency to the plugin configured
in build then it works.
--
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: (MANTRUN-51) Can't find plugin dependency in multiproject
[
http://jira.codehaus.org/browse/MANTRUN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133654#action_133654
]
seafoxx edited comment on MANTRUN-51 at 5/6/08 5:21 AM:
My guess is that the problem is caused ANT.
description of the ant-property-task:
*Properties are immutable: whoever sets a property first freezes it for the
rest of the build; they are most definitely not variables.*
i think, this might be the root cause of these problems.
ANT simply can set properties only ONE TIME. if you try to set a named property
severeal times, you succeed only the first time.
every next try does not overwrite the first value, thus when using the
property, you will always get the first value.
the {{maven-antrun-plugins}} tries to set several properties, for example:
{{maven.plugin.classpath}}.
so the first project wins. every property this {{maven-antrun-plugin}} sets
will be available in every other projet, running after this one. and no other
project can overwrite properties, the first project has set.
maybe the solution could be to start the ant-task in an own java-process, like
the {{fork}} of the {{maven-compiler-plugin}}.
another way could be to define a prefix or suffix for every property that
will be set by maven within a {{maven-antrun-plugin}}-block.
could be: prefix={{srcgen}} - maven property :
{{maven.plugin.classpath.srcgen}} instead of only {{maven.plugin.classpath}}
or one could use the {{maven-antrun-plugin}}-{{id}}, if one is provided.
so if my execution-id is {{backend-wsdl2java}} the maven-set properties could
be {{maven.plugin.classpath.backend-wsdl2java}}
i hope, this helps in understanding and solving...
was (Author: seafoxx):
My guess is that the problem is caused ANT.
description of the ant-property-task:
Properties are immutable: whoever sets a property first freezes it for the rest
of the build; they are most definitely not variables.
i think, this might be the root cause of these problems.
ANT simply can set properties only ONE TIME. if you try to set a named property
severeal times, you succeed only the first time.
every next try does not overwrite the first value, thus when using the
property, you will always get the first value.
the maven-antrun-plugins tries to set several properties, for example:
maven.plugin.classpath.
so the first project wins. every property this antrun-plugin sets will be
available in every other projet, running after this one.
and no other project can overwrite properties, the first project has set.
maybe the solution could be to start the ant-task in an own java-process, like
the fork of the maven-compiler-plugin.
another way could be to define a prefix or suffix for every property that
will be set by maven within a maven-antrun-plugin-block.
could be: prefix=srcgen - maven property : maven.plugin.classpath.srcgen
instead of only maven.plugin.classpath
or one could use the maven-antrun-plugin-id, if one is provided.
so if my execution-id is backend-wsdl2java the maven-set properties could be
maven.plugin.classpath.backend-wsdl2java
i hope, this helps in understanding and solving...
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
[jira] Issue Comment Edited: (MANTRUN-51) Can't find plugin dependency in multiproject
[
http://jira.codehaus.org/browse/MANTRUN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133654#action_133654
]
seafoxx edited comment on MANTRUN-51 at 5/6/08 5:17 AM:
My guess is that the problem is caused ANT.
description of the ant-property-task:
Properties are immutable: whoever sets a property first freezes it for the rest
of the build; they are most definitely not variables.
i think, this might be the root cause of these problems.
ANT simply can set properties only ONE TIME. if you try to set a named property
severeal times, you succeed only the first time.
every next try does not overwrite the first value, thus when using the
property, you will always get the first value.
the maven-antrun-plugins tries to set several properties, for example:
maven.plugin.classpath.
so the first project wins. every property this antrun-plugin sets will be
available in every other projet, running after this one.
and no other project can overwrite properties, the first project has set.
maybe the solution could be to start the ant-task in an own java-process, like
the fork of the maven-compiler-plugin.
another way could be to define a prefix or suffix for every property that
will be set by maven within a maven-antrun-plugin-block.
could be: prefix=srcgen - maven property : maven.plugin.classpath.srcgen
instead of only maven.plugin.classpath
or one could use the maven-antrun-plugin-id, if one is provided.
so if my execution-id is backend-wsdl2java the maven-set properties could be
maven.plugin.classpath.backend-wsdl2java
i hope, this helps in understanding and solving...
was (Author: seafoxx):
My guess is that the problem is caused ANT.
ANT simply can set properties only ONE TIME. if you try to set a named property
severeal times, you succeed only the first time.
every next try does not overwrite the first value, thus when using the
property, you will always get the first value.
the maven-antrun-plugins tries to set several properties, for example:
maven.plugin.classpath.
so the first project wins. every property this antrun-plugin sets will be
available in every other projet, running after this one.
and no other project can overwrite properties, the first project has set.
maybe the solution could be to start the ant-task in an own java-process, like
the fork of the maven-compiler-plugin.
another way could be to define a prefix or suffix for every property that
will be set by maven within a maven-antrun-plugin-block.
could be: prefix=srcgen - maven property : maven.plugin.classpath.srcgen
instead of only maven.plugin.classpath
or one could use the maven-antrun-plugin-id, if one is provided.
so if my execution-id is backend-wsdl2java the maven-set properties could be
maven.plugin.classpath.backend-wsdl2java
i hope, this helps in understanding and solving...
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]
[jira] Issue Comment Edited: (MANTRUN-51) Can't find plugin dependency in multiproject
[
http://jira.codehaus.org/browse/MANTRUN-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=133654#action_133654
]
seafoxx edited comment on MANTRUN-51 at 5/6/08 5:42 AM:
still got the same problem.
was (Author: seafoxx):
My guess is that the problem is caused ANT.
description of the ant-property-task:
*Properties are immutable: whoever sets a property first freezes it for the
rest of the build; they are most definitely not variables.*
i think, this might be the root cause of these problems.
ANT simply can set properties only ONE TIME. if you try to set a named property
severeal times, you succeed only the first time.
every next try does not overwrite the first value, thus when using the
property, you will always get the first value.
the {{maven-antrun-plugins}} tries to set several properties, for example:
{{maven.plugin.classpath}}.
so the first project wins. every property this {{maven-antrun-plugin}} sets
will be available in every other projet, running after this one. and no other
project can overwrite properties, the first project has set.
maybe the solution could be to start the ant-task in an own java-process, like
the {{fork}} of the {{maven-compiler-plugin}}.
another way could be to define a prefix or suffix for every property that
will be set by maven within a {{maven-antrun-plugin}}-block.
could be: prefix={{srcgen}} - maven property :
{{maven.plugin.classpath.srcgen}} instead of only {{maven.plugin.classpath}}
or one could use the {{maven-antrun-plugin}}-{{id}}, if one is provided.
so if my execution-id is {{backend-wsdl2java}} the maven-set properties could
be {{maven.plugin.classpath.backend-wsdl2java}}
i hope, this helps in understanding and solving...
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
