added Jira https://issues.apache.org/jira/browse/MNG-6503
On 11/1/2018 12:22 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> can you please file an issue in JIRA and please add an example project to
> reproduce the issue...
>
> Kind regards
> Karl Heinz Marbaise
>
> On 01/
This appears to be maven-release related, because this works in version 3.3.9,
but not in 3.5.4 or 3.6.0.
Anyone know a workaround?
-Marshall
On 11/1/2018 9:49 AM, Marshall Schor wrote:
> also tried with just released maven 3.6.0 - same behavior.
>
> On 11/1/2018 9:34 AM, Marshall Sc
also tried with just released maven 3.6.0 - same behavior.
On 11/1/2018 9:34 AM, Marshall Schor wrote:
> Hi,
>
> I can get parent pom relative path to work from a top level pom referencing a
> subfolder at the 1st level.
>
> But it fails for me when the top level inclu
Hi,
I can get parent pom relative path to work from a top level pom referencing a
subfolder at the 1st level.
But it fails for me when the top level includes a sub project contained
in another 1st level folder next to the parent pom's folder, where that
project's pom references the parent-pom us
rsion}
The ** ${project.version} ** I think was supposed be substituted, somewhere
along the way, with a maven project version - is that right? It's showing up as
the literal characters ${project.version} in the browser.
What can we do to fix this?
-Mars
ouchstone version... or you
> can use invoker.properties to pass the touchstone versions through to the
> executions
>
>
> On 12 November 2013 15:15, Marshall Schor wrote:
>
>> Hi,
>>
>> We would like to run tests that test for compatibility between newer
>&g
hear from others who have previously faced down this kind of
issue :-)
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
on in
> the committer school: Chris Graham, but don't let that stop you, we've had
> a 50% graduation rate so far)
>
> -Stephen
>
> On 8 February 2013 17:02, Marshall Schor wrote:
>
>> We have a POM, where the specifies a final name like this:
>>
>>
>
d value).
How can we fix this?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
I have a project which specifies in the a finalName which has 2
substitutable parts:
${project.artifactId}_${parsedVersion.osgiVersion}
where the parsedVersion.osgiVersion property is set by the
build-helper-maven-plugin, in the first life-cycle-phase.
This property is correctly substituted by
by quickly, and doesn't stop the build.
Later, the deploy attempts to get to the server using the encrypted pw, which
fails.
The fix: make the key needed to unencrypt the pw available to the build :-)
-Marshall Schor
On 8/24/2011 8:32 AM, Marshall Schor wrote:
> In trying to do an A
is used by the
"lightweight" wagon used to deploy.
The suggestion is "Try to force Maven to use some other wagon instead of the
lightweight one".
I don't know how to do that; any suggestions? Are there other work-arounds?
This is a b
choice, but it would seem to me it may be
perhaps rooted in a desire to have the "release:perform" step do a build from a
checkout of the tag from SVN and not be dependent on anything (at that version)
previously installed into the local repo.
-Marshall Schor
On 12/24/2010 8:07 PM, Benson
Also, I think the dependency unpack goal can check for dates, and skip the
unpack if the version in the local .m2 repo is up to date
-Marshall
On 12/22/2010 10:32 AM, Marshall Schor wrote:
> Here's another way (see below)
>
> On 12/21/2010 4:29 PM, Benson Margulies wrote:
>
of
unpacking it once, but do it to a more general spot, such as a place in your .m2
repo.
You can use the property ${settings.localRepository} in your POM to make this
work in general.
-Marshall Schor
> So, oh gurus of the maven way, where did I depart from the one true
> path? Did I sin mortally by '.
ml", which I
believe Eclipse (by convention) wants to find at the project "top level".
-Marshall
> -Stephen
>
> On 8 December 2010 22:49, Marshall Schor wrote:
>
>>
>> On 12/8/2010 4:40 PM, Anders Hammar wrote:
>>> I guess the dependency plugin can't r
ondering (since I know the "source" of the filtered values) if there was
a Maven-way of telling it this information?
Something like being able to declare: file xyz depends on files abc and def, so
if abc and def are both older than xyz, don't bother updating xyz.
-Marshall Schor
>
r you, I'm guessing there's some small detail
that's different, but I don't know what it might be.
Perhaps you could post some small "test case" scenario for others to try and see
what's going wrong?
-Marshall Schor
On 12/3/2010 6:17 PM, dloy wrote:
&
The Maven resources plugin has a goal "copy-resources" which has a configuration
parameter "overwrite". The default is "false" - meaning not to overwrite a
target file if not needed (if the target has a later date than the source).
This setting is ignored, however, if the file is being filtered.
27;s not right.
should be without the \javaw.exe ... should end with ...\bin
-Marshall Schor
> --
> From: "Anders Hammar"
> Sent: Tuesday, October 19, 2010 12:34 PM
> To: "Maven Users List"
> Subject: Re: clean
On 11/5/2010 4:01 PM, Antonio Petrelli wrote:
> 2010/11/5 Marshall Schor :
>> This seems to require the least special maven POM code (essentially, none, I
>> think - so that might qualify it as a maven best practice :-) ). Does
>> anyone see a flaw in this approach
so that might qualify it as a maven best practice :-) ). Does anyone
see a flaw in this approach?
-Marshall Schor
On 11/4/2010 5:06 PM, Antonio Petrelli wrote:
> 2010/11/4 Marshall Schor :
>> On 11/4/2010 4:21 PM, Antonio Petrelli wrote:
>>> 2010/11/4 Marshall Schor :
>&g
On 11/4/2010 4:21 PM, Antonio Petrelli wrote:
> 2010/11/4 Marshall Schor :
>> I not sure why you did the ant task to select/copy/rename some things - was
>> that
>> because you couldn't get the names right in the first place, or the wagon
>> couldn't be conf
es right in the first place, or the wagon
couldn't be configured to deploy just what you wanted?
-Marshall
On 11/4/2010 3:46 PM, Antonio Petrelli wrote:
> 2010/11/4 Marshall Schor :
>> Now, we are trying to better align with the Maven way, and are using Nexus.
>> The
>>
nd let them take up space in Maven central, even though
they're also in the conventional Apache distribution (with mirrors) system. Is
that the best practice?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@m
On 11/1/2010 3:05 PM, Marshall Schor wrote:
> Here's a bit more info that might help debug this, perhaps.
>
> The release:prepare step shows, for the first transformation (from -SNAPSHOT
> to
> release) a mixture of "Transforming" and "Updating&quo
] Transforming 'UIMA Base: uimaj-adapter-soap: SOAP Adapter'...
I think the Updating ... and Ignoring artifact version update... come from the
part of the code that updates the properties. And these messages are missing in
the 2nd transformation, which probably is indicative of this part
lt-cli)
-Marshall Schor
> On 01/11/2010, at 12:26 PM, Marshall Schor wrote:
>
>> I have a pom which has a property which has as a value "2.3.1-SNAPSHOT".
>>
>> The property is used to factor into one spot the version level for
>> dependencies,
>> whe
th release plugin 2.1
The release.properties file doesn't have any elements starting with
"checkpoint."
However, the development version was checked in because I can see the POM
version of the projects were updated to the next development level
2.3.2-SNAPSHOT. Only the value under was not upd
), to "2.3.1" for the tag, but then does *not*
update it for the next development version.
Any idea why? Is this a (known) bug? I can, of course, work around this by
manually updating this property to the right level and committing that change to
the trunk.
-Marshall Schor
--
;
> 2010/10/28 Anders Hammar
>
>> I think by using ${project.version}.
>>
>> /Anders
>>
>> On Wed, Oct 27, 2010 at 20:57, Marshall Schor wrote:
>>
>>> We have a common project parent-pom, and a build-resources-bundle project
>>> containing various &qu
cycle, just for it, and then
have the parent-pom depend on the released version.
What is the "maven way" for doing this kind of thing?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
this address your use case?
-Marshall Schor
On 10/26/2010 12:05 PM, Haszlakiewicz, Eric wrote:
>> -Original Message-
>> From: paulus.benedic...@gmail.com [mailto:paulus.benedic...@gmail.com]
> On
>> On Mon, Oct 25, 2010 at 11:09 PM, Paul Benedict
>> wrote:
a small set of strings (such as strings starting
with
rc or snapshot, etc.) then the rule 1-rc < 1 applies.
But if the string following the - is not one of these "well known" strings,
then that rule doesn't apply.
-Marshall Schor
On 10/21/2010 7:14 AM, Stephen Connolly wrot
also check parent poms.
-Marshall Schor
On 10/9/2010 8:35 PM, Niall Pemberton wrote:
> On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee wrote:
>> I am getting this warning for every module, yet I am not using this variable
>> any of the poms. Some poms do have ${project.versi
Just a guess:
Check the gpg plugin configuration:
true
This might be in in your poms or in your settings file?
-Marshall Schor
On 10/9/2010 5:35 PM, Hilco Wijbenga wrote:
> Hi all,
>
> I'm trying to build Spring's Roo and it wants to sign everything using
> the maven-g
built/installed.
This is described in the m2eclipse book, here:
http://www.sonatype.com/books/m2eclipse-book/reference/dependencies.html#dependencies-sect-resolving-dependencies
-Marshall Schor
On 10/2/2010 7:22 AM, Antonio Petrelli wrote:
> 2010/10/2 Iron Eagle :
>> Some times, I use the
s design decision was taken, versus an approach which
allows merging, or perhaps some kind of user (pom - specified) choice.
I was "bitten" by this also.
-Marshall Schor
>
>
> Benjamin
>
> -
> T
thanks! -Marshall
On 10/1/2010 6:31 AM, Benjamin Bentmann wrote:
> Marshall Schor wrote:
>
>> Is a workaround (until Nexus is patched), to use
>> -Dmaven.metadata.legacy=true on
>> the maven command line?
>
> The workaround is no longer necessary to deploy Apac
p package.
So, I think it's up to you, how you want to manage this.
Does this make sense? Or am I missing the main point?
-Marshall Schor
On 9/29/2010 4:29 PM, Nathaniel Auvil wrote:
> I am trying to figure out how to leverage mult-module builds in maven. Say i
> have a project
On 9/30/2010 9:34 AM, Benjamin Bentmann wrote:
> Marshall Schor wrote:
>
>> The file under-SNAPSHOT/maven-metadata.xml can't be read using
>> http://repository.apache.org/snapshots/org/apache/uima/parent-pom-docbook/4-SNAPSHOT/maven-metadata.xml.
>>
>
> r.a
http://maven.apache.org/xsd/metadata-1.0.0.xsd";
xmlns="http://maven.apache.org/METADATA/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
So - it looks like RC3 is missing the namespaces declarations? (I think this is
also true for RC2).
-Marshall Schor
On
Just a guess:
Maybe the getItems and setItems methods are not correct?
getItems should return items, and setItems should set items = labels ?
-Marshall Schor
On 9/22/2010 2:52 AM, Xavier D. wrote:
> I have written a multi-value plugin with parameter:
>
> /**
> * @required
&g
On 9/27/2010 6:29 AM, Marshall Schor wrote:
> Here's what I think I've learned.
>
> The release plugin operates in an unusual way, in that there are two
> invocations
> of work, the "outer" invocation, and an "inner" one.
>
> The inner one i
recent post for what the underlying cause of my problem was.
Thanks, again. -Marshall Schor
On 9/27/2010 8:01 AM, Nicola Musatti wrote:
> Hallo, Marshall.
>
> By flat hierarchy do you mean that the aggregator project directory is not the
> parent directory of your modules' direc
is the meaning of the word *still*, here.
This message isn't given if all of the -SNAPSHOTs were resolved during the
processing of all the modules in the Reactor in the "outer" invocation.
Maybe one of the implementors of the release plugin can confirm this theory :-).
-Marsha
he updated poms for those.
I guess the super-pom turning on apache-release happened after my in
my top level aggregator project was "processed", maybe... (not sure about
this).
-Marshall Schor
On 9/25/2010 4:51 AM, Antonio Petrelli wrote:
> 2010/9/24 Marshall Schor :
>>
>
On 9/24/2010 3:22 PM, Antonio Petrelli wrote:
> 2010/9/24 Marshall Schor :
>> Are you saying that the Maven Release plugin, in particular, has the
>> restriction
>> that in order for it to work, it the multimodule project has to be the
>> parent?
> At this poin
differing common
parts factored out into the parent).
As I've said previously, the other parts of Maven operation (building,
installing, etc.) seem to work just fine with this setup.
Are you saying that the Maven Release plugin, in particular, has the restriction
that in order for it to wor
On 9/24/2010 2:08 PM, Antonio Petrelli wrote:
> 2010/9/24 Marshall Schor :
>> The top pom and all the poms in the submodules have version numbers
>> 2.3.1-SNAPSHOT.
>> The top pom has *some* of the submodules also listed as , with
>> the
>> 2.3.1-SNAPSHOT
case, the
top pom is *not* the parent of any other pom.
Is it required that the aggregator pom also be the parent, for this to work?
-Marshall Schor
On 9/24/2010 12:23 PM, Marshall Schor wrote:
> Hi,
>
> I have a multi-module project, using a *flat* hierarchy.
>
> The top pom
rsion?
(Tried using release plugin version 2.0, trying both maven 3.0-beta-1 and
3.0-RC2 - same results.)
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
minutes, in case you're running things which
which need lots of signings, so it doesn't bother you for the pass phrase all
the time.
To activate this capability in your maven settings file, you add
true
-Marshall Schor
On 9/10/2010 1:29 PM, Simone Tripodi wrote:
> Hi Kalle,
>
d").
So I'm confused - it seems to me it is not fixed? What (if anything) changed?
-Marshall Schor
> On Tue, Sep 7, 2010 at 12:27 PM, Marshall Schor wrote:
>> Today, Maven central was updated with incomplete uploads of several eclipse
>> artifacts:
>>
>>
, who?)?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
time" education :-).
-Marshall Schor
On 8/23/2010 4:02 PM, Wayne Fay wrote:
>> I didn't know there was a nexus list. Thanks.
> This happens often. I don't know why there is such confusion. Perhaps
> the Sonatype folks need to make this more obviou
could likely be other metadata around that's being
associated to this name, and therefore, this might not be effective.
Maybe I need to do both an "ant-run" rename, plus a
maven-build-helper:attach-artifact to re-mark the renamed jar as the primary
art
also, for encryption, read
http://maven.apache.org/guides/mini/guide-encryption.html
-Marshall Schor
On 7/23/2010 3:04 AM, Stefan Cordes wrote:
> Hi!
> On
> http://maven.apache.org/scm/maven-scm-plugin/examples/bootstrapping-with-pom.html
>
>
> it is just stated that userna
ement is pointing to
the right place in your SVN or whatever. If you let these "inherit" from parent
poms, the inheritance makes often wrong assumptions that the children of the
parent are located underneath the parent pom directory. Specifying the actual
location overrides this behavior
plugin-name:goal-name" style,
then the which is used to configure the plugin for that invocation
is named (by convention :-) ) "default-cli" - which stands for the the
default command-line interface invocation.
That's why changing the to that value makes that configuration used
Hi Ron,
Did you read the documentation for writing descriptors for the assembly
plugin?
For instance, it has this bit:
http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html#class_dependencySet
with the parameter:
|useTransitiveDependencies| Determines whether transitive depen
On 6/28/2010 6:39 PM, Ron Wheeler wrote:
> Thanks for the quick reply. See below.
>
> On 28/06/2010 4:37 PM, Marshall Schor wrote:
>>
>> On 6/28/2010 4:12 PM, Ron Wheeler wrote:
>>
>>> I am trying to build a pom in its own project that will assemble a t
blies, see:
http://www.sonatype.com/books/mvnref-book/reference/assemblies.html
-Marshall Schor
>
> I have built a test pom shown below.
> Since it has
>
> jar-with-dependencies
>
> it restructures the internal jar contents rather t
On 6/28/2010 9:52 AM, Marshall Schor wrote:
> The Apache common top-level pom (
> http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom ) has a
> profile activated when doing "releases", which invokes the
> maven-assembly-plugin to build the source-release.zip art
rojects?
If so, is there a plugin which does this?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
On 6/24/2010 2:29 PM, Umer Khan wrote:
> Hey,
>
> Is there any possible way to check if the file exist or not, thorough maven
> script,
Yes, have a look at
http://maven.apache.org/enforcer/enforcer-rules/requireFilesExist.html
> Actualy when packaging my project, I need some files to be in jar,
It may also help to speed things up to install a local NEXUS repository
and use it as a mirror, if the slowness is due to accessing things over
the internet.
-Marshall
On 6/24/2010 4:43 PM, Shan Syed wrote:
> this has to do with what's in your WAR, perhaps analyze what dependencies
> its using, a
Marshall
On 6/23/2010 2:26 PM, Marshall Schor wrote:
> I looked at the poms in the SVN Tag, and they were re-written as
> expected by the release-prepare,
> but without the extra "trunk" directory. For example:
>
>
>
>
> scm:svn:http://svn.apache.org/re
d (with no extra "trunk" directory.
-Marshall
On 6/23/2010 10:36 AM, Marshall Schor wrote:
> forgot to add: I'm using maven version 3.0-beta-1
>
> -Marshall
>
> On 6/23/2010 10:31 AM, Marshall Schor wrote:
>
>> I'm trying to do our first release using
forgot to add: I'm using maven version 3.0-beta-1
-Marshall
On 6/23/2010 10:31 AM, Marshall Schor wrote:
> I'm trying to do our first release using version 2.0 of the maven
> release plugin for a multi-module project at Apache, with a flat
> hierarchy. After failing becaus
I'm trying to do our first release using version 2.0 of the maven
release plugin for a multi-module project at Apache, with a flat
hierarchy. After failing because the Apache common pom was specifying
version 2.0-beta-9 of the release plugin (which didn't have the flat
hierarchy support), and redo
On 6/17/2010 3:17 PM, Anders Hammar wrote:
> Have you tried specifying the parent.relativePath element?
>
Thanks, that appears to have done the trick! -Marshall
> /Anders
>
> On Thu, Jun 17, 2010 at 17:43, Marshall Schor wrote:
>
>
>> For a collection of
release votes, waiting in each case for the "1" version to
reach the central repo before commencing with the release:prepare of the
the next lower one in the hierarchy?
-Marshall Schor
-
To unsubscribe, e-mail: users-un
define a parent-pom having this as its
... , and then (since you say *most* projects
use this assembly, have those projects which do use it inherit from this
parent-pom, and those which do not use it, skip inheriting from this pom.
To avoid having the
Hi,
See if the http://maven.apache.org/plugins/maven-changelog-plugin/ does
what you want.
-Marshall Schor
On 6/8/2010 5:34 AM, rgubler2 wrote:
> Hello,
>
> can maven create a changes file from svn log messages between releases?
>
>
&g
Maybe you need to set the this way (see [1]):
${project.build.directory}/thirdparty/vtk/lib/vtk-5.4/
-Marshall Schor
[1]
http://maven.apache.org/guides/mini/guide-configuring-plugins.html#Mapping_Maps
On 5/20/2010 9:48 AM, Thiébault Benoît wrote:
> Hi everyone,
>
> I&#x
ome default id - you can
find out what it is by running once with the -X parameter, I think)
Then, configure your version of the plugin for Cobertura like:
xyz
I haven't tried this myself, but if you do, I'd like to know if it
succeeds in "getting rid of"
assembly to be built by this project - how would I arrange
> for that to happen?
>
The assembly descriptor supports this directly, I think: use
dependencySet and specify unpack.
-Marshall Schor
-
To unsubscrib
Hi,
I've posted earlier about a couple of possible improvements to the
Apache Common Parent POM - used by Apache projects [1].
I'd like to add some Jira issues for these, but I was unable to
determine what Jira system to use. Does anyone know the right Jira to
use for this?
-Marshall
/c/ ? In other words, does the url
part starting after the hostname get mapped to people's top directory?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
ult images etc.
>
This chapter of the Maven complete reference describes these topics:
http://www.sonatype.com/books/mvnref-book/reference/site-generation.html
-Marshall Schor
> Best regards,
> Eric
> -
> To u
is seems to work (at least for my project). I think it should be
considered for the common Apache Parent pom. Should I open a Jira for
this, and if so, what Jira system is being used for the Apache Parent poms?
-Marshall Schor
On 5/17/2010 5:13 PM, Brian E. Fox wrote:
> This descriptor assum
e Parent and specify the form
of assembly?
Or is there another preferred way to do this?
-Marshall Schor
[1] http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.
ok - where do Jira's for updating the common Apache Parent go? The pom
in question is missing an "" element... ;-)
-Marshall Schor
On 5/17/2010 3:00 PM, Brian Fox wrote:
> When that was written the jar goal didn't fork iirc.
>
> On Mon, May 17, 2010 at 2
think.
Is there a reason the goal "jar-no-fork" isn't used instead?
-Marshall Schor
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
a which has the dynamically altered
information and links.
HTH. -Marshall Schor
> Thanks!
> -Rob
>
>
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
On 4/28/2010 11:53 AM, Marshall Schor wrote:
> There's a new way to get the build date, documented here:
> http://maven.apache.org/guides/introduction/introduction-to-the-pom.html -
> search for maven.build.timestamp.
>
> This is nice.
>
> I would like to have multi
ifference. I still get
>
> "unknown protocol: null"
>
> I also note that I was wrong in my previous post. The
> features-maven-plugin does not work under the 3.0-alpha-7 either.
> Seems like the problem has to do with maven 3, and possibly the class
> loading cha
On 5/1/2010 7:29 AM, Marshall Schor wrote:
> Thanks, that saves me from doing another learning experiment :-)
>
I had occasion to check this while doing something else, and I found
that it doesn't just unpack the whole archive.
While doing the unpack, it iterates over each
On 5/8/2010 2:55 AM, Bengt Rodehav wrote:
> No one has any ideas?
>
Here's an idea - Maven 3 has been doing more class loader isolation
stuff. Perhaps an element is needed? See
https://cwiki.apache.org/MAVEN/maven-3x-class-loading.html
-Marshall
> I'm thinking along the lines that somethin
On 5/7/2010 2:52 PM, Wayne Fay wrote:
>> The problem I'm having is that the factored-out build steps run when I
>> do "mvn install" on the parent-pom to get it into my local repo. These
>> steps don't work and throw errors, when run here.
>>
> Put the common stuff in depMgmt in the parent,
nce of a file, named something like
"marker-file-identifying-parent-pom-XXX". And then, I put a dummy file
of that name into the parent project. This keeps the pom from running
the build steps in the parent, but makes those steps available to the
child
One thing you could do is to follow what this line says:
[INFO] For more information, run Maven with the -e switch
Another thing is you could run with the -X switch which will generate lots of
output, probably enough for you to see what's going wrong.
-Marshall Schor
On 5/7/2010 12:
cept for packaging type=pom).
See
http://www.sonatype.com/people/2010/01/how-to-create-two-jars-from-one-project-and-why-you-shouldnt/
for a discussion of this.
-Marshall
> On 5/4/2010 2:39 PM, Marshall Schor wrote:
>> Well, I was able to reproduce your problem, and then f
m file.
>
> I do have a parent defined but it's there just to define release
> profiles as well as version information. No additional configuration
> (for the maven-jar-plugin) is in the parent pom.
>
> On 5/3/2010 7:53 PM, Marshall Schor wrote:
>> it looks like your jar f
it looks like your jar file has no classifier. A plain jar file is
being uploaded. Can you post the part of the POM where you are defining
the classifier artifact, and attaching it?
-Marshall
On 5/3/2010 7:09 PM, Michael Delaney wrote:
> All,
>
> I have a simple maven project that generates a j
" or simply as a set of
> properties that are passed on to the children?
>
The POMs are clearer when you put these in dependencyManagement, I think.
-Marshall
> Ron
>
> On 03/05/2010 2:44 PM, Marshall Schor wrote:
>> What I've surmised from the various sources of m
at update
"propagated" to the other poms).
-Marshall Schor
On 5/3/2010 12:37 PM, Frank Maritato wrote:
> Hi,
>
> I have a multi module project and in my top level pom I am using a
> property to define the version number like this:
>
> ${myproject.version}
>
>
>
to timezone issues in timestamps.
-Marshall
[1] http://ant.apache.org/manual/CoreTasks/unzip.html
On 4/30/2010 10:55 PM, Brian Fox wrote:
> Currently it just unpacks the whole archive.
>
> On Thu, Apr 29, 2010 at 10:31 AM, Marshall Schor wrote:
>
>> The documentation for depen
The documentation for dependency:unpack [1] says that the default is to
overwrite (only) if newer. But it seems to apply to the entire archive
being unpacked, meaning that the check is on whether the archive file
itself is "newer" or not, using what the plugin calls "marker files",
and perhaps not
1 - 100 of 142 matches
Mail list logo
