>>>>> Steinar Bang :
>> https://github.com/steinarb/bang-bompom/blob/20d12dd29b2d3758f1c237b3c29df98ecc9125f8/pom.xml#L96
>> When you set a configuration parameter via XML, you may not override it
>> anymore with the property in my experience.
> Thanks! Acco
> Tamás Cservenák :
> Howdy,
> for start https://issues.apache.org/jira/browse/MNG-8012
> Basically BOM _should not_ be used within a reactor (in other words,
> in a reactor where BOM is being built, it must/should not be
> referenced).
> Maven "managed dependencies" should be handled the "usu
>>>>> Steinar Bang :
>>>>> Mirko Friedenhagen :
>> https://github.com/steinarb/bang-bompom/blob/20d12dd29b2d3758f1c237b3c29df98ecc9125f8/pom.xml#L96
>> When you set a configuration parameter via XML, you may not override it
>> anymore with the pro
> Mirko Friedenhagen :
> https://github.com/steinarb/bang-bompom/blob/20d12dd29b2d3758f1c237b3c29df98ecc9125f8/pom.xml#L96
> When you set a configuration parameter via XML, you may not override it
> anymore with the property in my experience.
Thanks! According to the git history, this seems
Platform: debian 13 "trixie", amd64, maven 3.9.10, java 21.0.4,
versions-maven-plugin 2.18.0
I am trying to change the bang-servlet.version property in this pom
https://github.com/steinarb/bang-bompom/blob/master/bang-pom/bang-app-pom/pom.xml#L31
using this script:
#!/bin/sh
SERVLET_VERSION=$
> Tamás Cservenák :
> Cool! So then we are sorted out?
Yep!
> If yes:
> In cases like this, if we'd get a beer, half of it would be yours :D
Let's share! :-)
Thanks!
-
To unsubscribe, e-mail: users-unsubscr...@maven.apac
>>>>> Steinar Bang :
> So I put the javadoc generation config back, and "mvn release:prepare"
> stopped working again.
> I have tried the following:
> 1. Remove the aggregate javadoc
> 2. Go back from javadoc-no-fork to javadoc as the execution goal
&g
>>>>> Steinar Bang :
> Tried again to remove source attachments and javadoc attachments and
> that made "mvn release:prepare" run without errors.
> However, "mvn release:perform" failed, and it looks like maven central
> rejected the deploy b
Tried again to remove source attachments and javadoc attachments and
that made "mvn release:prepare" run without errors.
However, "mvn release:perform" failed, and it looks like maven central
rejected the deploy because there was no source jars or javadoc jars
attached to the artifacts.
https://
> Tamás Cservenák :
> Steinar, also try with newer Maven, see 3.8.8 and 3.8.9 (if 3.9.10 is
> not an option for you):
> https://issues.apache.org/jira/projects/MNG/versions/12352869
> https://issues.apache.org/jira/projects/MNG/versions/12353108
> There were some bugfixes related to forking
>>>>> Steinar Bang :
> Thanks! Unfortunately it didn't work for me. :-/
> Here is what I did (I may have changed the wrong config...?)
>
> https://github.com/steinarb/authservice/commit/8da1dfdb3cf896ee20c496ab662e4dffdae160b1
> Here is the resulting output
> Tamás Cservenák :
> Howdy,
> I performed local some changes:
> https://gist.github.com/cstamas/7f8194817660df4b0ed62ee16eb620f9
> Note: `local/` was just added to be able to use -Dmaven.repo.local=local
> And cannot reproduce with those:
> https://gist.github.com/cstamas/be6448a532a7c21511
>>>>> Steinar Bang :
>> (I presume this is a problem to do with this being built with a
>> non-snapshot version...? I see 3.0.2 in the failing compilation and that
>> is the version I am trying to release?)
What's left over when "mvn release:prepar
>>>>> Steinar Bang :
> Platform: debian 12.11 "bookworm", amd64
> java 21.0.4 2024-07-16 LTS
> Apache Maven 3.8.7
> I have a Java project built with maven that builds ok with "mvn clean install"
> https://gist.github.com/ste
Platform: debian 12.11 "bookworm", amd64
java 21.0.4 2024-07-16 LTS
Apache Maven 3.8.7
I have a Java project built with maven that builds ok with "mvn clean install"
https://gist.github.com/steinarb/389a0b9c3e33cd186536bc476c0d9e1d
but fails with "mvn release:prepare"
https:
>>>>> Steinar Bang :
> Side note: Heh, I just discovered an unexpected side effect of my schema
> conversion with System.exit(): it can bring down eclipse that has a
> maven project where the schema conversion is done.
exec-maven-plugin has been released and this now wo
Side note: Heh, I just discovered an unexpected side effect of my schema
conversion with System.exit(): it can bring down eclipse that has a
maven project where the schema conversion is done.
I wonder if the exec-maven-plugin fix mentioned in this thread also will
fix eclipse or if I need a differ
> Slawomir Jaranowski :
> Hi Steinar
> Can you test my patch: https://github.com/mojohaus/exec-maven-plugin/pull/472
Looks successful to me:
https://gist.github.com/steinarb/922753fd7bcb7189c1716e7761d237df
Thanks!
Here is what I did to test:
git clone https://github.com/mojohaus/exec-mav
> Thomas Broyer :
> Use exec:exec instead:
> https://www.mojohaus.org/exec-maven-plugin/examples/example-exec-for-java-programs.html
I don't wish to start a separate process for to convert schemas, so this
isn't an option for me.
But thanks for responding.
-
> Thorsten Heit :
> Out of curiosity I cloned your project, executed "mvn clean install",
> but couldn't reproduce the error you've seen...
Actually, you did.
> convert-xsd-to-rnc % mvn clean install
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< no.priv.bang.xml.schema:c
>>>>> Steinar Bang :
>> What do you mean by "Maven build abrubtly terminates"?
> Here's the output of "mvn clean install" on the project. Maven build
> ends on line 26 with no error message:
> https://gist.github.com/steinarb/12596b7771b
> Alexander Kriegisch :
> A quick test shows that the feature still seems to work as expected up
> to JDK 24 [1].
I forgot to say what I was using, but I'm currently using Java 21.0.4
from openjdk on debian 12.10 "bookwork" on amd64.
> What do you mean by "Maven build abrubtly terminates"?
> Slawomir Jaranowski :
> You can try with - blockSystemExit
I am trying with blockSystemExit:
https://gist.github.com/steinarb/9f5105c68bf0c5978272e5af99b2ab5f#file-pom-xml-L205
-
To unsubscribe, e-mail: users-unsubscr..
I am trying to make exec:java from exec-maven-plugin convert a Relax-NG
schema in XML notation (RNG) to a Relax-NG schema in compact notation:
https://gist.github.com/steinarb/9f5105c68bf0c5978272e5af99b2ab5f#file-pom-xml-L197
The config successfully does the file conversion, but then the maven
>>>>> Steinar Bang :
>>>>> Stanimir Stamenkov :
>> Did you have test in the exec plugin
>> configuration?
> Ah, no. I did not. I will try with that in place (and a test scope
> project dependency).
Using test and test on
the project depen
> Stanimir Stamenkov :
> O.k. Looking back I couldn't see any of the gists with a test scope
> "msv-rngconverter" – am I missing it?
No that's correct. I did not make a gist of that, since what I tried was
just the same as the compile scope one, with of the depedency
changed.
> Did you hav
> Stanimir Stamenkov :
> Does it work adding the dependency to the plugin dependencies, instead?
>
> org.codehaus.mojo
> exec-maven-plugin
> 3.5.0
>
>
> net.java.dev.msv
> msv-rngconverter
> 202
Platform: debian 12.10 "bookworm", amd64, java 21.0.4, maven 3.8.7,
exec-maven-plugin 3.5.0
If I add the jar file containing the mainClass as a compile scope
dependency on the project:
https://gist.github.com/steinarb/d177a1c1146fedf374608390fbbe4841#file-pom-xml-L119
Then this exec-maven-plug
> Nils Breunese :
> Fabric8’s docker-maven-plugin works for my projects on macOS with Rancher
> Desktop providing Docker.
> The GitHub issue you reported seems to be specifically related to the docker
> command being run by docker-maven-plugin not being supported by the docker
> binary on y
> Tomaž Majerhold :
> Maybe look at https://github.com/GoogleContainerTools/jib
Thanks for responding, but... not sure if this one does what I want?
Unless I'm mistaken this one is for packaging up a jar inside a docker
image?
And that's not what I'm looking for. I'm looking for a maven pl
I recently discovered that the docker-maven-plugin I had been using was
archived on March 21 2022 and had the last code update on Januar 15 2020:
https://github.com/spotify/docker-maven-plugin
The first thing I did was google and this one came up first, and seems
actively maintained:
https://git
Versions: debian 10.5 "buster", amd64
openjdk 11
maven 3.6.0 (debian) and 3.6.3 (apache binary) (same issue on both
versions of maven)
When I introduced a nexus-staging-maven-plugin config into my project's
top pom, "mvn deploy" of snapshots stopped working.
Does anyone know
Thanks to Thomas Broyer and Karl Heinz Marbaise!
Replacing aggregate-jar in the parent POM with aggregate-no-fork (and an
extra jar:jar) cut down the build time from around 2:50 min to around
50s on a 3.30GHz i5 with openjdk11.
The maven output contained much less clutter avoided re-running npm a
> Thomas Broyer :
> In this specific case, what causes the forking is the javadoc:aggregate
> goal. That one is meant to be used on the command line. If you want to bind
> it to a build phase, you should use javadoc:aggregate-no-fork.
Thanks! I will switch goal here!
> Also, javadoc:aggregat
> Karl Heinz Marbaise :
> based on what I can identify in your pom files/output is that in your
> currenty configuration the maven-javadoc-plugin is configured to use the
> goal: aggregate[1] which is a goal which forkes the lifecycle. There is
> an equivalent "aggregate-no-fork"[2] which coul
This project https://github.com/steinarb/authservice has a lot of
messages like this in the build output:
[INFO]
[INFO] Forking Authentication webapp 1.8.0-SNAPSHOT
[INFO] >
>>>>> Steinar Bang :
> Versions: Java 1.8
> maven 3.5.0
> frontend-maven-plugin 1.6
> maven-bundle-plugin 2.5.3
> I'm using frontend-maven-plugin to get webpack to put a webpack'd
> version of a react.js frontend into target
Versions: Java 1.8
maven 3.5.0
frontend-maven-plugin 1.6
maven-bundle-plugin 2.5.3
I'm using frontend-maven-plugin to get webpack to put a webpack'd
version of a react.js frontend into target/classes/bundle.js
However, maven-bundle-plugin by default doesn't pick up s
>>>>> Steinar Bang :
> I'm deploying maven snapshots from travis CI-builds, to a "low-cost" (in
> terms of server resources) repository, consisting of an ftp server, and
> served out with nginx.
> I would like to clean up the snapshots, so that only the
> Karl Heinz Marbaise :
>> Ie. there is no "post-deploy" lifecycle phase to run my mojo in.
> We are thinking already of such things and which might be part of
> Maven 4+...[1]
> [1]:https://issues.apache.org/jira/browse/MNG-5666
Great news! :-)
>> Is there a way to order mojos bound to th
I would like to run a mojo to run after deploy has completed
successfully, to notify some OSGi bundles running in karaf, that they
should update themselves with new deployed snapshots in a maven
repository.
The problem is that the deploy lifecycle phase is the last lifecycle
phase of the default l
I'm deploying maven snapshots from travis CI-builds, to a "low-cost" (in
terms of server resources) repository, consisting of an ftp server, and
served out with nginx.
I would like to clean up the snapshots, so that only the most recent
snapshot of each artifact is kept.
I'm thinking that the b
>>>>> Steinar Bang :
>>>>> Anders Hammar :
>> Possibly you could use a range with no upper limit for a dependency and
>> then bind dependency:unpack.
> Ah, ok, so that is possible...?
> Definitely something to try!
That worked, but not for depen
> Anders Hammar :
> Possibly you could use a range with no upper limit for a dependency and
> then bind dependency:unpack.
Ah, ok, so that is possible...?
Definitely something to try!
Thanks for the tip!
-
To unsubscribe,
Is there a way to find what the latest version of an artifact, and then
download and unzip the artifact?
My usecase is that I would like a simple way to download and unzip the
newest version of an izpack installer from a local Nexus repository.
I've googled a bit, and a possible solution would be
> "Preston, Dale" :
> I was just wondering why this group uses an email list rather than a
> forum. It seems forum software is more searchable and filterable than
> email lists.
If you want to, you can read this list in a forum-like, searchable form here:
http://blog.gmane.org/gmane.comp.ja
If I add the atlassian repos (the SDK local disk repo and the
https://maven.atlassian.com/repository/public repo to the settings.xml,
will maven still fetch dependencies from maven central?
I have tried googling for the behaviour here, and I have tried running
mvn help:active-profiles
without be
> Anders Hammar :
> I categorize different usage of Maven into two categories:
> A) As a build tool
> B) As a utility tool
[snip!]
> My point here is that if you're in category A then Maven is absolutely
> appropriate. At least if you're building everything else with
> Maven. But if you're in
I have access to a Jar-file that contains code that:
- Reads an excel file containing a JQL query, the names of the fields
from the JQL results to include in excel, as well as the sheets that
are to be populated
- Talks to Jira, using the Jira REST API, to do the query and extract
the re
>>>>> Steinar Bang :
> On the recommended book list mentioned earlier, I will in particular
> mention "Maven by example"
> http://www.sonatype.com/Support/Books/Maven-By-Example
The download page lists PDF and HTML versions. I was able to build
myself an ePu
> "Rob Withers" :
> I am guilty for being lazy. I really hate all this build config
> stuff...
[snip!]
FWIW, in my experience embracing maven patterns allows you to reduce
build config to a minimum.
On the recommended book list mentioned earlier, I will in particular
mention "Maven by examp
> "Rob Withers" :
> Ok, I got around the issue with number 3 by removing the modules and
> building the top pom, then adding the modules.
Ok. What you did with that, was to add the top POM to your local
repository, and then the modules will find it there, rather than in
their parent directo
> "Rob Withers" :
>> What's the directory layout of your projects? Where do you issue the
>> command? What are the error messages you're getting.
> workspace/
> murmur/
> pom.xml
> murmur-events/
> pom.xml
> I issue the command in the murmur-events dir and I have n
> "Rob Withers" :
> Here are my questions, I suppose:
> 1.. How can I install murmur-events, even though pmd/findbugs is issuing
> warnings? The mvn install is failing.
What's the directory layout of your projects? Where do you issue the
command? What are the error messages you're getti
>>>>> Steinar Bang :
>>>>> Steinar Bang :
>> If it's still 3.8.1, I'll file a bug.
> Hm... that didn't work...?
I have now filed a bug, in case anyone would like to vote on it:
https://jira.codehaus.org/browse/MARCHETYPES-41
(Note: 3.8.1
>>>>> Steinar Bang :
> I haven't been able to list all Jira issues here yet. I think I will
> try to instantiate a quickstart archetype from 5-SNAPSHOT and see what
> happens.
> If it's still 3.8.1, I'll file a bug.
Hm... that didn't work...?
I
> Olivier Lamy :
> Agree it's old :-)
> Jira project is here: http://jira.codehaus.org/browse/MARCHETYPES
Thanks! And from the above URL I got to here:
http://maven.apache.org/archetype/maven-archetype-bundles/maven-archetype-quickstart/
"quickstart", not "simple".
Checking what I actua
> Tim Pizey :
> Not everyone uses annotations, the surefire plugin requires the JUnit
> 3.8.1 naming conventions,
That doesn't seem to be the case:
http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html
Quote:
"Surefire supports three different generations of JUnit: JUn
I created a project with maven-archetype-simple, and it creates a
project with a dependey to JUnit 3.8.1.
JUnit 3.8.1 is really old. In fact it's so old I've been unable to
google when it was released. The oldest relase I find is the release of
JUnit 4.5 in 2008 http://www.junit.org/node/401
Ah
> Jason van Zyl <[EMAIL PROTECTED]>:
> Just trying to determine if it's a Ant problem, or an Ant inside Maven
> problem.
If the behaviour wasn't so unpredictable, I would have tried to create a
simple test case to make it appear, and then reported the issue to
antrun, and if it was revealed t
> Jason van Zyl <[EMAIL PROTECTED]>:
> Does it work in a simple ant script.
You mean to just do:
?
I don't know. I haven't tried (I don't know ant very well, outside of
googling for ant tasks, to be put inside a configuration element
of antrun executions...).
--
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
[snip! Things that didn't work]
I added a of the original jar file, before the zip task, and
then it worked. Ie.
So it was probably something about zip and overwriting of the existing
file that caused the flaky be
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> Maybe timing related...?
> As an experiment, inserting a
>
> between the unzip and the worked for all of the projects
> except for the two latest projects (which consistently failed).
> But
> 1. I
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> I have a config to fix the version numbers of OSGi bundles for
> snapshot version. Eg. change "1.1.0-SNAPSHOT" to "1.1.0.SNAPSHOT". The
> full config is shown at the end of this message.
> It wo
Platform: Ubuntu 8.04, Intel Pentium M,
maven 2.0.8,
maven-antrun-plugin 1.1
I have a config to fix the version numbers of OSGi bundles for
snapshot version. Eg. change "1.1.0-SNAPSHOT" to "1.1.0.SNAPSHOT". The
full config is shown at the end of this message.
It works by:
Platform: Ubuntu 7.10, Intel pentium M,
Sun Java 1.5.0_11
eclipse 3.2.2 SDK,
eclipse-Automated-Tests-3.2.2.zip,
maven 2.0.7,
pde-maven-plugin 1.0-alpha-1
I have been successful in building a feature based RCP product, using
the pde-maven-plugin.
N
> [EMAIL PROTECTED]:
> C:\Program
> Files\JavaWorkEnv\eclipse
Is the line break here actual, or an artifact of your email program? If
it is actual, it could be the problem.
-
To unsubscribe, e-mail: [EMAIL PROTECT
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
>>>>> "Olivier Lamy" <[EMAIL PROTECTED]>:
>>> In order to save your fingers :-), you can use -DskipTests (with
>>> surefire 2
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> Locking maven-jar-plugin to version 2.1 seems to be the least
> intrusive approach. I'll try that first.
But how do I do that. Just putting
org.apache.maven.plugins
maven-jar-plugin
2.1
in
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
>>>>> "Olivier Lamy" <[EMAIL PROTECTED]>:
>> In order to save your fingers :-), you can use -DskipTests (with
>> surefire 2.4) This will compile test classes but not execute units.
> Tha
> "Olivier Lamy" <[EMAIL PROTECTED]>:
> In order to save your fingers :-), you can use -DskipTests (with
> surefire 2.4) This will compile test classes but not execute units.
Thanx! In addition to saving my fingers from typing, it seems to have
the effect that I don't get the dependency fail
> "Olivier Lamy" <[EMAIL PROTECTED]>:
> * [MJAR-90] - when maven.test.Skip is set, the test-jar artifact is empty
The fix is to make no test-jar on maven.test.skip.
This fix may have created a new bug, but I'm unsure of which plugin has
the bug (ie. what plugin to report it on). Is it m
> Huang <[EMAIL PROTECTED]>:
> Has anyone encountered this issue when using maven2 Eclipse plug-in?
> Basically, after I use it to generate .classpath and .project file for
> a project, Eclipse IDE has a trouble with processing .classpath and
> complains:
> cannot next "blah_blah_blah.../res
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> So... if I move it to eg. generate-sources, I may get rid of the
> problem? I'll try, and post back the results.
Moving the dependency:copy config from generate-sources to
generate-resources, and doing the antrun:run pa
First an update: removing this from both the SuperPOM and the
Project parent POM, caused my forked lifecycle message to go away.
I tried doing like this page does
http://maven.apache.org/plugins/maven-source-plugin/usage.html
ie. changing the original
org.apache.maven.plugins
m
> "Brian E. Fox" <[EMAIL PROTECTED]>:
> Any plugin that declares @execute [phase] will cause the build to
> fork. The dependency plugin does not, but one of your other plugins
> must. I know that javadoc did, assembly does (depending on which
> goal), enforcer:enforce-once does. Take a look a
Platform: maven-2.0.8, maven-dependency-plugin 2.0-alpha-4,
maven-antrun-plugin 1.1, maven-jar-plugin 2.1
Why does maven lifecycles fork? Ie. what makes them fork?
I have a setup where I use dependency:copy to pull in some files from
the maven repository, and put them under target/clas
> "Tomasz Pik" <[EMAIL PROTECTED]>:
> yes, add something like this:
>
>idOfProfile
>idOfOtherProfile
>
> listing profiles that needs to be activated at the end of settings.xml
> file (before ).
So simple! Thanx! :-)
I noted something strange on maven 2.0.4: I also needed a
eleme
Is it possible to activate a profile in the top POM from settings.xml?
What I want to do is to have a set of properties describing OS name, and
architecture of shared libraries (ie. redhat4 and x86, or win32 and
x86_64) for different build systems, and to have a single switch in
settings.xml, to s
> "nicolas de loof" <[EMAIL PROTECTED]>:
> You can also set this in you $HOME/.m2/settings.xml
>
> true
>
> so that you don't have to set -D... everytime you launch eclipse:eclipse
I actually prefer to control it with the command line, since using this
flag can take a long time on a
> "Jeff MAURY" <[EMAIL PROTECTED]>:
> I you use the maven eclipse plugin, there is an option in the
> preference that tells maven to download source artifact as well as
> binary artifact. Once you've checked this flag, when Eclipse buids
> the classpath from you pom, the source artifact will
> "Borut Bolčina" <[EMAIL PROTECTED]>:
> Anybody saw this post?
> http://fishbowl.pastiche.org/
I came in four days later. Presumably y'all are talking about this
article:
http://fishbowl.pastiche.org/2007/12/20/maven_broken_by_design
--
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
Here's my mistake:
>
>org.eclipse.osgi
>org.eclipse.osgi
>3.2.1-R32x_v20060919
>system
>
> ${basedir}/target/dependencies/someosgiapp/org.eclipse.osgi_3.2.1_R32x_v20060919.
> "Stuart McCulloch" <[EMAIL PROTECTED]>:
> I did a quick test and using ${basedir} appeared to work for me
I'm stuck with maven 2.0.4. Perhaps that's the cause of my problems?
> - note that the basedir is the directory with the pom, so if you
> unpack to "target/someosgiapp" then you need
> "Stuart McCulloch" <[EMAIL PROTECTED]>:
> FYI, you might be interested in:
>http://wiki.ops4j.org/confluence/x/A4A6Pax-Runner
>http://wiki.ops4j.org/confluence/x/8QPax-Construct
> which aim to make OSGi development and deployment a breeze with Maven
Thanx for the tip!
> "Stuart McCulloch" <[EMAIL PROTECTED]>:
> well, there are system scope dependencies that let you refer to
> library artifacts in a fixed location like "/usr/share/lib/..." but
> their use is discouraged, because it makes things less portable:
> http://maven.apache.org/guides/introduction/in
> "Wayne Fay" <[EMAIL PROTECTED]>:
> That's just not the way Maven works. What libraries in particular do
> you need -- many should be available in the Maven repo already, so its
> simply a matter of writing the proper pom.xml entries.
That's not always sufficient.
Eg. if you want to start
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
> I would like to limit the classpath for a maven-surefire-plugin to
> something other than what comes from the .
> Is that possible? How does one do it?
It's in Subversion, but I can't tell from here wh
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
[snip! On using a profile to detect file presence]
> It now works when I do "mvn install" (config is modified), and
> repeated installs (config is left alone).
> But when I do "mvn clean install" then con
I would like to limit the classpath for a maven-surefire-plugin to
something other than what comes from the .
Is that possible? How does one do it?
I would like the classpath to contain three things:
- the target/classes/ directory
- the target/test-classes/ directory
- the JAR file
target/u
>>>>> Steinar Bang <[EMAIL PROTECTED]>:
>>>>> "Wendy Smoak" <[EMAIL PROTECTED]>:
[snip!]
>> But actually it sounds like you may want to just activate the profile
>> if one of the files that would be created is _missing_.
> Y
>>>>> "Wendy Smoak" <[EMAIL PROTECTED]>:
> On Dec 15, 2007 2:19 PM, Steinar Bang <[EMAIL PROTECTED]> wrote:
>> Platform: Ubuntu 7.10, Intel Pentium M, maven 2.0.4
>>
>> How does one avoid doing a maven-antrun-task when a file is present?
Platform: Ubuntu 7.10, Intel Pentium M, maven 2.0.4
How does one avoid doing a maven-antrun-task when a file is present?
Here's what I do:
- Unzip a zip file with dependency:unpack
- Add a couple of jars into the unpacked zip file with dependency:copy
- Modify the config in two XML files in th
> "Wayne Fay" <[EMAIL PROTECTED]>:
> Not that I'm aware of. You may want to use
> instead of straight dependencies -- then you can control what deps are
> needed in your children.
I found a fairly clear description of here:
http://www.bhaskarvk.info/content/maven/dependency_management.html
Is there a way to make a child POM inherit the parent's property
settings, but not the parent's dependecies list?
Thanx!
- Steinar
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
> "Barrie Treloar" <[EMAIL PROTECTED]>:
> On 10/12/07, Dan Tran <[EMAIL PROTECTED]> wrote:
>>
>> maven-eclipse-plugin
>> 2.5-SNAPSHOT
> [del]
>> then run 'mvn eclipse:configure-workspace' at your root
> Note this is a SNAPSHOT version of the eclipse plugin, so you will
> need to wait until i
>>>>> Dennis Lundberg <[EMAIL PROTECTED]>:
> Steinar Bang wrote:
>> Two things have locked us to 2.0.4:
>> - a bug in maven proper (I think) where maven will ungzip a tar.gz
>> or tgz file it downloads, before dropping it in the local maven
>> repo
> Dennis Lundberg <[EMAIL PROTECTED]>:
> Thanks for your input Steinar.
> But this isn't at all helpful. Because is to vague. In order for us
> (the Maven devs) to fix things we need you (the Maven users) to let us
> know *exactly* what is wrong. Please give us concrete examples, then
> we ca
> "Tomasz Pik" <[EMAIL PROTECTED]>:
> Configure plugins in profiles in parent pom and activate profiles in
> child poms? This won't be automatic (I do not know if there's a way
> to activate profile using packaging, maybe there's?) - you'll need
> to add avtivation to child poms but should so
> "Wayne Fay" <[EMAIL PROTECTED]>:
> You just need multiple parents. One top parent, then another one
> "below" it that sets the dependency plugin configs, then have your
> bundles inherit from it, and the other modules inherit from the top
> parent.
That would require a project restructuring
1 - 100 of 167 matches
Mail list logo