Also you are using a rather old version of maven (1.1)...
The entire architecture of maven was changed moving to maven 2... I suspect
not many people remember much about maven 1.x.
(Personally all I recall is that it was a pile of sh1t)
-Stephen
2009/3/20 Lukas Theussl
>
> That will be diffic
I thought the test-jar packaging was supposed to make this work
of course I have not been able to get it to work
I've been thinking it's because my tests are all JUnit 4.4 and not 3.8.2...
but maybe it's just that surefire does not look inside test-jar dependencies
-Stephen
2009/3/21 Br
google is your friend "animal sniffer Kohsuke"
Sent from my [rhymes with myPod] ;-)
On 21 Mar 2009, at 19:43, Stefan Armbruster
wrote:
Hi,
is there a maven plugin that provides a in-depth check of the java
class
version in a generated artifact, e.g. a war file?
Assume a deployment envi
s on both. This could cause bugs of nightmarish
> difficulty to track.
>
>
> Stephen Connolly wrote:
>
>> No.
>>
>> e.g.
>>
>> (I own one-dash.com)
>>
>> I might roll a custom version of log4j...
>>
>> I would deploy this as
>>
2009/3/24 Karl Heinz Marbaise
> Hi,
>
> i have a large project which contains multiple modules and sub-modules.
>
>
> Base (packaging: POM)
> +--- M1 (parent: Base)
> +--- M2 (parent: Base)
> +--- M3 (packaging: POM; parent: Base)
> +--- M3.1 (parent: M3)
> +--- M3.2 (paren
2009/3/24 Karl Heinz Marbaise
> Hi Stephen,
>
> If you are doing that you'd be better omitting the version entirely as it
>> will be inherited from the parent...
>>
> Yeah i changed that and it worked...great...
>
>
>>
>>foo
>>bar
>>1.0-SNAPSHOT
>>
>> manchu
>>
>>
>> is exact
FYI, working on getting ready for th 1.0-alpha-3 which fixes a lot of
issues but it looks like it will be second week in april before it's
ready
2009/3/25 Brian E. Fox
> Google for the versions-maven-plugin
>
> -Original Message-
> From: Marcin Wiśnicki [mailto:mwisni...@gmail.com]
>
You cannot have two modules in the reactor with the same groupId and
artifactId...
from your pom snippets it looks like this is the case...
consider changing either the groupId or the artifactId of one of the modA's
(Note that the artifactId does not have to be the same as the directory
name...
only because the group ids are the same
2009/3/25 Paul Gier
> I think it's the duplicated artifactId's that is causing the problem.
> Maybe the artifactId of the pom in the subdirectory modA/modA should be set
> to "modA-modA" or something like that.
>
>
> huser wrote:
>
>> Hi,
>>
>> I have a s
attach the execution to the process-classes phase
2009/3/26 fachhoch
>
> I am using maven-ant-run plugin to call hibernate byte code
> insturmentation
> , i also have maven jetty plugin , every time i run jetty plugin first
> all modified java files gets complied and then test cases and fin
Well you could stage them yourself
You need a staging repository... I see no reason why this cannot be file
based
You then need to do some scripting and use the maven-stage-plugin (
http://maven.apache.org/plugins/maven-stage-plugin/index.html) to copy the
contents of the staging repository t
2009/3/26 Martin Eigenbrodt
> Hello Trevor,
>
> contrary to some responses here I don't think your issues is SCM/Version
> Control issue. This is not your fault.
> Your issue is missing "soft" or dynamic version support in maven.
> Actually the responses propose some workarounds:
>
> 1.Manual:
>
2009/3/26 Martin Eigenbrodt
> >
> > >
> > > 2. Custom scripts
> > > >We use a little script
> > > >that invokes the version plugin and checks in the pom.xml if versions
> > were
> > > >updated. Hudson runs the update script nightly.
> > > This looks like a working solution. However a "native" Mav
if your module requires the dependency to complie then it is a
dependency of your module
what you describe as a "work around" is actually what you are supposed to do
the real issue is that compile is transitive. compile needs to be
transitive as a runtime dependency but should not be a transitive
When 1.0-alpha-3 of versions-maven-plugin is released
you could build your own snapshot of it at the moment
look at the lock-snapshots and unlock-snapshots goals
-Stephen
2009/3/27 Torben Knerr
> Hi all,
>
> we have "AppA" and "AppB", both having a dependency to "Common".
>
> All of these
Any chance you could post your solution?
2009/3/27 Jim McCaskey
> I have found a solution that is working nicely. Having said that, I don't
> think the request is that farfetched. When doing a deploy, you would
> definitely want to make sure that all the components that made up the run
> built
Have a look at the plugin mojo... you'll see there's a config option to
control whether snapshots are overwritten and whether releases are
overwritten.
2009/3/27 Richard Chamberlain
> Hi,
>
>
>
> I'm using dependency:unpack-dependencies to get some zips of artefacts
> from our company repository
we deploy the site to a local directory and then afterwards copy the site to
the web server location
2009/3/27 Hoehmann, Andreas
> Hi folks,
>
> i have a multi-module-project (~30 artifacts).
>
> I wrote a little script to release the whole project from root
>
> - check dependencies
> - try site
The danger with that is that the metadata (local vs remote) will be
incorrect and version ranges will not work correctly
2009/3/29 Tim
> Are you on a linux system? I just rsynced my repo recently to accomplish
> the
> same thing.
> It was really easy.
>
> On Sat, Mar 28, 2009 at 12:05 PM, Jeff W
was the point of having transitive dependency support in
> Maven. If this isn't the reason, what is?
>
> Regards,
> Brian.
>
>
> Stephen Connolly-2 wrote:
> >
> > if your module requires the dependency to complie then it is a
> > dependency of your module
versions-maven-plugin
some of the mojo's we're (or I'm) intending on putting in are not there yet.
The first mojo to look at is: update-properties
(you'd be wanting the version from 1.0-alpha-3-SNAPSHOT btw)
This picks up any dependencies who's version comes from a property and
allows picki
I am going to bet that you might be using the dependency:copy or the
dependency:unpack goals and not dependency:copy-dependencies
If you are picking something up from the reactor you need to use goals that
look in the reactor
2009/3/30 Karl Heinz Marbaise
> Hi David,
>
> sorry.. a second one...
You need to configure filtering for the file you want filtered.
Have a look at the war plugin for how to define which files get filtered
2009/3/30 James Depaul
>
>
> I've searched the archives for this but no luck -
>
> I need to build my web.xml file with specific values based on the target
>
d anywhere that I could
> find, so I am guessing that not many folks are interested in it. Frankly
> without the nudges in the right direction from this list, I would not have
> been able to figure it out. So thanks to everyone.
> >
> > -Jim
> >
> >
> > -Or
dependency:unpack???
2009/3/30
> Jeff:
>
> If it was a single file (ie. CheckStyle) I would have most likely gone down
> the URL route. However, I have multiple configuration files (CheckStyle,
> PMD, FindBugs, testing, etc) so I would like it all as single dependency.
> If I go down the *.jar
Has anybody tried switching from neon to serf as the repository access
method???
I read on the svn list that 1.5.1+ WC->URL tagging for http/https
repositories works with serf but not neon
I have not been able to try this yet as it would mean recompiling my client.
This is a client only setting
Yes
2009/4/1 Todd Thiessen
> Consider your response acknowledged ;-).
>
> We may be moving to 1.6 soon (on the server side). Would a 1.6 client
> work with a 1.5 server?
>
> ---
> Todd Thiessen
>
>
> > -Original Message-
> > From: Stephen Connolly
Unless you write a pre-commit hook to ban 1.6 clients
afaik, you can use a 1.1 client with a 1.6 server and a 1.6 client with a
1.1 server (put it may only be officially supported as far back as 1.4)
-Stephen
2009/4/2 Stephen Connolly
> Yes
>
>
> 2009/4/1 Todd Thiessen
>
&
2009/4/2 Brian E. Fox
> >It's things like this that give maven a bad rep. Folks spend hours
> >trying to get it to work and never do. Fixing it is in order, but why
> >on earth can't the keepers of the plugin document this in an obvious
> >place?
>
> Because that assumption below isn't true. Th
setup nexus and pull off a mirror of repo1
2009/4/2 Hayes, Peter
> The company that I work for has blocked all access to the Amazon S3
> hosting site due to security / threat concerns. Due to this, I am no
> longer able to download the central index. Has anyone else had this
> issue and if so
release goal.
>
> I just want to unpack two artifacts at two locations before package
> phase, is there a different plugin that can handle this simple case?
>
> -Dave
>
> On Thu, Apr 2, 2009 at 2:28 PM, Stephen Connolly
> wrote:
> > 2009/4/2 Brian E. Fox
> >
Also have a look at versions-maven-plugin
I use properties to define outside of reactor version... then if I build a
different project I do a local install of that project and then
mvn versions:update-properties -DallowSnapshots=true
which updates my properties to the latest version visble to me
Hi,
ok so I'm working on a new goal for the versions plugin, analyze (and an
associated report analysis-report)
I would like this goal to highlight potential issues with respect to
versions
first problem I see is:
1. Referencing a reactor project as a plugin or plugin dependency consumed
l
3. when the same plugin is specified in multiple projects in the
reactor, using different versions (severe warning fir 2.x minor for 3.x)
4. when reporting plugins specify a different version from build plugins
Sent from my [rhymes with myPod] ;-)
On 4 Apr 2009, at 22:30, Stephen Connolly
5. When locked snapshots are in use ( i.e. 1.0-20090406.102308-2 and not
1.0-SNAPSHOT ) (minor warning)
2009/4/6 Stephen Connolly
> 3. when the same plugin is specified in multiple projects in the reactor,
> using different versions (severe warning fir 2.x minor for 3.x)
>
> 4. wh
2009/4/3 David Hoffer
> Please send sample when you get back.
>
> Dave Hoffer
> - sent via G1
>
> On Apr 3, 2009 12:51 AM, "Stephen Connolly" <
> stephen.alan.conno...@gmail.com>
> wrote:
>
> I have this working no problem but
If you are prepared to run maven multiple times as part of your CI build you
could achieve some of what you are looking for with the
versions-maven-plugin.
step 1. use versions-maven-plugin to update the pom to the latest releases
of all dependencies
step 2. use maven-scm-plugin to commit the modi
don't use aggregate with the reporting as it messes up your build...
try setting inherited to false for the reporting plugin config... it
might just reduce your issues
Sent from my [rhymes with myPod] ;-)
On 6 Apr 2009, at 06:51, Andrew Hughes wrote:
Hi Wayne, thanks again.. as you rightfu
[Hack alert]
You could put them in a separate folder tree
e.g.
src/main/example-java/
and then use the build-helper-maven-plugin to add this as an extra source
directory *but bind the execution to a phase in the lifecycle after compile
but before package*
[/Hack alert]
-Stephen
2009/4/7 Eric
2009/4/7 Todd Thiessen
> > ...that is we decide when a release is ready and
> > use the release plugin to do this. The CI is only producing
> > snapshots on a constant basis.
>
> So your formal releases are produced by manually running the release
> plugin? And if it fails, you manually do a roll
phase...
-Stephen
2009/4/7 Eric B.
> "Stephen Connolly" wrote in message
> news:88c1b40904071005m3b1b53feg3b0edf4222b4...@mail.gmail.com...
> > [Hack alert]
> > You could put them in a separate folder tree
> >
> > e.g.
> >
> > src/main/examp
sounds like you want version ranges
[1.0,2.0-!)
Sent from my [rhymes with myPod] ;-)
On 8 Apr 2009, at 01:39, Tim wrote:
http://jira.codehaus.org/browse/MNG-4089
I need to read over the bug that was linked as a duplicate more
closely but
I don't think it's the same thing.
What I asked for
2009/4/8 Sergey Shcherbakov
> Thank you Brian,
>
> The way we currently prevent developers from deploying their local
> builds to the repo are the security permissions. But I have understood,
> that some kind of a repo-managing system should be used for more
> flexibility.
>
> Regarding snapshots
Ehhh,
FYI, AFAIK
maven-_-plugin is reserved for o.a.m.p plugins
all other plugins are supposed to use the pattern
_-maven-plugin
-Stephen
2009/4/8 Hubert Iwaniuk
> Maven Overview Plugin version 1.4 has been released.
>
> http://code.google.com/p/maven-overview-plugin/
>
> Maven Over
2009/4/9 Nord, James
>
> > -Original Message-
> > From: Rémy Sanlaville [mailto:remy.sanlavi...@gmail.com]
> > Sent: 09 April 2009 08:27
> > To: Maven Users List
> > Subject: Re: Maven Overview Plugin version 1.4 has been released
> >
> > >
> > > as long as the plugin has its own groupId,
.
-D
On Thu, Apr 9, 2009 at 6:08 AM, Stephen Connolly
wrote:
2009/4/9 Nord, James
-Original Message-
From: Rémy Sanlaville [mailto:remy.sanlavi...@gmail.com]
Sent: 09 April 2009 08:27
To: Maven Users List
Subject: Re: Maven Overview Plugin version 1.4 has been released
as long as
because executing mojos directly never invokes the lifecycle.
you could have a profile with a default goal of validate and with the
plugins you want bound to the validate phase of the lifecycle
then
mvn -Pmagic
would do it for you (if your profile id is magic)
Sent from my [rhymes with myP
2009/4/10 David Hoffer
> My project currently creates javadocs during the install goal, see pom
> below. How can I configure this to run only if deploy goal is run instead?
>
> Alternatively, is there a way this can be externalized so that individual
> developers can turn this feature off when t
2009/4/13 nodje
>
> I'm not sure of what you mean exactly Stephen.
> This is how I interpreted it:
>
>
>build-jetty
>
>validate
>
>
>org.codehaus.mojo
>buildnumber-maven-pl
Hoffer wrote:
Thanks much, I think you intended to say deploy.
-Dave
On Sat, Apr 11, 2009 at 12:08 PM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
2009/4/10 David Hoffer
My project currently creates javadocs during the install goal, see
pom
below. How can I con
by any chance are you using
dependency:copy
or
dependency:unpack
anywhere in your build?
If you are that could well be the source of your issues.
It sounds like one of the plugins you are using is not searching the reactor
for dependencies.
-Stephen
2009/4/16 David Hoffer
> Then there is
>
>
> ${project.build.directory}/generated-resources
>
> ${project.groupId}
>true
>pom,jar
>
> cdf-blaze-svcs-config
>
>
>
>
>
> -
That would be my concern too.
I suspect you can reproduce your build failures if you:
mvn clean
mvn dependency:purge-local-repository -DreResolve=false
mvn install
(assuming that you have not deployed any of the -SNAPSHOT artifacts to a
remote repository)
you should recreate the build failure
gt;
> What does -DreResolve do?
reResolve will turn around and re-pull the dependencies from the
remote repository unless you disable it with -DreResolve=false
(reResolve is a parameter of the purge-... goal)
>
> -Dave
>
> On Thu, Apr 16, 2009 at 11:09 AM, Stephen Connolly <
it works yet because I didn't change any code.
> I will have to try this again when we have added breaking code to dependent
> module(s).
>
> This is a nasty issue!
>
> -Dave
>
> On Thu, Apr 16, 2009 at 12:02 PM, Stephen Connolly <
> stephen.alan.conno...@gmai
You should probably file a JIRA against the changelog plugin
AFAIK it should be looking up the passwords from settings.xml or
prompting from the command line... storing passwords in the pom.xml is
asking for trouble
Although perhaps those fields are designed to pick up from the system
prooperties
t; > there are errors in how maven calculates snapshot timestamps
>> > or something. For instance, if the previous snapshot
>> > deployed by the CI server has a later timestamp than what is
>> > being built currently, would maven prefer the former? (Our
>> >
Ah
OK, that explains some things, but I'm not sure how you go about fixing them ;-)
I suspect some of your site reports are forking a build... the forked
build will not have reference to the reactor artifacts from the main
build, so as a result will pull the version from the local
repository/
this is a question for d...@hudson.dev.java.net
Sent from my [rhymes with myPod] ;-)
On 17 Apr 2009, at 22:06, "david.schroeder" cubed.com> wrote:
I am trying to use maven to build a plugin to Hudson
org.jvnet.hudson.tools:maven-hpi-plugin:1.34:create
Is giving me a BUILD ERROR
" Internal
Have you locked down the version of surefire you are using in your pom?
if you have not locked it down, then you will be picking up a newer
version of surefire with 2.1.0.
AFAIK, a newer version of surefire has issues passing system
properties to the forked process.
in any case you should always
AFAIK the order is, for each phase:
1. lifecycle added goals, in the order they are defined in the lifecycle
2. project added goals in plugin order from the pom.
where it gets confusing is profiles and inherited plugins, and where
they go in the sequence
-Stephen
2009/4/20 Tony Giaccone :
> I'v
2009/4/21 Kogel, Jonck-van-der :
>
>>> Sounds right; system scoped stuff are supposed to be provided by the
>>> JVM etc. so they shouldn't be any need for the manifest to point them
> out.
>
>>Also to expand a bit; if you intent to bundle those jars with your app
> use the default (compile) scope a
Here's what you are doing wrong:
you are trying to do things the ANT way (i.e. let's check in a
directory of jars into SCM) using Maven.
Use a repository manager and don't keep a local repo contained within
your project.
;-)
-Stephen
2009/4/21 nino martinez wael :
> Hi
>
> I have a multimodule
nly have access to the CI server .. So you
> >> are saying that I should use a repository manage just to contain the 4
> >> dependencies that I have..? It would complicate a lot of things.. I do
> >> get the idea to use repository manages, but for just 4 deps, it seems
>
2009/4/22 Michael Hüttermann
> Hello experts,
>
> how do you set up the process if you use RELEASE for a dependency in a
> POM, and work with VCS branches ?
you stop using RELEASE for a dependency.
RELEASE corresponds to the last released version... so if you release, in
order
1.0.0
1.0.1
1.1
If anything I see problems in untangling the rats nest of dependencies
between code and tests if you don't just pull each one out one by one.
Since the tests will initially have the entire dependency tree available,
you could have a situation that tests fail to compile as you move the main
code in
If anything I see problems in untangling the rats nest of dependencies
between code and tests if you don't just pull each one out one by one.
Since the tests will initially have the entire dependency tree available,
you could have a situation that tests fail to compile as you move the main
code in
A
you want to use the value from the parent if the parent is in the current
reactor but if the parent is not in the current reactor, you want to use the
value from the child?
Is that what you are trying to do?
-Stephen
2009/4/22 Anastasios Angelidis
> Sometime we build the entire project
cases,
> include snapshots although that's both not intended and violates the
> version
> range spec.
>
> -Dave
>
> On Wed, Apr 22, 2009 at 10:05 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
>
> > 2009/4/22 Michael Hüttermann
> >
>
versions:lock-snapshots
and then
versions:unlock-snapshots
to turn them back to normal before reintegrating your branch
2009/4/22 Michael Hüttermann
> ok, I see, thanks! There is another concept using a generic version:
> snapshots. What do you do with your SNAPSHOTs while branching then? Do
I should point out that I never use timestamp snapshots... but then we build
everything locally, and our CI server does not deploy snapshots... we had
too many issues with both random snapshot updates, and non-full builds
2009/4/22 Stephen Connolly
> versions:lock-snapshots
>
>
I think (actually I hope) he's talking about between releases.
trunk might be moving rapidly, so you fork a branch to work on a feature...
you don't want the changes to the artifacts from trunk screwing with your
build until you are ready to merge the branch back to trunk...
If he's got some othe
2009/4/22 David Hoffer
> Ahhh,
>
> A plugin to fix version range problems, I'll have to ckeck this out.
>
> -Dave
>
> On Wed, Apr 22, 2009 at 10:41 AM, Stephen Connolly <
> stephen.alan.conno...@gmail.com> wrote:
> > 2009/4/22 David Hoffer
> &
I guess we need to separate 3rd party dependencies and internal
dependencies.
In general you do not want to depend on a -SNAPSHOT version of a third party
dependency...
for example in between releases, there is no way I'd switch from
log4j-1.2.15 to log4j-1.2.16-SNAPSHOT ___unless___ there was a
It depends...
if your build is reliable and never fails... if all your components always
have the same version number... if all your modules are in the same tree...
then yes the the release plugin will sort it out for you.
however, if you have a long flakey build (we have one that is about 4 hour
2009/4/22 David Hoffer
> Sorry, I might not be clear on the big problem you are trying to solve.
> The
> release plugin works for us. Its used for each dependency you need to
> release. We try to limit snapshot usage overall, that's just for things a
> project is actively changing, else use a
Bash the manager over the head until he changes his mind
;-)
-Stephen
2009/4/22 Michael K. Craghead
> I know this seems like a strange request, but what is the best way to
> convert a Maven 2 project to Maven 1? Our development team was going to
> start to move to Maven 2, but the plans have c
Sent: Wednesday, April 22, 2009 1:40:42 PM
Subject: Re: Converting to Maven 1.x
And has the manger mandated all code shall be written in C? Strange
indeed.
-Dave
On Wed, Apr 22, 2009 at 11:37 AM, Stephen Connolly <
stephen.alan.conno...@gmail.com> wrote:
Bash the manager over the head until he
put the exclusion in a profile
Sent from my [rhymes with myPod] ;-)
On 22 Apr 2009, at 20:17, Grant Rettke wrote:
Hi,
By default, we need to exclude some classes from inclusion in the JAR
file. It looks like in jar:jar I can use the excludes property to
specify this.
The thing is that, some
bind the execution to the pre-site phase
Sent from my [rhymes with myPod] ;-)
On 22 Apr 2009, at 22:40, huser wrote:
Hi ,
I added maven ant run plugin to my project POM.xml. Then I ran mvn
clean
install antrun:run.
I do not see the javadoc target getting generated. The plugin is not
w
> it's in the child module use the child one.
>
>
> Stephen Connolly wrote:
>> A
>>
>> you want to use the value from the parent if the parent is in the current
>> reactor but if the parent is not in the current reactor, you want to use
>> th
Short answer: because maven does not guarantee the execution order
within a phase.
Long answer:
maven-install-plugin:install installs all the artifacts that are
attached to the current module in the current build reactor into the
local repository.
maven-javadoc-plugin:jar creates a jar of the mod
H...
what I would do is run two executions of the jar plugin...
execution #1 generates the artifact without a classifier but excludes the
persistance.xml
execution #2 generates the artifact with the classifier and includes the
persistance.xml
That would at least work around your issue (as y
maven embedded
2009/4/23 Todor Boev
> Hi,
> I am working on a requirement to resolve and download the transitive
> closure of a set of maven artifacts. The plan is to use a pom.xml with
> "pom". That pom will contain the set of artifacts as
> dependencies together with some repository definition
http://www.lmgtfy.com/?q=maven+profile+activation
2009/4/23 Anastasios Angelidis
> So any good samples anywhere?
>
>
> Stephen Connolly wrote:
>
>> hmmm
>>
>> I suspect that what you'd need is profiles
>>
>> you could activate a profilein th
You now know all that I know
2009/4/23 Todor Boev
> 10x
> This looks promising.
> You happen to know if I can use it to only download the dependencies? I
> don't want to build a project because this downloads a bunch of maven
> plugins, which get mixed with the dependenc
> pre-site
>
>
>
>
>
>
>
> run
>
>
>
>
>
> I still dont see the ant task being run.
>
> mvn antrun:run
>
> javadoc is not getting create
The Mojo team is pleased to announce the release of the Versions Maven
Plugin, version 1.0-alpha-3.
The Versions Plugin has the following goals.
* versions:display-dependency-updates scans a project's dependencies and
produces a report of those dependencies which have newer versions available
Create a new module(s) which just has the log configuration...
then A & B can both depend on this(ese) new module(s)...
C can exclude the module(s) from it's dependencies on A & B
2009/4/26 Olivier Cailloux
> Hello list,
>
> I am new to maven and couldn't find a simple and elegant solution to
define a property with value true. use that property as the value of skip,
then the CLI can override the property value
2009/4/28 aldana
>
> Hi,
>
> by default my integration tests should not be run implicitly, so I set
> true. Is there a way to tell surefire plugin to switch the
> skip
> test f
You do not have to specify the version if you are happy with how Maven
determines the versions. Also if you do not specify the version your build
is not reproducible.
Can you please file a JIRA against the antlr-maven-plugin to get the usage
page to show the version in accordance with best practi
ugh!
that sounds hacky hacky hack
you probably should try having the dependency plugin unpack for you
-Stephen
On 04/05/2009, huser wrote:
>
> Hi,
>
> I am running maven release plugin by:
>
> mvn -f pom.xml -Pabc.debug.release --batch-mode -Dtag=REL1.5-TEST
> -DtagBase="https://abcsvn001.na.ab
ubli
> c),
> [INFO] snapshots
> (http://abcsvn001.na.abcglobal.com:8081/nexus/content/reposito
> ries/snapshots<http://abcsvn001.na.abcglobal.com:8081/nexus/content/reposito%0Aries/snapshots>
> )
> [INFO]
> [INFO] [INFO]
> --
>
> Steph
I think he wants to update the scm section in the pom to match what is
displayed from svn info
2009/5/5 Mark Struberg
>
> Hi Baptiste!
>
> It isn't clear to me what you mean with 'update tag'.
>
> Do you like to re-tag in the SCM?
>
> LieGrue,
> strub
>
>
>
> - Ursprüngliche Mail
> > Vo
gt; retrieve the "svn info" output from the working copy and update
> and accordingly.
>
> I guess there could an option to update ,
> or both with the retrieved value. For example, we always have the same
> value
> there.
>
> Cheers.
>
> 2009/5/5 St
9/5/5 Baptiste MATHUS
> I just discovered that subtag of scm :). Well, then yes. Although you'd
> have
> to provide some viewscm root url to start from.
>
> 2009/5/5 Stephen Connolly
>
> > You'd probably also want to update the url providing that it follows an
&
use getResource to get the URL of the resource and then parsethe URL
to find the file path
On 07/05/2009, Pete Siemsen wrote:
> That seems reasonable, but I still don't understand how to make it work.
>
> The program I'm trying to test is like a compiler. It reads source
> files that can contain
Sent from my [rhymes with myPod] ;-)
On 10 May 2009, at 18:01, Stevo Slavić wrote:
"Just because that's the way things are doesn't mean that's how they
should
be.", said a character in the movie "Australia".
In this particular scenario, local test scoped dependency vs compile
scope
tran
IIRC maven warns you that you have changed a dependency from compile
scope to test scope.
you may have a valid reason for so doing, but maven is no medium and
cannot ask a higher plain what you wanted to do. if a warning is not
good enough, tough
Sent from my [rhymes with myPod] ;-)
On 1
2009/5/7 Harper, Brad
> Possible, but I checked the ${M2_HOME}/conf/settings.xml and the
> repositories have valid username/passwords on the associated servers.
>
> Credentials for scp wouldn't be resolved differently from within the
> release plugin, would they?
Depends
if you have two de
701 - 800 of 2426 matches
Mail list logo
