yes, we'll release m-site-p 3.0 shortly, with a hard work to fill the gap
We're pretty confident about features and doc, which should be quite exaustive
about the few little changes that could not be avoided
please help us testing it in the final step and these difficulties should
belong
to th
maven3 enforces the good practice of using timestamped snapshots (by dropping
support for uniqueVersion=false) so I had no choice but to try and get it to
work, even though I was just fine with non-unique snapshots.
My project setup is pretty typical: projectA depends on projectB which
depends on
Hi,
I have one quick Question for you guys.
I am having one issue to adopt Maven. My company needs following features
available with Maven. I am trying to force my company to choose Maven as
build TOOL. but they have one critical question for you guys.
My company is looking to write something l
Hopefully site 3.0 will pull this together.
On Fri, Jul 22, 2011 at 2:50 PM, Maven User wrote:
> Sorry Benson - it's been pretty frustrating in general working with maven 3
> (I wasn't the adopter here, just the maintainer).
>
> Didn't mean to take it out on the list like that - my apologies.
>
>
> Is there a way to rebuild the default directory structure from an existing
> pom.xml
>
> Say someone sends you just the pom.xml and you want to recreate the default
> folder structure.
If none of the directory paths have been modified from the "default"
(convention), then you could just use a
Sorry Benson - it's been pretty frustrating in general working with maven 3
(I wasn't the adopter here, just the maintainer).
Didn't mean to take it out on the list like that - my apologies.
I love the speed of maven 3 but liked the "just works" nature of maven
2(.2.1).
Thanks again all for the
As a heavy user of site, your view that maven '3' isn't real yet is
entirely understandable.
On Fri, Jul 22, 2011 at 11:43 AM, Maven User wrote:
> Ok, maybe I'm misunderstanding - but initially, I thought the goal of maven3
> was that it should have been a direct replacement with backward
> compa
Ok, maybe I'm misunderstanding - but initially, I thought the goal of maven3
was that it should have been a direct replacement with backward
compatibility.
For companies who rely heavily on site generation/deployment, this truly
isn't the case.
There are a lot of flaming hoops to jump through for
I don't think that you're being quite fair here.
When 3.0-beta-3 was released, the default assumption was that the next
release would be beta-4. So any bugs fixed got marked 'fixed in beta
4'. Typically, a JIRA spends at least some weeks, if not months,
marked 'fixed' in a release that isn't relea
On 22/07/2011 10:33 AM, Julien HENRY wrote:
So you must have version 5.1 of project 1-1 depending on version 5.0 of project
2-1
and version 5.1 of 2-1 depending on 5.0 of project 1-2?
No, Maven is able to build even when all have the same version. See attached
test project. But I would like to
>So you must have version 5.1 of project 1-1 depending on version 5.0 of
>project 2-1
>and version 5.1 of 2-1 depending on 5.0 of project 1-2?
No, Maven is able to build even when all have the same version. See attached
test project. But I would like to prevent users of doing so.
>Is that what
Impressive.
Maven 3 should still be labeled a beta release...
Thanks Benson for the heads up, I appreciate it.
There isn't one. In fact, the current plan is to make the next release
be called '3.0' and release it quite soon.
You could build and run a snapshot from source.
On Fri, Jul 22, 2011 at 10:15 AM, Maven User wrote:
> Where can I get 3.0-beta-4?
>
> Looks like you can't adjust the timeout using t
Where can I get 3.0-beta-4?
Looks like you can't adjust the timeout using the option
with 3.0-beta-3 (see: http://jira.codehaus.org/browse/MSITE-581).
So you must have version 5.1 of project 1-1 depending on version 5.0 of
project 2-1
and version 5.1 of 2-1 depending on 5.0 of project 1-2?
Is that what you are trying to detect?
A better way to fix the problem is to use Maven properties to specify
the versions of the project
Then project 2-1
I have just tested to be sure and it works (Maven 3.0.3):
[INFO] Reactor Summary:
[INFO]
[INFO] module-1 .. SUCCESS [0.471s]
[INFO] module-1-2 SUCCESS [2.141s]
[INFO] module-2
On 22/07/2011 4:08 AM, Julien HENRY wrote:
Hi,
Background: I'm trying to develop a release helper tool for my company. We can't use the
maven-release-plugin for several reasons. We have a notion that is like a "release
train" were several projects must be released at the same time. These proje
fyi, since sonar is migrated from the old codehaus repository to
https://nexus.codehaus.org/, we now can guarantee that there won't be any
broken checksum of sonar artifacts deployed to central.
Nexus Pro has staging rules checking this, and it's very handy to fix
existing broken checksum, just ru
Hi,
Background: I'm trying to develop a release helper tool for my company. We
can't use the maven-release-plugin for several reasons. We have a notion that
is like a "release train" were several projects must be released at the same
time. These projects can be Maven multi-module projects. Thes
19 matches
Mail list logo
