Hi Guillaume,
with inheritRefs attachartifact works perfectly for me.
Merci beaucoup,
Juergen
Am 03.06.2017 20:26 schrieb "Guillaume Boué" :
> That means you're missing inheritRefs=true in the task. It is
> necessary for the references to be propagated to subprojects.
>
>
That means you're missing inheritRefs=true in the task. It is
necessary for the references to be propagated to subprojects.
I've also added an integration test in
https://github.com/apache/maven-plugins/tree/trunk/maven-antrun-plugin/src/it/attach-artifact-from-ant-task
that you can maybe
Hi,
no, still does not work.
Where is your changed source? I could run it in the debugger..
Juergen
Maven project reference not found: maven.project.ref
at
org.apache.maven.ant.tasks.AttachArtifactTask.execute(AttachArtifactTask.java:80)
Am 01.06.2017 19:17 schrieb "Guillaume Boué"
It's currently in Apache snapshot repository located at
https://repository.apache.org/content/repositories/snapshots. You can
add this repository as a plugin repository to your settings or POM for
the test.
apache-snapshots-plugin
There is no 3.0.0-SNAPSHOT of maven-antrun-plugin, is it?
org/apache/maven/ant/tasks/AttachArtifactTask.class is in
maven-antrun-plugin-1.8.jar
Am 31.05.2017 19:57 schrieb "Guillaume Boué" :
Hi,
I looked into this issue and committed a fix for it. The core problem was
that
Hi,
I looked into this issue and committed a fix for it. The core problem
was that the 'attachartifact' task launched from the external Ant build
was working from a clone of the Maven project, instead of the project
itself. Can you try the latest 3.0.0-SNAPSHOT and report back?
Le
Hi,
I found a solution, not pretty, but it actually works:
in an pom-inline antrun task call a Javascript function with the
project as parameter, in Javascript one can do all interesting things
(loop over properties from an ant property file) and call the
attachartifact task.
Cheers,
Juergen
Hi,
if i correctly understand you have a property file for each environment
and maybe some other files and a base artifact (jar/war?) now it sounds
you have to build for each environment a different jar/war ?
Maybe something like this could help here:
Hi Jörg,
problem is, I have to build message driven beans, some 20, only difference
is the queue name in the deployment descriptor. Queue names are listed in a
property file.
I know that Maven wants no environment specific properties in artifacts,
but Sun defined the activation spec for MDBs. And
Hi Jürgen,
Jürgen Weber wrote:
> What is the recommended work-around for attaching artifacts created by
> antrun?
>
> * forward target directory as variable to ant ?
That helps if the created files should be removed in a normal "clean" phase.
> * build-helper-maven-plugin attach-artifact ?
10 matches
Mail list logo