Jason, shouldn't that be reposit...@apache.org instead?
On 2010-07-29 21:11, Jason van Zyl wrote:
The Apache repository specific concerns go to
repo-maintain...@maven.apache.org. Maybe we can try and whip up a solution
for you that you can use with your Ant build so you can deploy directly
Hi,
I have defined additional repositories in my settings.xml - works OK.
I have manually installed one dependency - OK (it is in my .m2 directory).
Problem is, that this dependency is always looked for in all of those
additional repositories and Maven complains Unable to find resource
Hi, Likin.
Is this dependency SNAPSHOT or not?
Aleksey.
30.07.2010 12:36, Lukin пишет:
Hi,
I have defined additional repositories in my settings.xml - works OK.
I have manually installed one dependency - OK (it is in my .m2 directory).
Problem is, that this dependency is always looked for in
Thank you for your reply.
It is not snapshot,
I have defined it this way:
dependency
groupIdcom.microsoft/groupId
artifactIdsqljdbc4/artifactId
version2/version
/dependency
it is located in my
How did you install it in your local repo? Wit install:install-file or
manually? I'm guessing here, but could it be that the local metadata files
don't include this version of the artifact and therefore Maven will go
remote?
/Anders
On Fri, Jul 30, 2010 at 11:18, Lukin i...@seznam.cz wrote:
Hi
Im having problem with dependency plugin and release process. Stage looks
like:
/parent.pom.xml
/impl/pom.xml
/doc/pom.xml
/docs/sources/pom.xml
/docs/prepare/pom.xml
On regular mvn install - /docs/sources just creates bundle with files - lets
say it creates docs-sources-SNAPSHOT.jar.
Hmm it seems I solved this by adding:
preparationGoalsclean install/preparationGoals to release plugin.
But still, should reactor be searched be dependency plugin.
On Fri, Jul 30, 2010 at 12:05 PM, Bartosz Baranowski baran...@gmail.comwrote:
Hi
Im having problem with dependency plugin and
Solved!
Thank you for assistance. I have probably made some mistake when I was
experimenting with Maven for the first time. You pointed me to the right
direction - the jar was not very well installed. The problem was, that in
.m2\repository\com\microsoft\sqljdbc4\2\ was missing .pom file.
I
Yes, or file an INFRA ticket: https://issues.apache.org
On Fri, Jul 30, 2010 at 4:28 AM, Dennis Lundberg denn...@apache.org wrote:
Jason, shouldn't that be reposit...@apache.org instead?
On 2010-07-29 21:11, Jason van Zyl wrote:
The Apache repository specific concerns go to
If you are going to be doing your development with Maven and want to
speed things up and make your life a lot better install Nexus.
It make not make the sex or the beer better but you will have more time
to pursue them.
Ron
On 30/07/2010 6:40 AM, Lukin wrote:
Solved!
Thank you for
Hello List
I have a multimodule project similar to the following:
toplevel
pom.xml
modA
pom.xml
modB
pom.xml
modC
pom.xml
Modules A B are specified explicitly in the toplevel pom. Module C is not.
It is only to be run when required and is done stand-alone.
When I do mvn
Using a profile where you specify the modules? I.e. a special profile for
the release work where C is included.
/Anders
On Fri, Jul 30, 2010 at 16:30, Gordon Cody gc...@zafinlabs.com wrote:
Hello List
I have a multimodule project similar to the following:
toplevel
pom.xml
modA
is there a way to force a project to refresh certain dependencies every
build? i.e. replicate SNAPSHOT behaviour with released artifacts
S
is there a way to force a project to refresh certain dependencies every
build? i.e. replicate SNAPSHOT behaviour with released artifacts
Absolutely not. Released artifacts MUST NOT CHANGE.
Wayne
-
To unsubscribe, e-mail:
Maven won't do that, and we would never make that possible. If you require this
you have something seriously wrong with your project infrastructure. Seriously
bad project infrastructure smell.
On Jul 30, 2010, at 12:01 PM, Shan Syed wrote:
is there a way to force a project to refresh certain
Shan,
Maven has a policy how often it checks for updated snapshots. Is that what
you are looking for?
Paul
On Fri, Jul 30, 2010 at 11:39 AM, Jason van Zyl ja...@sonatype.com wrote:
Maven won't do that, and we would never make that possible. If you require
this you have something seriously
I was actually under the impression you could do this like this:
repository
releases
updatePolicyalways/updatePolicy
/releases
/repository
Although I've never tried this because it's a terrible idea.
If this doesn't work, someone should probably remove the corresponding
section from
On 07/30/2010 07:16 PM, Wayne Fay wrote:
is there a way to force a project to refresh certain dependencies every
build? i.e. replicate SNAPSHOT behaviour with released artifacts
Absolutely not. Released artifacts MUST NOT CHANGE.
+1, never ever ;-)
Released artifact versioning is supposed
Hi
I have manually configured Eclipse WTP to deploy my web-app from my
project's target directory (so my deployment includes the result of JSP
pre-compilation). I have done this by manually editing my project's
settings/rg.eclipse.wst.common.component file.
But now every time I run an mvn clean
I just downloaded the latest version of eclipse 3.6. When I try to debug
using the maven jetty plugin, I get all sorts of classloader problems, where
resources in src/main/resources in dependent projects cannot be found
(FileNotFoundException).
I have no such problems in eclipse 3.4 or running
ok, thanks
basically for liability reasons for a certain project, we have to provide
specific times of when a project was built and when/where all its
dependencies were retrieved at/from
we have to ensure a sanitary build for all these JARs and a complete log of
going from 0 to 100 for the build;
Replacing a SNAPSHOT with a non-SNAPSHOT version is equivalent to upgrading.
Jason is right in that this should never be automatically done by Maven.
Maven cannot guess or determine when you are ready to give up SNAPSHOT
versions.
However, perhaps you need an external batch process that discovers
On 30/07/2010 12:57 PM, Manos Batsis wrote:
On 07/30/2010 07:16 PM, Wayne Fay wrote:
is there a way to force a project to refresh certain dependencies every
build? i.e. replicate SNAPSHOT behaviour with released artifacts
Absolutely not. Released artifacts MUST NOT CHANGE.
+1, never ever
Wouldn't you be better off implementing such mechanism in an SCM package?
Audit can be done with scripts either sitting on top of SCM or Unix/Linux
machine.
Added logging layer from hosting it on Linux/Unix would benefit you far more
and provide better flexibility.
Hope it helps,
Dave
On Fri,
Hi,
I'm trying to use maven-site-plugin and the wagon-webdav artifact. I
get this error when I do mvn site-deploy. But according to
http://maven.apache.org/wagon/wagon-providers/wagon-webdav/ it says it
does support directory copying... anyone know what could produce this
error?
Thanks,
On Jul 30, 2010, at 2:21 PM, Shan Syed wrote:
ok, thanks
basically for liability reasons for a certain project, we have to provide
specific times of when a project was built and when/where all its
dependencies were retrieved at/from
we have to ensure a sanitary build for all these JARs and
You could try changing the repository location property on the command line to
a fresh empty directory. That will force the download and logging of all
SNAPSHOT and release dependencies.
mvn ... -Dmaven.repo.local=new-temp-directory
!-- Frank Gorham-Engard →
Be kinder than necessary.
not my organization - our client wants a log of everything that came down
the pipe to create this build, that's all
it's not a matter of worry or concern, so no need to be overly dramatic
some companies just want a complete audit trail of what they paid for, which
is fine by me
I'm looking for
On Jul 30, 2010, at 3:45 PM, Shan Syed wrote:
not my organization - our client wants a log of everything that came down
the pipe to create this build, that's all
it's not a matter of worry or concern, so no need to be overly dramatic
some companies just want a complete audit trail of what
deleting the m2 works, I was just curious to see if there was a switch in
maven to force all downloads again
This makes absolutely no sense, doesn't change your BOM, and is just
wasteful. Consumes bandwidth unnecessarily from a resource that is being
used by the whole Maven community.
I'd
it only applies to our final release cuts, not our day-to-day
just once for this project really; I wanted to insert such this switch (if
existed) in our delivery build profile
we use archiva for everything else, and actually only make use of public
maven repositories when we up a version of our
There is a maxim to follow when deploying: do not redeploy a version more
than once. Once you deploy version X.Y.Z, it should never be updated, and
those who download it never need to download it again. So, back to the
original problem, are you guys doing that?
On Fri, Jul 30, 2010 at 3:57 PM,
no, this isn't in regard to our own published artifacts
I regret starting this thread, I apologize
I didn't mean this question to be an affront to maven conventions - I just
need to figure out a better way to capture a full log
they even want a log of how the build environment was downloaded and
You can use -X for a debug log. Or you can funnel system out to a file. I
believe tools like Continuum or Hudson do such things.
Paul
On Fri, Jul 30, 2010 at 4:07 PM, Shan Syed shan...@gmail.com wrote:
no, this isn't in regard to our own published artifacts
I regret starting this thread, I
On 30/07/2010 5:09 PM, Paul Benedict wrote:
You can use -X for a debug log. Or you can funnel system out to a file. I
believe tools like Continuum or Hudson do such things.
Paul
On Fri, Jul 30, 2010 at 4:07 PM, Shan Syedshan...@gmail.com wrote:
no, this isn't in regard to our own published
Hrm, that worries me a bit. If the packaging type=pom then most tools
will expect that there is only a pom with no classifier (ie main
artifact). The better way is to use a classifier. I'm pretty sure this
setup you propose will confuse the indexer.
On Fri, Jul 30, 2010 at 1:18 AM, Jörg Schaible
36 matches
Mail list logo
