Bruno Marti wrote:
In maven 1.x xdoc site documentation there could be the following for menus
(navigation.xml):
menu name=myMenu
item name=Maven 1.x href=http://maven.apache.org/maven-1.x/;
target=_new /
...
(creates a link to maven 1.x in a new window or tab)
In maven 2.x site.xml
Brian,
I was able to build the jar with just the templates in it as
resources so dependecy-unpack is exactly what I was looking for. If I add
the plugin to any pom using these templates during the install phase they
will be unpacked into the local repository as I desire. Thanks for the
We should also add http://jira.codehaus.org/browse/MJAR-30 to the
release, since patches has been applied for it.
Jerome Lacoste wrote:
On Dec 6, 2007 1:44 AM, Jerome Lacoste [EMAIL PROTECTED] wrote:
Hei,
The latest maven jar plugin release was in August 2006. Is there any plan
to make a
Hi,
An easy question here but how can't find any documentation about it.
I want to upload a jar to the maven repository. This jar extends a parent
pom.
And I have no clue on how to upload the parent (repository plugin can't
create bundle for pom projects).
Anyone can help?
Thanks,
Henri
On Mon, 10 Dec 2007 11:49:27 Henri Tremblay wrote:
Hi,
An easy question here but how can't find any documentation about it.
I want to upload a jar to the maven repository. This jar extends a parent
pom.
And I have no clue on how to upload the parent (repository plugin can't
create bundle
We were using maven 2.0.6 in a team with Artifactory as a proxy.
I then upgrade my environment to 2.0.8. A whole bunch of new plugins get
fetched.
Other people were using 2.0.6 but it appears that they also get a whole
heap of new plugins.
As a result, test cases in another project which had
On Dec 9, 2007 4:24 PM, Michael McCallum [EMAIL PROTECTED] wrote:
the same way as the jar... deploy-file that would be my guess i have not
actually tried it...
have you tried including the repository from this 3rd party?
That was my first answer as well. This works:
$ mvn deploy:deploy-file
its just coincidental that surefire 2.3.1 was released at the same time as
2.0.8...
if you specify surefire 2.3 or less in you pluginManagement then the tests
will start working again... of course its best practice to specify plugin
versions anyway so magic upgrades don't break things
On Mon,
No, it's because 2.0.8 is not backwards compatible with 2.0.6, as
documented in the release notes.
On 10/12/2007, Michael McCallum [EMAIL PROTECTED] wrote:
its just coincidental that surefire 2.3.1 was released at the same time as
2.0.8...
if you specify surefire 2.3 or less in you
Right, thanks for the explanation.
Explicitly specifying the plugin version would help in this particular
case but would we then need explictly declare every single plugin in the
project to guard against future problem? i.e., clean, compiler, deployer,
install, jar, war etc... would you then
It is a best practice - in a shared parent POM so that you don't need
to do it frequently. The release plugin doesn't do it, but the
enforcer plugin can be used to ensure that you have.
Cheers,
Brett
On 10/12/2007, [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote:
Right, thanks for the explanation.
Ok, but our problem is not a simple backward compatibility.
I was working on project A on my machine. I upgraded to 2.0.8. Nothing
breaks here but it it break then fair enough.
A colleauge was working on project B and still using 2.0.6.
Some how my action of upgrading to 2.0.8 in my machine
Your act of upgrading certainly can't have broken his environment :)
There are two possibilities:
a) something changed in a surefire snapshot. This is possible as its
under active development, though I'm not sure if new snapshots are
being deployed regularly.
b) a test was added to your
Hi there,
I set up a mirror of repo1.maven.org/maven2 for my group and added the
following profile to the settings.xml file. The key point here is that I
overrided the central repository with my mirror, so that the mavens using
this profile will go to myrepo instead of repo1.maven.org/maven2
On Dec 9, 2007 6:36 PM, Fred Zhang [EMAIL PROTECTED] wrote:
Hi there,
I set up a mirror of repo1.maven.org/maven2 for my group and added the
following profile to the settings.xml file. The key point here is that I
overrided the central repository with my mirror, so that the mavens using
I've worked out what happened. Surefire 2.3.1 is not in the central
repository yet but apparantly it has been tagged
(http://jira.codehaus.org/browse/MNG-3118).
Last Friday, I've downloaded maven source and build it on my local machine
(and added apache snapshot into Artifactory). As a
Is there a philosophical reason why release plugin shouldn't do that on
behalf of the users?
Maven makes alot of things simpler and pleasant for you (i.e., transitive
dependencies, lifecycles management etc..) and then there are occasional
things like this that makes you wonder why would I
New issue posted in JIRA:
http://jira.codehaus.org/browse/MSITE-278
http://jira.codehaus.org/browse/MSITE-278
Dennis Lundberg-2 wrote:
Bruno Marti wrote:
In maven 1.x xdoc site documentation there could be the following for
menus
(navigation.xml):
menu name=myMenu
item
Hi Wendy,
Thanks a lot for the reponse!
Regards
Fred Zhang
-邮件原件-
发件人: Wendy Smoak [mailto:[EMAIL PROTECTED]
发送时间: 2007年12月10日 10:11
收件人: Maven Users List
主题: Re: How does maven find the real central repository even when I overrided
the central repository in my profile
On Dec 9, 2007
19 matches
Mail list logo
